Claude for Financial Advisors for Small RIAs: Team or Enterprise Under 20 People

1. The Short Answer: Twenty Seats, Eight People

Any RIA on a paid Claude plan can install Claude for Financial Advisors, and the plugin itself costs nothing. The hard part for a small firm is the plan. The one Anthropic recommends starts at 20 seats, and the typical advisory firm is far smaller.

The Investment Adviser Association's 2026 industry snapshot counted 16,544 SEC-registered advisers. Advisers whose business centers on individual clients averaged about eight employees and $424 million in assets under management, and 92.8 percent of all advisers employ 100 or fewer people.

Anthropic's advice is direct: "We recommend Enterprise plans for registered investment advisers, because it includes the audit logs that support recordkeeping" (Anthropic). InvestmentNews, citing Anthropic's website, put the Enterprise price at a $20 seat fee per user per month, a 20-seat minimum, and usage billed on top at API rates.

So an eight-person firm on Enterprise pays for twelve empty seats. This guide works out whether the records capture that comes with Enterprise is worth that, and what the cheaper route gives up. It is operational guidance; your CCO and counsel own the call on records.

2. Your Three Real Options

Every small RIA is choosing among three options, whether it says so or not.

1. Enterprise with empty seats. You pay the 20-seat floor and get the plan Anthropic recommends: audit logs, the Compliance API that archive vendors plug into, and the install path the launch post describes: "If you already have an Enterprise license, open Cowork and find 'Claude for Financial Advisors' in the plugin browser, and install it and follow the guided setup to connect your tools."

2. Team, with the plugin added from GitHub. Plugins work on every paid plan (Anthropic Help Center). On Team you can add this one from its public repository (Customize, Plugins, Add marketplace, Add from a repository, then anthropics/claude-for-financial-advisors), and an Owner can distribute a copy firm-wide as an organization plugin, synced from a private GitHub repository.

Team comes with Cowork, workplace-tool connectors, SSO, role-based permissions and spend controls, and it shares Enterprise's commercial terms, under which your inputs are not used to train models. The missing piece is the records layer. Team lacks both the audit log export and the Compliance API, and Smarsh Capture for Claude Enterprise runs on that API.

3. Wait. Hold off until the connectors you depend on work on your plan, your CRM data is clean enough to feed the skills, and your CCO has a records answer. Section 8 covers when that is the smart move.

3. The Math for 3, 5 and 8 People

Here is the arithmetic from published prices, laid out so you can redo it at your own headcount. Every figure is an estimate: the Enterprise math treats everyone as an active user at Anthropic's ballpark, your real usage will differ, and a spend limit puts a ceiling on it.

Enterprise

The seat fee has a floor. Twenty seats at $20 a month for 12 months is $4,800 a year (20 × $20 × 12), whether you have 3 people or 19, and each seat works out to $240 a year ($20 × 12).

Usage comes on top, pooled across the firm and charged at API rates (Anthropic Help Center). Peter Nolan, Anthropic's head of asset and wealth management, put it at roughly $70 to $120 per user per month for firms that use it actively, TechTimes reported. Multiply by 12 and usage runs $840 to $1,440 per active user a year ($70 × 12 and $120 × 12).

• 3 people. Usage of $2,520 to $4,320 (3 × $840 to 3 × $1,440) on top of the $4,800 floor gives $7,320 to $9,120 a year. Seventeen of the 20 seats sit empty, which is $4,080 of the seat fee (17 × $240).
• 5 people. Usage of $4,200 to $7,200 (5 × $840 to 5 × $1,440) plus the $4,800 floor gives $9,000 to $12,000 a year, with 15 empty seats costing $3,600 (15 × $240).
• 8 people. Usage of $6,720 to $11,520 (8 × $840 to 8 × $1,440) plus the $4,800 floor gives $11,520 to $16,320 a year, or $1,440 to $2,040 per person, with 12 empty seats costing $2,880 (12 × $240).

Team

Team is priced per seat, for 2 to 150 members (Anthropic Help Center). A standard seat is $25 a member a month on monthly billing or $20 on annual billing, and a premium seat is $125 or $100. Each seat carries a usage allowance with weekly limits: 1.25 times the Pro plan's per-session usage for a standard seat, 6.25 times for a premium one.

On annual billing, a standard seat is $240 a year ($20 × 12) and a premium seat $1,200 ($100 × 12):

• 3 people. $720 a year on standard seats or $3,600 on premium (3 × $240, 3 × $1,200).
• 5 people. $1,200 a year on standard seats or $6,000 on premium (5 × $240, 5 × $1,200).
• 8 people. $1,920 a year on standard seats or $9,600 on premium (8 × $240, 8 × $1,200).

The Team figures assume people stay inside their seats' limits; if your advisors will run skills all day, price the premium column too.

Neither plan covers what you pay your other vendors. Connectors use your existing accounts, and access "may require a separate subscription or API key from the respective provider" (Anthropic tutorial). Setup costs your time or a consultant's fee, and the pricing guide covers larger headcounts.

4. Team vs Enterprise for an Eight-Person RIA

Side by side, for a firm of eight on annual billing:

Price the gap honestly. Against eight standard Team seats, Enterprise costs $9,600 to $14,400 more a year ($11,520 minus $1,920, and $16,320 minus $1,920). Against eight premium seats, the gap shrinks to $1,920 to $6,720 ($11,520 minus $9,600, and $16,320 minus $9,600).

That difference buys the records layer and the setup Anthropic recommends. For an SEC-registered firm that will put client work through the plugin, Enterprise is the safer default; Team is a reasonable choice when your CCO accepts the workaround below and the connectors you need work on it.

5. Recordkeeping on Team: The Workaround and Its Limits

Rule 204-2 generally requires advisers to keep required records for five years (17 CFR 275.204-2). Which AI outputs count as records is a judgment for your CCO and counsel. The practical question is whether you can capture them.

On Enterprise, the pipe exists. The Compliance API gives an archive the chat data, file content and activity events, and Smarsh built Smarsh Capture for Claude Enterprise on it in May 2026, capturing prompts, conversations, files and activity logs, deleted and archived conversations included. The audit log alone would fall short, because it covers events for 180 days per export and leaves out chat titles and content.

On Team there is no such pipe, so the workaround is a procedure: every final output lands in a system your archive already covers.

• Client emails go out through the firm's own email, so the sent version reaches whatever archive already captures email.
• Notes, tasks and opportunities written by /post-meeting live in the CRM.
• The two files /compliance produces for each review, and the rationale memo from /portfolio-rebalance-review, get saved to the compliance file by a named person. The skill's own scratchpad does not count, and the skill says so itself.
• A written procedure says who files what and when, and the CCO tests it.

Say it plainly: this is weaker. It depends on people following the procedure every time, and it keeps the final version without the prompts, drafts and conversation behind it, which is exactly what content capture on Enterprise keeps. When an examiner asks how you know the procedure works, your only evidence is your own testing.

The workaround stops being enough in four situations:

• Your CCO or counsel concludes that the conversations themselves are records.
• More than a handful of people use the plugin, or some of them will not follow a filing procedure.
• An exam is coming, or past exams found books-and-records problems.
• You are a dual registrant and answer to FINRA as well, which makes this a question for the CCO before anyone signs up.

If none of those applies and your CCO signs the procedure, Team can work. If any applies, the empty seats are the cheaper problem.

6. Connectors Outside Enterprise: Ask in Writing

Most launch material describes the Enterprise path, so do not assume every connector behaves the same on Team or Pro. Whether a given partner connector runs outside Enterprise is a question for Anthropic and for the vendor, answered in writing before you buy.

Schwab matters most, because no other RIA custodian was integrated at launch. A firm switches the connector on once for the whole firm, decides which users get it, and pays through its Anthropic licenses rather than through Schwab (Financial Planning). Even so, the plugin's README still showed that connector as coming soon, and until it lands the skills run on pasted or uploaded data (see whether you need Schwab).

Send the same short email to Anthropic and to each vendor you rely on:

1. Does your connector work for a firm on Claude Team? On Pro?
2. Does it need a separate subscription or API key from you?
3. Is it read-only, or can it write back, and with whose approval?
4. For Schwab: can a firm on Team switch the connector on for the whole firm and limit who uses it?

Keep the replies in your vendor files. If a connector turns out to need Enterprise, the skills still run on Team with paste or upload in its place, which costs advisor time rather than license fees. Tyrone Ross's doubt, quoted below, is the reason to ask before you buy.

7. Solo Advisors

A solo advisor has the same three options, plus one more. Plugins work on the individual Pro plan, but Pro has no admin controls, so there is no organization to push the plugin to and no records layer.

Team needs at least two members, so a solo advisor on Team pays for two seats: $480 a year on standard seats billed annually (2 × $240), or $2,400 on premium (2 × $1,200). Enterprise for one person is the full floor plus one person's usage: $4,800 plus $840 to $1,440, or $5,640 to $6,240 a year.

Check the data terms, too. The protection this guide relies on, that your inputs are not used to train models, comes from Anthropic's commercial terms for Team and Enterprise. Pro runs under Anthropic's consumer terms, where each user chooses whether chats can help train models, so check that setting, and the rest of the plan's terms, before any client information goes near it.

Being your own CCO does not make the records question go away. If you are state-registered (generally under $100 million in assets under management), you answer to your state regulator; many state rules track the SEC's, but confirm with your state.

A sensible solo start: run /onboarding and its fictional household on whichever plan you pick, settle how you will keep records, and only then bring in real client data.

8. When Waiting Is the Right Call

Waiting costs nothing in licenses, and the product only launched on September 14, 2026. Four signs say wait:

• Your key connector is missing. If you custody at Schwab and its connector has not reached your plan, the estate and rebalance reviews run on pasted data. Other custodians were not integrated at launch at all.
• Your CRM notes are thin. /pre-meeting reads the CRM and /post-meeting writes to it. Sparse notes produce sparse prep documents, and advisors conclude the tool is weak.
• You have no records answer. Enterprise is out of budget and your CCO will not sign a Team procedure.
• Nobody will own it. The repository calls itself a "reference implementation. Not actively maintained or monitored, and not accepting contributions." A firm that adapts it owns its copy, and someone has to look after it.

Your platform may also get there first. Dynasty Financial Partners, for one, is bringing its own Claude-powered Dynasty AI OS to the roughly 60 independent RIAs in its network, with a wider release planned for the fourth quarter of 2026.

Wait well, though. Clean the CRM, draft the AI policy addendum and collect the vendor answers from section 6, so that when you start, the slow parts are already done.

9. What to Do This Quarter

Six steps, in order, for a firm under 20 people:

1. List your systems (CRM, portfolio, planning, custodian, email, archive) and check each against the connector list.
2. Ask your CCO the records question first: Team with a written procedure, or Enterprise with the Compliance API feeding your archive.
3. Send the vendor email from section 6, starting with Schwab if you custody there.
4. Price both plans at your headcount with the math in section 3, and write down the spend limit you would set; on Enterprise, limits can be set for the firm and for each user.
5. Pilot with one or two advisors for a week, on the fictional household first and then on real meetings.
6. Decide by a date, and file the reasoning with your compliance records.

Steps 1 to 4 cost nothing but time. The setup guide covers everything after the decision.