# Lesson 1: Map Your Customer Lifecycle

> Draw the lifecycle stages your product actually has, pick the one metric each stage owns, and mark the gaps where no email exists today, in about two hours.

Source: https://saas-marketing.net/courses/saas-lifecycle-email/01-map-your-lifecycle/
Topic: SaaS Email Marketing
Type: course-lesson
Published: 2026-09-11
Last updated: 2026-09-11
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/courses/saas-lifecycle-email/01-map-your-lifecycle/

## Short answer

Mapping a SaaS customer lifecycle means naming the stages your own funnel data shows, not copying a generic template. Pull your product analytics, find the points where users visibly change behaviour (signup, first value, habit, paid, expansion, risk, churn), give each stage exactly one owning metric, then list every email you currently send against those stages. The gaps and overlaps that appear become your build backlog.

## Key takeaways

- Derive stages from behaviour changes in your own product data, not from a six-stage template someone published in 2019.
- Give every stage exactly one owning metric; two metrics means nobody can say whether the stage improved.
- Self serve and sales assisted products need different maps because the moment of commitment sits in different places.
- Most teams find 40 to 60 percent of their lifecycle stages have no email at all, and one stage has four.
- A finished map fits on one page and names the metric, the current emails and the gap for each stage.
- Overlap is more dangerous than gaps because competing sequences train users to ignore you.

---

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](/guides/saas-email-marketing-platforms/) 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.

Teams copy a six-stage model, discover stage three doesn't match their product, and rather than change the model they stretch the definition until it covers nothing. Six months later nobody can explain what stage three means and the emails in it get 11 percent open rates.

## 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.

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.

| Stage | Owning metric | Where you read it | Healthy range |
|---|---|---|---|
| Signup | Verified signups per week | ESP or product DB | Trending, not absolute |
| Setup | Percent reaching setup complete in 5 days | Product analytics | 45% to 70% self serve |
| Activated | Percent of signups activated in 21 days | Product analytics | 20% to 40% self serve |
| Habit | Week 4 retention of activated users | Amplitude or Mixpanel cohorts | 55% to 75% |
| Paid | Trial to paid conversion | Billing system | 8% to 25% depending on gate |
| Expanded | Net revenue retention | Billing plus CRM | 100% to 120% |
| At risk | Percent of MRR flagged at risk | CRM or health score | Below 12% |

The ranges above are practitioner bands, not a benchmark study. Check them against the [SaaS email benchmarks](/research/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.

**1** Metrics per lifecycle stage. Not two. Not a dashboard.

## 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.

**The two hour mapping exercise**

## 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.

| Stage | Emails today | Verdict | Backlog item |
|---|---|---|---|
| Signup | 3 (welcome, verify, product tour) | Overlap, all within 6 hours | Merge tour into welcome, delay to hour 24 |
| Setup | 1 (generic checklist) | Thin | Split by install path, SDK vs CSV |
| Activated | 0 | Gap | Build the celebrate-and-extend send |
| Habit | 0 | Gap | Weekly digest tied to shared dashboards |
| Paid | 2 (receipt, dunning) | Transactional only | Add a 30 day post-purchase check-in |
| Expanded | 0 | Gap | Seat limit and usage limit triggers |
| At risk | 1 (win-back, fires at day 60) | Too late | Move trigger to day 14 of inactivity |

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](/guides/post-sale-customer-journey-map/) and in [lesson one of the customer marketing sprint](/courses/saas-customer-marketing-sprint/01-map-the-post-sale-journey/).

The temptation after this exercise is to start drafting. Resist it for one more lesson. Every sequence you build before the tracking plan exists will need rebuilding, because the triggers won't be there and you'll fall back on time delays.

## 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](/checklists/lifecycle-email-audit/) to walk the stages.

**Your map is finished when**

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](/glossary/lifecycle-email-marketing/) covers terminology, and the broader [SaaS email marketing strategy guide](/guides/saas-email-marketing-strategy/) 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](/comparisons/customer-io-vs-braze/) is the comparison that comes up most in mid-market SaaS, and the wider [SaaS email marketing hub](/saas-email-marketing/) 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.

## Frequently asked questions

### What are the customer lifecycle stages for a SaaS product?

Most SaaS products settle on six or seven: visitor, signup, activated, habitual, paid, expanded, and at risk or churned. The names matter less than the boundaries. A stage boundary should be a behaviour you can query, like the first time an account invites a second seat, not a feeling like 'considering'.

### How long does lifecycle mapping take?

Budget two hours for a first pass if you already have product analytics and access to your email tool. The mapping itself takes about forty minutes. The inventory of existing emails takes longer than people expect, because emails live in three or four systems and nobody has a full list.

### Should each lifecycle stage have more than one metric?

No. One metric per stage forces a single owner and a single conversation. Secondary numbers can sit underneath as diagnostics, but the stage is judged on one. When a stage has two headline metrics, teams quietly report whichever one moved and the map stops being useful.

### What is the difference between a lifecycle map and a customer journey map?

A journey map describes what the customer experiences, including feelings and friction. A lifecycle map describes what your systems can see and act on. You need both, but only the lifecycle map can be wired to triggers, because every boundary on it is a queryable event.

### How do I audit the emails I already send?

Export the list of active automations from every system that can send: your ESP, your product, your CRM, your support desk and your billing provider. Billing emails are the ones teams forget, and they often land on the same day as a lifecycle send. Put each one in a spreadsheet with its trigger, audience and stage.

### Do I need product analytics before I can map the lifecycle?

Not for a first pass. You can draw the stages from what you know about the product and check them later. You do need analytics before you set thresholds, because a guessed activation threshold will be wrong by a factor of two or more in either direction.