The purpose of an onboarding sequence is one thing: get the person to their first real outcome. Not to tour features, not to re-explain the value proposition they already accepted. Most sequences do the latter, which is why they get ignored while the support inbox fills with questions the sequence should have answered.
Sequence timestamps that work
| Timing | Purpose | If skipped |
|---|---|---|
| Immediately | Confirm access, one first action | People never start |
| 24 hours (if no action) | Remove the specific blocker | Silent drop-off |
| Day 3 | The second action, once the first works | Trial without value |
| Day 7 | Recap progress, one next step | Forgetfulness |
| Day 10–12 | Paywall / decision email | Expired trial, no conversation |
The twelve
Replace every [bracket].
1. Immediate access
Use when: signup completes.
You are in. One thing to do first: [single action, with the direct link]. It takes about [minutes]. Everything else can wait until that works — here is the guide if you want it: [link]. Reply to this email if anything blocks you; it reaches a person.
2. The 24-hour nudge
Use when: account created but first action not completed.
[Name] — you signed up yesterday but have not [action] yet. The two things that most often stop people: [blocker one] and [blocker two]. If it is neither, reply and tell me what you see. Here is the link to pick up where you left off.
3. The Day 3 expansion
Use when: the first action succeeded.
You have [first outcome]. The next useful thing most people do is [second action], because [reason tied to their situation]. It takes [time]. No setup needed if [condition already true].
4. The team invitation
Use when: the product benefits from more than one person.
[Product] works better with whoever else touches [shared thing]. Here is the invite link, with [role] permissions already set. Two is usually the right number to start with — adding eight people before the workflow exists rarely helps.
5. The integration prompt
Use when: connecting another tool unlocks value.
If you use [tool], connecting it removes [specific manual step]. Takes [minutes]: [link]. If you are not using [tool] yet, skip this — everything else works without it.
6. The Day 7 recap
Use when: a week has passed.
Your first week: [metric one] and [metric two], which is [honest assessment]. The gap I would close next is [specific next step]. If you would rather talk it through, here is a [minutes]-minute slot.
7. The use-case example
Use when: their situation resembles a known pattern.
People doing [their apparent use case] usually get the most from [feature]. Here is what one of them set up in their first fortnight: [concrete description]. None of it took longer than [time per step].
8. The quiet-account check
Use when: activity has stopped after early use.
You have not been in since [date]. No pressure — if the timing is wrong, tell me when to come back and I will. If something did not work, tell me what it was; that is the version of this email I find useful.
9. The paywall email
Use when: approaching trial end.
Your trial ends [date]. What you have built stays [stated honestly — kept / exported / deleted, whichever is true]. If you are deciding against it, I would genuinely like to know why — reply with one line.
10. The reactivation
Use when: someone churned or lapsed.
It has been [period]. Two things have changed since you left: [change one] and [change two]. If either was what stopped you, worth another look. If not, no reply needed.
11. The human handshake
Use when: account size or complexity justifies it.
Sent from a person, not the system, at the point where the person has enough context for a conversation — usually after their first successful outcome, not before. Two sentences: what you noticed about their setup, one question.
12. The handover to ongoing
Use when: onboarding ends and the normal relationship starts.
You are set up for [what they can now do]. From here: [where support lives], [where changes are announced], and who asks for what. No further onboarding emails.
Two emails a person should write
The human handshake — a generated "checking in from the founder" email is recognisable and reads worse than silence. And anything responding to a complaint, because that reply becomes the record of how a problem was handled. Both are short enough to write in two minutes.
Editing time, from our 30-day benchmark
Our 30-day test put each onboarding email at roughly 5 minutes with a general assistant and about 9 minutes with a low-cost dedicated writer. The saving is in phrasing, not planning: what actually determines whether a sequence works is whether each email points at one specific action, and no tool can decide that for you.
Frequently Asked Questions
How many onboarding emails should I send?
Five to seven over the first fortnight is plenty for most products. Each should point at one action; more emails with less specificity get ignored.
When should the first email be sent?
Immediately on signup, while motivation is highest. It should confirm access and point to one specific first action with a direct link — nothing else.
What if someone does not complete the first action?
Send a nudge at 24 hours that names the two most common blockers. Asking what stopped them gets replies, and those replies tell you what is broken.
Should onboarding emails come from a person or the system?
System emails for sequence and logistics; a person for the handshake once there is enough context to have a real conversation, and for anything arising from a complaint.
Can AI write an onboarding sequence?
Yes, once you have decided what each email should make someone do. That decision is the sequence; the wording comes after.