Intelligence
Lifecycle programmes sized by realised customer value, not by flow count
Segment by order history, set spend by payback period per tier and flow frequency by repurchase cycle. Klaviyo's definitions of historic and predicted value.
- Author
- Johnson Lim
- Last verified
- October 2026
- Reading time
- 5 min
- Topics
First shared on LinkedIn on 21 June 2026, rewritten and re-verified on 23 October 2026.
Lifecycle programmes are usually planned as a list of flows by channel. Cart abandonment, browse abandonment, post-purchase and win-back are the common four. The money behind each flow, what it costs and when it pays back, is often decided later or not at all. The sequence below puts the economics first.
The sequence, economics first
Before adding another flow
- Segment by order history
- Set spend by payback period per tier
- Set frequency by repurchase cycle
- Then build or cut flows
Segment on what the customer has done
Klaviyo’s help documentation defines historic customer lifetime value as the total value of a customer’s previous orders, taking refunds and returns into account. Its predicted value is a forecast of spend over the next year. Total value is the sum of both. The two answer different questions. Historic value is a recorded fact and can be audited against order data. Predicted value depends on a model, which must have enough order history to work and changes as the model does.
For programme design, order count and spend to date are the safer first segmentation. A first-time buyer and a buyer with four orders are different customers, whatever a model predicts for each.
Size spend by payback period per tier
Each retention action has a cost per customer reached. A loyalty perk, a discount in a win-back flow and a free sample all cost money. The question for each tier is how many orders it takes for that customer to repay the cost.
An illustrative case, with invented numbers for the arithmetic only. A voucher costing S$5 sent to a customer who contributes S$12 of margin per order repays after one extra order. The same voucher sent to a first-time buyer who has a lower chance of ordering again may not repay at all. The figures are hypothetical and are not a benchmark for any category.
The brand’s own repeat purchase data by tier is what fills these numbers in. Published flow benchmarks were reviewed and not used. Third-party summaries of Klaviyo benchmark data gave abandoned cart revenue per recipient anywhere from about US$3 to US$7. Those figures count revenue attributed within a default window, not incremental revenue.
Set frequency by the repurchase cycle
A flow can send as often as the platform allows. The right frequency follows how often the category is bought. Take a consumable with a 30 to 45 day repurchase cycle, which is an example and not a sourced benchmark. A reminder placed inside that window fits the customer’s buying rhythm. Weekly messages in the same period add cost without a matching purchase moment.
Each brand’s cycle comes from its own data, measured as the median gap between first and second orders in that category.
What to do before adding another flow
| Step | What it produces |
|---|---|
| Pull repeat purchase counts by tier (first-time, second order, three or more) | The size of each segment and its observed repurchase rate |
| Calculate margin per order and cost per message by tier | A payback period for each programme at each tier |
| Measure the median gap between orders per category | A send window for each flow |
| Compare each existing flow’s cost with its tier’s payback period | A list of flows to extend, cut or limit to certain tiers |
The recommendation
A team that is about to add a flow can first run the four steps above. If a proposed flow cannot show a payback period for the tier it targets, the flow count increases while the payback gets longer, which is the pattern the sequence is meant to avoid. If order history is thin, start with two tiers (one order, two or more) and refine as data accumulates.
Disclaimer
This article is general information drawn from public sources on the date it was last verified. It is not legal, financial, tax or investment advice. Prices, fees, terms and programme details change, so confirm them with the company concerned before relying on them. Company, product and platform names belong to their owners. Uncommon Engine is not affiliated with, sponsored by or endorsed by any company named. It may work with some of them in future. Items marked INFERRED in the ledger come from secondary sources and have not been confirmed by the company. Readings and recommendations are the author’s opinion and are not statements of fact by any company. This article was drafted with AI assistance and checked against the sources listed. To request a correction, use the Contact page. The payback example uses invented numbers for illustration only. It is not a benchmark or a forecast of results.
Research Ledger (3 claims)
| Entity | Claim | Source | Date verified | Status |
|---|---|---|---|---|
| Klaviyo | Historic CLV is the total value of previous orders, net of refunds and returns | Klaviyo Help Center | 23 Oct 2026 | VERIFIED |
| Klaviyo | Predicted CLV forecasts spend over the next year, total CLV is the sum | Klaviyo, what is customer lifetime value | 23 Oct 2026 | VERIFIED |
| Third-party summaries | Abandoned cart revenue per recipient ranges from about US$3 to US$7 and uses last-touch attribution | Agency blogs summarising Klaviyo benchmarks, not primary | 23 Oct 2026 | INFERRED |
The article states no benchmark figures as fact. The payback example and the 30 to 45 day cycle are labelled illustrations. Dropped: nothing numeric from the original post, which stated none.
Questions
What is the difference between historic and predicted customer lifetime value?
Klaviyo defines historic value as the total of a customer's previous orders, net of refunds and returns. Predicted value is its forecast of what the customer will spend in the next year. Total value is the two added together.
Why segment lifecycle programmes by order history?
A first-time buyer and a repeat buyer carry different payback profiles for the same cost. Order count and spend to date are recorded facts, so a segment built on them can be checked against actual repurchase data.
How should flow frequency be set?
By the repurchase cycle of the category, taken from the brand's own order data. A product bought every 30 to 45 days, as in the example here, needs a trigger inside that window. A weekly send adds cost without matching how the customer buys.
Sources (2)
- Klaviyo Help Center, historic customer lifetime value definition
- Klaviyo, what is customer lifetime value (historic, predicted and total)
Spot an error or have a data tip?
Tell us what to check
Wrong fee figure, stale rate, a source that changed. A few words is enough.