Email 1 — "the job you rebuild every year" · Wednesday 2026-07-29
Channel: MailerLite broadcast · Slot: in the wild · Engaged segment: 363 in Complete | Client Intelligence Brief Status: DRAFTED — awaiting Piper's review against the bar, then Kathryn. Nothing scheduled, nothing sent. Written by: Sloane (direct, in-thread — agent spawn hit a 529), 2026-07-29 Replaces: the invoice ("somewhere to look") and inbox ("inbox that stays empty") drafts as first send — both parked, payoff too small. This one has magnitude: recurring hours saved every year + a durable asset the reader owns.
Subject + preheader
Subject: the job you rebuild every year Preheader: You already did the work once. Keep it.
Register + structure matched to her 2026-07-06 send (the hour you can't bill / Plenty happened. They just couldn't see it.): subject names the recurring waste the reader feels; preheader turns it — you don't have to rebuild it.
Alts: 1) the task you dread every year 2) you'll do it from scratch again next year
Body
Hi {$name},
There's a job you do once a year and dread every time.
Maybe it's a big annual invoice, a renewal, a year-end summary — the one built from a dozen moving parts that eats hours before you've sent a thing.
You finally finish it.
You exhale, and you close the tab.
And you throw away the most valuable part.
Next year, you'll build the whole thing from scratch again.
You won't remember how you did it a year later.
Nobody does.
Here's the move I gave a business owner who was mid-dread on exactly this.
Before you close the tab, ask Claude to turn what you just did into a skill.
Not notes, not a document you'll never open — the actual steps, built so Claude can run the job with you next year, for this exact client and the way their version really works.
It takes a few minutes now, while the work is still in front of you.
Next year, you don't rebuild it. You run it.
And the year after that.
Do it once, and it pays you back every year you're in business.
So the next time you finish something you only do occasionally and hate doing — don't close the tab yet.
Hand it to Claude first.
— KathrynFormat = her 7/6 rhythm: one sentence per paragraph, blank line between each.
Why it clears the bar the last two failed
Bar: a reader finishes believing the tool gets them a real result.
- Magnitude. The payoff isn't a tidy inbox or a mail rule — it's hours of dreaded work you never repeat, every year, plus a durable thing you own. That compounds. It's the size of result that moves a practice owner.
- They can see it. The move is concrete and picturable: finish the thing you dread, and before you close the tab, have Claude turn it into a skill. Voice test #1 — can I see it in my head — passes, which is exactly where the inbox draft failed.
- Actionable this week without waiting for the annual task. The close generalizes: next time you finish anything you do occasionally and hate, hand it to Claude first.
- The AI does real work — builds a reusable skill from what you just did. Not a folder, not a filter.
Source trace — 7/24 Otter "Client Communication Strategies" (ZVh0w2dlleoVegk9ZX4kUBGmATg)
| Line | Source |
|---|---|
| a job you do once a year and dread | "I really dread doing this invoice" + invoiced once a year |
| built from a dozen moving parts, eats hours | "charging by time… by effort… by a lot of different mechanisms" + "huge amount of time to put together an invoice" |
| you'll build it from scratch again / won't remember | "you will not remember this this time next year" |
| ask Claude to turn what you just did into a skill | "ask Claude to help you create a skill, so you don't have to do as much of this" |
| the actual steps, run the job next year, this exact client | Claude offered generic-vs-specific; Kathryn: make it specific to this unique client |
| not a document — a skill | pre-AI was "create an SOP"; a skill = runnable steps Claude executes, not an SOP (standing rule) |
No number invented. The tape says "huge amount of time," not a specific before/after — so the email says "eats hours," never "2 hours → 15 minutes" (that was a brief framing, cut).
Clearance
Anonymized: "a business owner," no name, no profession, no identifying detail. This is Kathryn recounting a coaching move she made — her own action — not a client testimonial, so it's within bounds without separate permission. Vertical stripped: the example is a generic dreaded recurring task, not tax-specific.
QC (Sloane)
- copy-qc: No "not X — it's Y" twin (rewrote "not because you're disorganized — because…" out). "Not notes, not a document" collapsed to one line, not a three-beat. One dramatic beat ("Nobody does."). No mirror reversal.
- sentence-editor: openers vary; longest sentence one em-dash clause; every line advances.
- Banned sweep: no coach language, "walk through," "honest," "firm," "silent/quiet," SaaS jargon, hashtags. "skill" used correctly (runnable steps). Contractions throughout.
- Agreement test: subject (rebuild every year) / preheader (you can keep it) / payoff (turn it into a skill Claude reruns) — agree; preheader doesn't pre-spend the skill mechanic.
Piper reviews against the bar before this reaches Kathryn or the card.