How to Build an Email Nurture Sequence From Scratch
How to build an email nurture sequence: settle the trigger, destination and exits first, then give each of a few emails one job. A plain, linear path to follow.
To build an email nurture sequence, decide the trigger, the destination and the exits first, then write a short, linear run of emails where each one has a single job and a single call to action. The writing is the easy part. The decisions around it are what separate a sequence that produces deals from one that produces email.
This is the whole path at overview level, from the first decision to the monthly review. Where a step deserves its own treatment, there is a link to the post that goes deeper, so you can read this one straight through and dip into the others when you reach the step you are stuck on.
How to build an email nurture sequence: spend the first afternoon deciding
Before you write a word, settle five things. They take an afternoon, and they determine whether the finished sequence helps the reader or harasses them.
| Decision | What you write down | The trap it avoids |
|---|---|---|
| Entry trigger | An event, such as submitting a specific form | A vague description of a person, which forces you to write for everyone |
| Exclusions | Who is kept out even if they trigger it | Pitching existing customers or people already in a deal |
| Destination | The one action the sequence exists to produce | Judging a sequence only on engagement |
| Exit conditions | Every reason a person should leave, enforced automatically | Emailing someone who has already acted |
| Situation | The one reader situation this sequence serves | Several half-built flows colliding |
Taking them in turn: the trigger should be written as an event, not a description. "Interested in pricing" is not a trigger, while "submitted the pricing enquiry form" is. Precise entry lets you write for a reader whose circumstances you actually know.
The destination is a single action: booking a call, starting a trial, replying with a question, requesting a proposal. Engagement is not a destination. It is what a sequence produces when nobody decided what it was for.
The exits get a post of their own, how to set email sequence exit conditions, because they are the decision teams skip most often and the one that makes nurturing feel helpful or harassing.
Choose the right instrument first
A nurture sequence is triggered by something a person did and runs on that person's clock. If the right moment depends on what this person did, you need a sequence. If it depends on the calendar, you need a different tool. The distinction, and why mixing them up is the commonest failure, is set out in sequence vs campaign vs newsletter. For this build, assume a sequence.
Start with one situation, not one product
The useful unit of nurturing is the reader's situation: just downloaded a guide, just started a trial, went quiet after a demo. It is not your product catalogue. Pick the situation that produces the most leads and build one sequence for it. Do not start the second until the first works.
The reason is collision. Five half-built sequences mean the same person qualifies for three and hears three voices at once. Decide a collision rule up front: one nurture sequence per person at a time, and the more specific one wins. Also keep to what you promised. Someone who downloaded a guide expected the guide and some related thinking, not every announcement you will ever make.
Keep the shape short and linear
The temptation is to draw a branching flowchart with dozens of paths. Resist it. A short, linear sequence with a few well-chosen exits beats an elaborate one that nobody can maintain, and the elaborate one is usually wrong in ways nobody notices.
A workable sequence is five to seven emails. A reliable shape looks like this.
| Position | The one job |
|---|---|
| First | Deliver what was promised, immediately, with no pitch attached |
| Second | Name the problem in the reader's own words and show you understand what it costs them |
| Third | Teach something useful they can apply without you |
| Fourth | Show proof: someone in a similar situation and what changed, told honestly |
| Fifth | Address the real objection, the one your sales conversations keep meeting |
| Sixth | Make the direct ask, plainly, with one clear next step |
| Last | Close gracefully: say it is the final message, offer a lower frequency, leave the door open |
If you cannot state an email's job in one sentence, it does not have one, and it should be cut. Writing each of these well, including the voice and the single call to action, is the subject of how to write a nurture email.
Set the timing from the reader's trigger
Interest is highest just after the person acted and decays from there. So the first email goes immediately, the next few follow at short intervals, and the gaps then widen. Measure every delay from the person's own trigger or from the previous email, never from a calendar date.
Decide whether your audience reads at work or at home and whether weekend email is welcome, then set send times and days to match. It does not need to be precise. It needs to avoid the obvious mistakes: several emails in as many days for one downloaded guide, or an offer landing at midnight on a Saturday.
Branch a little, and only on strong signals
A small amount of branching is worth having. Someone who clicks the pricing link has told you something, and it is reasonable to move them towards a conversation, or out of the sequence and into a salesperson's hands. Someone who has clicked nothing in four emails may need a different approach or a graceful close.
Branch on clicks, replies, tags and actions. A sequence that branches on opens is making decisions on noise, because some mail applications open messages on the reader's behalf and privacy features hide whether anyone looked.
Make sure it arrives before you switch it on
Everything above assumes the email reaches the inbox, and that assumption fails silently. The sequence runs, the dashboard shows sends, and a meaningful share of the mail sits in spam folders or is never accepted. Before you turn the sequence on, check three things: that your sending domain is authenticated, that a suppression list is checked before every send, and that the list itself is clean. The reasoning behind all three is in email deliverability for founders.
Decide how you will judge it before it runs
A sequence needs a measure agreed in advance, and the measure is the destination, not the opens. Define it as a rate over a fixed window among the people who entered, pick the window once, and keep it. Then decide the rule that links a deal to the sequence before you look at any result. Both are covered in how to measure email nurture by deals.
Plan the hand-off at the same time. When someone shows readiness by clicking pricing, replying or booking, a person should pick them up with context, and the automated emails should stop. Then put a review in the calendar. An email sequence written once drifts out of date as the offer changes, the proof ages and links break, and the decay is invisible from the dashboard until it is severe.
What to leave out of the first version
Most first builds fail by being too ambitious, not too modest. Leave out the second sequence, the elaborate flowchart and the clever subject line experiments. Leave out any email that exists only because the sequence felt short without it. Every message spends a little of the reader's attention and patience, so an email that cannot justify its job costs you something real for no return.
What you keep is small enough to hold in your head: one trigger, one destination, a handful of exits and a few emails that each do one thing. That is also small enough to review monthly, which matters more than it sounds.
A build checklist in plain words
- I can name the event that starts the sequence and the people it excludes.
- I can name the one action it exists to produce.
- Every exit is defined and happens automatically.
- Each email has one job, one call to action and a delay measured from the trigger or the previous email.
- Any branch depends on a click, reply, tag or action, never on an open.
- The sending identity and the suppression check are in place.
- I know how I will measure it and when I will review it.
If you can tick every line, you have a sequence worth switching on. If you cannot, the unticked line is your next task, and it is almost always a decision rather than a piece of writing.
Frequently asked questions
How many emails should a nurture sequence have?
The simplest workable sequence is five to seven emails, each with one nameable purpose. Fewer emails with clear jobs beat many emails without them.
Should I build several sequences at once?
No. Build the one for the situation that produces the most leads, make it work, then build the next. Half-built sequences collide and are never maintained.
Do I need a branching flowchart?
No. A short, linear sequence with a few well-chosen exits is easier to maintain and usually more accurate. Add a little branching on clicks and replies only where the signal is strong.
When should the sequence stop?
When it has nothing more to offer that person: they reached the destination, replied, booked, became a customer, started talking to your team, unsubscribed or their address bounced.
The full method, with the checklists, is in The Email Nurture Playbook, a free 34-page playbook.