Claude Prompts for Financial Advisors

Compliance teams at wealth management firms report rejecting a meaningful share of advisor-drafted client communications on the first review pass, and AI-assisted drafts aren't immune — often for the exact same reason human-drafted ones get flagged: language that reads as a guarantee or a specific recommendation without required disclosure. Claude prompts for financial advisors need to build compliance awareness into the prompt itself.

Before: The Weak Prompt

Write an email to clients explaining why the market dropped this
week and what they should do.

Why It Fails

"What they should do" invites Claude to generate specific action recommendations — exactly the kind of individualized advice that triggers compliance review, since it wasn't tailored to any actual client's situation and risk profile. This prompt also has no disclosure requirements built in, which most compliance departments require on any client-facing market commentary.

⚠️ Common mistake: Asking for content that sounds like individualized financial advice when the actual deliverable is general market commentary meant for a broad client list. These are legally and functionally different documents, and the prompt needs to specify which one you're producing.

After: The Improved Prompt

Write a general market commentary email (not individualized advice)
explaining this week's market movement: [paste key data points].
Audience: retail clients with varying risk tolerances and time
horizons — this is being sent to our full client list, not one
specific client.

Requirements:
- Explain the market movement factually, citing [specific data points]
- Do not recommend any specific action (buy, sell, hold, reallocate)
- Include a closing line directing clients with questions about their
  specific situation to contact us directly
- Tone: calm, factual, not alarmist or reassuring in a way that
  understates real volatility

What this does: Explicitly banning specific action recommendations and stating this is broad commentary, not individualized advice, keeps the output in the category compliance teams are comfortable approving quickly. The "contact us directly" closing line is standard practice for exactly this reason — it routes anyone who actually needs individualized advice to a compliant channel.

⚡ Pro tip: Always run AI-drafted client communications through your firm's standard compliance review before sending, regardless of how carefully the prompt was written. The prompt reduces the odds of a rejection; it doesn't replace the review requirement, and no prompt should be treated as a substitute for compliance sign-off.

Breaking Down Each Element

The "not individualized advice" framing at the top of the prompt sets the register for everything that follows — Claude is noticeably better at staying within that lane when it's told explicitly up front, rather than left to infer the boundary from context.

The explicit ban on recommending buy/sell/hold actions is the single most important constraint in this prompt. Without it, Claude will often include a line like "this may be a good time to consider rebalancing," which sounds harmless and is exactly the kind of unindividualized recommendation that draws compliance scrutiny.

The factual data citation requirement keeps the commentary grounded in specific numbers rather than vague sentiment ("markets were volatile this week"), which is both more useful to clients and easier for compliance to verify against source data.

Variations for Different Contexts

For internal team communication about a market event (not client-facing, different compliance bar):

Summarize this week's market movement for our internal advisor team,
including talking points for how to discuss it with clients who call
in concerned. This is internal use only — you can be more direct
about our house view than in client-facing materials.

For a specific client's quarterly review prep (with that client's actual data):

Here's [client]'s portfolio allocation and stated goals: [paste
de-identified summary]. Draft talking points for their quarterly
review discussing performance relative to their stated goals. This
will be delivered verbally by their advisor, who will apply
professional judgment — draft talking points, not a script.

Scenario: Wealth management firm sending quarterly newsletters A four-advisor wealth management firm used the general-commentary structure for a quarterly client newsletter, running every draft through their existing compliance review process but finding first-pass approval rates improved once the explicit no-recommendation constraint was baked into the prompt itself rather than caught only during review.

Scenario: Advisor preparing for a volatile market day An advisor used the internal-communication variation to quickly prepare talking points for her team on a day the market dropped sharply, giving junior advisors consistent, house-view-aligned language to use on client calls that day rather than improvising individually.

Scenario: Compliance officer drafting advisor communication guidelines A compliance officer at a mid-size RIA used Claude to draft internal guidelines for advisors on what language patterns to avoid in client communications, then used those guidelines as the basis for a training session — turning a reactive compliance problem into a proactive one.

Save and Reuse This

The core fix in claude prompts for financial advisors is building the compliance boundary into the prompt itself — general commentary versus individualized advice, with explicit bans on recommendation language — rather than relying on a review pass to catch it after the fact. Once you've built this compliance-aware structure for your firm's communications, save it in PromptABCD so every advisor on your team starts from the same compliant template instead of each person reinventing the wheel, and re-risking the same rejection.