A five-email SaaS onboarding sequence runs like this: a welcome email the moment someone signs up, a first-action nudge about a day later if they have not done the action, a help email when setup stalls, a depth email after their first success, and a decision email two to three days before the trial or activation window ends. Each email has one job, one button and a rule that stops it from sending once the job is done. Treat the timings below as starting values and replace them with your own data as it comes in.

The right count depends on how long a user takes to reach value. Hostinger's guide suggests about 3 emails for simple journeys with one obvious next step, 5 to 7 for products that need setup and education first, and 8 or more for long onboarding periods. MailerLite puts a typical SaaS sequence at 3 to 10 emails. Five suits a self-serve product where the first useful result takes days. Kompassify's framework has seven emails, and the five here leave out its proof and expansion emails, which you can add once the core five are working.

Decide the activation event first

Before writing anything, pick the one in-product action that counts as activated. For an invoicing app it might be sending a first invoice. For a scheduling tool it might be connecting a calendar. Every stop rule, send condition and success metric in the sequence hangs on that choice, so look at which early action your retained users have in common and use that.

Timing: behavior first, clock second

Kompassify recommends behavior triggers as the primary logic, with a time-based fallback so inactive users still receive something. Calendar timing suits deadline messages such as a trial ending. Behavior triggers only work if your event tracking is reliable, so if you cannot track product events yet, start with delays and add skip conditions as the events become available.

Hostinger suggests a follow-up within one or two days of signup and later emails spaced several days apart, with faster sends for short trials. One more rule is worth adding. Send at most one onboarding email per day, and when a user qualifies for two, send the more specific one.

The five emails: an illustrative outline

Illustrative sample. The outline below is for a fictional invoicing app with a 14-day trial, where activation means sending a first invoice. The subject lines and merge fields are examples of structure, not results from a real product.

Email 1: Welcome (immediately)

  • Job: confirm the account and name one next step.
  • Send if: always. Skip if: never.
  • Subject idea: Your account is ready: start with one invoice
  • Body: one button that opens the first step, and a line saying replies reach a person.
  • Track: click-to-action rate and bounces.

Email 2: First-action nudge (about 24 hours later)

  • Job: bring the user back to where they stopped.
  • Send if: no invoice sent. Skip if: one was sent.
  • Subject idea: Pick up where you left off
  • Body: a deep link to the exact step, not to the dashboard.
  • Track: share of recipients who send the first invoice within 48 hours.

Email 3: Stall recovery (about 48 hours after last activity)

  • Job: name the likely blocker and offer a way past it.
  • Send if: the user started setup, for example added a client, but has not finished. Skip if: setup is complete.
  • Subject idea: Stuck on adding a client?
  • Body: a two- or three-sentence answer to the most common problem at that step, a help link, and an invitation to reply. When a user qualifies for emails 2 and 3 together, send this one.
  • Track: replies, help-link clicks and completion of the stalled step.

Email 4: Depth (about a day after first success)

  • Job: introduce the second thing retained users do, with no upsell.
  • Send if: activated. Skip if: the user already used the feature.
  • Subject idea: Next: stop retyping the same invoice
  • Body: one feature, one short explanation of the problem it solves, one button.
  • Track: adoption of that second feature within a week.

Email 5: Decision (two to three days before the trial ends)

  • Job: recap what the user did, say what happens at trial end, and give one button to choose a plan.
  • Send if: not yet converted. Skip if: converted.
  • Subject idea: Your trial ends in 3 days. Here is what you have set up
  • Body: merge fields such as {{invoice_count}} and {{client_count}}. For users who never activated, replace the recap with an offer of help on the stalled step.
  • Track: trial-to-paid conversion, split by activated and not activated.

Subject-line approach

Name the step or the outcome, and use the user's own progress when you have reliable data for it. Kompassify advises leading with the outcome over the mechanic. Userpilot's onboarding examples say generic deadline notices such as a plain trial-ending warning work worse than lines that show the user's own work or a concrete next step. The CAN-SPAM guide adds a legal limit: do not use deceptive subject lines, and make sure the subject matches what the email says.

  • Names a specific step or result, such as Add your first client, rather than a category such as Getting started.
  • Puts the specific words first so they survive truncation on a phone.
  • Uses a merge field only when the data behind it is reliably correct.
  • Matches the email body. If the subject promises a tip, the email delivers one.
  • Gets tested one variable at a time, judged by clicks and product actions rather than opens.

What to track

Hostinger separates email-level metrics from sequence-level ones, and the split is useful. Email-level numbers tell you which message to fix. Sequence-level numbers tell you whether onboarding is working at all.

  • Per email: click-to-action rate (the share of clickers who finish the task, which Kompassify uses to spot problems on the page the email links to), unsubscribe rate, spam complaints and bounces.
  • Per sequence: activation rate by signup cohort, time to activation, and where users drop out between emails. Hostinger calls activation rate the most important measure of whether a sequence works.
  • Cohort comparison: users who received the new sequence against users who received the old one. Hostinger advises against reacting to a single cohort or a short-term swing, so wait for a repeated pattern.

Treat opens as a diagnostic at most. Apple's Mail Privacy Protection preloads images, including tracking pixels, and Postmark says senders can see opens that no person made, up to a 100% open rate for Apple Mail recipients. Postmark points to unsubscribes, bounces and spam reports as steadier signals.

Stop rules and compliance

End the sequence when the user activates and move them into regular lifecycle messaging, which our guide to email automation workflows for SaaS covers. Kompassify calls these cancel conditions the most important thing to build first, because continued sends cost deliverability and goodwill.

Classification needs a decision too. A welcome email that confirms an account sits close to the transactional or relationship side, but the FTC says the law views those categories narrowly and that the primary purpose of a message decides. Emails 2 to 5 push product use or a purchase, so treat them as marketing: include an unsubscribe link and a valid postal address, and honor opt-outs quickly. Yahoo asks for unsubscribes to be honored within 2 days and Google recommends 48 hours, while CAN-SPAM allows up to 10 business days.

Google's bulk-sender rules, which add one-click unsubscribe for marketing messages and a spam-complaint rate below 0.10%, apply once you send close to 5,000 messages a day to Gmail accounts. This is a summary of the sources, not legal advice.

If you want the five emails written and set up in your own email platform, the Automated Email Sequence is the closest fit, and the Email Marketing Automation page describes the service.