Two jobs, done in seven days.
A welcome sequence has to do two things, and almost every one that fails is doing only the first. It has to hand over what was promised, and it has to establish what happens now — who you are, how often you show up, and what you will eventually ask for.
Job oneSettle the debt
Somebody gave you an address in exchange for a specific thing. Until that thing is delivered you are in arrears, and nothing else you send reads properly. This is the first email and it is the only one with a hard deadline: immediately.
Job twoSet the terms
The other four emails establish the relationship: who is sending, how often, what it is worth, why it exists, and what you will ask for. Get these right and later emails arrive as expected rather than as intrusions.
The brackets are the work
Everything in [brackets] is yours to replace — including the parts that read like instructions, which are written that way on purpose. The story email in particular is a scaffold rather than a draft: a borrowed origin story is the one thing in this sequence a reader can smell, and it costs more than sending nothing.
Swap the brackets for your tool’s merge fields where a merge field exists. Field names differ by platform, so these are written in plain brackets rather than any one product’s syntax. The copy button gives you the subject, the alternate subject and the body as plain text.
The whole sequence
Day counters, not calendar dates — the clock starts when somebody subscribes. Spacing is a starting cadence to adjust against your own list, not a benchmark to hit. If you send more often than this normally, compress it; the frequency guide covers how to choose a rhythm you can hold.
| When | Email |
|---|
| Immediately | Deliver the thingThe link they came for, and nothing else asked of them. |
|---|
| Day 1 | Who you are and what happens nowThe cadence promise. The email that prevents the later unsubscribe. |
|---|
| Day 3 | One small complete winProof that reading you pays. Finishable today. |
|---|
| Day 5 | Why this existsYour reasons, so the next ask is predictable rather than sudden. |
|---|
| Day 7 | The first askOne request, the smallest real one. Then the sequence ends. |
|---|
| Day 10 → | Regular cadence beginsThey join the normal list at the next scheduled send. |
|---|