After a 90-minute client review meeting, the advisor who can follow up with a clear, specific, human-sounding recap within the same day is materially different from the advisor who sends a boilerplate summary three days later. Clients notice. The relationship is different. The trust level is different.
The short version: Wealth advisors who use Claude with a structured recap protocol โ three to five minutes of input preparation, followed by a targeted Claude prompt, followed by a compliance-and-voice review โ can produce higher-quality, more personalized client meeting recaps in six to ten minutes. This is not a mass-communication shortcut. It is a workflow for advisors who want to maintain a personal, attentive relationship with each client while reducing the administrative drag that degrades both output quality and the timeliness of follow-up. The Leverage Years teaches this as part of a broader advisor communication system.
The problem with most advisor recaps is not effort โ it is structure. Advisors who write well still spend 30 to 45 minutes per recap because they are doing three things simultaneously: remembering what was discussed, deciding what to include, and writing it in a way that is both compliant and human-sounding. This workflow separates those three steps. You remember and decide; Claude drafts the structure; you apply the relationship layer and compliance review.
If your current recap process is either too slow, too generic, or both, this is worth reading carefully.
Who this is for
- Registered Investment Advisors and fee-only wealth advisors with recurring client relationships
- Wirehouse and independent broker-dealer advisors managing 50+ client households
- Ensemble practice advisors who want consistent recap quality across the team
- Financial planners who hold comprehensive annual reviews or regular check-ins
- Any advisor whose client communication lag currently exceeds 24 hours
This is not for you if: you are looking for a way to automate client relationships or reduce the personal contact in your practice. The workflow below produces better recaps because it gives you more deliberate time with the relationship layer, not less. Advisors who want to remove themselves from the communication process entirely should look elsewhere.
The Six-Minute Recap Workflow
The premise is simple: a client meeting recap has a predictable structure. Every quality recap contains the same five elements in some form โ what was discussed, decisions that were made, action items with owners and deadlines, any concerns or open questions, and the next step. Advisors know this. The problem is that writing those five elements from scratch after every meeting, while managing a full client load, produces work that is either delayed, abbreviated, or formulaic.
Claude handles the structural work. You handle the relationship.
Here is the protocol.
Step 1: Take three minutes of structured notes during or immediately after the meeting
The quality of your recap will be determined entirely by the quality of your input. The biggest mistake advisors make with this workflow is trying to use Claude to compensate for sparse notes. It will not work. Claude can organize and articulate what you give it; it cannot reconstruct what you did not capture.
Three minutes of focused note-taking immediately after a meeting is more valuable than ten minutes of notes taken two hours later. You are not taking comprehensive minutes. You are capturing the five elements: topics covered, decisions made, action items, concerns raised, and next meeting focus.
A working format that takes about two minutes to complete:
- Topics covered: [2-4 bullet points]
- Decisions made: [any choices the client confirmed โ rebalancing, contribution changes, beneficiary updates, etc.]
- Action items: [who is doing what by when โ include items for both you and the client]
- Concerns or open questions: [anything the client raised that requires follow-up or monitoring]
- Next meeting: [timing, agenda focus]
If the meeting involved any compliance-relevant discussion โ suitability concerns, product recommendations, changes to investment objectives โ note that explicitly. You will add the compliance language in your review; you just need to flag the trigger.
One note on data handling: do not include specific account numbers, Social Security numbers, or other PII in the notes you pass to Claude. Use the client's first name only or a reference like "the Johnson household." Your compliance team may have specific data-handling requirements that go beyond this; follow those first.
Step 2: Write one sentence of relationship context before the Claude prompt
This is the step that separates advisor recaps that sound personal from those that sound generated. Before you give Claude your meeting notes, write one sentence โ not for Claude to quote, but to frame the tone of the communication:
"David is 67, recently retired, and has been anxious about sequence-of-returns risk since our last meeting โ he needs reassurance as much as information."
"Maria is a disciplined saver who wants precise language about what was decided and why โ she will read this carefully."
"The Hendersons are in the middle of a business sale and every communication needs to acknowledge the complexity of their situation without adding anxiety."
This sentence tells Claude how to weight the tone of the draft. It takes 30 seconds to write and produces a meaningfully different output. An anxious retired client and a detail-oriented accumulator both need a recap โ but the same structural draft should not go to both of them without a tone adjustment.
Step 3: Run the recap prompt with notes and context together
The working prompt structure for advisor recaps has three components: the framing (who is the reader, what is the purpose), the input (your notes from Step 1), and the constraints (what Claude should and should not include).
The prompt pattern:
"I am a financial advisor writing a follow-up email to a client after our annual review meeting. The client is [brief description from Step 2]. Please draft a client-facing meeting recap email using the following notes. The tone should be warm, direct, and specific โ not formulaic. The email should: (1) open with a brief personal acknowledgment specific to this meeting, (2) summarize the key topics we discussed in 3-4 bullets, (3) list action items clearly with owners and deadlines, (4) note any open questions we are monitoring, (5) close with the next meeting timing and a brief forward-looking sentence. Do not include any specific investment product recommendations, performance projections, or regulatory disclosures โ I will add compliance language in my review. Do not invent any information not present in the notes below."
Then paste your meeting notes from Step 1.
The explicit instruction not to invent information is the most important constraint. Without it, Claude will occasionally fill structural gaps with plausible-sounding content โ a reference to a topic that came up "briefly" that you don't remember discussing, or a client concern that was implied but not stated. Those subtle fabrications are dangerous in an advisor-client communication context. The instruction keeps Claude in its proper role: structural articulation of what you gave it, not inference or elaboration.
Step 4: Review for compliance, voice, and relationship fidelity
This step is not a formality. It is the step where your professional judgment determines whether the communication goes out.
Compliance review is first. Read every sentence for anything that could be construed as a performance guarantee, a specific product recommendation that requires disclosure, or a statement about future investment outcomes. If anything in the draft triggers a compliance concern, rewrite or remove it before anything else. Your compliance department may require you to retain copies of all client communications; your standard archiving process applies here.
Voice review is second. Does this sound like you? Senior advisors who have worked with clients for years have a distinctive communication style โ a level of formality, a way of framing portfolio discussions, a particular kind of closing sentence. Claude will produce competent, grammatically clean prose that sounds like a capable advisor. It will not sound exactly like you. Read for places where the tone is slightly off, where a phrase is technically correct but not something you would say, and adjust those sentences.
Relationship fidelity is third. Does the recap accurately reflect what happened in this meeting, for this client, at this point in their financial life? A client who lost a spouse six months ago and whose entire estate plan is being rebuilt needs a recap that acknowledges that context, even briefly, even implicitly. A client who just made a significant emotional decision about their retirement date needs a recap that honors the weight of that decision. Claude does not know any of this unless you tell it. The relationship layer is entirely yours.
Step 5: Send within the same business day
The timeliness of the recap is part of the value. An advisor who follows up within the same business day signals attentiveness and organization. An advisor whose recap arrives three days later signals busyness, or indifference, or both.
The six-minute workflow is specifically designed to enable same-day follow-up. If the recap takes 45 minutes, it competes with every other obligation in the afternoon. At six to ten minutes, it is the last thing you do before leaving the office, or the first thing you do the following morning for late-in-the-day meetings.
Timeliness is the hidden benefit of this protocol. Most advisors who implement it comment that the quality difference between their old recaps and the new ones is smaller than they expected โ and the timeliness difference is larger.
Checklist: The Six-Minute Recap Quality Gate
Run this before every recap goes out:
- Notes contain the five elements. Topics, decisions, action items, concerns, next meeting.
- No PII in the Claude prompt. Account numbers, SSNs, and full client names are not in the text you gave Claude.
- Relationship context sentence was included. The tone reflects this client's current situation.
- No invented information. Every claim in the recap can be traced to something that actually occurred.
- Compliance review complete. No performance projections, no product recommendations requiring disclosure, no guarantees.
- Voice review complete. The recap sounds like you, not like a template.
- Action items are accurate. Every item with a deadline and owner has been confirmed.
- Sending within same business day (or first thing the following morning for late meetings).
An Illustrative Example: The Annual Review Recap
Suppose an advisor has just completed an annual review with a client who is 58, five years from her target retirement date, and focused on whether she is on track. The meeting ran 75 minutes and covered: updated retirement income projection, a discussion about increasing 401(k) contributions, a concern about a concentrated stock position she inherited, and a preliminary conversation about long-term care planning.
The advisor spends two minutes after the meeting writing structured notes in the five-element format. She notes that the client is analytically oriented and will re-read the recap carefully. She writes a one-sentence context note: "Sarah is detail-focused and specifically wants confirmation that we addressed the stock concentration issue, which she raised herself and has been on her mind."
She runs the recap prompt with the notes and the context sentence. Claude produces a structured draft in 90 seconds. The draft has four bullets, correctly captures the action items (advisor: request stock concentration analysis; client: confirm contribution increase with HR), notes the LTC discussion as a topic to revisit, and closes with the Q4 annual review timing.
She reviews it. One thing is off: Claude's phrasing about the stock concentration is slightly vague โ "we discussed your inherited position" โ when Sarah specifically wants to see that the advisor is treating this with urgency. She rewrites that bullet in two sentences that reflect the conversation's actual weight. She checks for compliance issues (none โ no specific projections, no product recommendations). She reads the tone: it sounds like her, mostly, though one sentence in the opening is slightly formal. She adjusts it. Total editing time: four minutes. Total workflow time: six minutes and thirty seconds. She sends it before leaving the office.
Sarah replies within the hour with a brief note: "This is exactly what I needed. I'm going to share the LTC piece with my husband before we talk again."
That response does not come from a generic template. It comes from a recap that reflected the specific conversation, the specific concern, and the specific next step that Sarah cared about.
Pitfalls and Decision Rules
Use Claude for: structural consistency. Every recap from your practice should have the same structure: topics, decisions, actions, open questions, next step. Claude enforces that structure reliably.
Use Claude for: tone calibration. The one-sentence context note is a lightweight way to differentiate communication style by client without writing every recap from scratch.
Use Claude for: reducing first-draft friction. The hardest part of writing any recurring communication is starting. A Claude draft removes the blank page entirely.
Do not use Claude for: compliance disclosures. Any required disclosure language โ Regulation Best Interest documentation, suitability statements, performance disclosure requirements โ must come from you and your compliance team. Claude has no knowledge of your firm's specific compliance framework.
Do not use Claude for: difficult relationship moments. If a client has experienced a loss, received a significant medical diagnosis, or is in the middle of a contentious divorce, the communication around those conversations needs to be written by you. Claude will produce something grammatically appropriate. Appropriate is not sufficient.
Do not use Claude for: performance attribution or market commentary. If your recap includes commentary about why the portfolio performed as it did, or what market conditions drove specific outcomes, that language needs to come from you. It is the kind of statement that sounds credible from an AI assistant but has not been reviewed with the care that professional market commentary requires.
How this becomes a practice-wide operating system
For advisors in ensemble practices, the real leverage is not in a single advisor's recap quality โ it is in the consistency of communication quality across the practice.
When every advisor on the team uses the same recap protocol, clients experience a consistent communication standard regardless of which advisor they see. New advisors ramp into the communication standard faster. Compliance review of outgoing client communication becomes more predictable. And the practice-level data on client concerns, decision triggers, and relationship touchpoints becomes more structured and more actionable.
The protocol above is a single-advisor workflow. The Leveraged Wealth Advisor builds on it with the full communication system: quarterly touchpoint structures, proactive outreach protocols, review meeting preparation, and the prompt vault for the ten most common advisor communication scenarios. It is designed for advisors who want to run their practice with less administrative friction and more genuine client presence.
Not sure which course fits your work? Take the 6-question course selector.
You can also review the full curriculum at the courses page if you are still exploring.
Frequently asked questions
Is this workflow compliant with FINRA and SEC communication requirements?
The workflow produces a draft that you review and approve before sending โ it does not send communications autonomously. Compliance obligations for advisor-client correspondence remain entirely with the advisor and the firm. Before implementing any AI-assisted workflow for client communication, confirm with your compliance department that the process meets your firm's requirements for supervision, archiving, and review of outgoing client correspondence.
How do I handle the archiving requirement for advisor-client communications?
Your standard archiving process for client communications applies to recaps produced with this workflow, as they do to any client correspondence. The draft that Claude produces is an internal working document; the version you review, edit, and send is the client communication that enters your firm's archiving system. This is no different from an email you write in your email client before sending.
What if my compliance team prohibits the use of AI tools for client-facing communications?
If your firm prohibits AI-assisted drafting of client communications, you should not use this workflow for client-facing output. You may still find the protocol useful for internal meeting notes, advisor team summaries, or your own planning documents, where those restrictions do not apply. Always confirm your firm's specific policies before using AI tools in any professional communication context.
How do I maintain my voice if Claude is drafting the structural content?
The voice review step in Step 4 is specifically for this. Claude's draft is a structural starting point โ it organizes what you gave it and applies a generic advisory tone. Your edits in the voice review step are what make the communication yours: adjusting phrasing, adding a sentence that reflects a specific moment from the meeting, removing language that is technically correct but not how you speak. Most advisors find that after five or six recaps with this workflow, the editing step gets faster because they have a clearer picture of where their voice differs from Claude's default.
Can I adapt the recap format for quarterly letters or broader client updates, not just post-meeting recaps?
The same principles apply to quarterly letters and broader updates, with one adjustment: those communications typically involve more market or portfolio context, which requires more careful compliance review. The workflow is well-suited to the structural and organizational layer of quarterly communication โ ensuring consistent section structure, clear action language, and personalized opening and closing โ while you provide the market commentary and portfolio context yourself.
How do I train a junior advisor or associate to use this workflow consistently?
The five-element note format and the recap prompt pattern are easily documented as a team standard. The most important training element is the review protocol โ specifically, ensuring that junior advisors understand that the Claude draft is a starting point requiring full compliance and relationship review, not a finished product. The compliance review step in particular should be treated as a supervised skill until the advisor has demonstrated consistent judgment about what requires disclosure and what does not.