A Nurture Email Sequence That Writes Itself
Design a full nurture sequence — every email, the timing, the branching, and the exit — in your voice and tied to one clear outcome, instead of three emails and good intentions.
A sequence is one argument told over time — not five unrelated emails that happen to share a list.
Most 'sequences' are a welcome email and two follow-ups someone wrote in a hurry. A real one moves a reader from where they are to one decision, with each email earning the next. Store your voice and the outcome, and the whole arc gets designed at once.
Disconnected emails sent on a timer aren't nurture — they're noise on a schedule, and the unsubscribe link is right there.
Every email in a sequence should move the reader one step toward a single decision. If it doesn't, it shouldn't be in the sequence.
Draft the whole arc, then cut. A tight four-email sequence that builds beats a seven-email one that pads.
| Complexity | Easy |
| Tools needed | Claude Pro or above, Claude Desktop → Cowork mode, on macOS or Windows, Claude Projects |
| Time to build | ~25 min first time · ~10 min per sequence after that |
| Best for | Owner or marketing lead who writes their own email — B2B services and SaaS |
What this solves
Sequences built one email at a time — a strong welcome, a weaker follow-up, then filler — because nobody designed the arc before the writing started.
The problem
You know nurture sequences work, so you sit down to build one and write a decent welcome email. Then the second one is harder, the third feels like filler, and by the fourth you’re padding to hit a number you picked arbitrarily. The sequence ships, but it reads like five separate emails rather than one story, and readers drop off because nothing pulls them to the next one. The problem isn’t the writing — each email is fine. It’s that the arc was never designed. Nobody decided what the whole sequence was supposed to move someone toward, or how each email earns the open after it.
The fix is designing the whole arc first, then writing to it.
Ingredients
- Claude Subscriptions — Cowork and Projects aren't available on the free plan
- Platforms & Modes — Cowork runs in the desktop app only — not on web or mobile. This recipe designs an arc and drafts every email — multi-step work across files
- Claude Projects — Your voice, your audience, and your offer are constant across sequences. A Project stores them so every flow sounds like you and points at the right outcome
How it works
You build sequences for different purposes — onboarding, nurture, re-engagement — but your voice and audience stay the same. A Project stores them so every sequence sounds like you and you’re designing the arc, not reinventing your tone each time.
- Open Claude Desktop and click Cowork in the mode selector across the top (Chat · Cowork · Code).
- In the left panel, find Projects and click the + button.
- Choose Start from scratch. Name the project “Email Sequences” and let Claude set up its folder.
- You’ll know it worked when the project appears in the left panel with its own folder and an instructions field.
Your project has a folder on your computer — that’s where the two working files live.
- Ask Claude, right in the project: “Create two files in this project’s folder:
voice.mdandaudience.md. Leave them empty — I’ll fill them in.” (Or create them yourself in any text editor and save them into the project folder.) - Fill in both files using the descriptions below.
- Confirm Claude can see them: ask “List the files you can see in this project.” Both filenames should come back. If they don’t, see If It Doesn’t Work.
voice.md
How you write email — length, tone, how you open and close, what you never do. This keeps every email in the sequence sounding like one person, not a brand committee.
Example: “Short. One idea per email. No ‘Hope you’re well.’ Subject lines are specific, not clever. Plain sign-off. Never more than one CTA.”
audience.md
Who’s on the receiving end and where they are when the sequence starts — so the arc meets them where they are and moves them somewhere specific.
Example: “New trial signups who haven’t activated. They’re curious but busy, skeptical of being sold to. Goal of the sequence: get them to complete the one setup step that makes the product click.”
Open your Project in Claude Cowork. Give Claude the specifics for this run, ask for the main output, then follow up for any additional pieces you want. The exact wording for each prompt — with what it’s asking for and why — is in What you actually type below.
Check three things before this goes into your email tool:
- Each email has a distinct job. Read the one-line purpose of each. If two emails do the same thing, one should be cut, not kept for length. A shorter sequence that builds beats a padded one that repeats.
- There’s a real exit condition. A sequence that keeps emailing someone after they’ve already converted is how you earn an unsubscribe. Confirm there’s a clear stop — they activate, they reply, they buy — and the flow respects it.
- It sounds like you, not “marketing.” Run every email against your voice file. The moment one slides into hype or filler openers, the whole sequence reads automated. Tighten the voice file if a pattern slips through. (See the brand-voice recipe.)
Before you load it in: does the arc match how your buyers actually decide? If the real blocker to activation is confusion, not motivation, the sequence should teach, not cheerlead. Your knowledge of the audience corrects what the draft assumes.
What you actually type
Name your files explicitly the first few runs, and ask Claude to show its work on anything that matters.
“Design a nurture sequence for new trial users who haven't activated, using `voice.md` and `audience.md`. The one outcome: they complete first setup. Give me the full arc — how many emails, what each one's job is, the timing between them, and an exit condition when they activate. Then draft every email in my voice, with subject lines.”
“Email 3 repeats email 2's point — give it a distinct job or cut it.”
“Add a branch: if they open but don't click by email 3, the next one leads with a different angle.”
A sequence design plus full drafts: the arc first (how many emails, each one's one-line job, the timing between them, and the exit condition when the reader converts), then every email written in your voice with a subject line. Each email should read as one step in a single argument, not a standalone blast. If two emails do the same job, the exit is missing, or a draft slides into marketing-speak, it missed — send it back.
- It doesn't send anything. The sequence still has to be loaded into your email platform, with the timing and any branching rebuilt there.
- It can't see your open or click data. Which subject lines work and where readers drop off is something only your platform's reports can tell you.
- It designs to the audience you describe. If `audience.md` guesses wrong about why people stall, the arc will cheerlead when it should teach.
If it doesn’t work
- No Cowork tab in Claude Desktop — update the app to the latest version and confirm you’re on a paid plan; Cowork isn’t on the free tier. On Windows, Cowork also needs the Virtual Machine Platform feature enabled — if the tab still won’t appear, that’s the fix.
- Claude can’t see
voice.mdoraudience.md— the files aren’t in the project’s folder, or they’re in a different folder than the one the project owns. Open the project, check which folder it points to, and move the files there. Then re-run “list the files you can see.” - The emails repeat each other — the arc never got pinned down before drafting. Ask for the structure alone first: “List each email’s job in one line — if two match, cut one.” Approve the arc, then ask for the copy. A padded sequence reads as nagging by email three.
- The drafts sound like “marketing,” not you — your
voice.mddescribes a tone instead of setting rules. Replace adjectives with prohibitions (“no ‘Hope you’re well,’” “one CTA, never two”) and run it again. Claude follows rules more reliably than vibes.
Extra credit
Small additions that pay back the next time you run it.
- Email platform connector — connect your email tool so Claude can help load the sequence, or export it in the format your platform imports. See the Connectors guide.
- A/B the openers — ask for two subject-line and first-line variants per email to test, keeping the body constant.
- Reuse the skeleton — once one sequence works, ask Claude to adapt its arc for a re-engagement or win-back flow, keeping the voice and structure.
“A sequence works when each email makes the next one worth opening.”
What this teaches you about Claude Cowork
The recipe is one application. The principles apply to everything you’d hand to Claude.
Design the arc before the copy. Sequences fail at the structure level, not the sentence level. Having Claude lay out the whole arc — each email’s job, the timing, the exit — first is what makes the individual emails write themselves, because each one finally knows what it’s for.
The exit condition is a courtesy that protects results. A flow that keeps sending after the goal is met trains people to unsubscribe. Building the stop in is the difference between nurture and nagging — and stored audience context is what defines when to stop.
One voice across many emails. A sequence is where inconsistent voice shows most, because readers see several in a row. Storing the voice once keeps all of them sounding like the same human, which is what keeps people opening.
Who this is for
Owner or marketing lead who writes their own email in B2B services and SaaS (2–50 employees).
The pain: Sequences that read as disconnected blasts because the arc was never designed
The outcome: Every flow ships with a designed arc, a clear exit, and one consistent voice
Published June 18, 2026 · 0 views