Claude Project: Your Persistent Insurance Planning AI Assistant

What This Builds

A Claude Project — a persistent AI workspace that already knows your practice, your compliance language, your most-used products, and your writing style — before you type a single word. Unlike standard Claude conversations that forget everything when you close the tab, Projects retain your context permanently. Every time you open your practice assistant, it's already briefed. This is the highest-leverage AI setup an insurance financial planner can build — a knowledgeable, always-available assistant that drafts, analyzes, and explains in your established voice.

Prerequisites

• Claude Pro subscription ({{tool:Claude.price}}/month) — Projects require Pro — Sign up
• 30 minutes to gather materials before building
• 3–5 examples of your best written work (suitability narratives, client letters, product summaries)
• A list of products you commonly recommend with key specs

The Concept

A Claude Project is like a dedicated filing cabinet that Claude can always access — combined with an always-on briefing document that tells Claude exactly who you are and how you work. Every conversation you start inside the Project begins with Claude fully aware of your practice context, your language preferences, and your compliance requirements.

Think of it as the difference between calling a temp agency for a new typist every day vs. having a long-term assistant who already knows your style after week one.

Build It Step by Step

Part 1: Gather your materials (30 minutes)

Collect the following in text or Word format:

1. Your practice brief (write this fresh — 1 page): Describe your practice in your own words:

• What types of clients you work with (age range, financial situation, primary concern)
• Products you most commonly recommend (FIA, MYGA, IUL — with key specs for each)
• Your compliance obligations (Reg BI, state best-interest standards)
• How you like documents structured (tone, length, sections you always include)
• Any language your IMO or broker-dealer requires in suitability documents

2. Your best example documents (3–5 files):

• 2 suitability narratives (anonymized)
• 1–2 replacement analyses (anonymized)
• 1 client summary letter

3. A product reference sheet: Create a simple one-page sheet listing your top 5–8 products with:

• Product name and carrier
• Product type (FIA, MYGA, IUL)
• Surrender period
• Key income rider details (if applicable)
• AM Best rating
• Why you recommend it

Part 2: Create the Claude Project (30 minutes)

1. Go to claude.ai and log in with your Pro account
2. In the left sidebar, click Projects → New Project
3. Name it: "Insurance Planning Practice" (or your firm name)

Step 2a: Write the Project instructions Click Edit project instructions (or the settings icon). Paste your practice brief here — this is the persistent context Claude reads at the start of every conversation in this project.

A strong instructions section for an insurance financial planner looks like:

You are a specialized AI assistant for [your name], an insurance financial planner who focuses on retirement income planning using fixed indexed annuities, multi-year guaranteed annuities, and life insurance cash value strategies.

About the practice:
- Clients are typically age 55–72, within 5 years of retirement or recently retired
- Common concern: running out of money, outliving income, market risk near retirement
- Primary products: [list your 3-4 most common products with key specs]
- Compliance obligations: Reg BI (if applicable), [state] best-interest standard
- IMO/firm: [name if relevant]

Your role in this project:
1. Draft compliance documentation (suitability narratives, replacement analyses) — always first drafts for advisor review
2. Write client communications (letters, emails, follow-ups) — warm, plain language
3. Analyze product documents and contracts — extract key terms and client-relevant summaries
4. Create sales and education content (seminar outlines, objection responses, FAQs)
5. Prepare meeting agendas and talking points

Writing style:
- Suitability documents: professional, third-person, structured with clear sections
- Client communications: warm, plain language, second-person ("you", "your")
- Education content: accessible, analogy-based, no unexplained jargon
- Length: thorough but not padded — every sentence should earn its place

Compliance reminders (include in relevant outputs):
- Always note that suitability documents are first drafts for advisor review
- Never guarantee specific financial outcomes
- Never make representations beyond what the advisor provides
- Use "the client" or first name only — no full names or sensitive identifiers in outputs

[Add any specific required compliance language from your IMO or firm here]

Step 2b: Upload your knowledge files Click Add content in the Project panel. Upload:

• Your practice brief (from Part 1)
• Your anonymized example documents
• Your product reference sheet

What you should see: Your uploaded files listed in the Project panel with green checkmarks.

Part 3: Test your Project assistant (30 minutes)

1. Start a new conversation within your Project (click New conversation in the Project view — not the general Claude chat)
2. Test it with a real pending case: type just the client's details and product details, nothing else
3. Ask: "Draft a suitability narrative for this client"

What good looks like: Claude produces a document that uses your required structure, references your stated compliance obligations, and mirrors the tone of your uploaded examples — without you needing to explain any of it.

Common refinements:

• If Claude ignores your required sections: make the section headings explicit in your instructions ("Always include these 4 sections: 1) Client Profile, 2) Client Objectives, 3) Product Suitability Rationale, 4) Conclusion")
• If the tone feels wrong: add one of your best letters to the knowledge files so Claude can reference your actual voice
• If product specs aren't being used: make your product reference sheet more prominent in the knowledge section

Real Example: A Monday Morning With Your Project

Setup: Your "Insurance Planning Practice" Project has been running for 2 weeks. You have 3 cases pending.

9:00 AM — Case 1: Barbara Kim, new FIA recommendation You open your Project and type:

Barbara Kim, 66, widowed, $210K in a brokerage account she's tired of worrying about. SS income $1,650/month, expenses $2,400/month, $750/month gap. Conservative. Wants income in 7 years. Recommending [your FIA product], 10-year surrender, 6.8% income rollup.

Draft suitability narrative.

Claude produces the full narrative in 45 seconds, already structured in your established format.

9:20 AM — Case 2: Product question from new prospect You type:

Prospect is asking: "How is a fixed indexed annuity different from putting money in the stock market?" Write a clear email response appropriate for a 63-year-old with moderate financial literacy.

Claude drafts the email in your voice — because it's already read your examples.

9:35 AM — Case 3: Replacement analysis You paste the old and new contract details. Claude produces the replacement narrative in 90 seconds.

Total time for 3 documentation tasks: 20 minutes, vs. 2+ hours manually.

What to Do When It Breaks

• Claude forgets your context → Make sure you're opening conversations inside the Project (via the Project panel), not starting general Claude conversations. The project instructions only apply inside the Project.
• Output doesn't match your style → Add more of your example documents to the knowledge files. The more Claude has read of your actual writing, the better the style match.
• Product specs are wrong → Don't rely on Claude to know product details — always provide exact specs in your prompt. Your product reference sheet is a starting point, not a substitute for current product data.
• Knowledge file limit reached → Claude Projects have a context limit. If you've added many files, prioritize: instructions + 2 example docs + product sheet. Remove less-used files.
• Subscription lapses → Project content is saved but dormant. Renewing Pro restores full access — nothing is deleted.

Variations

• Simpler version: Use Claude's free tier without Projects — start every conversation by pasting your standard context block (practice description + current case). Less convenient but same output quality.
• Extended version: Create a second Project specifically for client education content — loaded with your seminar materials, FAQ library, and product explainers. Use it to generate newsletters, social posts, and email sequences without compliance context bleeding in.

What to Do Next

• This week: Build the Project using your practice brief and 3 example documents. Run 5 real cases through it.
• This month: Add your product reference sheet; refine instructions based on what Claude gets wrong; add your best new examples as the quality bar rises.
• Advanced: Build a separate Project for business development content (seminar copy, emails, LinkedIn posts) with a different persona and style guide than your compliance writing project.

Advanced guide for Insurance Financial Planner professionals. Claude Projects require a Claude Pro subscription.