Customer lifecycle
The customer lifecycle is the sequence of states a customer moves through after their first order - typically new, active repeat, at-risk, lapsed and won back. Each state is assigned by time since last order relative to the brand's expected repurchase interval, and operators use it to time retention and win-back actions.
| Median repurchase interval | Median days between consecutive orders across your file. The yardstick every boundary is a multiple of |
| Time since last order | Days since the customer's most recent order |
| State boundaries | Brand-chosen multiples of the interval, e.g. at-risk beyond 1.5× and lapsed beyond 3×. Conventions differ - there is no industry standard, only your own repurchase behaviour |
Worked example
A brand's median time between orders is 60 days, so its state boundaries are set as multiples of that interval (example numbers, flagged as such).
The snapshot matters less than the migration: 3,000 at-risk this month becoming 2,600 next month is the health signal, and every migration between states has a contribution value attached.
What is a good customer lifecycle distribution?
There is no universal healthy split, because the distribution is mostly set by what you sell. A consumables brand should hold a large active base; a durables brand is structurally lapsed-heavy between purchase cycles and can be perfectly healthy that way. Young brands skew new because the file has not had time to age.
What is worth judging is direction - whether customers migrate towards active or towards lapsed month over month - and what each migration is worth in contribution. Your margin structure sets the stakes: the same 5% reactivation is a different decision at a 20% contribution margin and at 45%. Our free margin LTV calculator puts a contribution value on the customers each state holds.
Customer lifecycle vs related metrics
| Metric | What it measures | How it differs |
|---|---|---|
| RFM segmentation | How every customer ranks on recency, frequency and value | A score cube over the whole file. Lifecycle collapses the same signal into named states with explicit boundaries and tracks migration between them. |
| Cohort analysis | How fixed groups behave as they age | Cohorts never change membership. Lifecycle states are reassigned continuously as customers order or go quiet. |
| Win-back | How lapsed customers are recovered | The action taken on one lifecycle state. The lifecycle model defines who counts as lapsed in the first place. |
| Retention rate | Share of customers who stayed active | One summary percentage. The lifecycle map shows where the non-retained customers actually sit and which are still reachable. |
Common mistakes
- Copying day thresholds from another brand instead of deriving them from your own median repurchase interval.
- One set of boundaries across categories with different cycles. A 30-day consumable and a two-year durable cannot share a lapse rule.
- Reading the snapshot, not the migration. The count of at-risk customers matters less than whether it is growing or shrinking.
- Calling a durables customer churned inside a normal gap between purchases.
- Valuing every lapsed customer equally instead of ranking the pool by historical contribution margin.
Frequently asked questions
In Blufire, S4 Customer Value & Segmentation assigns lifecycle states and tracks migration between them from your reconciled order history - with CLV, the margin-true RFM cube and Financial Buckets alongside - and S8 Persona Analytics turns each state into audiences.
Updated July 2026