Should You Segment by Lifecycle Stage? Yes — But Each Stage Has a Different Job

I once sat in front of a slide that looked like good work. It showed our customers split into neat stages: new, active, slipping, lapsed. Four boxes, four colours. Clean.

Then I looked at what each box actually got. Every stage got the same promotion, with a new subject line. The new customer, the slipping customer, and the lapsed customer all got the same discount — the lapsed one just got it a week later, in a louder font.

That slide taught me something I have carried since: a lifecycle stage is a signal, not an instruction. It tells you where someone is, not what to do next.

What a lifecycle stage actually is

A lifecycle stage is just a label for where a customer sits in their relationship with you. The labels most B2C brands use are simple ones.

New means they just arrived, or just bought for the first time. Active means they are buying at their normal rhythm. Slipping means they are quieter than usual, but not gone. Lapsed means they have been quiet long enough that you need a reason to believe they will come back. Segmentation, in plain words, means splitting your list into groups so each group gets a message that fits them, instead of one message for everybody.

So should you segment your email list by lifecycle stage? Yes. Sending the same message to someone who bought yesterday and someone who has not bought in a year is not efficient. It is careless, and customers can tell.

But the stage only does half the job. Two customers can sit in the same stage and need completely different next steps. If your journey stops at the label, you will send the right message to the wrong person, and the wrong message to the right one.

How teams do this now, in practice

The better-run teams I have worked with keep the stages simple — four or five, no more — and then add a short check before any message goes out. They do not build fifty segments. They ask, for each stage, what is the one job of this message?

For a new customer, the job is to help them use what they just bought, and earn a second purchase — not to discount the next one before they have opened the first. For an active customer, the job is to keep the rhythm going: a useful reminder, a relevant next product, a reason to stay. Not a win-back offer for someone who never left.

For a slipping customer, the job is to find out what changed. Busy, something went wrong, or found something else — three different problems, and one discount does not fix all three.

For a lapsed customer, the job depends on context even more. This is where most journeys break. A good team checks four things before the lapsed flow starts.

First, how much did they buy last time, and how long does it last? A customer who bought three months of product is not overdue at six weeks. Second, are they still engaged? Someone who opened your last email is a very different case from someone who has not opened anything in months. Third, is there an unresolved problem — a late delivery, a return, a complaint? Sending a promotion over an open complaint reads as not listening. Fourth, can you even reach them? If emails are bouncing, another email is noise, not a win-back strategy.

Only after those checks does the team choose the message: a helpful reminder, a fix for the problem, a reason to come back — or, in some cases, nothing yet. Doing nothing for a customer who is not due yet is not neglect. It is good timing.

One worked example

Take two customers. Both last bought 45 days ago, and both land in the same "lapsed" bucket under a simple 45-day rule.

Customer A bought one pack of a product that lasts about 30 days. She is 15 days overdue, opened your last email last week, and has no open complaint. She is a genuine recovery candidate: a short, helpful reminder, maybe a note about what is new, and no discount yet. She may only need a nudge.

Customer B bought three packs in one order — about 90 days of product. At day 45, she still has roughly half her supply left. She is not lapsed at all. She is mid-use.

Now send both the standard win-back offer: 15% off their next order. Customer A might come back, and you will never know if the discount did it or the reminder did. Customer B comes back too — but she was going to buy anyway, when her supply ran out. If her next order is $75, that discount costs you $11.25 for a sale you already had.

That sounds small until you scale it. Say 1,000 customers hit your 45-day rule in a month, and 400 of them are like Customer B — stocked up, not gone. Sending all of them 15% off a $75 order gives away $4,500 in margin in one send, and teaches those 400 people to wait for the win-back email next time.

The fix costs nothing. Before the flow starts, split the bucket by what they bought and how long it lasts. Customer A gets the recovery message. Customer B gets nothing until she is actually due — then a replenishment reminder at full price, at the right moment.

What changed

A few years ago, building those context checks took real work. Branching a flow by units bought, engagement, and support history usually meant spreadsheets, manual lists, and someone remembering to update them.

That is no longer the excuse it was. Most email tools now let you branch a flow on purchase history, engagement, and other simple conditions without a big project. The check above is a few conditions in a flow builder, not a new system.

What has not changed is the temptation to skip it. It is still faster to build one flow per label and call the job done. The tools made branching cheaper. They did not make thinking cheaper.

What I would do on Monday

Before you add another version of a journey, write one sentence per stage, starting with the job. For example: "New: help them use the first purchase well, so they come back on their own." "Slipping: find out what changed before offering anything." "Lapsed: only message people who are actually overdue, after checking supply, engagement, and open problems."

Then take your existing lapsed list and run the four checks on it, once, by hand if you have to. How many are actually overdue? How many are still stocked up? How many have an open problem you should fix first?

Segment by lifecycle stage, by all means. Just remember what the stage is for. It is a signal. Your job is to decide what that signal means, for that customer, before you send anything.

This is the kind of work I now do with B2C teams: not more journeys, but journeys where each stage has a job, and each message earns its send.

Sources: Campaigner, Should you segment your email list by customer lifecycle stage; Klaviyo Community, Winback flow strategies: timing, segmentation and offers, and community discussion on segmenting lapsed customers by context before a win-back flow.