Lifecycle, Onboarding and Nurture Email Flows for SaaS

#01Which lifecycle flows does a SaaS company need?

For copy prompts and AI drafting of these flows, see Claude for lifecycle email copy. This lesson focuses on structure.

#02How do you design trial onboarding?

Step 1: define activation

Activation is the first event that predicts a user will pay or retain. Find it in product data by comparing converted and non-converted trials. For an AP product, "approved the first invoice through a workflow" is a stronger signal than "logged in twice".

Step 2: list the steps to activation

For example: connect ERP, invite approver, upload first invoice, approve first invoice.

Step 3: map one email per blocker

Each email checks the user's state before sending. If they have already invited an approver, skip that email.

Step 4: add branching and exits

• Activated: exit to a "getting more value" flow and notify sales if the account fits.
• No login for 5 days: switch to a shorter "need help?" path.
• Booked a demo: pause marketing emails; sales takes over.

#03How do you design lead nurture?

Nurture is for people who are interested but not evaluating. The aim is to be helpful often enough to be remembered.

1. Pick themes by role: for AP managers, month-end close, fraud prevention, approval speed.
2. Mix formats: practical tip, short case study, benchmark, invitation.
3. Space it: weekly or fortnightly, merged with the newsletter rather than in addition to it.
4. Score intent: pricing visits, integration page visits and demo-page views raise the lead score and trigger a sales notification or high-intent email (lesson 9).
5. Exit: after six to eight months with no click, move to the newsletter only or sunset.

#04How do you prevent email overload?

• Global frequency cap: for example, no more than one marketing email per day and four per week per contact.
• Priority order: transactional, then onboarding, then sales-triggered, then nurture, then newsletter.
• Suppression rules: contacts in an open deal skip nurture; customers skip trial and lead flows.
• Quiet hours: send in the recipient's local working hours for B2B.

#05How do you prove a flow works?

Put 10% of new entrants in a holdout that receives no flow emails (only transactional). Compare the goal rate after 30 or 60 days. Without a holdout, you cannot separate the flow's effect from people who would have activated anyway.

#06Worked example: Ledgerline

Ledgerline is a fictional accounts-payable software company. Figures are illustrative, not benchmarks.

Ledgerline's trial onboarding is seven emails on fixed days, sent whether or not users finished each step. Activation is not defined. Trial-to-paid is flat.

Walkthrough

1. Define activation: analysis shows trials that approve an invoice within 7 days convert at three times the rate of others (illustrative). Activation is "first invoice approved".
2. Map blockers: ERP connection is the biggest drop-off.
3. Rebuild the flow with state checks: emails for completed steps are skipped.
4. Add a person: day 3 plain-text email from a solutions engineer; replies go to a shared inbox with a 4-hour response target.
5. Holdout: 10% of new trials.
6. Result after 60 days: activation rises from 22% to 31% in the flow group versus 21% in holdout (illustrative). The team keeps the flow and tests day 1 copy next (lesson 14).

#07Common mistakes

• Writing onboarding before defining activation.
• Time-based drips that ignore behaviour.
• No exit rules, so customers get trial emails.
• Nurture and newsletter both sending weekly.
• No holdout, so nobody can prove impact.

#08Try it yourself

Pick one flow you run. Write its trigger, goal, exits and branches on one page. List each email with the condition that sends or skips it. Set up a 10% holdout and a date to read the result.

#09Quick quiz

1. What should you define before writing onboarding emails? Answer: The activation event.

2. Why use a holdout group? Answer: To measure the flow's real effect against people who would have converted anyway.

3. What should happen when a trial user books a demo? Answer: Pause marketing emails and let sales take over.

4. What is a sensible priority order for messages? Answer: Transactional, onboarding, sales-triggered, nurture, newsletter.

#10What should you check before the next lesson?

• Activation event defined and tracked.
• Each flow has trigger, goal, exits and holdout.
• Global frequency cap in place.
• Replies go to a monitored inbox.

Previous: Segmentation and personalisation · Next: B2B newsletter strategy

Or return to the Email Marketing for Marketers track.

Related: A/B testing that holds up · Copywriting and subject lines · Claude for lifecycle email copy

#11Common questions

How many emails should a SaaS onboarding sequence have? As many as there are steps to first value, usually four to seven over the trial, each triggered or skipped by what the user has done. Exit users who reach activation into a different flow.

What is the difference between onboarding and nurture? Onboarding helps a user reach value in the product. Nurture educates a lead who is not yet ready to evaluate, so they think of you when they are.

Should lifecycle emails come from a person or the brand? Use a real person for emails that invite replies, like a check-in from a customer success manager, and the brand for product updates. Make sure replies go to a monitored inbox.

Do lifecycle emails need one-click unsubscribe? If they are marketing or promotional, yes, for bulk senders. Pure account or transactional notices do not, but most onboarding and nurture emails count as marketing.