3 Ways to Decide How Many Emails Your SaaS Welcome Sequence Needs

    November 16, 2026
    11 min read
    By Tamsin Velkovane
    Share this article

    A product manager opens the email tool on a Monday morning and finds the onboarding sequence that a former growth lead set up two years ago. It has 11 emails. Email 4 still describes a dashboard that was redesigned last spring. Email 7 promotes an integration the company dropped.

    The trial is 14 days long, but the last email goes out on day 21, a week after most free users have already expired. Nobody knows which of these messages helps anyone activate, and the head of product wants a recommendation by Friday: cut it, rebuild it, or leave it alone.

    That situation is common in SaaS companies, and the question behind it is almost always phrased as "how many emails should a welcome sequence have". Blog posts answer with a number, usually 3 to 7. The number on its own is not useful, because a project management tool with a 5-step setup and a note-taking app with a single "aha" action need very different sequences.

    This memo sets out the decision, three ways to arrive at the count, how to space the sends, and how to check whether the emails do anything at all. Figures marked illustrative are invented for the example; the method is what transfers.

    The decision: a fixed drip or an activation-triggered sequence

    There are two basic designs, and the count follows from which one you choose.

    A fixed drip sends the same emails to everyone on a schedule: day 0, day 1, day 3, day 5, and so on. It is easy to build in any email platform and easy to reason about. Its weakness is that it ignores what the user did. Someone who invited three colleagues on day 1 still receives the "invite your team" email on day 4, which makes the product look like it is not paying attention.

    An activation-triggered sequence sends emails based on product events. If a user has not created a first project within 24 hours, they get the "create your first project" email. If they have, they skip it and move to the next step.

    The count is no longer fixed: a fast activator might receive 3 emails, a stalled user 8. This design needs event tracking flowing into the email tool, usually through a customer data platform or a direct integration, and it needs someone to maintain the rules when the product changes.

    Most product teams end up with a hybrid. A small number of emails go to everyone because they carry information that does not depend on behaviour: the welcome itself, the trial end reminder, a note from the founder. The rest are conditional on activation steps.

    Here is the recommendation in short. If you cannot get at least your 3 to 5 key product events into the email tool within a sprint, start with a fixed drip of 4 to 6 emails and plan the migration. If you can, build the hybrid now, because every month spent on a pure time-based drip is a month of sending irrelevant emails to your best users.

    How many emails: three ways to arrive at the number

    The title promised three approaches. Each gives a defensible count; using two of them and comparing the results is a good sanity check.

    The first approach counts activation steps. Write down the actions a new account must take before it is likely to stay. For a team collaboration tool this might be: create a workspace, connect a data source, invite at least two teammates, complete a first shared task. Four steps.

    Give each step one primary email and allow at most one follow-up for users who stall. Add the welcome, a trial-end reminder and a last-chance email. That gives a ceiling of 4 + 4 + 3 = 11 messages for the slowest user, and around 5 for someone who completes everything quickly.

    The second approach works back from the trial clock. A 14-day trial with a minimum gap of 1 day early and 2 to 3 days later can hold about 7 sends before it starts feeling like spam. A 30-day trial can hold 9 or 10. A freemium product with no end date needs a different logic: front-load 4 or 5 emails in the first 10 days, then switch to monthly product updates.

    The third approach uses your own data. Pull the last 6 months of signups and find the day on which most eventual paying customers completed their final activation step. If 80% of converters were activated by day 6, then emails after day 8 are mostly reaching people who are unlikely to convert, and the count should shrink. If activation is spread across 3 weeks, a longer sequence is justified.

    When the three approaches disagree, trust the data-driven one, then check it against the activation step count. The trial clock is a constraint, not a target.

    Spacing the sends around the trial clock

    Intervals matter as much as the count. Early emails should come close together because intent is highest in the first 48 hours after signup. Later emails should be further apart and tied to deadlines. The table below shows an illustrative hybrid schedule for a 14-day trial with four activation steps.

    Send Timing Who gets it Purpose
    Welcome Immediately after signup Everyone Confirm access, one link to the first step
    Step 1 nudge 24 hours if workspace not set up Stalled users only Show the 2-minute setup path
    Step 2 nudge Day 2 to 3 if no data source connected Stalled users only One integration, one screenshot
    Team invite Day 3 to 4 if fewer than 2 invites Stalled users only Explain why the product works better with colleagues
    Founder note Day 5 Everyone Plain text, invites a reply
    Use case email Day 7 Activated users One advanced workflow to deepen usage
    Trial ending Day 11 Everyone not yet paid Three days of warning, plan comparison
    Last day Day 14 Everyone not yet paid Short, one call to action

    Two details in the table are easy to miss. The stalled-user nudges wait a fixed time after the expected action, not after the previous email, so a user who stalls on step 1 does not get the step 2 nudge the next morning. And the trial-end emails go out on fixed days regardless of activity, because their job is to communicate a deadline, and a deadline has to be predictable.

    Time of day matters less than people think. For B2B tools, sending around the start of the recipient's working day in their own time zone tends to do well, and most platforms can do this from the signup location. The bigger risk is the opposite: an email platform configured in one time zone sending the "your trial ends today" message at 2 a.m. for half your users.

    Finally, watch the gap at the weekend. A user who signs up on Friday afternoon should not receive three nudges before Monday. A simple rule that delays conditional emails falling on Saturday or Sunday to Monday morning removes most of that problem without extra logic.

    Worked example: sizing the sequence with an activation formula

    To judge whether an extra email is worth sending, you need a way to estimate what it adds. A simple model is enough for a first pass.

    incremental_paid = signups_reaching_step * stall_rate * nudge_recovery * step_to_paid_rate
    email_value = incremental_paid * monthly_price * expected_paid_months
    

    Here stall_rate is the share of users who reach a step but do not complete it unaided, nudge_recovery is the share of those stalled users who complete the step after the email, and step_to_paid_rate is the conversion rate of users who complete the step.

    Illustrative numbers. A product gets 2,000 trial signups a month. Of those, 1,400 create a workspace (step 1). Of the 1,400, 60% stall on connecting a data source (step 2), so 840 users are stuck. A holdout test showed that the step 2 nudge recovers 9% of stalled users, which is about 76 users.

    Users who connect a data source convert to paid at 18%, so the email produces around 14 extra paying accounts a month. At $40 a month and an expected 14 months of paid life, each account is worth $560, and the email is worth about 14 x $560 = $7,840 in lifetime revenue per monthly cohort.

    Now compare a second follow-up for the same step. Its recovery rate on users who ignored the first nudge is likely to be lower, say 3%. Of the 764 still stuck, that recovers about 23 users and 4 paying accounts, roughly $2,240.

    Still positive, but it also adds unsubscribes and complaints. If the unsubscribe rate on that follow-up is 1.5% of 764, you lose about 11 contacts from future marketing. For most SaaS teams that trade is acceptable on a high-value step and not acceptable on a low-value one.

    Run the same arithmetic for every conditional email. The ones with the lowest value are your candidates for removal, and the count of emails becomes an output of the model rather than an opinion.

    Risks, owners and the checklist before you ship

    The rebuilt sequence will fail quietly unless three risks are covered.

    The first is drift. The product changes every sprint and emails do not. Screenshots go stale, links break, features get renamed. Assign one owner, usually the PM for onboarding or the lifecycle marketer, and put a quarterly review of every email in their calendar. When a release touches an activation step, the release checklist should include "update the matching onboarding email".

    The second is deliverability. Since February 2024, Gmail and Yahoo require bulk senders to authenticate mail with SPF, DKIM and DMARC, to support one-click unsubscribe, and to keep spam complaint rates below 0.3%. Onboarding mail usually goes out from the same domain as product notifications, so a badly targeted welcome sequence can hurt password reset delivery too. Some teams send lifecycle email from a subdomain to isolate that risk.

    The third is measurement. Open rates have been unreliable since Apple Mail Privacy Protection began preloading images in 2021, so do not judge the sequence by opens. Judge it by activation rate and trial-to-paid conversion against a holdout group that receives only the welcome and the trial-end emails. A 10% holdout for 4 to 6 weeks is usually enough for a product with a few thousand signups a month.

    Before launch, run through this list:

    • Every conditional email has a clear trigger event and an exit condition.
    • Users who complete a step are removed from that step's nudges within an hour.
    • The welcome email has one primary link, not a menu of six.
    • Trial-end emails show the actual end date in the user's time zone.
    • Weekend sends are delayed to Monday for conditional nudges.
    • A 10% holdout group is defined and excluded from conditional emails.
    • SPF, DKIM and DMARC pass for the sending domain, and one-click unsubscribe works.
    • Every screenshot matches the current UI and every link has been clicked once.
    • Converting to paid moves the user out of the trial sequence immediately.
    • An owner and a quarterly review date are written into the team's documentation.

    Questions product teams ask about welcome sequences

    Should the welcome sequence stop when a trial user converts to paid? Yes for the trial-specific emails, but move the person into a short paid onboarding track of 2 or 3 messages about seats, billing and admin settings, since new payers churn most in their first 60 days.

    Do plain-text emails work better than designed templates for onboarding? For founder-style notes and nudges plain text often gets more replies, while feature walkthroughs usually need one screenshot or a short GIF; test both on the same step rather than switching the whole sequence.

    How should a welcome sequence handle users who signed up through a teammate invite? Invited users skip workspace setup, so give them a separate 2 to 3 email track focused on their first personal action, such as commenting or completing an assigned task, and suppress the admin setup emails.

    Is it worth sending a welcome email in the user's language? If more than about 10% of signups come from one non-English market, localising the first 3 emails is usually cheap and lifts click rates; the later feature emails can wait until you see whether that segment activates.

    There are cases where you should not build any of this yet. If your product has fewer than a few hundred signups a month, a holdout test will take months to read, and a founder writing personal emails to each new account will teach you more than an automated sequence.

    If you have not defined your activation steps, an email sequence will simply automate guesswork; do the activation analysis first. And if the in-product onboarding is broken, with a setup flow that loses half of users on one screen, emails will only send more people back to that screen. Fix the product step, then write the email that points to it.

    Related Articles