A young cohort is measured against another cohort's first months, never against a finished one.

A recent cohort may look unprofitable simply because it has not reached its second renewal. We align cohorts by maturity rather than calendar date, creating a like-for-like comparison before you draw conclusions about customer quality. You end up with comparable retention and LTV curves with maturity and data limitations stated clearly.

A Zeo researcher lining up cohort jars on shelves by month, with an LTV curve above

Some of the 500+ brands we've worked with

See all references
  • BMW
  • Gedik Yatırım
  • Hotiç
  • DYO
  • Elle
  • Tatilsepeti
  • Amazon
  • Shell
  • Hyundai
  • PepsiCo
  • Red Bull
  • Decathlon
  • MediaMarkt
  • Bayer
  • Sanofi
  • EY
  • KPMG
  • GE
  • 3M
  • Domino’s
  • Lexus
  • Trendyol
  • Hepsiburada
  • Yandex

Fair cohort comparisons account for the time each group has had to develop. Four steps produce a maturity-aligned comparison with its uncertainty visible.

How we hold ourselves to it

  • Apply one customer definition to every cohort — We fix what counts as a customer and when the cohort clock starts, then use that rule throughout the comparison.
  • Let maturity set the comparison window — We fix the comparison window to the youngest cohort's age, so a 6-month-old cohort only ever meets another cohort's first six months, whatever that cohort's total lifetime turns out to be.
  • Label unfinished cohorts clearly — When a cohort has not fully matured, we project cautiously and identify the result as a projection rather than an observed fact.
  • Add cost to turn retention into LTV — We connect retention curves with actual revenue and service cost, producing a usable LTV figure rather than a percentage alone.
  1. Define the cohort model

    We agree on cohort entry, customer grain, and the value and cost definitions that go into LTV. Your analytics owner confirms the customer definition.

    Cohort definition

    Illustrated figure sketching plans at a drafting table
  2. Build the curves

    We calculate retention and value curves for each cohort, handling censored (not-yet-mature) cohorts explicitly. The analyst flags any cohort with too little data.

    Cohort curves

    Illustrated figure stacking patterned building blocks
  3. Align and compare

    We compare cohorts at matched maturity points and flag where a difference is real versus an artifact of timing. The analyst rules out timing as the explanation before calling a gap real.

    Maturity-aligned comparison

    Illustrated figure reading an oversized measurement dial
  4. Walk through the findings

    We present the findings with their uncertainty and discuss what decision they can support. You confirm the decision the findings support.

    Cohort readout

    Illustrated figure presenting a bar chart on an easel

Every cohort gets compared at the same age

Automation calculates the curves, matches cohorts at the same maturity point, and drafts the readout from that aligned comparison. A person owns the definitions and the verdicts: what counts as a customer, which cohort has too little data to speak, and whether a gap is real or just timing.

You receive comparable curves and their limitations, each cohort measured at the same maturity point rather than collapsed into one average that hides the differences.

  • A cohort and LTV report next to a retention curve reference card

    Working document

    Cohort and LTV model

    The reproducible model defining cohort entry, retention, value, and cost calculations.

  • A cohort and LTV report next to a retention curve reference card

    Comparison report

    Maturity-aligned comparison

    Cohorts compared fairly at matched points in their lifecycle, with projections clearly labeled.

  • A cohort and LTV report next to a retention curve reference card

    Decision memo

    Readout and limitations

    What the curves actually show, what remains uncertain for less mature cohorts, and what decision they support.

We call it done when: every comparison in the readout runs on matched time windows and each projected point is labeled as a projection, not an observation.

These signs help show whether a cohort analysis fits the decision ahead.

A good fit when

  • You need to see whether customer quality is improving or declining from one acquisition cohort to the next.
  • Recent cohorts appear weak, but you do not know whether the difference is real or simply reflects their younger age.
  • You need a defensible payback period or LTV figure, and the readout must separate projected cohort values from observed ones.

Better handled as other work when

  • You need to identify which marketing channel drove an acquisition rather than how customers behave once they're in. That is Marketing Attribution Modeling.
  • You need a controlled test of a specific product change rather than an observational comparison across cohorts. That is Product Experimentation Measurement.

If one of these is closer to your situation, start here instead: All Product & Customer Analytics tasks

We call it done when: the customer definition, the cohort entry point, and the value grain are agreed with the data owner before a single curve is drawn.

  • Jupyter

    runs the LTV projection so a forecast for an active cohort is a shown calculation, not an opaque platform estimate

  • Amplitude

    builds the maturity-aligned curves so a young cohort isn't compared against an old one at the same calendar date

Bring us your customer and revenue data. We will align cohorts by maturity and explain what the differences can support.
Plan cohort analysis

Why can a recent cohort appear weaker?

It may not yet have reached the renewal or repeat-purchase points that create later value. Aligning cohorts by maturity prevents that timing difference from distorting the comparison.

How are active cohorts handled?

We project their likely path from the development of similar past cohorts and clearly separate observed figures from projections.

Can the analysis identify which acquisition channel deserves more investment?

It shows which cohorts, including cohorts segmented by channel, retain and pay back better. A controlled test is needed to establish whether the channel caused the difference rather than simply attracting different customers.

How much customer history is required?

We need transaction-level or subscription data covering at least one full retention cycle. Cost data is also required for an LTV figure rather than retention alone.