Build an Automated Lead Nurture Sequence

You'll end up with: A 5-email nurture sequence that warms leads from signup to sales call

Overview
30-40 min
Intermediate
Free to start
2 tools
Common mistake

Treating each email as a standalone pitch. Nurture works when mail n + 1 references the idea in mail n and moves one belief forward (problem → mechanism → proof → risk reversal → call). If every email "sells the call," trust collapses.

Before you start
  • One clear signup source (lead magnet, waitlist, or webinar)
  • One primary conversion (book a discovery call)
  • Access to an ESP (Mailchimp, Kit, etc.) even on free tier
  • Claude open in the browser
1

Define the arc, cadence, and one CTA per email

Lock who opted in, entry belief, and send cadence so every later email stays consistent.

Claude.aiFreeOpen Claude.ai
Exact action

1. Open Claude (claude.ai) and start a **new chat**. You will reuse this same chat for Steps 2–6. 2. Paste this prompt (fill the bracketed bits briefly): --- I'm building a 5-email nurture sequence for solopreneurs. Context: [what they downloaded / signed up for]. My primary conversion is booking a **discovery call**. Generate: (a) One-line description of who just joined the list and what they believe right now. (b) Five send offsets from signup (e.g. Day 0, 2, 4, 7, 10) that are simple to automate — keep total workflow friendly for a 30–40 minute session. (c) One sentence: the **single transformation** they should feel ready for by Email 5 (leading to booking a call). (d) A markdown **table** with 5 rows (Email 1 … Email 5) and columns: Goal | **One primary CTA** | What **not** to do on that email (e.g. don't pitch the call in Email 1). Important: **Reserve "book a discovery call" for Email 5 only.** Emails 1–4 should use lighter CTAs (consume the lead magnet, reply, read a case, reflect). If my lead magnet is **video** vs **PDF**, note one sentence on how Email 1's opening should differ. --- 3. Read the table. Edit in chat until each row has a **different** CTA and Email 5 is the only "book a call" row.

You have a 5-row table (Emails 1–5) with **non-repeating CTAs** — e.g. consume resource / reply / read case / soft question / **book a call** on Email 5 only.
If every row says "book a call" or the same CTA, reply in the same chat: "Reserve book-a-call for Email 5 only. Assign lighter CTAs to Emails 1–4 and regenerate the table."
2

Email 1: Welcome and set expectations

Deliver the lead magnet, set tone, and preview what Email 2 will cover — no hard pitch.

Claude.aiFreeOpen Claude.ai
Exact action

1. In the **same Claude chat** from Step 1, paste: --- Using the table from above, draft **Email 1 only** (welcome + expectation-setting). Output: - **2 subject line options** (clear, human, under ~60 characters) - **Preview text** (the inbox snippet, ~35–50 characters) - **Body** as short **outline bullets** only (not full prose): greeting → deliver the lead magnet / confirm access → why you're emailing → what Email 2 will cover → **one light CTA** (consume asset, hit reply, or confirm receipt — **not** book a call) - Optional **P.S.** if it adds warmth Keep the whole Email 1 package concise enough to scan on one screen. --- 2. If the draft pitches your call, ask Claude to remove the pitch and keep CTAs to "consume / confirm / reply" only.

Subject + preview + bullets fit on **one screen**; **no** hard sell; CTA is consume, confirm, or reply — not book a call.
If Email 1 feels like a sales letter, reply: "Rewrite Email 1 as welcome + expectation only. Remove booking language. Keep one light CTA."
3

Email 2: Teach the real problem (mechanism)

Move from thanks to **why** their problem persists — one framework, one question, no call pitch.

Claude.aiFreeOpen Claude.ai
Exact action

1. In the same chat, paste: --- Draft **Email 2** to follow Email 1. Requirements: - Open with a **callback** to a specific promise or phrase from Email 1's outline. - Teach **one mechanism**: why their situation is stuck (one framework or metaphor — not three ideas). - End with **one question** that prompts reflection or a reply. - **CTA:** point to a helpful resource (your article, short video, or doc) **or** ask them to reply — **not** book a call. Give: 2 subject options, preview text, bullet outline for the body. --- 2. Check that the opening line explicitly references Email 1.

Email 2 opens with a **callback** to Email 1; the body develops **one** core idea; CTA is read/watch/reply — still not book a call.
If the email packs multiple frameworks or sneaks in a booking link, reply: "One mechanism only. Remove booking CTA. Tie the opening directly to Email 1."
4

Email 3: Proof with a story or mini case

Show evidence before you ask for time — specifics beat superlatives.

Claude.aiFreeOpen Claude.ai
Exact action

1. In the same chat, paste: --- Draft **Email 3** as **proof**. Include a **before/after** or anonymized client vignette with **concrete detail**: timeline, constraint, or a number — avoid vague "great results." Output: 2 subject options, preview text, bullet outline. - **CTA:** invite them to read/skim proof (case summary, one-pager) — **still not** book a call. --- 2. Count specifics: you want **at least three** concrete details in the story arc.

The story includes **at least three** concrete specifics (numbers, constraints, or named steps); it reads like evidence, not hype.
If the "case study" is all adjectives, reply: "Rewrite with three concrete facts (timeline, metric, or constraint). Remove unsubstantiated claims."
5

Email 4: Handle one objection

Pre-handle time, fit, or DIY objections so the call invite in Email 5 feels safe.

Claude.aiFreeOpen Claude.ai
Exact action

1. In the same chat, paste: --- Draft **Email 4** to address **one** common objection for this audience (pick **one**: time, fit/skepticism, or "I'll DIY it"). Use a short **FAQ** tone — acknowledge who this **isn't** for as well as who it's for (builds trust). Output: 2 subject options, preview text, bullet outline. - **CTA:** soft — invite a reply with their concern **or** click a short FAQ/resource — **bridge** to Email 5 without booking yet. --- 2. Confirm only **one** objection theme; don't stack four FAQs.

It's clear **who should not book** as well as who should; one objection theme; CTA stays soft — **no** direct book-a-call button yet.
If the email feels defensive or lists many objections, reply: "Pick one objection only. Shorten. Keep CTA to reply or light resource."
6

Email 5: Invite to the call and assemble your sequence

One booking CTA, then consolidate all five emails and cadence into one implementation doc.

Claude.ai + Google DocsFreeOpen Claude.ai + Google Docs
Exact action

1. In the same chat, paste: --- Draft **Email 5** — the **only** email with a **direct CTA to book a discovery call**. Include: - 2 subject line options - Preview text - Bullet outline: what happens on the call, who it's for, **single booking CTA** - Optional P.S. with one proof point Use **real urgency** only if you have a real deadline (e.g. limited spots this month). Skip fake scarcity. --- 2. Open **Google Docs** (docs.google.com). Create a doc titled: `Lead nurture — [your offer name]`. 3. Paste into the doc **in order**: - Your **cadence table** from Step 1 (offsets + goals + CTAs) - For Emails **1–5**: subject options, preview text, and bullet outlines from this chat 4. Optional: copy the same block into your ESP (Kit, Mailchimp, ActiveCampaign, etc.) as **drafts** — scheduling automation is outside this guide. 5. Keep Email 5's outline as the **only** step that asks for the call.

One doc (or ESP draft folder) holds **cadence + Emails 1–5**; Email 5 has **exactly one** primary booking CTA.
If booking CTAs appear earlier than Email 5, fix the outlines in the doc so **only Email 5** closes for the call.

All done!

You now have: A 5-email nurture sequence that warms leads from signup to sales call

Explore more guides

Want this workflow built for your business?

Book a free audit