03 — GOLDEN EXAMPLE: 1:1 Recap

Two goldens, both Rob. The 3-11-2026 email below is the standard for structure and voice (opener → wins → what we covered → action items → agenda → warm close). The 6-10-2026 email (added at the bottom, "Updated Standard") is the standard for editorial discipline — lean agenda, no procedural minutiae, member action items screened for live-and-executable, no progress-verdict close, member-track vs program-track separation. Read both. When they appear to conflict on the close, 6/10 wins: factual-warm is fine, progress-verdict is not.

Reference Email

The golden example for this kit is the recap email sent to Rob Foncannon after the March 11, 2026 1:1 session.

Subject: Meeting recap - 3-11-2026 Sent: 2026-03-12 Recipient: rob@foncannontax.com

The Email (As Sent)

Hi Rob,

Great to hear tax season is running ahead of last year and the team is locked in.

Here's the meeting recap from 3-11-2026.

Wins & Progress
- Revenue ahead of prior year
- Three January tax planning engagements closed (~$22,500 total)
- Wealth management transfers at $45K — ahead of pace toward $200K by June
- Daniel and Caitlin both thriving with strong work habits
- Google reviews system and website revisions progressing
- New investment advisor referral relationship established

What We Covered
1. Tax Season Status — ahead of last year, 1040s solid, corporates coming
2. Team Performance — Caitlin and Daniel both in a strong rhythm
3. Google Reviews & Website — system running; website links ready for your review
4. Advisory Conversations — ~5 scheduled, ~5 more being set up before filing
5. Wealth Management Transfers — $45K of $200K, on track for June
6. Monthly Recurring Revenue — reassessing in June; 8–10 conversions expected April/May
7. Tax Planning Pipeline — two large engagements ahead; post-season segmentation planned
8. Investment Advisor Relationship — referral structure and Christie positioning model
9. Post-Tax Season — visualization tool, advisory structure, client segmentation

Proposed Agenda for Next Meeting
- Advisory conversation results and conversions
- MRR update (April/May conversions)
- Wealth management transfer progress
- Website final review
- Tax planning visualization tool
- Advisory pricing/structure
- Investment advisor next steps
- Post-tax season client segmentation

Finish strong — you and the team are in a great spot!

Talk soon,
Kathryn

Note: Gmail auto-adds Kathryn's signature block. Do NOT include it in the draft.

What Makes This Example Good

Opening

"Great to hear tax season is running ahead of last year and the team is locked in."

• One sentence, factually specific to this call
• Acknowledges the energy without grading it
• No "great session" or generic opener

Wins & Progress

• Six bullets, factual
• Mix of metrics ($22,500 closed, $45K of $200K) and behavioral wins (Daniel and Caitlin thriving)
• No editorializing — just the facts
• Names spelled per reference data

What We Covered

• Numbered list, one line per topic
• Topic header + key point — never a paragraph
• 9 topics covered in 9 lines
• No sub-bullets

Proposed Agenda for Next Meeting

• Bullet list — terse phrases, not full sentences
• Action items folded in — Rob's open items show up here as agenda items
• Connects to the topics in "What We Covered"

Closing

"Finish strong — you and the team are in a great spot!"

• Short, specific to where Rob is in the season
• Factually encouraging — not motivational
• One exclamation point — used because Rob's email voice is warmer than other clients'

Sign-Off

Talk soon, Kathryn

Locked. Plus signature block.

The Ledger That Produced This Email (illustrative reconstruction)

The 3-11 recap predates the structural pass that introduced Step 5's Commitments / Decisions / Specifics Ledger. But to make the standard concrete, here's what the ledger would have looked like for this session — and how the email maps to it.

5.1 Commitments

5.2 Decisions

5.3 Closing-eligible specifics

This single specific anchored the close: "Finish strong — you and the team are in a great spot!" The close didn't generate warmth; it selected from the ledger.

5.4 New surfaced data

5.5 Calendar / next-session facts

(Pulled from calendar at the time — next session Wednesday, monthly cadence)

Why the reconstruction matters: Every assertion in the email — "Revenue ahead of prior year," "Three January tax planning engagements closed," "Daniel and Caitlin both thriving" — has a corresponding extracted fact. The composition step selected from these. Nothing was generated. That's the standard the ledger formalizes.

What's NOT in This Email and Why (negative space)

Equally important as what made it in: what the transcript surfaced that the recap correctly excluded. This is the negative-space golden example — the discipline of what to leave out is as much the standard as what to include.

The pattern: The email is shorter than the transcript by roughly 10x. Most of what was said is correctly excluded. The discipline is "what serves the engagement record" — not "what was discussed." This is what the ledger encodes structurally: most rows are tagged in ways that route them away from the email.

Failure modes the negative space prevents:

• Including everything as Action Items (over-attribution of commitment)
• Stating recommendations as decisions (over-attribution of resolution)
• Generating closings from "what felt warm" (fabrication)
• Including backstory the client already knows (signal/noise dilution)

Voice Patterns to Match

What's NOT in This Example (and shouldn't be)

• No separate "Action Items" section (folded into Proposed Agenda)
• No "Outstanding Items from Prior Sessions"
• No "Next Meeting" date line
• No JSON, no friction analysis, no embedded asks
• Rich text formatting — bold section headers, real bullet/numbered lists (not hyphens or markdown). Use htmlBody when creating the Gmail draft.

Note on action items: When a session has explicit named action items by owner (e.g., "Rob will send the X document by Friday, Kathryn will draft the Y template"), include a separate Action Items section grouped by owner — before the Proposed Agenda. The Rob 3-11 email folded items into the agenda because the items WERE the agenda. Use judgment per session.

Updated Standard — Rob 6-10-2026 (sent, Kathryn-edited)

This is the recap that went out after the 6/10 hands-on Claude deployment session, as Kathryn edited it before sending. The cascade's first draft was longer; Kathryn's edits are the editorial-discipline standard. Match these moves.

Subject: Meeting recap - 6-10-2026 Recipient: rob@foncannontax.com

Hi Rob,

We ran a full client-onboarding loop end to end on a live opportunity, and it produced a complete, client-ready package.

Here's the meeting recap from 6-10-2026.

Wins & Progress
- Ran your first full onboard-client loop live, start to finish — it produced a welcome email, an advisory roadmap (auto-branded to your colors), a pre-meeting agenda, a kickoff prep brief, goal-setting questions, and a client recap email
- onboard-client 2.0 skill loaded; your practice setup and voice reference files now live in a Claude project as your single source of truth
- Natalie's Claude Team onboarding booked for June 17
- Several advisory opportunities teed up — the client you met with today, plus more in the pipeline

What We Covered
1. Project setup — practice context + voice reference files loaded as your source of truth; update them in one place and everything downstream updates
2. One project per client — each chat only sees that project's data; rename chats to match their real purpose (e.g., planning the offer conversation, not "onboarding")
3. onboard-client 2.0 — replaced the previous skill file and ran it live on today's opportunity from your Otter transcript
4. Adding Natalie — she was missing from the practice context; added her role so she shows up in the team intro and the client-facing pieces
5. Voice input — talk it through; rambling is fine, it synthesizes and plays it back for you to confirm
6. Capturing calls — pull the raw transcript (not the summary) and label the speakers; getting Otter into all of your calls is key
7. Renewal — June is your renewal month; link coming in separate email
8. What's next in TPC builds — pre-meeting and post-meeting cascades, plus Claude co-work with Outlook for a morning and end-of-day briefing

Kathryn's Action Items
- Send your renewal link (with this recap)
- Put together the layer-one walkthrough — projects, chats, skills, and project instructions, and how they fit together — for you and Natalie
- Look into the cleanest way to capture phone calls (Otter on speaker vs. moving calls to Zoom)

Proposed Agenda for Next Meeting
- June 17 with Natalie — get her onboarded to Claude Team and set up a shared folder structure so you both pull from one place

Let me know if you have any questions!

Talk soon,
Kathryn

What Kathryn's edits teach (the discipline standard)

Why this is the standard — two artifacts, two jobs (this is the load-bearing point). The cascade's thoroughness is correct and necessary — but it belongs in the internal record (the .md: the full ledger, everything discussed and what each piece relates to, the backstory, takeaways, connections, both-session agendas). Keep that exhaustive — that's the value, and it's what Kathryn needs to hold the whole picture. The recap email is a different artifact: a client-facing projection of the record that carries only what was explicitly relevant to the conversation — no backstory, no internal threads, no program/cohort context, no how-to.

The edit is NOT "be less thorough." It's "route the completeness to the record, and send the client the relevant slice." Do not thin out the .md — thin out what gets projected into the email. When the first draft of the email reads like the record (carrying backstory, program context, every teed-up build, how-to steps, a verdict on how they're doing), that's the signal it's leaking record-content into a client artifact. Filter the email down to conversation-relevant only; the cut material stays in the .md, it doesn't disappear.