How to Write Onboarding Emails That Reduce Churn
Onboarding emails reduce churn when they get new users to one activation event quickly, not when they send a fixed drip of product tours. Send a welcome with a single next step, follow up only with people who have not done that step, branch by behavior mid-trial, and stop emailing the moment someone activates, converts or replies.

Key takeaways
- Define one activation event before writing any email: the first action that shows a new user got real value.
- Trigger emails on behavior, not the calendar: an unblock email goes only to people who have not activated.
- A solo founder needs four or five emails in two branches, not a twelve-part drip.
- Every email should have one job and one link, and the sequence should stop when the user activates, converts or replies.
- Judge the sequence by activation rate and time to activation, with opens and clicks as secondary signals.
On this page 24
- TL;DR
- Why onboarding emails affect churn
- Step 1: Define your activation event
- Step 2: Track two things and send events to your email tool
- The sequence at a glance
- Email 1: The welcome email (one next step)
- Email 2: The unblock email (only if not activated)
- Email 3: The mid-trial branch
- Branch A: Stuck-user help (not activated)
- Branch B: Habit email (activated)
- Email 4: Near trial end, convert or help-or-close
- Branch A: Convert ask (activated)
- Branch B: Honest help-or-close (not activated)
- Exit rules: when the sequence must stop
- Writing rules for solo founders
- Metrics: how to tell if the sequence works
- Frequently asked questions
- How many onboarding emails should a SaaS send?
- What is an activation event?
- Should onboarding emails be plain text or designed HTML?
- When should onboarding emails stop?
- How is this different from reducing churn after customers pay?
- Where ZeroRaised fits
- Sources
Onboarding emails reduce churn when they get new users to one activation event quickly, not when they send a fixed series of feature tours. Write a welcome with a single next step, send follow-ups only to people who have not taken that step, branch by behavior mid-trial, and stop emailing as soon as someone activates, converts or replies. For a solo founder, that adds up to four or five short emails, not a twelve-part drip.
This guide covers the sequence, sample copy for each email, how to branch it and what to measure. It is about the weeks before and just after the first payment. For churn among customers who already pay, including failed payments, cancellation flows and cohort analysis, read our guide on how to reduce SaaS churn.
TL;DR#
- Define activation first. Pick the one action that shows a new user got value. Every email exists to move people towards it.
- Trigger on behavior. Send the unblock email only to people who have not activated. Never nag someone who has already done the step.
- Keep it short. Welcome, unblock, a mid-trial branch and a trial-end email are enough for a typical 7 to 14 day trial.
- Measure activation, not opens. Activation rate and time to activation tell you whether the sequence works.
- Let billing tools help. Stripe can send its own trial-ending reminder and fires a webhook before the trial ends, so you can time your conversion email (Stripe docs).
Disclosure: ZeroRaised publishes this guide and is a launch site for bootstrapped products. It contains no affiliate links, and ZeroRaised has no commercial relationship with Stripe or any other company named. Facts about Stripe come from its documentation as checked on 6 Nov 2026; the sequence, sample emails and advice are our own editorial view.
Why onboarding emails affect churn#
Many users who cancel never really started. They signed up, got stuck or distracted, and the trial ended. That looks like churn, but it is a failed onboarding.
Emails cannot fix a product that does not solve the problem. They can bring people back at the moments they are likely to drift and point them at the one step that makes the product useful. A user who reaches that step has a reason to pay and stay. A user who never reaches it has neither. To check whether your retention problem starts in onboarding or later, use the cohort work in how to reduce SaaS churn.
Step 1: Define your activation event#
Before you write anything, decide what "activated" means for your product. It should be:
- A single action you can track. "Created a first project and invited a teammate" is two events. Pick the one that matters more, or define activation as the second one.
- Close to real value. "Logged in twice" is not value. "Sent a first invoice", "published a first page" or "got the first report emailed to them" is.
- Common among people who stay. Look at your paying customers. Which early action did nearly all of them take? If you have too few customers to tell, pick the action that delivers the core result and revisit it later.
Write it down in one sentence: A user is activated when they [action] for the first time. Every email in the sequence points at that sentence.
If activation takes longer than your trial, the trial is too short or setup is too heavy. Our guide to freemium vs free trial for solo founders covers how to size the trial to your time to first value.
Step 2: Track two things and send events to your email tool#
Behavior-triggered email needs two pieces of data per user:
- Signup time, so you can time the sequence.
- An activation flag or event, set when the user completes the step.
Add a third, converted to paid, once people start paying. Use whatever email tool you already have. If it cannot filter by an event or contact property, a short recurring script that checks your database and sends the right email is enough at solo scale.
If you bill through Stripe, its docs say the customer.subscription.trial_will_end event is sent according to a Dashboard setting that defaults to three days before the trial ends, and that you can "use this event to send your own reminder email" (Stripe trials docs). That gives you a reliable trigger for the trial-end email without building your own timer.
The sequence at a glance#
Here is the structure we recommend for a solo founder with a 7 to 14 day trial. Days are approximate. Behavior decides who gets each email.
| When | Who gets it | Job | |
|---|---|---|---|
| Day 0 (signup) | Welcome | Everyone | Point to the one next step |
| 24 to 48 hours | Unblock | Only people not yet activated | Remove the likely blocker |
| Mid-trial | Stuck help or habit | Branch by activation | Rescue stalled users, deepen use for activated ones |
| Near trial end | Convert or help-or-close | Branch by activation | Ask for the sale, or offer honest help |
| Any time | Exit | Anyone who activates, converts or replies | Stop the current branch |
That is four or five emails per person, depending on their path. Nobody gets every email.
Email 1: The welcome email (one next step)#
The welcome email has one job: get the user to start the activation step. Skip the feature list, the founder's life story and the social links.
Sample (plain text):
Subject: Your first [result] takes about 5 minutes
Hi Sam,
Thanks for signing up for [Product]. The quickest way to see if it works for you is to [activation action], for example connecting your first [data source].
Start here: [single link to the exact screen]
If anything gets in the way, reply to this email. It comes straight to me.
[Your name], founder of [Product]
Notes on the copy:
- Only claim a time you have measured. If you have not timed setup yourself, drop the "5 minutes" and describe the step instead.
- Deep link to the exact screen, not the dashboard home.
- Invite replies. They are your best onboarding research and show which blockers Email 2 should address.
Email 2: The unblock email (only if not activated)#
Send this 24 to 48 hours after signup, and only to users who have not activated. Anyone who has already done the step should never see it.
The unblock email guesses at the most common reason people stall and removes it. Your support inbox and the replies to Email 1 will tell you what that reason is. Common ones include a missing integration, unclear first input, fear of breaking something or simply not having had time yet.
Sample:
Subject: Stuck on [setup step]?
Hi Sam,
Most people who haven't [activation action] yet get stuck at [specific step]. Here's the short version:
- [Step one]
- [Step two]
- [Step three]
Or skip it: reply with [the thing you need, such as a CSV or a URL] and I'll set it up for you.
[Your name]
The "reply and I'll do it" offer is something a solo founder can make and a large company usually cannot. It is the same hands-on approach that wins your first 10 paying customers.
Email 3: The mid-trial branch#
Around the middle of the trial, split users by whether they have activated.
Branch A: Stuck-user help (not activated)#
These users have had a welcome and an unblock email and still have not acted. Change the approach: ask a question instead of giving more instructions.
Subject: Quick question about [Product]
Hi Sam,
I noticed you haven't [activation action] yet. What were you hoping [Product] would help with?
One line is plenty. If it isn't a fit, that's useful to know too.
[Your name]
The replies tell you whether the problem is setup, positioning or the wrong audience.
Branch B: Habit email (activated)#
Activated users do not need help getting started. They need a reason to come back. Point them at the second most valuable action, the one that makes the product part of their routine.
Subject: Next: [second action]
Hi Sam,
Nice work on [what they did]. Most people who stick with [Product] also [second action], so [benefit] happens without you having to remember.
Set it up here: [link]
[Your name]
One habit email is enough. Activated users who feel nagged are a churn risk too.
Email 4: Near trial end, convert or help-or-close#
Time this email from the trial end date. If you use Stripe, the trial_will_end webhook is a good trigger. Note that Stripe can also send its own reminder: its compliance docs say that when customer emails are enabled, Stripe sends a reminder seven days before a trial ends, with a link for the customer to add or update their payment details (Stripe trial compliance). Check your settings so customers do not receive two reminders that contradict each other.
Branch A: Convert ask (activated)#
Subject: Your trial ends on [date]
Hi Sam,
Your [Product] trial ends on [date]. So far you've [concrete outcome, such as "sent 4 invoices"].
To keep going, pick a plan here: [link to billing]. [Plan] is [price] per [period], and you can cancel any time from settings.
If something is holding you back, reply and tell me.
[Your name]
Use their own usage as the argument, and say plainly what happens if they do nothing: a charge, a downgrade or a locked account. Your trial structure decides this, and our freemium vs free trial guide covers the choice of card-required, card-optional and reverse trials.
Branch B: Honest help-or-close (not activated)#
Do not send a stalled user a hard sales pitch. Offer one last route to value and make it easy to leave.
Subject: Before your trial ends
Hi Sam,
Your trial ends on [date], and it looks like you didn't get to [activation action]. If you still want to try it, reply and I'll extend your trial and help you set it up.
If [Product] isn't right for you, no hard feelings. A one-line reply telling me why would help a lot.
[Your name]
The extension offer is optional. Only make it if you will honour it quickly.
Exit rules: when the sequence must stop#
Exit rules matter as much as the emails themselves. Set these up before you turn the sequence on:
- Activated: remove from the not-activated branch immediately. Never send an unblock email to someone who has already done the step.
- Converted to paid: stop all trial emails. Move them to your normal product updates, if you send any.
- Replied: pause automation for that person and answer by hand. A reply means a conversation has started.
- Unsubscribed: honour it everywhere. Separate essential account emails, such as receipts and security notices, from onboarding messages.
An email that ignores what the user just did tells them nobody is paying attention.
Writing rules for solo founders#
- Send from a person, with a reply-to address you actually read. Plain text is often fine and gets replies.
- One job, one link. If an email needs scrolling on a phone, it is trying to do two jobs.
- Specific subject lines and no fake urgency. "Stuck on connecting Stripe?" beats "Getting started, part 2", and real trial end dates are urgent enough.
Metrics: how to tell if the sequence works#
Opens and clicks are easy to see, but they are not the goal, so treat them as secondary signals at best. Track these instead, ideally by weekly signup cohort:
| Metric | What it tells you |
|---|---|
| Activation rate | Share of new signups who complete the activation event within the trial. The main number. |
| Time to activation | Median time from signup to activation. Shorter usually means less drift. |
| Activation after each email | Share of recipients who activate within a day or two of an email. Shows which email does work. |
| Trial-to-paid conversion | Split by activated and not activated. If activated users rarely convert, the problem is value or price, not onboarding. |
| Reply rate and reply themes | Qualitative data on blockers. Tag replies by reason. |
| Early paid churn | Whether customers who converted after the sequence stay past the first renewal. |
Change one email at a time, wait for a few cohorts and compare. At solo-founder volumes you will rarely have enough signups for a statistically clean A/B test, so look for large, consistent differences and read the replies. We do not quote benchmark rates, because we have not found a primary source we trust for solo founders.
Frequently asked questions#
How many onboarding emails should a SaaS send?#
For a solo founder with a 7 to 14 day trial, four or five emails is usually enough: a welcome, an unblock email for people who have not activated, a mid-trial email that branches by behavior, and a trial-end email. Fewer, well-targeted emails beat a long fixed drip.
What is an activation event?#
It is the first action that shows a new user has got real value from your product, such as sending a first invoice, publishing a first page or connecting a first data source. Pick one that you can track and that retained customers almost always complete.
Should onboarding emails be plain text or designed HTML?#
Plain text is often fine for a solo founder. It reads like a note from a person, it is faster to write and change, and it invites replies. Use HTML only if you need screenshots or the brand calls for it.
When should onboarding emails stop?#
Stop the current branch as soon as the user completes the step the email is asking for, converts to paid or replies to you. A reply means a conversation has started, so continue by hand rather than with automation.
How is this different from reducing churn after customers pay?#
Onboarding emails work before and just after the first payment, getting users to value so they have a reason to stay. Reducing churn among paying customers also involves fixing failed payments, cancellation flows and cohort analysis, which our separate churn guide covers.
Where ZeroRaised fits#
ZeroRaised is a launch directory for products built without institutional VC or accelerator equity. A launch brings a burst of signups, and a behavior-triggered onboarding sequence is what turns those signups into activated users instead of a spike that fades. You can submit your product for free, and if you want more guides on growth and retention without investors, join the ZeroRaised newsletter.
Sources#
- Stripe: Configure trial offers on subscriptions, checked 6 Nov 2026
- Stripe: Manage trial compliance, checked 6 Nov 2026
- Stripe: Using webhooks with subscriptions, checked 6 Nov 2026
Frequently asked questions
How many onboarding emails should a SaaS send?
For a solo founder with a 7 to 14 day trial, four or five emails is usually enough: a welcome, an unblock email for people who have not activated, a mid-trial email that branches by behavior, and a trial-end email. Fewer, well-targeted emails beat a long fixed drip.
What is an activation event?
It is the first action that shows a new user has got real value from your product, such as sending a first invoice, publishing a first page or connecting a first data source. Pick one that you can track and that retained customers almost always complete.
Should onboarding emails be plain text or designed HTML?
Plain text is often fine for a solo founder. It reads like a note from a person, it is faster to write and change, and it invites replies. Use HTML only if you need screenshots or the brand calls for it.
When should onboarding emails stop?
Stop the current branch as soon as the user completes the step the email is asking for, converts to paid or replies to you. A reply means a conversation has started, so continue by hand rather than with automation.
How is this different from reducing churn after customers pay?
Onboarding emails work before and just after the first payment, getting users to value so they have a reason to stay. Reducing churn among paying customers also involves fixing failed payments, cancellation flows and cohort analysis, which our separate churn guide covers.