The SaaS Onboarding Email Sequence (With Examples)
A behaviour-triggered onboarding sequence beats a fixed drip. The emails that make up a good arc, what each one should say, when to send based on what the user has and hasn't done, and the metrics that tell you it's working.
A fixed onboarding drip talks past half its audience — the users who are ahead of it and the users who stalled two steps back. A sequence that works is triggered by behaviour: it sends the next-step email when the user finishes the previous step, the nudge email only to users who stalled, and the feature emails when the user is ready for them. Across the first two to three weeks that's usually five to eight emails, each with one job and one call to action. The first email gets the user to first value rather than listing features. The sequence hands off to regular lifecycle email once the user is activated.
The arc
| Trigger | Job | |
|---|---|---|
| 1 — Welcome | Immediately after signup | Get to first value; one action, one CTA |
| 2 — First-step nudge | 24–48h, if step 1 not done | Re-show the value, lower the barrier |
| 3 — Second step | After first value reached | Point at the next meaningful action |
| 4 — Feature spotlight | ~Day 5, if activated | Introduce one high-value feature |
| 5 — Social proof / use case | ~Day 7 | Show what success looks like for someone like them |
| 6 — Check-in / help offer | ~Day 10, if stalled | A person offering to help, not automation |
| 7 — Upgrade context | ~Day 14, if hitting limits / on free | Frame the paid value against what they've done |
Add or drop emails to fit your product. The structure to keep: each email adapts to what the user has and hasn't done.
What each email says
Email 1 — Welcome
Not a feature list. The one action that gets them to first value, with a short walkthrough of the outcome so they know the target:
One CTA. See putting an interactive demo in your onboarding emails for the mechanics.
Email 2 — First-step nudge
Only to users who haven't done step one. "You signed up but haven't [first action] yet — here's the two-minute version." Specific, not "we miss you."
Email 3 — Second step
After first value: "Now that you've [done first thing], the next step is [second thing], which lets you [benefit]."
Email 4 — Feature spotlight
One feature, shown not told. What it does, why it matters, a visual.
Email 5 — Social proof
A short story of a user like them getting a result. Concrete, named, one outcome.
Email 6 — Check-in
From a real person's name. "How's it going? Anything I can help with?" For users who've stalled.
Email 7 — Upgrade context
Frame the paid tier against what the user has actually done: "You've published three demos — the free plan's limit. Here's what more gets you." Not a generic sales email.
Every email should be readable and actionable on a phone in under 20 seconds. If an email needs scrolling, it's doing too much — split it or cut it.
Metrics
- Per-email: open rate, click rate, and — more useful — the completion rate of the action each email drives.
- Sequence-level: activation rate and first-week retention for users who received the sequence vs a holdout.
- Stall recovery: of users who got a nudge email after stalling, how many came back and reached first value.
If opens and clicks are healthy but activation isn't moving, the emails are engaging but pointing at the wrong actions.
Related: the SaaS onboarding checklist, self-serve onboarding, time to value.
Frequently asked questions
How many emails should be in an onboarding sequence?
Five to eight over the first two to three weeks is a common range, but the count matters less than the triggers. A sequence that sends the same emails to everyone regardless of what they have done wastes touches. A sequence that adapts — sending the 'you haven't created a project yet' email only to people who haven't — stays relevant.
Should onboarding emails be triggered or on a fixed schedule?
Triggered by behaviour wherever possible. Send the next-step email when the user completes the previous step, not on day three regardless. Send the nudge email when the user stalls, not to everyone. A fixed drip is easier to build but talks past users who are ahead or behind the schedule.
What should the first onboarding email say?
It should get the user to first value, not list features. Point at the single most important first action, ideally with a short walkthrough of the outcome so they know what they are aiming for. One call to action. Keep it short enough to read on a phone.
When should an onboarding sequence stop?
When the user is activated — has reached a real moment of value and is returning on their own — the onboarding sequence should hand off to your regular lifecycle or product-update emails. Continuing to send 'getting started' emails to an active user is noise.