Email sequence examples: 3-step and 5-step outreach that gets answered

A sequence is a follow-up plan you decided once, so you never have to decide it again. The best ones are short, mostly automatic, and stop themselves. Here are two you can copy, the timing behind them, the rules for stopping, and how to tell whether yours is working.

What is an email sequence?

An email sequence is a fixed series of messages to one person, each sent after a set gap if the previous one got no reply. The first email is the ask; the rest are follow-ups, and each follow-up is shorter than the last and adds one new thing. The point is to remove two decisions from your week: whether to chase, and when.

The reason to bother is in the numbers: the average cold email gets an 8.5% reply rate and a single follow-up lifts that by 65.8%, as covered in follow-up email statistics. A sequence is how you collect that lift on every thread instead of the few you remember.

The three-step sequence, for warm contacts

For people who know you: a customer, a partner, a colleague at another organisation.

1. Day 0, the ask. Context in one line, the ask in one line, a specific time option.
2. Day 3, the nudge. Same thread, a new detail, the ask again in fewer words.
3. Day 8, the close. "Still worth a look, or should I close it out?" Stop after this regardless.

Copy for day 3: "Hi Sam, adding one thing since Monday: the vendor confirmed they can start on the 12th if we sign by Friday. Shall I send the order form, or is Friday too soon?" Copy for day 8: "Sam, is this still worth a look, or should I close it out for this quarter? A one-word answer is perfect."

PeakLook does this from your own data. Drafts the reply. Keeps the follow-up going. Join the free beta →

The five-step sequence, for cold outreach

For people who do not know you yet. Longer, and every step must add something.

1. Day 0, the reason. Why them, why now, what you want, under a hundred words.
2. Day 3, the proof. One result from someone like them, with a link.
3. Day 7, the easier ask. Swap the call for a two-page document or a yes/no question.
4. Day 14, the different angle. A different benefit, or a different person on their side cc'd.
5. Day 21, the close. Polite, final, door left open.

Copy for day 7: "Hi Priya, a call may be too much right now, so here is the two-page version [link]. If one line in it is relevant to your team, reply with the line and I will answer that only." Copy for day 14: "Priya, copying Marcus in case this sits closer to his side. The short version: we cut onboarding from three weeks to one for a team your size. Worth fifteen minutes?"

Timing: how long between emails in a sequence?

Gaps widen as the sequence goes on: three days, then four, then a week. Early follow-ups catch a bad moment; later ones give the reader room. Send on weekdays only, in the reader's working hours, and skip public holidays in their country. The structure of each individual message, with templates, is in how to write a follow-up email.

Sequence examples by situation

The two templates above cover most outreach. Five other situations come up every week, and each is a small variation on the same shape.

The rule across all of them: the colder the contact, the more steps and the more each step must add; the warmer the contact, the fewer steps and the sooner the polite close. A recruiter chasing a candidate for three weeks is losing them; a colleague chased five times is a problem you have created.

Personalisation does not mean rewriting every step for every person. It means the first email is written for them, and the follow-ups carry forward the one or two details that made the first one specific: the thing they said, the result that matches their team, the date that matters to them.

The stopping rules

Any reply stops the sequence, including "no" and "not now". An out-of-office pauses it and resumes after the return date. A bounce ends it. A reply on a different thread from the same person stops it too. These rules matter more than the copy; a sequence that keeps sending after a reply damages more than it wins.

This is the same principle as an approval gate on any automated system: the automation runs until a human signal arrives, and then it stops without being asked twice. The argument for designing automation that way is in why approval gates are the safety feature.

How to measure whether a sequence works

Track three numbers per sequence: reply rate per step, positive reply rate overall, and the step at which most replies arrive. If step 2 gets more replies than step 1, your first email is too long. If replies cluster at the close, your middle steps add nothing. If positive replies are under a third of all replies, the targeting is wrong, not the copy.

Change one thing at a time, run it on at least thirty contacts, and compare. Opens are a weak signal and should not drive decisions on their own; replies are the measure.

A sequence with a stopping rule also produces a clean number: the share of enrolments that ended in a reply versus the share that ran to the close. If more than half run to the close, the list is wrong, not the copy.

Running it in PeakLook

PeakLook stores each of these as a template with its steps, drafts every step from the original thread in your voice, sends from the server on schedule, respects send days and quiet hours, and applies the stopping rules automatically. The monitor shows every enrolment in flight with opens, clicks and replies, filtered by who is active, paused or done. Where the line sits between what the machine writes and what you decide is covered in what an AI email assistant can and cannot do.

Hen Eytan · Founder, UPeak

Builds the UPeak apps and writes up the research behind them.