Claude CoWork for Financial Advisors
A practical guide to using Claude as your AI co-worker in your financial advisory workflow — from setup to daily use.
What is Claude CoWork?
Claude CoWork is the practice of using Claude as a persistent, context-aware assistant integrated into your daily financial advisory workflow. This goes beyond occasionally asking a chatbot for help. You configure Claude with your practice details, client communication style, and compliance preferences so that every interaction produces output that fits your practice and is ready to use with minimal editing.
Claude-native prompts. The prompts in this guide use Claude's native XML tag structure (,,,) for more precise, consistent output. These tags help Claude parse your intent with less ambiguity. They work in ChatGPT too, but are optimized for Claude.
Financial advisors face a unique documentation challenge. You serve dozens or hundreds of clients, each with different goals, risk tolerances, and life situations. Every client expects a personalized plan summary, quarterly review letter, and meeting follow-up. At 30-60 minutes per document, a book of 80 clients means hundreds of hours per year spent on documentation alone — time that could go toward advice, prospecting, and deepening client relationships.
This guide shows you how to set up Claude specifically for financial advisory work, the five workflows where it delivers the most value, and the privacy and compliance considerations that are essential in a fiduciary practice.
Setting Up Claude for Financial Advisory Work
Step 1: Create a Financial Advisory Project. In Claude, go to Projects and create one called "Financial Advisory Practice." This gives you a persistent workspace where your context carries across every conversation.
Step 2: Set your custom instructions. In the Project settings, add:
You are my financial advisory practice documentation assistant. Here is my context:
<practice-profile>
- Role: Financial Advisor / CFP / RIA at [Firm name / independent practice]
- Registrations: [RIA, Series 65, Series 7, insurance licenses]
- Practice focus: [Comprehensive planning / Investment management / Retirement planning / Estate planning]
- Custodian: [Schwab, Fidelity, Pershing, etc.]
- Planning software: [eMoney, MoneyGuidePro, RightCapital, etc.]
- Typical client profile: [Mass affluent / HNW / Pre-retirees / Business owners]
- Communication style: [Warm and educational / Direct and data-driven / Conversational]
</practice-profile>
<rules>
- All client-facing documents should be written in plain language — no jargon without explanation
- Quarterly review letters should be warm, transparent, and build confidence
- Meeting notes should be structured for both client reference and compliance documentation
- Recommendation memos must document rationale, alternatives considered, and risk factors
- Never generate content for a specific identifiable client — all scenarios must use de-identified data
- Include appropriate regulatory disclaimers where relevant
- Remind me to verify all figures and calculations against actual client records
</rules>Step 3: Upload reference documents. Add your preferred plan summary format, a quarterly review letter you are proud of, your compliance documentation template, and any firm-specific style guides.
Step 4: Always work inside this Project. Your context loads automatically, saving you from re-explaining your practice every session.
Your Top 5 Workflows with Claude
1. Financial Plan Summaries
Every client who receives a financial plan deserves a clear, readable summary. Most advisors spend 2-4 hours turning planning software output into something a client can understand. Claude cuts this to 20 minutes.
<task>Draft a financial plan summary for a de-identified client.</task>
<client-profile>
- Client: Married couple, both age 52, dual income ($185K combined)
- Primary goals: Retire at 62, fund youngest child's college (starts in 3 years), build estate for two children
- Current assets: $850K retirement accounts (401k + IRA), $200K taxable brokerage, $350K home equity
- Savings rate: 15% of gross income
- Risk tolerance: Moderate — comfortable with market fluctuations but priority is retirement security
- Debt: Mortgage $280K remaining at 4.5%, no other debt
- Insurance: Term life ($500K each), no long-term care coverage
</client-profile>
<instructions>
- Write a 2-3 paragraph executive summary in plain language
- Break down each goal with timeline, current progress, and recommended approach
- Include a recommended investment strategy aligned with their risk tolerance
- List 5-6 specific next steps with timeframes
- Tone: Warm, confident, and empowering — like a trusted advisor explaining a clear path forward
- Avoid financial jargon without explanation
</instructions>Before Claude: 2-4 hours per plan summary, often delayed days after the planning meeting.
After Claude: 20 minutes — draft generated in 2 minutes, 18 minutes to review, personalize, and align with planning software output.
2. Quarterly Portfolio Review Letters
Review season is the most documentation-heavy period for advisors. Writing 50-100+ personalized letters at 30 minutes each consumes entire weeks. Claude generates each letter in under a minute.
<task>Draft a quarterly portfolio review letter for a de-identified client.</task>
<review-data>
- Client: Retired couple, age 68 and 65
- Review period: Q4 2025
- Portfolio value: $1.35M (up from $1.28M)
- Portfolio return: +4.2% for the quarter, +12.8% YTD
- Benchmark (60/40): +3.1% for the quarter
- Asset allocation: 55% equities, 30% fixed income, 10% alternatives, 5% cash
- Key contributors: US large cap (+6.2%), international equities (+3.8%)
- Key detractors: Long-duration bonds (-0.5%)
- Changes made: Reduced long-duration bond exposure, added TIPS allocation for inflation protection
- Distributions: $12,500/quarter systematic withdrawal (3.7% annual rate)
</review-data>
<instructions>
- Open with a warm, personalized greeting referencing the quarter
- Explain performance in plain language with key numbers
- Put performance in context against benchmarks
- Explain allocation changes with clear rationale
- Address the sustainability of their withdrawal rate
- Close with a forward-looking statement and meeting invitation
- Length: 400-500 words
- Tone: Confident, transparent, and reassuring
</instructions>
<avoid>
- Defensive language about any underperformance
- Overly technical investment terminology
- Predictions about specific market outcomes
- Language that could be construed as guaranteeing future performance
</avoid>3. Client Meeting Documentation
Every client meeting generates documentation that serves both the client and your compliance file. Claude turns rough notes into complete meeting documentation packages.
<task>Generate a complete meeting documentation package from my rough notes.</task>
<meeting-details>
- Meeting type: Annual review
- Client: Married couple, both age 55
- Attendees: Both clients, advisor
- Date: February 2026
- Duration: 60 minutes
</meeting-details>
<rough-notes>
Reviewed portfolio performance — up 11% YTD, beating benchmark. Both happy with results. Discussed accelerating retirement timeline — he wants to retire at 60 instead of 65. She's open to it but worried about healthcare before Medicare. Ran Monte Carlo — 78% success rate at 60 with current savings, 92% if they max out catch-up contributions for next 5 years. Agreed to increase 401k contributions to max including catch-up starting next pay period. Discussed Roth conversion ladder strategy — makes sense to start converting in years between retirement and Social Security. Talked about long-term care insurance — both interested, will get quotes. 529 plan for grandchild — want to start one, $5K to open. She asked about estate plan — haven't updated wills since kids were minors. Referred them to estate attorney. Next meeting in 6 months unless they want to discuss Roth strategy sooner.
</rough-notes>
<instructions>
Generate three components:
1. Structured meeting notes suitable for the compliance file — organized by topic with key data points and decisions
2. Action items split into "Client Action Items" and "Advisor Action Items" with deadlines
3. A professional follow-up email to the clients summarizing decisions and next steps
</instructions>4. Recommendation Memos
Fiduciary advisors need to document their reasoning for every significant recommendation. Claude generates structured memos that serve both the compliance file and client understanding.
<task>Draft a recommendation memo for a de-identified client scenario.</task>
<recommendation>
Topic: Roth IRA conversion strategy during pre-Social Security gap years
</recommendation>
<client-situation>
- Client: Recently retired at age 60, spouse still working part-time ($35K/year)
- Traditional IRA: $650K
- Roth IRA: $85K
- Social Security projected: $2,800/month at 67 (client), $1,900/month at 67 (spouse)
- Current annual spending: $95K
- Tax filing status: Married filing jointly
- Current marginal rate: 22% (income gap between retirement and SS/RMDs)
- Projected future rate: 32% once SS + RMDs push them into higher bracket at 72
</client-situation>
<instructions>
- Write a formal recommendation memo with: Executive Summary, Background, Analysis, Alternatives Considered, Implementation Plan, and Suitability Statement
- Include a bullet-point rationale summary (5-7 points)
- Write a balanced risk disclosure section
- Create a plain-language client summary (1 page)
- Show the math on tax savings clearly
- Document why this recommendation is suitable for this specific client
</instructions>5. Market Commentary and Client Communication
Proactive communication differentiates great advisors. Claude helps you send consistent, personalized market updates and check-in messages.
<task>Write a brief market commentary email I can send to my client base after a volatile week.</task>
<context>
- S&P 500 dropped 4% this week on inflation concerns
- Fed signaled rates may stay higher for longer
- Bond yields rose sharply
- My clients are mostly moderate-risk, pre-retiree and retiree investors
- Several clients have emailed or called with concerns
</context>
<instructions>
- Subject line: Calm, informative (under 50 characters)
- Opening: Acknowledge the market movement directly — don't pretend it didn't happen
- Context: Explain what happened and why in 2-3 sentences a non-investor can understand
- Perspective: Put this in historical context — how often do weeks like this happen?
- Reassurance: Explain how their portfolios are positioned for exactly this kind of volatility
- Action: What we are doing (or not doing) and why
- Invitation: Open door for a conversation if they want to talk
- Length: Under 350 words
- Tone: Calm, confident, transparent — the voice of a steady hand
</instructions>
<avoid>
- Minimizing their concerns ("Don't worry about it")
- Predicting what happens next
- Technical jargon (basis points, duration, etc.)
- Anything that sounds like a form letter
</avoid>Prompt Engineering Tips for Financial Advisors
1. Always specify the audience. A plan summary is for the client. A recommendation memo is for the compliance file. A review letter is for both. Tell Claude who will read it and the output quality improves significantly.
2. Include specific numbers. Vague inputs produce vague output. "Portfolio did well" generates a generic letter. "Portfolio returned +4.2% vs. benchmark +3.1%, driven by US large cap +6.2%" generates a letter with substance.
3. Set the tone explicitly. Financial communication has a narrow tonal range — warm but professional, confident but not arrogant, transparent but not alarming. Name the tone you want and Claude will match it.
4. Use the "avoid" section. Financial communication has many landmines — guarantees, predictions, unsuitable recommendations. Tell Claude what to avoid and it will steer clear.
5. Ask Claude to review your work. Paste a draft review letter and ask: "Review this quarterly letter as if you were a compliance officer. Flag any language that could be construed as a guarantee, prediction, or unsuitable recommendation." This is a powerful quality check.
6. Build a library of your best prompts. Once you have a quarterly review letter prompt that consistently produces quality output, save it. Swap in client data each quarter and you have a repeatable system.
Privacy & Compliance
Never enter real client data into Claude. No names, account numbers, Social Security numbers, dates of birth, or any combination of information that could identify a specific client. Use de-identified scenarios: "Married couple, both age 55, $850K in retirement accounts" — never "John and Sarah Smith, account #12345."
De-identify all financial data. Round numbers, adjust ages slightly, and omit specific dates. Your prompts should describe a scenario, not a specific client record.
Claude output is a draft, not advice. Every plan summary, review letter, and recommendation memo Claude generates requires your professional review, verification against actual client data, and sign-off. Your license, your fiduciary duty, your responsibility.
Verify all figures. AI can generate plausible-sounding numbers. Before sending any client communication, verify every figure, return, benchmark comparison, and tax calculation against your actual records.
Check your compliance requirements. RIA compliance, broker-dealer supervision, and state regulatory requirements vary. Ensure your use of AI tools aligns with your firm's compliance policies and any applicable SEC or FINRA guidance on AI-generated communications.
Retain records. If your compliance framework requires retention of client communications, ensure AI-drafted documents go through your normal documentation and archival process.
Going Further
Want to deepen your AI-powered financial advisory workflow? Explore these resources: