Lesson 1: Map Your Customer Lifecycle

By the end of this lesson you’ll have one page on a wall: seven or so stages, one metric under each, every email you currently send pinned to the stage it belongs to, and a red mark on every stage where nothing goes out. That page is the whole rest of this course. Everything after it is implementation.

Set aside two hours. Open your product analytics tool, your email platform and a blank spreadsheet.

Why generic lifecycle templates produce dead sequences

Because they define stages by intent, and intent isn’t queryable. The standard template gives you awareness, consideration, decision, retention, advocacy. Try writing a trigger for “consideration”. You can’t, so you end up approximating it with a time delay, and a time delay is what turns lifecycle email into a newsletter with extra steps.

Your stages should be behaviour boundaries. Each one is a thing that happens in your database on a specific row at a specific timestamp. account.created. first_report_shared. seat_count >= 3. days_since_last_login > 14. If you can’t write it as a query, it isn’t a stage, it’s a mood.

How to draw stages from your own funnel data

Start at the end and work backwards. Pull your last two quarters of paying accounts and ask what they all did in their first two weeks that the churned accounts didn’t. In most products the answer is embarrassingly simple: they connected a data source, or they got a second person in, or they completed one specific workflow end to end.

That behaviour is your activation boundary. Everything before it is one stage, everything after it is another. Now do the same for expansion and for churn risk. Three boundaries found from data beats seven invented in a workshop.

Here’s a self serve map and a sales assisted map for the same fictional product, Cadence Analytics, a B2B product analytics tool at roughly $8K ACV.

Stage	Self serve boundary	Sales assisted boundary	Typical duration
Signup	Email verified	Demo booked	Day 0
Setup	SDK installed or CSV uploaded	Kickoff call held	Days 1 to 5
Activated	First dashboard shared with a colleague	First stakeholder readout delivered	Days 3 to 21
Habit	Logged in 3 of last 7 days	Weekly recurring usage across 2 seats	Weeks 2 to 8
Paid	Card added	Contract signed	Day 14 to day 90
Expanded	Fourth seat invited or usage limit hit	Second team or department onboarded	Month 4 onward
At risk	No login for 14 days	Champion left or usage down 40% QoQ	Any time

Notice the self serve boundaries are single events and the sales assisted ones are often a human confirmation. That’s fine. A CSM marking a kickoff complete in Salesforce is still a queryable timestamp.

Which metric each stage owns, and where you read it

One stage, one metric. This is the rule people push back on hardest and it’s the one worth defending. A stage with two metrics has no owner, because when the numbers disagree the team reports whichever one moved.

The ranges above are practitioner bands, not a benchmark study. Check them against the SaaS email benchmarks and your own history before you present them as targets to a board.

Yes, forcing one metric feels reductive. Activation clearly has more than one dimension. Do it anyway for the duration of this course. You can add diagnostics later, once somebody owns the headline number and is on the hook for it.

The current state inventory: every email you already send

Now the unglamorous part. Export the full list of active sends from every system that can put a message in an inbox, and there are always more than you think. In a typical 40-person SaaS company the list includes the ESP, the product’s transactional service, the CRM sequences your AEs built, support desk macros, the billing provider’s dunning emails and whatever someone set up in Zapier eighteen months ago.

Put each one in a spreadsheet with six columns: name, system, trigger, audience filter, lifecycle stage and last edited date. The last edited date is the interesting one. Anything untouched for over a year is either load-bearing or abandoned, and you can’t tell which from the outside.

Gap and overlap analysis, and what the backlog looks like

Two failure patterns show up in nearly every first audit. The first is an empty stage, usually the one between activation and paid, or anything after the first invoice. The second is pile-up, where four separate systems all fire something in week one.

Overlap is worse than a gap. A gap means a user hears nothing at a moment when they might have listened. Pile-up means they get six emails in five days, mark you as noise, and then don’t open the one that mattered. Fix pile-up before you fix gaps, even though gaps feel more urgent.

Here’s what the Cadence Analytics audit produced.

Three empty stages out of seven is completely normal. So is discovering that your win-back email fires long after the account has mentally left. The post-sale half of the lifecycle is orphaned at most companies, which is the same pattern we cover in mapping the post sale customer journey and in lesson one of the customer marketing sprint.

The filled-in template, and how to keep it alive

The map is a living document, which in practice means it dies unless someone reviews it on a schedule. Put a recurring 30 minute calendar hold at the start of each quarter, and use the lifecycle email audit checklist to walk the stages.

Two things will change the map after you build it. Pricing changes move the paid boundary, and new onboarding flows move the activation boundary. Both are worth a full remap rather than a patch.

If you want deeper background on the discipline itself, the lifecycle email marketing definition covers terminology, and the broader SaaS email marketing strategy guide sits one level up from this course. Platform choice matters less at this stage than most vendors will tell you, though if you’re already weighing options, Customer.io versus Braze is the comparison that comes up most in mid-market SaaS, and the wider SaaS email marketing hub collects the rest.

What to do before lesson two

Finish the map. Print it. Put it somewhere your engineers walk past, because lesson two asks them for events and the conversation goes better when they’ve already seen why.

Bring three things to the next lesson: your seven stages, the list of boundaries written as queries, and your gap ranking. We’ll turn all of it into a tracking plan an engineer can ship in one sprint.