Lifecycle email sequences for a SaaS: five triggers and the rules between them
A SaaS needs five lifecycle email sequences before it needs anything else: one when somebody signs up, one when a trial is about to end, one after the first payment, one when a customer cancels, and one when an active user goes quiet. Each is triggered by something that happened to one person, each has an exit condition that takes that person out the moment the sequence stops making sense for them, and all five share one rule: no contact receives more than one email a day, whatever sequences they are in.
The rest of this article goes through each sequence (what it is for, how many messages, when they go out, when to stop) and then the rules that hold them together, which is where most setups go wrong.
What makes a lifecycle sequence different from a campaign?
A campaign is sent to a list at a moment you choose. A lifecycle sequence is sent to one person at a moment they choose, by doing something.
That changes three things. Enrolment is continuous: somebody enters every time the trigger fires, whether that is once a week or forty times a day. Timing is relative: "two days after sign-up", not "on the 12th". And the sequence has to know when to let go, because the person keeps moving while it runs. Somebody who upgrades on day three of a fourteen-day trial should not receive "your trial ends tomorrow" on day thirteen.
So every sequence below is described by four things: the trigger, the goal, the messages, and the exit condition.
What should the sign-up sequence do?
Trigger: an account is created. Goal: get the person to the first moment the product is useful to them, which your data can usually name (the first project created, the first import, the first invite sent). Exit condition: they reach that moment, or they unsubscribe.
Three or four messages over the first week or two is enough. The first goes out soon after sign-up and does one thing: points at the single next step. Not a tour of every feature. The later messages each remove one reason people stall, using what your paying customers actually did before they paid.
Write the exit on the activation event, not on time. If someone reached the useful moment on day one, the day-four email explaining how to get there is noise, and noise teaches people to ignore your name in their inbox.
What should the trial-ending sequence say?
Trigger: a trial will end in a few days. Goal: a decision, either way. Exit condition: they start paying, they cancel, or the trial ends.
Two messages is usually right: one a few days before the end, one the day before. Say plainly what happens when the trial ends (do they lose data, does the account drop to a free tier, are they charged automatically?). People are far more annoyed by a surprise than by a reminder.
This is the sequence where exit conditions matter most. A person who upgrades halfway through the trial must leave this sequence at once. They should not necessarily leave the sign-up sequence, though: paying early does not mean they have finished setting up, and the onboarding emails may still be useful. Each sequence needs its own exit, not one global "stop everything when they pay".
What should happen after the first payment?
Trigger: the first successful payment. Goal: make the purchase feel like a good decision and widen the use of the product. Exit condition: time, or a cancellation.
One or two messages. The first is a thank-you from a person, with the receipt and invoice information in a separate transactional message rather than buried in it. The second, a week or two later, points at one feature that paying customers use and trial users rarely find, or asks a single question: "What almost stopped you from buying?" The answers to that question are some of the most useful copy you will ever collect.
Do not start selling the next plan in the same week. The person has just paid you.
How do you write a churn sequence?
Trigger: a subscription is cancelled. Goal: learn why, and leave the door open. Exit condition: they reply, they resubscribe, or the sequence ends.
One message is often the right length. Ask why, in a sentence, with a reply address that reaches a human. If the reason is something you have since fixed, a second message weeks later saying exactly that is fair. A series of discounts sent to someone who has told you they are leaving is not; it trains your customers to cancel in order to negotiate.
Be careful with consent here. A cancellation ends the contract, and depending on how a person subscribed to your mail and where they live, it can change what you are allowed to send them. A short, factual message about the cancellation itself is the safe default.
How do you bring back someone who has gone quiet?
Trigger: an active user has not done the product's main action for a period that is long relative to their normal rhythm. For a daily tool that might be two weeks; for a monthly reporting tool, two months. Goal: find out whether they still have the problem. Exit condition: they come back to the product, or they unsubscribe.
This sequence depends on product events, not billing events, so it needs your analytics data joined to the contact. Two messages at most. The first is a specific reminder of what they used to do ("your last report was generated on the 3rd") and what has changed since. The second, if they did not return, is a plain question about whether the product still fits.
A paying customer who has gone quiet is a cancellation that has not happened yet. This is often the sequence with the most revenue at stake, and the one most teams build last.
What rules should hold the sequences together?
Five sequences built separately will collide. The rules between them matter as much as the messages.
One email per contact per day, across every sequence. Somebody who signs up, starts a trial and hits a usage threshold on the same day should not receive three emails that evening. When two sequences want the same person on the same day, one waits. Decide in advance which takes priority: a message about money (trial ending, failed payment) usually comes before a message about learning the product.
Exit conditions are per sequence and checked before each send. Not only at enrolment. A person's state changes while they are in a sequence, and the check that matters is the one made just before the next message leaves.
An unsubscribe stops every marketing sequence. Not only the one they clicked from. Someone who unsubscribes from the onboarding emails and keeps receiving win-back emails will report you as spam, and they will be right. Transactional messages (receipts, password resets, security notices) are a separate category and keep going.
A hard bounce or a spam complaint stops everything for that address. The address is either dead or the person has told their mailbox provider they do not want you. Either way, writing again harms your domain.
Approve the path once, then let it run. Reviewing each individual send defeats the point of a triggered sequence. Review the whole path carefully once (every message, every delay, every exit), then watch the results and revise the sequence as a whole.
How do you measure a lifecycle sequence?
Against the goal you wrote for it, not against opens. The sign-up sequence is measured by the share of new accounts that reach activation; the trial sequence by trial-to-paid conversion; the quiet-user sequence by the share that come back and keep using the product. Compare to the period before the sequence existed, keep in mind that small numbers are noise, and change one thing at a time so you can tell which change did what.
Where Canopus fits
Canopus is an autonomous growth manager for SaaS: it writes your strategy from Stripe and your product, drafts the campaigns, sends them from your own domain once you approve them, and tells you what each one earned. Lifecycle sequences are part of that. The triggers come from your Stripe and PostHog connectors and land on contacts in the CRM. Enrolment is continuous, you approve the whole path once, and each sequence carries its own exit condition: upgrading mid-trial ends the trial reminder and leaves the onboarding running. One email per contact per day holds across every sequence. Messages are sent from your own domain with one-click unsubscribe, and nothing goes out before you approve it.
The comparison with a standalone sequencing tool shows what changes when the sequences read the same CRM and billing data, and the pricing page gives the monthly price excluding VAT.