ع
Learn Tracks Reference Guides Saved
playbook

Design an email nurture that earns the next step

Go from batch-and-blast to a designed lifecycle sequence — a journey map, an escalating arc, drafted copy in your voice, segmentation and branch logic, and a measurement plan — so every email earns the next instead of burning the list.

medium ~1 hour
when to reach for this

Most nurture is a batch-and-blast that treats a day-one signup like a sales-ready lead and torches the list. A lifecycle nurture is designed: the right message to the right segment at the right step, each email earning the next, with a measurement plan so you actually learn. You design it once with Claude in the Desktop chat — the journey, the sequence arc, the real copy, the branching, and what to measure — then it runs. No terminal needed.

gather this first
  • The goal of the sequence — activate a trial, nurture a lead to a demo, re-engage dormant contacts — and the single action each email should drive.
  • Who's in it: the segment(s), where they entered, and what they already know about you.
  • Your assets and constraints: the content and proof you can link (a case study, a guide, your messaging-framework.md), and what your sending tool can and can't do.
the workflow

  1. Map the journey before you write a single email

    Open the folder with your context in Claude Desktop and ask in the chat. Don't start with copy — start with the buyer's actual path, because the sequence is downstream of understanding it.

    you ask
    For this goal — [e.g. turn a free-trial signup into an activated user] — map the buyer's journey from entry to the action: what they feel, need, and object to at each step, and roughly how many emails it should take to get there. Don't write any copy yet.

    what you get back A journey map — the emotional and practical steps from entry to the goal — plus a recommended sequence length grounded in that path, not a default "five emails because everyone does five."

    This is the strategic step. A beautiful email in the wrong place in the journey still fails.

  2. Design the sequence arc

    Turn the journey into a skeleton: each email with one job, one angle, one CTA, and a send delay. One email, one job — the moment an email tries to do three things, it does none.

    you ask
    Design a [N]-email sequence for this journey. For each email give me: its single job, the angle, the asset or proof it leans on, the one CTA, and the send delay. Make the asks escalate — no email assumes a yes the previous one didn't earn.

    what you get back The sequence skeleton — jobs, angles, assets, CTAs, and timing — an escalating arc you can see end to end before any copy exists.

  3. Draft the emails in your voice and on message

    Now write them, all from the same voice and message so the sequence reads like one conversation, not seven strangers.

    you ask
    Using brand-voice.md and messaging-framework.md, draft all [N] emails: subject line, preview text, body, and one CTA each. Keep them short and value-first, and make each one build on the last — escalating toward the action, never assuming it.

    what you get back The full sequence drafted — consistent in voice and message, escalating in ask, each email short enough that someone actually reads it.

  4. Add the segmentation and branch logic

    A real nurture branches. Define who qualifies, what happens on click or conversion, and the suppression rules so you never email someone who already did the thing.

    you ask
    Add the logic: who qualifies for this sequence, what happens if someone clicks / converts / goes cold (branch, accelerate, or exit), and the suppression rules so we never email a contact who already converted or unsubscribed.

    what you get back The branching and segmentation plan — entry criteria, the if/then branches, and suppression rules — so the sequence behaves, not just sends.

  5. Build the measurement plan

    Close the loop. Decide what each email is judged on and the one number for the whole sequence, plus the first test worth running — a nurture you don't measure is one you can't improve.

    you ask
    Define what to measure per email (open, click, and conversion to the action) and the single number that tells me if the whole sequence works. Then propose the first A/B test worth running and what a win would look like.

    what you get back A measurement plan with a per-email and a sequence-level metric, plus a first A/B test — so next quarter's nurture is informed by this one's results.

    Pick one sequence-level number that maps to the goal. "Opens" feels good and proves nothing if no one takes the action.

make it your own
  • Re-engagement: point the same system at a dormant segment with a short "should we keep in touch?" arc — sometimes the win is a clean unsubscribe that improves deliverability.
  • Lifecycle, not just acquisition: the same method designs onboarding, adoption, and retention sequences — change the goal and the journey, keep the discipline.
  • Personalize at scale (Power Track): templatize the merge fields and branch logic as a reusable command so a new segment is a fill-in-the-blanks, not a rebuild (see the Features tab).
watch out for
  • Consent and compliance are not optional, and Claude doesn't clear you. Only email people who opted in, honor unsubscribes instantly, and keep the list in a tool your company approved. Claude drafts copy; you own GDPR / CAN-SPAM / PDPL compliance.
  • Don't let Claude invent the offer or the proof — link real assets. A nurture full of unbacked claims converts no one and creates risk you'll answer for.
  • Escalate, don't assume. The classic failure is email two writing as if the reader already said yes to email one. Each step earns the next; it doesn't presume it.
  • Personalization is only as clean as your data. A wrong merge field — "Hi [FNAME]" — undoes the whole effect in one line. Verify the data before the send, every time.

you'll end up with A designed lifecycle sequence — a journey map, an escalating arc, drafted copy in your voice and on message, segmentation and branch logic, and a measurement plan — that earns each next step instead of blasting the list.

Questions people ask

Does this handle the actual sending and compliance?
No. Claude designs the sequence and drafts the copy; you own the sending. That means consent (only emailing people who opted in), honoring unsubscribes instantly, keeping the list in a tool your company has approved, and meeting GDPR / CAN-SPAM / PDPL. The playbook makes the emails; it does not make you compliant.
How many emails should the sequence be?
However many the journey needs — which is exactly what step one decides. The sequence length comes out of mapping the buyer's path from entry to the goal, not from a default. A focused three-email arc that respects the journey beats a padded seven-email one that doesn't.
Can it reuse my brand voice and messaging?
Yes, and it should. Feed in `brand-voice.md` (from the brand-voice playbook) and `messaging-framework.md` (from the messaging-framework playbook), and the whole sequence stays on-voice and on-message instead of drifting email to email. That consistency is part of what makes a nurture feel like one conversation.
What about re-engaging contacts who've gone cold?
Use the re-engagement variation — point the same system at a dormant segment with a short "should we keep in touch?" arc. Sometimes the right outcome is a clean unsubscribe: pruning people who'll never re-engage actually improves your deliverability to the ones who will.