How to write a lead nurture email sequence
Learn to write a lead nurture email sequence for opted-in contacts. Set one goal, plan timing and stop rules, then draft and review each email.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What a lead nurture email sequence is
A lead nurture email sequence is a planned series of messages that helps an opted-in group take a specific next step. People who request a buying guide and opt in to follow-up could receive emails that help them use the guide, answer a buying question, and decide whether to book a demo.
A drip campaign sends messages at intervals after the person enters. To plan one, decide who qualifies, what each email helps them do, and how much time they need between messages. Hand off the drafts with a schedule measured from entry and stop rules that cover actions such as an early booking, a reply, or an unsubscribe.
What it does for the business
- Give leads a reason to take the next stepUse each email to answer a question the reader is likely to face after signing up. Someone who knows what a demo covers can decide whether to book it and bring the questions they want answered.
- Protect work already underwayA clear stop rule lets the person who handles replies or bookings take over. They can continue the conversation without a scheduled email repeating the request.
- Make campaign setup easier to reviewA colleague can compare the settings in your email tool with the agreed schedule and rules. The same records help the team revise the campaign when an offer or audience changes.
- Learn which messages deserve workCollect signals that tell you where readers get stuck. If replies keep asking about the same topic, you can revise the email or update the guide it links to.
How to build a lead nurture email sequence, step by step
Define the group, entry event, and goal
Every sequence starts with a documented reason the reader expects to hear from you.
What to do
- Pick one segment, a group of people with the same reason for receiving the emails. Read the current signup page and consent language to confirm who agreed to follow-up and where the record of that choice lives.
- Name your entry trigger, the event that starts the clock. For a guide campaign, use a recorded guide request with follow-up permission. Identify the field or event your team can use to verify both conditions.
- Name the event you want to accomplish. If the goal is a booked demo, use the confirmed booking event. Save link clicks as a separate signal you can use to understand interest.
- Collect the current offer, audience brief, and sources for claims you may use. Record where you found each fact and the passage that supports it. Flag missing details about the sender or offer before writing.
Why
A recognizable entry event gives the first email a natural opening and makes the schedule testable. A specific goal gives the team a reliable reason to end the sequence early.
Map the timing and stop rules
A send delay is useful only when everyone knows when its clock starts.
What to do
- Give each email a job. In a guide campaign, one message might help readers use the guide, another might address a question that comes up during comparison, and a third might explain what to bring to a demo.
- Set the email cadence, the spacing of messages, from one entry event. A plan with offsets of zero, three, and seven days puts the last email seven days after the request. Label the units in every row.
- Decide whether sends use elapsed time or need a local send window. If local time matters, record the time zone and what happens when a message becomes due outside the allowed window.
- Write eligibility and suppression rules, which keep contacts out when they meet specified conditions. Define how duplicate requests are handled, then check for a goal, reply, unsubscribe, complaint, or hard bounce before each email. A hard bounce means the address rejected delivery permanently.
Why
Gaps between emails are easy to mistake for delays from entry. A second request can restart a finished series if the rules leave out suppression. The map gives the campaign owner a way to check both errors.
Draft complete emails with one main action each
The reader should understand each email even if they skipped the last one.
What to do
- Write two subject lines that accurately describe what the email offers. Write preview text, the short inbox snippet beside the subject, that adds a specific detail the subject leaves out.
- Open with enough context for someone who missed the previous email. Put the reader's next task in plain language. If you link to the guide, say which section helps them with that task and verify that it is there.
- Choose one primary call to action, the action the message asks the reader to take. Make the wording specific to the destination. If your link opens a booking calendar, tell the reader they can choose a demo time.
- Use only personalization you can verify, such as a first name with a greeting that also works when that field is empty. Mark missing sender details, field syntax, and unsubscribe setup for the person who configures the campaign.
Why
People may open messages in a different order from the one on your map. Self-contained copy lets them act on the email they see. Accurate subjects, checked offer details, and a clear next action help the reader decide whether the message is relevant.
Test the rules on individual contact paths
Walk through the event that should stop each future email.
What to do
- Walk through an eligible subscriber from the entry event to the final send. Use the actual offsets and any local send window, then compare every planned time with the schedule you intend to set.
- Put a confirmed booking before a later email in the schedule and check that it ends the series. Repeat the check with a reply before the next step.
- Walk through an unsubscribe and a second guide request from the same person. Confirm that the second request leaves the suppression rule in force. Also check the rules for complaints and permanent delivery failures.
- Record what the examples establish about the sequence logic. Separately list what you can observe after launch, such as confirmed bookings, replies and unsubscribes, and note which copy choices still need evidence from readers.
Why
Walking through planned send times exposes gaps while you can make changes on paper. The person configuring the campaign can repeat those cases before activating it.
Review the copy and hand off the specification
A handoff is ready when another person can check the copy and reproduce every send decision.
What to do
- Record the draft versions and write a checklist before reviewing. Match each claim to its source, then read the subjects, preview and body together. Check that they describe the same offer and action.
- Verify that each message's timing matches the schedule and that the stop rules match your worked paths. Read the personalization with sample fields filled and blank so you can catch missing greetings or stray placeholders.
- List open setup decisions and give each a person to resolve it. Include decisions about the sender, unsubscribe handling, links, field names, and how the goal event reaches the email tool.
- Hand off the brief, email drafts, schedule, rules, and review findings together. Flag any material issue that still needs a fix so the person configuring the series knows which decisions are pending.
Why
The copy and timing have to agree. If a message mentions an upcoming deadline, the reviewer can check that claim against the source and the planned send window.
Common mistakes
- Treating a guide request as permissionVerify that the signup actually captures permission for follow-up before adding the contact.
- Using the previous email as the clockRecord each delay from entry so the schedule can be reproduced even when an intermediate email is skipped.
- Counting a calendar click as a bookingUse a confirmed booking to measure the goal and decide when to end the sequence.
- Assuming the reader saw the earlier emailsGive each email the context the reader needs to understand the action it asks them to take.
- Leaving exit checks until the endCheck for stops before every send so replies, bookings, and delivery or permission changes take effect in time.
What a good result looks like
- One documented group with a known permission source, entry event, and goal event.
- A schedule with a purpose, delay and unit for each email, plus any local send rules.
- Complete drafts with two honest subjects, preview text, one main action, and a signature.
- Worked examples for normal progression, early goal completion, a reply, and an unsubscribe.
- Sources for claims, safe personalization fallbacks, and a list of unresolved setup details.
And then what? Using the result
- Give the specification to the person configuring your email tool and resolve the open sender and field settings together.
- Test with internal addresses and compare the scheduled times and stopped messages with the worked examples.
- Assign someone to review replies and tell them where to record questions that may call for a copy change.
- After launch, review confirmed goal events, replies, and unsubscribes. Use what you observe to decide whether to revise a message, its timing, or the audience rules.
When to run it
- A guide draws opted-in readers who need follow-upA short sequence can help readers apply what they downloaded and decide whether a conversation would help.
- A trial has a clear setup milestoneUse the series to help people reach that milestone and end it once the completion event arrives.
- Several teams send overlapping follow-upMap the entry and stop events so each owner can see when an automated series should give way to a reply or booking.
Questions people ask
How do you write a lead nurture email sequence?
Define one opted-in group, one entry event and one goal, then map the timing, draft each email and test the stop rules. Check the copy against your current sources.
How many nurture emails should you write?
Start with three to five if each message has a distinct job. Cut any message that repeats the same request without adding something the reader can use.
How far apart should you send nurture emails?
Space the emails around the time the reader needs for each step. A guide may be useful immediately, while a follow-up that refers to a section of it should give the reader time to use it.
What should trigger a lead nurture email sequence?
Use a specific, recorded event that qualifies a contact with documented permission, such as an opted-in guide request. Record the event your team can actually find in its systems.
When should you stop a drip campaign for a contact?
Stop when the contact reaches the goal, replies, unsubscribes, registers a complaint, or has a hard bounce. Check for those events before sending each remaining email.
What should a nurture email say if the first name is missing?
Use a greeting that reads naturally without a name, such as "Hello". Check the rendered message with the first-name field empty before enabling the campaign.
More jobs in Marketing
Write a lead nurture email sequence, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac