The quote came in at $10,000. Six emails, one automation sequence, an agency that knew what they were doing. Not a scam — that’s genuinely what this work costs when you hire people with the right frameworks and the time to apply them properly.
I passed. Not because I didn’t want the result, but because I was already paying $200 a month for Claude, and I had a hunch the gap between “what an agency does” and “what I could do with the right prompt” had closed enough to be worth testing.
It had. The sequence is live, it’s beating the benchmarks, and the total additional cost was zero.
Here’s the exact workflow.
The Setup
I’m using Claude on the Max plan — Fable 5 when the task warrants it, which a copywriting project like this does. The model quality matters here; this isn’t a task where you want to cut corners on the underlying capability.
I also connected the beehiiv MCP, which lets Claude publish directly into beehiiv as draft automations rather than producing text I have to copy-paste across. If you’re not on beehiiv, or you don’t have the MCP set up, the workflow still produces clean, copy-ready email drafts — the MCP just removes the last manual step.
The One Move Most People Skip
Before I asked Claude to write a single word, I asked it a different question:
“What are good open rate and click-through rate benchmarks for an email sequence in the small business / IT space, targeting owners aged 35–55?”
It gave me specific numbers. I wrote them down.
This matters more than it sounds. If you ask an AI to write your emails and then ask it whether the emails are good, it will tell you they’re good. It wrote them. It has every incentive — structural, not intentional — to find them satisfactory. By setting the benchmark before any content exists, you’re giving yourself an independent standard to measure against after launch. Claude can’t retroactively adjust what “good” means to match what it produced.
A week in, we’re beating both numbers. But the point is I knew what I was measuring before I started, not after.
The Framework
The sequence itself is built on three frameworks: Russell Brunson for story and structure (origin story, epiphany bridge, big domino), Alex Hormozi for offer framing (value-first, Grand Slam Offer, transformation over features), and Dan Kennedy for the copy mechanics (specificity, urgency, PS lines that actually do work).
These aren’t obscure — they’re the frameworks that underpin most high-converting email sequences you’ve ever received without knowing it. What Claude can do is apply them consistently across six emails without the fatigue, drift, or “good enough” shortcuts that creep in when a human writer is on email four of six at the end of a long week.
The prompt I used, with placeholders you can adapt, is available free on the tools page. It covers the benchmark step, the sequence structure, what to ask Claude after the draft, and how to publish via the beehiiv MCP if you have it set up.
What the Sequence Looks Like
Six emails, each with a defined job:
- Welcome + Origin Story — who I am, what I had to overcome, why I do this. Ends with an open loop.
- The Problem Agitated — names the pain precisely, makes the cost of inaction concrete.
- The Epiphany — the one insight that reframes how they see the problem.
- Value Stack + Proof — specific results, transformations, evidence. Not features.
- The Offer — Grand Slam framing with a real deadline and a hard CTA.
- Last Chance — deadline reminder, personal PS, a lower-commitment fallback.
Claude produced all six, with subject lines, A/B alternatives, preview text, full body, and CTA copy for each. I reviewed, made minor edits to voice, and published.
The Broader Point
There’s an MCP for almost everything now. beehiiv. Facebook Ads. Your CRM. Most of the tools you’re already paying for have one, or will soon. The gap between “I need to hire someone for this” and “I can do this inside Claude” is closing fast for a specific category of work: tasks that require expertise to structure but not expertise to execute once the structure is clear.
Email sequence copywriting is a good example. The $10,000 quote was for the expertise — the frameworks, the sequencing logic, the copy mechanics. That expertise can now be encoded in a prompt. What’s left is the judgment: knowing your audience, reviewing the output, deciding what to publish.
That’s still your job. It’s just a much shorter one.
The prompt template is free to use on the tools page — copy it, adapt the placeholders, and run it in Claude. If you want help setting up the beehiiv MCP or building out a broader content automation workflow, get in touch.