Claude for Financial Advisors Training: A 30-Day Plan to Get Every Advisor Using It

1. The Short Answer: Real Meetings, One Skill Group a Week

The fastest way to train advisors on Claude for Financial Advisors is to skip the training day. Give each advisor one group of skills per week, used on their own client meetings, and check three numbers at the end of the month.

The plugin, which runs in Claude Cowork, makes this easier than most AI rollouts, because its eight skills already follow an advisor's week: prepare for the meeting, write it up, check what goes to the client, review the portfolio. Betterment's advisor playbook describes skills as a firm's own processes written down. Training means teaching people when to call each one and what to check in what comes back.

Anthropic's launch post cites Kitces research finding that a typical practice spends a sixth of its time in client meetings. The skills go after the other five-sixths: prep, notes, follow-up, compliance review and portfolio housekeeping. So train in those hours, on that work.

Thirty days is long enough to learn whether the skills fit your practice and to make the useful ones routine. That is what good Claude training for RIAs looks like: short, on real work, with a number at the end. The plan below assumes a small RIA; a larger firm can run it one team at a time.

2. Before Week 1: What Has to Be True

Training on a half-built setup teaches people that the tool does not work. Check six things before anyone runs a skill on a real household.

• The plan is settled. Anthropic points RIAs to Enterprise, citing the audit logs that support recordkeeping. A firm on Team needs a written records procedure from the CCO first.
• Everyone has the plugin. An Owner can push it through the organization marketplace as Required or Installed by default, so every advisor runs the firm's version, which members cannot edit.
• The main connectors work. Test the CRM, the portfolio system and email with an advisor's login as well as an admin's, because each connector inherits the signed-in user's own permissions (Anthropic tutorial).
• The records path is live. The Compliance API feeding your archive on Enterprise, or the approved procedure on Team.
• The policy addendum is written and read. Which client data may go into Claude, and the rule that none of it goes into a personal AI account.
• A champion is named. One advisor starts a week early and finds the rough edges before everyone else does.

If any of these is missing, finish setup first; the setup guide walks through it. A week's delay costs less than a bad first impression.

3. Who Needs What

Five groups use the plugin differently, so each needs its own briefing before week 1.

• Advisors. /pre-meeting, /post-meeting and /compliance every week, plus the portfolio skills for their own households. Their job is judgment: reading output critically, correcting it, and deciding what gets written back. Teach one setting as well: personal preferences go in Settings, General, Instructions for Claude, which apply to every conversation, so firm rules belong in the firm's copy of the plugin instead.
• Paraplanners and associates. They often do the prep, so they need the skills as much as advisors do. /prospect-intake takes whatever a prospect sends (statements, exports, even screenshots) and produces one consolidated view, a plain-English summary, a handoff for the analyst and a memo on what to expect, while leaving out allocations, fee quotes and return projections. Teach them to flag stale or missing data rather than work around it.
• Operations. Connectors, logins and access, the paste-or-upload fallback for systems with no connector, and CRM hygiene. The skills read your CRM, so thin notes produce thin prep documents.
• The CCO. What /compliance checks, what it escalates and where it stops. The skill appends each review to a working file, compliance-review-scratchpad.md, that it describes as outside the firm's books and records, so the CCO decides where reviews get filed.
• The owner. Sets the rules, goes first on /pre-meeting, and runs the week 4 review. People copy what the owner does and notice what the owner skips.

At a small firm one person often holds two of these roles, and the owner is frequently the CCO. Brief each role anyway, one at a time.

4. The 30-Day Plan, Week by Week

Each week adds one group of skills and one habit, and nothing from the week before gets dropped.

Week 1: /onboarding, then /pre-meeting on real households

On day one, each advisor runs /onboarding, the plugin's guided first-run setup (source on GitHub). It asks about the firm and the systems the advisor uses, helps connect each one with the advisor's own login, and runs a demo on the fictional Millers household so no real client data is involved. The session closes with a suggestion for which skill to try next.

From then on, every client review that week gets /pre-meeting. The skill assembles a prep document from whatever is connected: Salesforce, Redtail or Wealthbox for the relationship; Orion, Addepar or Envestnet Tamarac for the portfolio; Wealth.com for estate and tax status; Zocks or the CRM for past meeting notes; Gmail or Outlook for recent email; MoneyGuide for the plan. The output runs from a household snapshot and relationship signals through open items, a portfolio review and planning topics to a time-boxed agenda, talking points and draft action items.

Start here because prep is private. The document goes to the advisor, and the skill never sends anything to a client, never places a trade and never invents plan probabilities or performance, so a mistake gets caught at the desk.

Week 2: /post-meeting and the approval habit

/post-meeting starts from a meeting record in Zocks or Wealthbox, or a transcript pasted in, and drafts a CRM note, action items and opportunities. The advisor sees them as a single batch, and only what gets approved is written, in the CRM's native records: Wealthbox notes, tasks and opportunities, or Redtail notes, activities and opportunities. It does not create contacts or edit contact fields, and client follow-up emails route through /compliance.

The habit this week is the approval. Read the batch, fix what is wrong, delete what does not belong, then approve. The README says the advisor "must explicitly approve any action that writes back to an external system," and it also says that rule is enforced by the model following it rather than by the software around it, so teach one reflex: if anything is ever written without asking, stop and tell operations.

The target for the week is simple. Every meeting has a CRM note by the end of the same day.

Week 3: /compliance on every client-facing draft

Week 3 has one rule with no exceptions: every client-facing draft goes through /compliance before it goes anywhere else. The skill first asks who the audience is, which channel the draft will go through, and what kind of firm you are (SEC-registered, state-registered or dual registrant). Then it tests the draft against the Marketing Rule, Section 206's antifraud and fiduciary provisions, the books-and-records rule (Rule 204-2) and, if you are dually registered, Reg BI and FINRA 2210.

It hands back a verdict table that marks each issue Fail, Flag or Note, with suggested rewording, disclosure wording you can paste straight in, and a clean redraft. Anything involving performance, hypothetical performance or testimonials goes to the CCO every time. In the skill's own words, its output is "a draft review for the firm's CCO/compliance officer, not a legal determination or an approval," and every advisor should hear that sentence.

Teach its limits as well. Its rules come from a checklist it calls "a static snapshot, not a live firm-rules feed," so it knows your disclosures and banned phrases only if your firm has added them. It also warns about off-channel texting, a good moment to restate the firm's rule.

This week the CCO reads every verdict table. Where the skill and the CCO disagree, you have found the rules to add to the firm's copy (see customizing the plugin).

Week 4: portfolio skills and the usage review

The skills closest to advice come last. /portfolio-rebalance-review measures performance and drift against the IPS or model, sets out tax-aware options, and writes a rationale memo for the compliance file whose approval table stays empty until the advisor signs; it will not execute or even stage a trade. /alts-brief lines up a household's alternatives, pulled from iCapital or Addepar, next to its liquid holdings using the platform's own figures, and /estate-and-tax-brief compares the Wealth.com estate plan with how accounts are actually titled and who the named beneficiaries are, then flags the gaps.

Pick the one or two that match your practice; a firm with little in alternatives can skip /alts-brief for now. For where the line sits on advice, see whether it can give investment advice.

Close the month with a usage review of about an hour. Each advisor brings one output used as-is, one they fixed and one they threw away. Then compare the three numbers below against the baseline and decide what changes: a note format, a rule for /compliance, a connector that is not pulling, or a skill nobody needs.

5. What to Measure

Measure three things, and take a baseline in a normal week before week 1. A number you only start counting after launch cannot show a change.

• Prep time per client review. Minutes from opening the file to feeling ready, logged by each advisor for the baseline week and again in week 4. This is the number /pre-meeting exists to move.
• CRM notes logged the same day. The share of meetings with a note in the CRM by close of business, which the CRM's own timestamps show.
• Compliance escalations. How many drafts went through /compliance, how many came back Fail or Flag, and how many went to the CCO. More drafts reviewed and fewer Fails over time means advisors are learning the rules, while zero escalations across a month of client email means drafts are skipping the check.

Ignore vanity counts such as logins and prompts. On Enterprise, also check usage against the spend limits you set for the firm and for each user, since usage is billed separately at API rates.

6. Three Habits That Matter More Than Prompts

The skills already hold the instructions, so prompt-writing matters less here than in most AI training. Three habits matter more.

• Read the prep document before the meeting. The skill assembles, and the advisor decides what to say. The document is only as current as the CRM and portfolio data it pulls, and an advisor who skims it in the lobby will be caught by the one stale number.
• Keep client data inside the firm's workspace. The firm's Claude organization runs under Anthropic's commercial terms, which do not use your inputs to train models, and under the firm's retention settings and records procedures (see whether it trains on client data). A personal AI account sits outside all three, and the shadow AI guide covers how to make the firm's account the easy choice.
• Approve writes deliberately. The approval screen is where the advisor's judgment enters the CRM. Approving a batch unread turns a control into a formality and fills the CRM with notes nobody checked.

None of the three takes technical skill. All three take an owner who does them first.

7. Why Advisor Rollouts Stall

Advisor AI adoption tends to stall in one of four ways, set out in why AI rollouts fail at investment firms: no owner, breadth over depth, the trust gap, and no real work. Each has an RIA version.

• No owner. Nobody runs the week 4 review, and usage drifts quietly back to old habits.
• Breadth over depth. All eight skills in one afternoon. People remember the demo and use none of it.
• The trust gap. The first prep document shows a stale allocation because the portfolio feed was behind, and the advisor decides the tool is unreliable. Fix the data before week 1, and teach advisors to trace a number to its source.
• No real work. Training that never leaves the fictional Millers household. The demo teaches the buttons; habits form on real meetings.

Regulated firms add a fifth: the CCO hears about it last. A CCO who first meets the plugin in an advisor's draft email will slow everything down, and should, so bring the CCO in before week 1.

8. Where to Start

Pick a start date in a normal meeting week, away from quarter-end reporting, and take the baseline the week before. Name the owner and the champion. Put the week 4 review in the calendar today, because an unscheduled review never happens.

If setup is unfinished, do that first; the guide to setup help covers who can do it, including when you need no one.