The Senior Advisor's Touchpoint System.

Senior wealth advisors who serve high-net-worth clients know the tension: the relationship is the product, the communication is what makes the relationship feel managed and trusted, and yet the mechanics of producing that communication — recaps, quarterly letters, check-in notes, follow-ups after life events — consume a disproportionate amount of the week.

The short version: A senior wealth advisor can use Claude to build a repeatable client touchpoint system that maintains the warmth and precision of high-value communication without drafting every note from scratch. The Leverage Years teaches this specific workflow — calibrated for advisor communication standards, compliance awareness, and the professional judgment that keeps long relationships intact.

The advisors who feel most stretched are rarely struggling with portfolio management or financial planning. They are struggling with the production layer: getting the right communication to the right client at the right moment, consistently, without the overhead of composing each piece under time pressure.

This is not a problem you solve by adding another CRM. It is a problem you solve by building a system — a set of defined inputs, prompt templates, and review disciplines — that converts your knowledge of each client into polished communication without starting from a blank page each time.

This post describes that system.

Who this is for

• Senior wealth advisors and private client partners managing ten to eighty high-net-worth or ultra-high-net-worth households
• Independent RIA principals who own the client relationship, manage the investment work, and draft most communication themselves
• Wirehouse advisors who have a team but still own the voice and quality of senior-tier client communication
• Family office advisors and principals whose client communication extends across generations and multiple relationship types
• Advisors in transition — building or rebuilding a practice after a move — who need a scalable communication system from the start

This is not for you if: your practice has a dedicated communications team that drafts all client-facing content and your role is purely review. That is a different model, and the bottleneck is different.

---

The Senior Advisor's Client Touchpoint Stack

Client communication in a senior advisory practice clusters into five recurring output types:

1. Post-meeting summaries and action confirmations
2. Quarterly review letters and portfolio commentaries
3. Check-in notes after market events, life events, or extended silence
4. New client onboarding communication
5. Internal planning notes and relationship status summaries

Each of these can be materially compressed using Claude — not by replacing the advisor's knowledge of the client, but by eliminating the blank-page overhead. The advisor still provides the substance. Claude structures it and polishes the language.

Here is the system.

---

Step 1: Build a Client Context Layer

Before any communication workflow runs, build a short, sanitized client context document for each significant relationship. This is not a CRM record. It is a working brief that you paste at the top of any Claude conversation related to that client.

It contains: - Relationship type: couple, individual, family, foundation, business owner - Stage of life: accumulation, pre-retirement, distribution, estate planning focus, multigenerational - Communication register: formal, warm-formal, conversational, highly technical, plain-English preference - Key topics in current focus: recent portfolio conversation, major life event, planning project underway - Tone sensitivities: any topics that require particular care — health, family situation, prior anxiety around markets, preference for directness - Time since last communication: helps calibrate the opening register

No names, no account numbers, no specific asset details. This document describes the relationship dynamic, not the client's financial data.

This layer is updated after each significant client interaction — typically a ten-minute note after a meeting. It becomes the standing context that makes every Claude-assisted draft feel like it came from someone who knows the client.

Step 2: Produce Post-Meeting Summaries in Under Twenty Minutes

The post-meeting summary is one of the most time-consuming recurring outputs in an advisory practice, and one of the most important relationship-maintenance tools you have. Clients who receive a clean, accurate summary within 24 hours of a meeting feel more confident about the relationship than those who receive nothing — regardless of how the meeting itself went.

The input workflow:

Within an hour of the meeting, dictate a rough voice note or type a quick bullet list: what was discussed, what decisions were made, what is pending, what you will do, and what the client said they would do. Two to five minutes. Include the emotional register if it matters — was the client anxious about something? Enthusiastic? Uncertain?

Paste the client context layer plus your rough notes into Claude with a prompt along these lines: "Here are my rough notes from a client review meeting. Please draft a professional post-meeting summary: brief summary paragraph, key topics discussed, decisions or agreements reached, action items for each party, and next scheduled touch. Tone is [formal / warm-formal / conversational]. Do not invent any specifics I haven't mentioned. If anything is ambiguous, flag it."

The draft arrives in thirty seconds. Your review takes five to ten minutes: verify every action item is accurate, adjust the opening if the client is someone who appreciates a more personal first line, confirm the tone is right. Send.

This is not a lower-quality document. Done well, it is a higher-quality document than what most advisors produce under time pressure, because the structure is consistent and nothing gets dropped.

Step 3: Draft Quarterly Review Letters

Quarterly letters are the highest-visibility recurring communication in most senior advisory practices. They set the frame for how clients interpret their portfolios, communicate market conditions in the advisor's voice, and signal that the advisor is actively thinking about this specific client — not sending a templated firm blast.

The production challenge: for a practice with thirty-plus households, a quarterly letter season can consume two to three weeks of writing time — more if each letter is meaningfully personalized.

The workflow:

First, write your market commentary in your own words: your read on the quarter, what mattered, what you told clients to expect, how things unfolded. This is your professional voice and your view. It should be written by you, not delegated to Claude. Two to four paragraphs.

Second, for each client, note the personalization layer: what was specific to this client's situation this quarter — a portfolio construction decision, a planning milestone, a life event, a conversation that informed how you thought about their account. This can be a paragraph or three bullets.

Third, paste the client context layer plus your market commentary plus the personalization layer into Claude: "Here is a market commentary paragraph and some notes specific to this client's situation this quarter. Please draft a quarterly review letter that weaves these together in a [formal / warm-formal] advisor voice. The letter should feel personal to this client, not like a form letter with a name inserted. About [400 / 600] words."

Review, verify, and adjust the most personal sentences. For the closest relationships, rewrite the opening paragraph in your own voice. Send.

A senior advisor who does this systematically can produce thirty personalized quarterly letters in a week rather than three — without sacrificing the quality of the content.

Step 4: Write Check-In Notes After Market Events and Life Events

Market volatility events and client life events are the two moments when advisors most need to communicate proactively — and when they most commonly delay because they cannot find the right words under time pressure.

For market events, the check-in note does not require a portfolio analysis. It requires a brief, calm, informed sentence or two that acknowledges what happened, confirms you are monitoring the situation, and signals that the advisor is present. It should land within 24 to 48 hours of the event.

The input: three to five bullet points on your market read, tailored to this client's exposure and anxiety level based on your client context layer.

The prompt: "Here is my quick read on recent market volatility and notes about this client's situation. Please draft a brief check-in note — three to four sentences — that is calm, informed, and reassuring without being dismissive. Do not make any forward-looking claims about market performance. Tone is [warm-formal]."

For life events — a divorce, a significant inheritance, a family health situation, a business sale — the check-in note requires more care. In most cases, you are not discussing portfolio specifics; you are acknowledging that you are aware of a significant development and signaling that you are available and thinking about them.

The input: your notes on the situation and the nature of your relationship. The output: a brief, warm, carefully calibrated message that does not overstep.

Review these particularly carefully. Life event notes carry emotional weight that mechanical drafting can sometimes misread. Your judgment about what to say — and what not to say — is irreplaceable here. Claude provides the structural scaffolding; your professional and human instinct provides the final calibration.

Step 5: Build and Maintain Your Prompt Template Library

After the first quarter of using this system, you will have produced enough drafts to know: which prompts work, which clients require a different register, and which document types benefit from additional structure in the prompt.

At that point, build a personal prompt template library. Not a folder of saved prompts for individual clients — a library of reusable prompt structures for each document type, with client-specific fields marked as placeholders.

A template for a post-meeting summary might look like: [CONTEXT LAYER] + "Here are rough notes from a [type of meeting]. Draft a post-meeting summary: summary paragraph, discussion topics, decisions, action items for each party, next contact. Tone: [register]. Do not invent specifics. Flag ambiguities."

A template for a quarterly letter: [CONTEXT LAYER] + "Here is my market commentary and this client's personalization notes. Draft a [length]-word quarterly review letter in a [register] advisor voice. Weave the market and personal notes together. Do not insert forward-looking performance claims."

Store these in a text file, a notes app, or a document you keep open during client communication sessions. Each template is the baseline. You edit the bracketed fields before running. Over time, the templates improve with use — you refine the language of prompts that consistently produce results that require minimal revision.

---

Checklist: The Senior Advisor's Quarterly Communication Calendar

This rhythm keeps client communication consistent without requiring constant active management.

After every client meeting (within 24 hours):

• Dictate or type rough meeting notes (2-5 minutes)
• Update client context layer with any new developments
• Run post-meeting summary through Claude, review, send

Ongoing throughout the quarter:

• Check-in notes for market events within 48 hours of significant moves
• Check-in notes for life events within 24 hours of learning about them
• One or two proactive "thinking of you" notes per quarter for your closest relationships (these are short; the client context layer makes them fast)

Quarterly:

• Write your market commentary draft first, before personalizing any letter
• Run quarterly letters in batches by client tier — start with highest-relationship clients
• Review every quarterly letter before sending — especially the personalized sentences
• Update context layers for any clients whose situations or register changed this quarter

Annually:

• Review the entire client communication template library
• Retire templates that are no longer producing clean output
• Build new templates for any document type you've been drafting from scratch repeatedly

---

What This Is Not

Senior advisors often have legitimate questions about this kind of system, and they deserve direct answers.

This is not Claude drafting financial advice. The investment decisions, the planning recommendations, the risk assessment — none of that is in this system. Claude is assisting with the communication layer: structuring your knowledge of the client, organizing the summary, polishing the language. The advice is yours. The communication that conveys it is built from your notes.

This is not a compliance shortcut. The compliance review requirements for client communications at your firm or under your regulatory framework do not change. This system does not bypass any approval process; it reduces the time required to produce a draft that can then be reviewed. Whether your compliance workflow requires a review before a letter goes out, that review still happens.

This is not a confidentiality risk if handled correctly. The client context layer deliberately contains no names, no account numbers, no specific portfolio data, and no identifying financial details. Your notes, when used as prompts, should reflect the same discipline. Describe the situation, the relationship dynamic, and the communication need without including client-identifying information. Most advisors apply similar judgment when speaking to colleagues about client situations; the same instinct applies here.

This is not about volume at the expense of quality. The advisors most at risk from a system like this are those who use it to increase the number of clients they're communicating with without increasing the care of each communication. The system is calibrated to produce fewer, better drafts — not more, cheaper ones.

---

From Touchpoint System to Relationship Operating Model

There is a meaningful difference between advisors who use Claude for one document type and advisors who have built a client relationship operating model.

The latter have: a context layer for each significant relationship, a template library for each document type, a quarterly rhythm that runs on a defined calendar, and a review discipline that ensures every Claude-assisted draft goes out with the advisor's judgment in it.

This operating model compounds in two ways. First, client communications become more consistent — not more uniform, but more reliably timely and high quality. Clients notice when they hear from their advisor after every meeting, after every market event, after every life development. That consistency is itself a form of value delivery. Second, the advisor's own time becomes more controllable. Communication overhead — which in many practices operates as an unpredictable, anxiety-inducing drain on the week — becomes a defined, manageable set of tasks.

The Leveraged Executive for Wealth Advisors is built around this operating model. It covers the full touchpoint stack — context layer design, prompt vaults for every major client communication type, the compliance-aware review framework, quarterly letter production workflows, and the transition from ad-hoc drafting to a system that makes client communication feel like a strength rather than an overhead.

Not sure which course fits your specific practice? Take the 6-question course selector.

You can review all available courses at The Leverage Years and find the path that fits where you are.

---

Decision rules: When to use Claude in client communication, and when not to

Use Claude for:

• Converting dictated or typed rough notes into structured post-meeting summaries
• Drafting quarterly letters from your market commentary plus client personalization notes
• Writing proactive check-in notes from brief bullet inputs
• Tightening the language in communication drafts you've already written
• Building and refining your prompt template library
• Drafting internal relationship status notes from meeting records

Do not use Claude for:

• The underlying financial advice or investment recommendation
• Any content that will be represented as your analysis without your substantive authorship
• Communications where compliance requires a specific pre-approval workflow that cannot incorporate AI-assisted drafts
• Situations where the client has expressed discomfort with AI-assisted communication
• Life event notes where the human calibration of what to say — and what to withhold — requires your direct judgment without a drafted scaffold

The judgment calls above are professional decisions, not technical ones. Apply the same standard you would apply to any other production tool in your practice.

---

Frequently asked questions

Is using Claude for client communication appropriate under advisor regulatory requirements?

Regulatory requirements for client communication vary by jurisdiction, firm, and registration type. Using Claude to assist in drafting does not change what your compliance obligations are — it changes the production time of the draft. The communication still goes through your normal review and approval process. That said, some firms have specific policies about AI-assisted content; check with your compliance department before building this into your workflow.

How do I protect client confidentiality when using Claude to draft communications?

The key discipline is the same one you apply when discussing client situations in any third-party context: describe the situation, relationship dynamic, and communication need without including identifying information. The client context layer in this system is specifically designed to contain no names, no account numbers, no portfolio specifics, and no personally identifying data. What you paste into Claude describes the communication challenge, not the client's financial details.

What if the draft doesn't capture the tone I use with a specific client?

This is the most common early calibration issue and the most easily addressed. The client context layer is where you document the communication register for that specific relationship. The more specific you are in the tone guidance — "warm, slightly informal, this client prefers directness and short sentences" — the closer the first draft will land. Over time, you will also build a set of prompt templates tuned to your own writing style, which reduces the revision needed on any given document.

How long does this system take to set up?

Writing context layers for your top fifteen to twenty relationships takes approximately three to four hours — about fifteen to twenty minutes each, done thoughtfully. Building an initial prompt template library for your five most common document types takes another two hours. After that, the ongoing maintenance is light: updating a context layer after a significant meeting, refining a template after it produces a draft that needed heavy revision.

Can junior advisors or client service associates use this same system?

Yes, and this is how the system scales. Your junior team can run the same prompt templates using the context layers you've built, producing first drafts that you review before sending. This preserves the quality standard and the advisor's voice while reducing the production burden on the principal. The context layer is the key to consistency across team members — it ensures that anyone running the workflow has the same background on the client relationship.

Does this system work during high-volatility periods when communication volume increases?

That is precisely when it is most valuable. During volatile markets, advisors who have a functioning touchpoint system can produce a high-quality, personalized check-in note for every significant client in a morning, rather than spending three days drafting while the moment passes. The templates are already built; the context layers are current; the workflow is a known quantity. Preparation during calm periods is what allows high-quality output during demanding ones.