Send five emails, give each exactly one job, and trigger them on what the user did rather than what day it is. The first email should drive a single action that produces a result; the rest should respond to whether that happened. Send them in plain text from a real person at a real reply-to address, and remove anyone from the sequence the moment they complete the action it was pushing them toward.
The four principles
One job per email. If you cannot state the single action an email is asking for, it does not have one, and the recipient will not invent it for you.
Useful even if they never buy. Each email should leave the reader slightly better off. This is what buys the next open.
From a person, to a person. Real name, real reply-to, plain text. The replies to a plain email are the best product research available to an early company.
Stop when the job is done. The moment someone completes the action, remove them from the rest of the sequence. Nothing trains a user to ignore you faster than being told to do something they did last Tuesday.
The five emails
The sequence assumes your product has one core job that produces a visible result. If it does not, no email sequence will save it, and you should read why SaaS customers churn in month two first.
1. The one action (immediately on signup)
Not a welcome. One sentence on what they are about to get, one link to the single action that produces the first result, and nothing else. No feature list, no social links, no founder story. If the email contains four links, you have asked them to make a decision instead of taking an action.
Subject lines that work here are boring and specific: the name of the thing they are about to do.
2. The nudge (fires only if they did not do it, ~24 hours)
This is the highest-value email in the sequence, because it targets the exact moment most products lose people. Assume something got in the way rather than that they lost interest. Ask, in one line, what stopped them, and repeat the single link.
Never send this to someone who completed the action. That is what the trigger is for.
3. The second use case (fires after they got the first result)
They have seen it work once. Now show one more thing it does, chosen because it is the most common second job, not because it is your favourite feature. One use case, one example, one link.
4. The question (about a week in, to active users)
"What were you trying to do when you signed up?" or "What is still missing for you?" Genuinely asking, with no pitch attached. Two things come back: product insight you cannot get any other way, and a reply, which is the strongest possible signal to a mailbox provider that your mail is wanted.
5. The decision (before the trial ends or the first renewal)
What happens next, when, and what it costs. If they have used the product, remind them concretely of what they did with it: the things they created, the time it saved, the specific output. Then the plain ask. No fake scarcity, no countdown that resets.
Triggers, not days
A calendar sequence sends the same email to someone who has used the product daily and someone who has never logged in. Both receive something irrelevant, and both learn to ignore you.
Trigger
Send
Do not send
Signed up
Email 1, immediately
Anything else
No first action after ~24h
Email 2
Email 3, 4 or 5
Completed first action
Email 3
Email 2, ever
Returned 3+ times
Email 4
Nudges of any kind
Trial ending or renewal due
Email 5
A discount, by default
Silent for 7+ days
A personal note, written by you
An automated re-engagement campaign
That last row is worth doing manually for as long as you possibly can. A short personal message asking what got in the way occasionally produces the single insight that fixes retention for an entire cohort.
Why they go to spam
Almost always configuration rather than content. The basics, in the order they matter:
Authenticate your sending domain. SPF, DKIM and DMARC records, set up properly. The major mailbox providers now expect all three from bulk senders, and without them your mail is filtered before anyone reads a word of it.
Send from your own domain. Not a free mailbox provider address. You cannot build a reputation on a domain you do not control.
Warm up gradually. A brand new domain sending to thousands of addresses on day one looks exactly like a spammer, because that is what spammers do.
Keep early emails plain and link-light. One link, minimal images, no link shorteners or unfamiliar tracking domains.
Make unsubscribing trivial. A one-click unsubscribe that works. An unsubscribe costs you one address; a spam complaint costs you deliverability for everyone.
Remove people who never open. Sending to dead addresses degrades your reputation for the people who do want your mail.
The common mistakes
User signs up, lands on a dashboard with 47 options, has no idea what to click first, and churns in a week.
via r/SaaS
The email version of that dashboard is the welcome email that lists every feature. Both fail for the same reason: they hand the user a menu when the user wanted a next step.
The rest, briefly:
The founder story as email one. Nobody has earned curiosity about you yet. Send it later, if at all.
noreply@ as the sender. You are telling people their reply is unwelcome, and discarding your best research channel.
Designed templates at small scale. They signal marketing, which is a category people delete faster.
Continuing to nudge after conversion. The fastest way to make a new customer regret it.
Discounting by default at the trial end. You train everyone to wait for the discount, and you learn nothing about whether the price was ever the problem.
Five is enough for most products, each with a single job. More than that and you are competing with yourself for attention, and each additional email lowers the open rate of the next one. The constraint is not the count but that every email must be useful on its own, even to someone who ignores the rest.
Should onboarding emails be time-based or behaviour-based?
Behaviour-based wherever you can manage it. An email that arrives because someone signed up and then did nothing is relevant; the same email arriving on day three regardless of what they did is noise. If you can only build one trigger, make it the one that fires when a user has not completed the first meaningful action.
What should the first onboarding email say?
One thing: the single next action that gets them to a result. Not a tour of the features, not a welcome letter about your journey, and not a list of links. The first email exists to get one click that leads to one outcome, and every additional option in it reduces the chance that happens.
Should onboarding emails come from a person?
Yes, from a real name at a real address that accepts replies. Plain text from a founder outperforms a designed template at early scale, because it reads as correspondence rather than marketing and because the replies you get are genuinely useful product research.
Why do my onboarding emails go to spam?
Usually because the sending domain has no authentication set up or no reputation yet. Configure your domain authentication records properly, send from your own domain rather than a free provider address, warm up gradually, and keep the early sends plain and link-light. Content matters less than configuration here.
When should onboarding emails stop?
When the user has done the thing the sequence was designed to get them to do. A user who has already reached the first result should be removed from the rest of the sequence immediately, because emails telling them to do something they have done are the fastest way to train someone to ignore you.
Where these numbers come from
This guide is a method rather than a study. We deliberately do not quote open or click rates: ours come from our own audience and market, and presenting a single company’s numbers as an industry standard is exactly the kind of unsourced benchmark we try to avoid. The deliverability guidance reflects the published requirements of the major mailbox providers as of September 2026; verify the current specifics with your sending platform, because these requirements change.
Cite this page
Last verified: September 22, 2026
BigIdeasDB Research. (2026). A SaaS onboarding email sequence that gets opened. BigIdeasDB. Retrieved from https://bigideasdb.com/guides/saas-onboarding-email-sequence