LTV (customer lifetime value)
What an average customer from a given cohort brings in over a fixed window after their first order. An LTV only means something when you say which window, whether it's revenue or margin, and which customers it covers.
Always label it: "180-day CM1 LTV" is a number you can use. "LTV" on its own isn't.
What is LTV?
LTV answers a simple question: once someone becomes a customer, how much are they worth to you? The answer decides how much you can afford to pay to acquire them, which is why it sits behind almost every scaling decision.
The trouble is that "lifetime" is never actually a lifetime. Every LTV is measured over some window, on some basis, for some group of customers. Change any of the three and the number moves a lot. The same brand can honestly quote an LTV of โน2,400 or โน593, depending on those choices.
How it's calculated
Take every customer whose first order fell in a period. Add up everything they spent, or everything you kept after variable costs, within N days of their first order. Divide by how many of them there are.
| Input | Source and range | What it gives us |
|---|---|---|
| first_order_date | Each customer's earliest delivered order | Which cohort they belong to, and when their clock starts |
| net_revenue | Delivered orders within N days, after discounts and GST | Revenue LTV |
| cm1 | Net revenue minus COGS, shipping (incl. RTO legs), payment gateway fees and handling | CM1 LTV, the one to compare with CAC |
| cohort_size | Customers whose first delivered order fell in the period | Denominator |
Tracking it as cohort curves
A single LTV number hides whether newer customers are better or worse than older ones. Track each acquisition cohort as a curve instead, and compare cohorts at the same age.
- 1Group by first orderOne cohort per acquisition month. Optionally split by channel or first product.
- 2Accumulate monthlyEach month, add the cohort's revenue and CM1 to its running total per customer.
- 3Align by agePlot months since first order, not calendar months, so cohorts line up.
- 4Compare at the same ageIs the August cohort's 90-day LTV above or below May's 90-day LTV?
Worked examples
Example 1: One cohort, three honest LTVs
An illustrative January 2026 cohort of 5,000 customers. Average first order โน1,200, with a 38% CM1 margin assumed throughout.
| Window after first order | Revenue LTV | CM1 LTV |
|---|---|---|
| First order only | โน1,200 | โน456 |
| 30 days | โน1,320 | โน502 |
| 60 days | โน1,450 | โน551 |
| 90 days | โน1,560 | โน593 |
| 180 days | โน1,860 | โน707 |
| 270 days | โน2,150 | โน817 |
| 365 days | โน2,400 | โน912 |
- โน2,400365-day revenue LTV. The number that ends up in pitch decks.
- โน1,56090-day revenue LTV. Faster to measure, still revenue.
- โน59390-day CM1 LTV. Four times smaller than the first, and the honest ceiling on what you can pay to acquire this customer if you want your money back within a quarter.
Example 2: The first product shapes the customer
Same brand, customers split by what they bought first. Illustrative 180-day numbers at a 38% CM1 margin.
Using LTV to decide
Compare cohorts at the same age, and compare CM1 LTV with new customer CAC from the same cohort. Treat these as starting rules.
Common mistakes
- Quoting LTV without a windowAlways say 90, 180 or 365 days. Without it, nobody can check or compare the number.
- Comparing revenue LTV to CACCAC is paid out of margin. Use CM1 LTV for any spend decision.
- Counting RTO ordersUndelivered COD orders aren't revenue. Build LTV from delivered orders only.
- Averaging across all customersMixes old and new cohorts. Compare cohorts at the same age instead.
- Projecting too farA 3-year LTV built from 6 months of data is a forecast. Label it as one.
Frequently asked questions
Should LTV use revenue or margin?
Use CM1 for anything involving spend: CAC targets, LTV:CAC, payback. Revenue LTV is fine for tracking whether customers are reordering more or less over time.
Which window should I use?
The one that matches how long you can wait to get your acquisition spend back. Many brands use 90 or 180 days for decisions and keep 365 days for planning.
Does LTV include the first order?
Usually yes, and it should, because the first order's margin is part of what pays back CAC. If you report repeat-only LTV, label it clearly.
Why does my LTV differ between tools?
Different windows, revenue vs margin, whether RTO and cancellations are removed, and how customers are matched across phone and email. Line those up and the numbers usually agree.
Related metrics
See LTV by cohort, channel and first product
BooleanMaths builds cohort LTV from delivered orders and your real costs, so you can compare revenue and CM1 LTV at any window.
LTV (customer lifetime value)
What an average customer from a given cohort brings in over a fixed window after their first order. An LTV only means something when you say which window, whether it's revenue or margin, and which customers it covers.
Always label it: "180-day CM1 LTV" is a number you can use. "LTV" on its own isn't.
What is LTV?
LTV answers a simple question: once someone becomes a customer, how much are they worth to you? The answer decides how much you can afford to pay to acquire them, which is why it sits behind almost every scaling decision.
The trouble is that "lifetime" is never actually a lifetime. Every LTV is measured over some window, on some basis, for some group of customers. Change any of the three and the number moves a lot. The same brand can honestly quote an LTV of โน2,400 or โน593, depending on those choices.
How it's calculated
Take every customer whose first order fell in a period. Add up everything they spent, or everything you kept after variable costs, within N days of their first order. Divide by how many of them there are.
| Input | Source and range | What it gives us |
|---|---|---|
| first_order_date | Each customer's earliest delivered order | Which cohort they belong to, and when their clock starts |
| net_revenue | Delivered orders within N days, after discounts and GST | Revenue LTV |
| cm1 | Net revenue minus COGS, shipping (incl. RTO legs), payment gateway fees and handling | CM1 LTV, the one to compare with CAC |
| cohort_size | Customers whose first delivered order fell in the period | Denominator |
Tracking it as cohort curves
A single LTV number hides whether newer customers are better or worse than older ones. Track each acquisition cohort as a curve instead, and compare cohorts at the same age.
- 1Group by first orderOne cohort per acquisition month. Optionally split by channel or first product.
- 2Accumulate monthlyEach month, add the cohort's revenue and CM1 to its running total per customer.
- 3Align by agePlot months since first order, not calendar months, so cohorts line up.
- 4Compare at the same ageIs the August cohort's 90-day LTV above or below May's 90-day LTV?
Worked examples
Example 1: One cohort, three honest LTVs
An illustrative January 2026 cohort of 5,000 customers. Average first order โน1,200, with a 38% CM1 margin assumed throughout.
| Window after first order | Revenue LTV | CM1 LTV |
|---|---|---|
| First order only | โน1,200 | โน456 |
| 30 days | โน1,320 | โน502 |
| 60 days | โน1,450 | โน551 |
| 90 days | โน1,560 | โน593 |
| 180 days | โน1,860 | โน707 |
| 270 days | โน2,150 | โน817 |
| 365 days | โน2,400 | โน912 |
- โน2,400365-day revenue LTV. The number that ends up in pitch decks.
- โน1,56090-day revenue LTV. Faster to measure, still revenue.
- โน59390-day CM1 LTV. Four times smaller than the first, and the honest ceiling on what you can pay to acquire this customer if you want your money back within a quarter.
Example 2: The first product shapes the customer
Same brand, customers split by what they bought first. Illustrative 180-day numbers at a 38% CM1 margin.
Using LTV to decide
Compare cohorts at the same age, and compare CM1 LTV with new customer CAC from the same cohort. Treat these as starting rules.
Common mistakes
- Quoting LTV without a windowAlways say 90, 180 or 365 days. Without it, nobody can check or compare the number.
- Comparing revenue LTV to CACCAC is paid out of margin. Use CM1 LTV for any spend decision.
- Counting RTO ordersUndelivered COD orders aren't revenue. Build LTV from delivered orders only.
- Averaging across all customersMixes old and new cohorts. Compare cohorts at the same age instead.
- Projecting too farA 3-year LTV built from 6 months of data is a forecast. Label it as one.
Frequently asked questions
Should LTV use revenue or margin?
Use CM1 for anything involving spend: CAC targets, LTV:CAC, payback. Revenue LTV is fine for tracking whether customers are reordering more or less over time.
Which window should I use?
The one that matches how long you can wait to get your acquisition spend back. Many brands use 90 or 180 days for decisions and keep 365 days for planning.
Does LTV include the first order?
Usually yes, and it should, because the first order's margin is part of what pays back CAC. If you report repeat-only LTV, label it clearly.
Why does my LTV differ between tools?
Different windows, revenue vs margin, whether RTO and cancellations are removed, and how customers are matched across phone and email. Line those up and the numbers usually agree.
Related metrics
See LTV by cohort, channel and first product
BooleanMaths builds cohort LTV from delivered orders and your real costs, so you can compare revenue and CM1 LTV at any window.