A SaaS onboarding email sequence is a set of automated emails sent over a new user's first two weeks, each designed to push them toward one specific product milestone. The best sequences are not tours — they are a series of single requests, ordered so that each completed step makes the next one obviously worth doing.
Start with the activation event, not the emails
Before you write a single subject line, answer one question: what action, taken in the first week, most strongly predicts that someone becomes a paying, retained customer? For a project tool it might be inviting a second teammate. For an analytics product it is installing the tracking snippet. For an email platform it is importing a list and sending one campaign.
That action is your activation event. Everything in the sequence either drives someone toward it or, once they have done it, builds on it. If you cannot name yours, your onboarding emails will default to a feature tour, and feature tours convert badly because they ask the reader to care about your product before it has done anything for them.
A useful test: pull your last 200 signups, split them by whether they still use the product 30 days later, and look for the first-week behavior where the two groups diverge most sharply. That is the milestone worth every email you have.
The nine-email sequence, day by day
| Day | Single goal | Send condition | |
|---|---|---|---|
| 0 | Welcome + first step | Complete setup step 1 | All signups, within 2 minutes |
| 1 | The activation nudge | Reach the activation event | Only if not yet activated |
| 2 | Quick win | Second core action | Only if activated |
| 4 | Objection / friction email | Remove the blocker | Only if not yet activated |
| 5 | Social proof | Build confidence | All still-active users |
| 7 | Team invite / expansion | Add a second seat | Activated users only |
| 9 | Advanced use case | Deepen habit | Activated users only |
| 11 | What happens next | Set expectations on trial end | Trial users |
| 13 | Convert | Upgrade | Trial users |
Note how much of this is conditional. A user who activated on day zero should never receive the day-four friction email — it makes your product look like it is not watching. Two branches, activated and not activated, is enough complexity for the first version.
Example copy for the five emails that matter most
Day 0 — welcome
Subject: Your account is ready — start here
Preview: One step, about 90 seconds, and you will have your first result.
Body: two sentences of welcome, one button, nothing else. Resist the urge to list features. The only job of this email is to get them back into the product while intent is still hot. Signing it from a named person with a real reply-to address measurably increases replies, and replies from new users are the cheapest product research you will ever get.
Day 1 — the activation nudge
Subject: You are one step from [specific outcome]
Preview: Most people finish this in under three minutes.
Name the outcome, not the feature. Not finish configuring your integration but start seeing where your signups come from. Include the estimated time — it directly addresses the unspoken objection, which is never “I do not want this” and almost always “I do not have time right now.”
Day 4 — the friction email
Subject: Stuck on the import?
Preview: Three things that trip people up, and the fix for each.
This is the highest-value email in the whole sequence and most teams do not have one. Ask support for the three questions new users ask most in week one, then answer all three. End with a genuine offer of help — a reply, a call, a shared screen. People who reply to this email convert at dramatically higher rates than those who do not.
Day 7 — expansion
Subject: Working alone in here?
Preview: Accounts with two or more people stick around far longer. Here is why.
Multi-seat accounts retain better in almost every SaaS category. Ask for the invite explicitly, make it one click, and say what the second person gets out of it — not what you get.
Day 13 — convert
Subject: Your trial ends tomorrow
Preview: Here is exactly what happens to your data either way.
Be direct and be honest about the downside. Tell them what they keep, what they lose, and how to get it back. Recap what they actually did during the trial — “you imported 4,200 contacts and sent 3 campaigns” — because specificity beats persuasion at the decision moment.
Six rules that separate good onboarding from noise
- One ask per email. Two buttons halves the click-through on both.
- Branch on behavior, not just time. The difference between a sequence that feels smart and one that feels like a mailing list is whether it notices what people did.
- Talk about outcomes, not features. Every subject line should survive the question “so what?”
- Send from a person. A founder's name and a monitored reply address, at least for the first three emails.
- Keep emails under 150 words through day seven. Length is permission you have not earned yet.
- Suppress marketing broadcasts for the first 14 days so onboarding is the only thing they hear from you.
Common failure patterns
- The feature tour. Nine emails, one feature each, no ordering logic. Reads like documentation with a send button.
- Sending everything to everyone. Activated users getting “still need help getting started?” is the fastest way to look unserious.
- Waiting until day three to say anything. Signup intent has a short half-life. Email one goes out in minutes.
- No exit on conversion. Upgrade emails arriving after someone paid.
- Ignoring the invited user. Someone who joins via a teammate's invite has completely different context and needs their own short sequence.
- Never revising it. Onboarding written for a product two versions ago is actively misleading.
Measuring it properly
Open rate is a weak signal here. Measure product outcomes instead:
- Activation rate — percentage of signups who complete the activation event within seven days. This is the number the sequence exists to move.
- Time to activation — median hours from signup. Shortening this is usually easier than raising the rate.
- Step drop-off — where in the sequence people stop opening. A cliff at one email means that email is wrong.
- Trial-to-paid by branch — compare activated vs. non-activated conversion to confirm you picked the right activation event.
- Reply rate on the friction email — an underrated leading indicator of both conversion and product problems.
Run a holdout: leave 5–10% of new signups out of the sequence for a month. It is the only way to know whether onboarding email is doing the work or the product is carrying it. Building the branches themselves is straightforward with a visual builder — see our walkthrough of email automation workflows for trigger and condition setup, and if you are pre-Series A our notes on email marketing for startups cover doing this on a small budget.
A two-week build plan
- Days 1–2: Define the activation event from real retention data.
- Days 3–4: Interview support. Write down the top five week-one questions verbatim.
- Days 5–7: Draft all nine emails as plain text in one document. Read it start to finish as a single story.
- Days 8–9: Wire the trigger, delays, and the activated/not-activated branch with placeholder copy. Test with a real signup.
- Days 10–11: Load the real copy. Send yourself through both branches on a phone.
- Days 12–14: Launch to 100% with a 10% holdout, and set a calendar reminder to review the numbers in 30 days.
Frequently asked questions
How many emails should a SaaS onboarding sequence have?
Between six and nine over the first two weeks works for most products. The count matters far less than the branching — nine emails split across activated and non-activated paths outperform fifteen emails sent to everyone.
When should the first onboarding email be sent?
Within two minutes of signup, ideally instantly. Intent decays quickly, and the first email's only real job is to bring someone back into the product while they still remember why they signed up.
What is an activation event and how do I find mine?
It is the first-week action that most strongly predicts long-term retention. Find it by comparing users who are still active after 30 days against those who are not, and looking for the behavior where the two groups diverge earliest and most sharply.
Should onboarding emails be plain text or designed HTML?
Plain text usually wins for the first week because it reads as a message from a person rather than a campaign. Designed templates make more sense from day seven onward, when you are showing results, screenshots, or customer stories.
Should users who upgrade early keep getting onboarding emails?
They should exit any email whose goal they have already achieved, particularly trial and upgrade messages. Educational emails that deepen product usage can continue, since those remain relevant after payment.
Ship your onboarding sequence this week. Start free with IGSendMail — visual automation, AI copy tools, and up to 2,500 contacts free.