Twenty-six ERISA practice areas, encoded and ready to install.
The skill library we built for our own ERISA practice, tuned for use by plan sponsors and packaged so your benefits team can install it in the Claude account they already have — with a getting-started SKILL that teaches them to set it up and use it well. Perpetual license. No assessment, no build queue, no waiting.
What you are buying, and what you are not.
This is a set of AI SKILLs designed to tell Claude how to think about the ERISA issues that plan sponsors — and the third parties that advise them — face every day. It is not custom designed for particular employers, but it includes features that help you to give Claude your specific ERISA facts so that its output is more precise.
What you get
- Twenty-six substantive ERISA SKILLs, each covering one practice area, with reference summaries, checklists, and worked numerical examples.
- A master SKILL that routes a question to the right practice area and holds the house analytical conventions.
- A getting-started SKILL that walks your team through setting up a Project, loading your own plan documents, and prompting well.
- A perpetual license. The release you buy does not expire and does not stop working.
- Judgment-call flagging. The SKILLs recognize when a question turns on legal judgment rather than a plan term, and say so before you act.
What you do not get
- We do not load your documents. You do that yourself — the getting-started SKILL teaches you how, and it takes an afternoon, not a project.
- No attorney reviews the output. Not before you see it, not after. Every answer is unreviewed by definition.
- No customization. Your house positions and interpretations are not encoded. Nothing is built to your specification.
- We host nothing. The SKILLs run inside your own Claude account, under your own agreement with Anthropic.
- Installation is yours. Roughly fifteen minutes, no developer tools, no command line — but it is your fifteen minutes.
Twenty-six practice areas, plus setup and routing.
Organized the way benefits work actually arrives — by the question in front of you, not by statute. You do not need all of them. A sponsor with a 401(k) and a health plan may only ever use six or seven.
Qualified Retirement Plan Compliance
- Testing & eligibility
- Plan documents, amendments & terminations
- Distributions, loans, rollovers & RMDs
- Pension & cash balance plans
- 403(b) plans
Health & Welfare Benefits Compliance
- COBRA, HIPAA & welfare plans
- ACA employer mandate & reporting
- Parity, transparency & the CAA
- Fringe benefits & payroll taxation
Fiduciary Governance & Plan Administration
- Fiduciary duties & prohibited transactions
- Benefits cybersecurity & data incidents
- Reporting, disclosure & claims
Corrections — When Something Goes Wrong
- Plan corrections
- Government audits & investigations
- Litigation risk & preemption
Executive & Equity Compensation
- Nonqualified deferred compensation & 409A
- Equity & incentive compensation
Corporate Transactions & Workforce Changes
- Employee benefits in M&A
- Severance, WARN & reductions in force
- Controlled groups & affiliated service groups
- Multiemployer plans & withdrawal liability
Specialized Employers & Plan Structures
- Government, church & tribal plans
- ESOPs & employee ownership
- Pooled, multiple-employer & small-employer plans
Life Events & Employee Leave
- Leave, military service & wellness programs
- QDROs & dividing retirement benefits
The answer to “I’m one person — I can’t set this up.”
A one-person benefits function is exactly who this is built for, so setup is a product feature rather than your problem. One of the twenty-eight SKILLs does nothing but teach you to use the other twenty-seven.
Install the files about 15 minutes
A printed sheet ships with the package. Upload the SKILLs to Claude and switch them on. No developer tools and nothing to configure. You do not need all twenty-eight to start — two of them, and then add practice areas as questions come up.
Ask the skill to set you up guided
Tell it to teach you how to use it. It assumes you are starting cold — no Project, no documents, no prior conversation — and walks you through creating a Project, naming it, and writing the instructions that tell it how to treat your plans.
Load your own plan documents your grounding layer
It names the specific documents to start with: plan document and adoption agreement, current SPD and SMMs, trust agreement, administrative forms, service agreements, the last two Form 5500 filings. This is the step that makes answers about your plan rather than a plan in general — and you keep control of what goes in.
Confirm the documents are actually being read verification
A step people skip, so the skill insists on it. It gives you a test question and tells you how to read the answer: a good one names the file and the section it came from. A general description means your documents are not being reached, and it tells you what to check.
Learn to ask well six habits
Six named prompting habits, each with a worked before-and-after example — leading with context, pointing at the documents instead of letting the tool assume, asking for an issue-spotting pass before a finished memo, working iteratively, correcting bluntly, and treating every output as a draft for your counsel. Including the one question that catches more errors than any other: what did you assume that I did not tell you?
What you need before you start
A Claude account on any plan, with code execution enabled. Projects, for the plan-document workflow — though you can ask useful questions in a plain chat on day one and set up a Project later. An organization-wide install path is available on Team and Enterprise Claude plans at the Enterprise and Professional tiers. The Suite is built for Claude and is not currently packaged for other platforms.
It tells you not to trust it.
This is the whole posture of the product, and it is not a disclaimer buried in a license. It is stamped on the bottom of every response the Suite produces, it cannot be turned off, and it does not get shorter if you ask nicely.
On every response
This response has not been reviewed by an attorney and cannot be relied on.
Confirm it with competent ERISA counsel before acting.
ERISA SKILLs Suite · release and license ID
And when a question turns on judgment
This question turns on legal judgment, not just plan terms or a figure that can be looked up. Unreviewed output is especially unsafe to rely on here. Have competent ERISA counsel review this analysis before acting, communicating a position, or committing the plan.
Three things follow from that, and they are worth stating plainly. Nobody reviews these answers — not us, not anyone. The Suite will not tell you it has flagged something for review, because it has not. And it will never name a particular firm or lawyer to send you to; the referral is always to competent ERISA counsel of your own choosing.
Three tiers. Buy once, update when you want to.
Each tier is a perpetual license to the release you buy. It does not expire, lapse, or stop working, and none of this is a subscription. ERISA guidance keeps moving, so updated releases are sold separately at a reduced charge and we recommend updating at least annually — a copy past that date still works, it is simply answering from older law, which is why it tells you its release date when currency matters.
Small Employer
$1,750 per annual update release
One employer, up to three named users. Built for a benefits function of one to three people.
Enterprise
$3,750 per annual update release
One employer, unlimited users inside that employer. For a benefits department, and where in-house counsel will use it alongside the team.
Professional
$6,250 per annual update release
One organization that provides benefits guidance to others — a TPA, advisory firm, or broker — for use in serving its own customers. It does not permit handing the files themselves to those customers.
What the license does not allow
Redistributing, reselling, sublicensing, publishing, or posting the files. Use beyond the scope of your tier, or sharing with another organization. Removing or suppressing the AI-output labels, the identification block, or the response footer. Building a derivative product for distribution from the content. Each copy is individually identified: the license ID appears in the footer of responses your copy produces, and the copy carries further identifying characteristics that are not visible on inspection.
Built by people who practice ERISA law.
This is not a general AI consultancy's read of the benefits field. The content was written by practising ERISA attorneys for use in their own work, and it exists because they needed it. The reference summaries are original syntheses of primary authority rather than repackaged treatise material. The worked examples — coverage testing, ADP correction, cross-testing rate groups, top-heavy, 415 aggregation — are the calculations a practitioner actually runs.
What that means, and what it does not: it describes who wrote the content. It does not make the product legal advice, and it does not make anyone your lawyer.
ERISA Benefits Tech, LLC is a technology company and a technology affiliate of ERISA Benefits Law Group, PLLC. It is not a law firm, it does not practice law, and it does not represent you. Buying or using the Suite creates no attorney-client relationship with anyone. Output is unreviewed, is not legal advice, and must be reviewed by competent ERISA counsel of your own choosing before you act on it.
Everyone starts here. Some go further.
The Suite is the front door for every client, including the large ones. It is the fastest way to find out where AI actually helps your function and where it does not — and that answer is worth more than a proposal.
A custom build
Where the Suite ends, a custom build begins: SKILLs grounded in your own plan documents by us rather than by you, your house positions and interpretations encoded into how each SKILL reasons, and — for employers — escalation criteria configured to route judgment calls to counsel, with ERISA legal review provided by ERISA Benefits Law Group, PLLC under a separate engagement letter.
How you would get there
It starts with a fixed-fee readiness assessment: an inventory of your plans, documents, workflows, and current AI posture, and a written roadmap you keep whatever you decide next. What you have already paid for the Suite is credited toward it. Pricing for the assessment and for a build is quoted to scope — start a conversation and we will walk you through it.
The Suite is not on sale yet.
We are finishing the license terms and the purchase path. Join the waitlist and we will tell you when it opens — and when the first training sessions are scheduled.