Email Automation Strategies for SaaS: Six Lifecycle Flows
By Rowan Ellis · Updated October 7, 2026
Six SaaS lifecycle email flows with triggers, exit conditions and failure points, plus list prices for Customer.io, Loops, Brevo and ActiveCampaign.
Lifecycle email for a SaaS product comes down to six flows, each started by an event your product or billing system emits: an account is created, a trial end date approaches, an invoice fails, a subscription ends, usage crosses a limit, or a user goes quiet. Customer.io and Loops handle event-driven branching, Brevo and ActiveCampaign cover contact-based automation with cheap volume or a built-in CRM, and any of them can run the failed-payment flow. This guide gives the trigger, exit condition and typical failure point of each flow, and what the four tools cost at list price.
Which Tool Type Fits Lifecycle Flows
The billing unit matters more than the feature list, because a lifecycle program has many people and few emails per person. List prices below are read from each vendor's pricing page on October 7, 2026.
| Tool | Billing unit | List price | Where it fits |
|---|---|---|---|
| Customer.io | Profiles | Essentials from $100/month billed monthly ($145 at 10,000 profiles, $235 at 20,000); Premium from $1,000/month billed yearly | Event-driven journeys with branching on attributes |
| Loops | Subscribed contacts | Free for up to 4,000 sends in a rolling 30 days, with a Loops footer; Growing Audience shown at $99 for 9,998 subscribers | Small SaaS teams wanting sequences and transactional sends in one place |
| Brevo | Monthly email volume | Free at 300 sends/day; Starter from $9 and Standard from $18, both starting at 5,000 emails/month | Low-volume flows where per-contact pricing would hurt |
| ActiveCampaign | Contacts | Starter from $15, Plus from $49, Pro from $79, Enterprise from $145, each at 1,000 contacts, billed annually | Teams whose sales follow-up lives next to the emails |
Three details on those pages change which flows you can afford to build. Brevo's Standard plan is the one that lists automation, A/B testing and advanced reports. ActiveCampaign's Starter plan allows 5 actions per automation, so count the steps in your longest flow before choosing it. Loops' free plan only covers sends to the 1,000 newest contacts.
What the Billing Unit Does to Your Bill
Take a product with a three-email onboarding sequence. On a volume-priced tool, 150 sign-ups a day settle at 450 onboarding emails a day, which is already above Brevo's free limit of 300 sends a day before a single trial or billing email goes out. On Loops' free plan, a four-email onboarding sequence uses the 4,000-send allowance up after 1,000 sign-ups in a rolling 30 days.
On a profile-priced tool the same product pays for people, not sends. Customer.io lists $145 per month at 10,000 profiles and $325 at 30,000, so 20,000 more profiles add $180, which matches the $0.009 per additional profile on its pricing page (20,000 x $0.009). A free tier with a large sign-up base is therefore priced like a large customer base even if most of those people only ever receive one email.
Six Flows, With Triggers, Exits and Failure Points
Every flow below is described the same way: what starts it, what ends it, and where it usually breaks. The exit condition is the part teams skip, and it causes most of the embarrassing emails.
Flow 1: Onboarding That Branches on One Event
Trigger: account created. Pick the one event that proves the user got value (for a project tool, "created first project"; for an API product, "first successful request") and branch on that event alone before adding anything else. If it arrives within a day, send the next step in the product, such as inviting a teammate. If it has not arrived after 24 hours, send one email that names the single missing step and deep-links into it.
Exit: the activation event, or a paid subscription, whichever comes first.
What goes wrong: late events. If the activation event reaches the email tool through a queue or a warehouse sync that lags by hours, the flow tells someone who already created a project that they have not created one yet. Measure the delay between the action and the event appearing on the profile, and do not set a wait shorter than that delay.
Flow 2: Trial Ending, Scheduled From the End Date
Trigger: a fixed offset before a trial end date stored as an attribute on the profile, not a delay counted from sign-up. Two emails are enough: one three days before the end that lists what the user has set up and what will be locked, and one on the last day that says what happens to their data and how to add a card.
Exit: a payment method added, a subscription started, or the trial extended.
What goes wrong: extensions. When support extends a trial by a week, a flow that counted 11 days from sign-up still sends "your trial ends today" in the middle of the extension. Recompute the end date attribute whenever the trial changes, and have the flow re-read it before each send. Accounts with an open sales conversation belong in an exclusion segment as well, otherwise the rep and the automation contradict each other in the same inbox.
Flow 3: Failed Payment, Timed Against the Retry Schedule
Trigger: the failed-invoice event from your billing system (Stripe's is invoice.payment_failed). The first email goes out immediately and carries one thing: a link to a page where the customer can update the card, such as Stripe's customer portal. Later emails follow each retry attempt rather than a calendar of their own.
Exit: the invoice-paid event, or the subscription being cancelled by the billing system after retries run out.
What goes wrong: two clocks. The billing system decides when it retries a card; the email tool decides when it writes. If the email promises "we will try again tomorrow" and the next retry is five days away, the message is wrong. Configure the retry schedule in Stripe or Paddle first, then hang one email on each failed attempt. The second failure mode is a missed exit: a customer who fixes the card at 9:02 and then receives "your access will be paused" at 9:15. Make each send check the current invoice status, not elapsed time.
You can build this on any event-capable tool in the table above. Specialist options exist too: Churnkey's pricing page lists Payment Recovery with its Starter plan at $250 per month billed yearly, for teams with under $5k a month of churn volume. Sequenzy is a billing-aware email tool: per sequenzy.com, a Stripe invoice.payment_failed event starts a dunning email flow with a card-update page, and the retry logic itself stays in the billing system. Its pricing page lists a free plan with 2,500 emails a month and $19 a month for 15,000, with unlimited contacts.
Flow 4: Win-Back, Split by Why They Left
Trigger: the subscription-ended event, after a wait. Before any message goes out, split the audience. A customer whose card failed through every retry did not decide to leave, so they get a "restore your account" message with the card-update link, not a survey. A customer who cancelled on purpose gets a short email with one-click reasons, where each link records the chosen reason as an attribute. A second email, sent only when something has shipped that matches the stated reason, is worth sending; a generic "we miss you" is not.
Exit: a new subscription, or an unsubscribe.
What goes wrong: sending to people who should be gone. Accounts deleted after a data-removal request, and people who unsubscribed from marketing mail, must be suppressed before this flow starts. Winning back a person who asked to be forgotten is a compliance problem, not a retention tactic.
Flow 5: Usage Threshold, Once Per Billing Cycle
Trigger: your product computes usage against the plan limit and sends an event when it crosses a line you choose, for example 80% of seats or monthly volume. The email goes to the billing owner of the account, not to every member, and explains what the next plan unlocks using the numbers the account already has.
Exit: a plan change, or the end of the billing cycle.
What goes wrong: repeated events. If the product emits the threshold event each time usage is recalculated, an account sitting at 82% is eligible on every page load. Emit the event once per cycle per limit, and add a rule in the flow that skips anyone who already received it in the last 30 days. A related slip is routing the message to the wrong person, so confirm which contact is stored as the account's billing owner.
Flow 6: Inactivity, Defined by a Real Event
Trigger: no key event for N days, where N comes from your own data: look at how long active users normally go between sessions and set N comfortably above that. Define activity by the event that signals real use, not by login. An API-only customer may never log in and still be your healthiest account. Send a short check-in that names the last thing the user did, and a second message only if a relevant feature has shipped since.
Exit: any key event.
What goes wrong: teams and seasons. A team account that pauses over a holiday is not at risk, and one inactive seat in a ten-person account should not trigger a message to the whole company. Evaluate inactivity per account for team products and per user for single-seat ones.
Rules Every Flow Needs
Entry limits. A flow should run once per user per trigger, and re-enter only after the exit has fired. Without this, one noisy event produces the same email several times.
Priority. When a customer is in the failed-payment flow, hold the win-back, usage and inactivity flows. A simple way to do it is an attribute such as in_dunning that the failed-invoice event sets and the paid event clears, with the other flows excluding anyone who has it.
Separate billing notices from promotions. A failed-payment email is a service message; an upgrade nudge is marketing. Keep unsubscribes honoured in marketing flows and make sure billing notices travel on a stream that your tool treats as transactional. Loops' pricing page, for example, lists transactional sends as included on its paid plan.
Test with a profile you control. Push each trigger event by hand, then push the exit event partway through, and confirm the flow stops. This one test finds most missed-exit bugs before a customer does. Our automation mistakes guide covers the wider failure list.
Which Tool for Which Team
Choose Customer.io when your product already sends events and you want branches on attributes such as plan, role or last action. Essentials starts at $100 a month, and the profile-based unit suits products with a bounded customer base. See the Customer.io vs Braze comparison if you are weighing larger platforms.
Choose Loops when you are a small SaaS team and want onboarding, announcements and transactional email without much setup. The free plan has a send limit and a footer, so plan to move to the paid plan before real traffic arrives.
Choose Brevo when sending volume is modest and per-contact pricing would be wasteful, for instance a large free tier that gets only a handful of messages. Its Free plan lists 2,000 contacts in marketing automation, so confirm your active contact count against that figure.
Choose ActiveCampaign when the same person who reads the lifecycle email will be followed up by a salesperson. Starter, Plus, Pro and Enterprise include 1, 1, 3 and 5 users respectively, which matters if sales and marketing both need seats.
Questions Teams Ask Before Building
Which flow should I build first?
Failed payment, then onboarding. Both have unambiguous triggers and exits: an invoice either fails or it does not, and a user either reaches the activation event or does not. Trial ending comes third because it depends on a clean end-date attribute. Usage, inactivity and win-back need more definitions and are easier once the first three are running.
Should dunning emails come from the billing tool or the email tool?
Retries come from the billing tool, and the messages can come from either. If your email tool receives the failed-invoice event, it can hold the whole conversation. A dedicated service such as Churnkey bundles recovery campaigns and retries, at a monthly price tied to your churn volume.
Do I need a separate transactional email service?
Not always. Loops lists transactional sends on its paid plan, so a small team can run both streams in one tool. Teams sending password resets at high volume often prefer a dedicated sender; our email automation category lists the options.
How do the events get from my product to the email tool?
Directly through the tool's API or a tracking library, through a connector such as Zapier or n8n, or through a customer data layer. Each hop adds delay and a place to fail, which is why the late-event problem in Flow 1 is common. The integration guide compares the connector options by billing unit, and the billing automation category covers the billing-side tools.
Ready to pick a tool for these flows?
Compare email automation tools built for SaaS.
View Email Automation Tools