Which onboarding emails should a SaaS send in its first 30 days?

1. Blog
2. Demand & Channels

By Saroj Jha · November 2, 2026 · 15 min read

Send one email for each step a new user must take to reach first value, and send it when that user stalls before the step, not on day 3 because the calendar says so. In my view a good first-30-days sequence usually has five to seven emails: a welcome that asks for the first step, one nudge per milestone, one plain-text note from the founder to people who are stuck, a trial-end notice and one email that marks activation and hands over to the regular product lifecycle. Each email asks for one action. The sequence stops when the user reaches the milestone, replies, unsubscribes or goes quiet, and you judge it by the share of signups who reach activation, because Apple’s Mail Privacy Protection has made open rates an unreliable count of who read anything.

Here is how I build the sequence, one question at a time.

Running case: Example Co. Fictional

Example Co. is a fictional seed-stage B2B SaaS company that turns a team’s support tickets into a weekly product-feedback report for product managers at software companies with 20 to 200 employees. About 1,200 people a month start its 14-day free trial, which then costs $49 a seat a month, and a new account buys three seats on average. Today it sends a seven-email drip on days 0, 1, 3, 5, 7, 10 and 13 to everyone, whatever they have done. Example Co. and every number attached to it are illustrative.

Why should onboarding emails follow milestones, not a calendar?

Because users do not move at the same speed. A product manager who connects her helpdesk in the first ten minutes does not need the day-3 “how to connect” email, and the one who has not logged in since signup gets nothing useful from the day-5 “advanced reports” tip. A calendar drip answers the question “what day is it?” when the useful question is “what is this person’s next step?”.

So I start from activation: one observable action that shows the product has done its job for this user, inside a time window. Then I list the two to four steps that lead to it. Each step is a milestone, and each milestone gets at most one email that helps the user over it. The retention article covers why activation is the job (Retention is a marketing job too); this article is the email sequence that serves it.

Example Co., step 1 Fictional

Example Co. defines activation as “first feedback report shared with a teammate within 7 days of signup”. The steps before it are connecting a helpdesk and generating a first report. Of last month’s 1,200 trials, 660 connected a helpdesk (55%), 480 generated a report (72.7% of those who connected) and 288 shared it (60% of those with a report). Activation is 288 ÷ 1,200 = 24%. The biggest loss is the first step: 1,200 − 660 = 540 people never connected anything, against 180 lost at the report and 192 at sharing.

Do this

Write your activation event and its time window in one sentence, then list the two to four milestones before it and how many of last month’s signups reached each.

When should an email be triggered by behaviour, and when by time?

Use behaviour for progress and time for deadlines. A behaviour-triggered email fires on an event, or on the absence of one: “connected the helpdesk but has not generated a report within 48 hours”. It reaches only the people who need it, at the moment they need it. A time-based email fires on a date, and it is the right tool for things that really are dated, such as the end of a trial.

My rule of thumb, not a benchmark: every milestone email is written as “if not by”, meaning if the user has not reached milestone N by a set number of hours after milestone N − 1, send the email for milestone N. Users who move fast skip it. Users who move slowly get it when it is relevant. Time still sets a ceiling on how long you wait, so nobody falls out of the sequence because an event never fired.

Your tracking has to be good enough to send on events. If your email tool cannot see product events, fix that before you rewrite copy; the tracking setup guide covers naming the events.

Example Co., step 2 Fictional

Example Co. replaces its seven calendar emails with a welcome and six others. Four are behaviour-triggered (connect, generate, share, activated), one is the founder’s note to anyone not yet activated on day 3, and one is time-based: the trial-end notice on day 11. A user who activates on day 1 receives the welcome, the activated email and the trial-end notice: three emails instead of seven.

Do this

Mark each email in your current sequence “behaviour” or “time”. Any time-based email that teaches a step should become an “if not by” trigger on that step.

Who should send each email, the founder or the product?

Both, for different jobs. How-to emails come from the product: they are short, they link straight to the step, and the user expects them. The one email where a person beats a product is the note to someone who is stuck, because its job is to start a conversation, and people reply to a person.

The founder note works when it is real. It is plain text, from the founder’s own address, asks one question and gets answered by the founder or by someone who signs their own name. A note that says “reply to this email” and goes to a no-reply inbox teaches users that replies vanish. The law is on the same side: the FTC’s guide says your From, To and Reply-To fields must be “accurate and identify the person or business who initiated the message”^[2].

There is evidence that small personal signals change how people treat an email. In randomized field experiments with three companies, run on email ads to millions of recipients, adding the recipient’s name to the subject line raised the open rate from 9.05% to 10.80%, sales leads from 0.39% to 0.51% and cut unsubscribes from 1.2% to 1.0%^[3]. Those were marketing emails, not onboarding, so I read the result as a direction: a message that looks written for one person gets more attention than one that looks broadcast.

Example Co., step 3 Fictional

Example Co.’s founder sends E5 on day 3 to every trial user who has not activated. It reads, in full: “Hi Priya, I saw you signed up on Monday but haven’t connected a helpdesk yet. Is something in the way? Reply and I’ll read it myself. Dana, founder.” Replies go to Dana’s inbox, and she answers each one within a working day.

Do this

Pick the one email in your sequence aimed at stuck users, rewrite it as three plain-text sentences from a named person, and make sure a reply reaches that person.

What should each email ask the user to do?

One thing: the next milestone. An onboarding email with a feature tour, a webinar invitation, a blog link and a “book a demo” button asks the user to choose, and choosing is work. One ask, one button, and the button lands on the exact screen where the step happens, not the dashboard home.

Write each email in three parts: what the user gets from this step, how long it takes, and the button. Leave everything else for the product’s help centre. If you want to teach more, the next milestone email will arrive when the user is ready for it.

Example Co., step 4 Fictional

Example Co.’s old day-5 email had five links. Its new E3 has one sentence on the benefit (“Your first report groups last month’s tickets by theme, so you can see what customers ask for most”), one on the effort (“It takes about a minute once your helpdesk is connected”) and a single button that opens the report builder with the connected helpdesk already selected.

Do this

Count the links in each onboarding email. Cut every email to one primary button that deep-links to the step it asks for.

When should the sequence stop?

Sooner than most do. I stop the activation track for a user on any of five events, and I write them down before the first send so nobody has to decide later:

• The user reaches the milestone. The next email in line is for the next step, or, after activation, the regular lifecycle and newsletter take over.
• The user replies. A person now owns the conversation, and automated emails that ignore the reply look careless.
• The user unsubscribes. For commercial email this is a legal duty, not a courtesy (see the last section).
• The user goes quiet. My rule of thumb, not a benchmark: if a user has not signed in or clicked anything after two consecutive milestone emails, send the trial-end notice and nothing else.
• The trial ends. One notice before the end; after it, the user leaves onboarding.

Complaints are the other brake. Google’s sender guidelines ask anyone sending to personal Gmail accounts (addresses ending in @gmail.com or @googlemail.com) to keep the spam rate shown in Postmaster Tools below 0.10% and to avoid ever reaching 0.30%^[1]. Senders of more than 5,000 messages a day to personal Gmail accounts must also authenticate with SPF, DKIM and DMARC, and their marketing and subscribed messages must support one-click unsubscribe^[1].

A sequence that keeps emailing people who have lost interest is how a startup’s spam rate creeps up, and then the onboarding emails stop reaching the users who want them. The Email Authentication Checker shows whether your domain’s SPF, DKIM and DMARC records are in place.

Example Co., step 5 Fictional

Under the old drip, every trial user got all seven emails. Under the new rules, a user who activates on day 1 gets three (welcome, activated, trial-end notice), and a user who never connects gets four (welcome, connect nudge, founder note, trial-end notice). A one-a-day cap holds back any second onboarding email due on the same day until the next morning.

Do this

Write your five stop rules above the sequence in your email tool, and check last month’s spam rate in Google Postmaster Tools before you add any email.

How do you know the sequence works?

By activation rate, not open rate. Since 2021, Apple’s Mail Privacy Protection “stops senders from using invisible pixels to collect information about the user” and helps users “prevent senders from knowing when they open an email”^[4]. It does this by downloading remote content, the tracking pixel included, “when a message is received (instead of when you view it)”^[5]. For users with the feature on, the pixel fires whether or not they read the email, so your tool records an open either way.

That makes opens a poor test of a subject line and no test at all of whether onboarding works. The number that matters is the share of a signup cohort that reaches activation inside its window, plus the share that reaches each milestone. To learn whether one email helps, hold it back from a random slice of users and compare milestone rates, not opens.

Small holdouts need patience. A test on one month of trials can show a gap that is still within chance; pool months until the intervals separate, or make the holdout larger. The A/B Test Significance Calculator does the comparison.

Example Co., step 6 Fictional

Suppose 400 of 1,000 welcome-email recipients use Apple Mail with the feature on, and 30% of the other 600 really open it. The tool reports (400 + 180) ÷ 1,000 = 58% opens; the only opens it can measure honestly are 180 of 600, or 30%. The 400 is my assumption for illustration, not a market share. So Example Co. judges the new sequence by activation instead. It holds back 10% of trials, who keep the old drip. In month 1, 335 of 1,080 new-sequence users activated (31.0%, 95% interval 28.3% to 33.8%) against 29 of 120 in the holdout (24.2%, 17.4% to 32.6%): the intervals overlap, and a two-proportion test gives p = 0.12. After three months, 1,005 of 3,240 against 87 of 360 is the same 31.0% against 24.2%, but now the intervals (29.4% to 32.6% and 20.0% to 28.8%) do not overlap, p = 0.007. If activated users keep converting to paid at 28% and others at 2%, the paid rate moves from 0.24 × 28% + 0.76 × 2% = 8.24% to 0.31 × 28% + 0.69 × 2% = 10.06%: about 22 more paying accounts from each 1,200 trials, or about $3,210 of new monthly revenue at three $49 seats each. The conversion rates holding is my assumption, not a forecast.

Do this

Replace open rate on your onboarding report with activation rate by weekly signup cohort, and keep a 10% holdout on any email you are not sure earns its place.

Which onboarding emails count as commercial under US law?

Most onboarding emails are a mix, so it is worth knowing where the line sits. The FTC’s guide to the CAN-SPAM Act says the law covers any message whose primary purpose is “the commercial advertisement or promotion” of a product or service, and “The law makes no exception for business-to-business email”^[2]. Messages that only facilitate a transaction the recipient has agreed to, or notify them of “a change in the terms or features” of their subscription or account, are transactional or relationship messages, which are “exempt from most provisions” but still may not carry false or misleading routing information^[2].

Two practical consequences follow. First, a message’s primary purpose is commercial if a reader of the subject line would likely conclude it contains an advertisement, or if the transactional content does not appear mainly at the beginning^[2]. A trial-end notice that states the date and the options is close to transactional; the same email led by an upgrade discount is commercial.

Second, commercial email needs a clear way to opt out, a valid physical postal address and accurate headers, and you must honour an opt-out “within 10 business days”^[2]. If you are unsure which kind an email is, treat it as commercial and include the opt-out. The guide also says “you can’t contract away your legal responsibility”^[2], so using an email vendor does not move the duty.

Consent rules outside the US, such as in the EU, the UK and Canada, are stricter and work differently. My privacy and advertising rules article covers them, so I do not repeat them here.

Do this

Label each onboarding email “transactional” or “commercial” and give every commercial one a working unsubscribe link and your postal address.

This is orientation, not legal advice.

What changes by stage?

• Pre-seed — The founder sends every onboarding message by hand, from a list of who signed up this week and where each person got stuck. The point is to learn the milestones.
• Seed — Five to seven emails: welcome, one “if not by” nudge per milestone, the founder note, the activated email and a trial-end notice. Measure activation by weekly cohort and hold back one email at a time.
• Series A–B — Split the sequence by role or plan where the milestones differ, give lifecycle email an owner who shares the activation target with product, and keep a standing holdout so every email keeps earning its place.

Free template

Map every automated email to the milestone it serves

The Lifecycle Email Audit lists every automated email you send against the lifecycle stage and milestone it serves, so you can see which onboarding emails teach a step and which only fill a calendar.

The sequence above gets users to first value; what happens after it, from value records to expansion, is in Retention is a marketing job too. If your trial or freemium model is still undecided, Free Trial, Freemium or Demo? comes first, because the entry model sets the milestones. For the emails users receive once onboarding ends, see How to Grow a Startup Newsletter That Brings in Customers.

If you want me to look at your own funnel, positioning and channels, my Growth Audit ends with three prioritized fixes and a 30-day action plan.