Time to revenue by acquisition cohort measures the interval from a defined marketing or customer event to a revenue milestone. It can inform investment timing, but only if the start, end, and treatment of immature records are consistent.
Choose a start event and revenue milestone
Possible start events include first known lead, opportunity creation, trial start, or first marketing response. End events might be closed-won, first invoice, or recognized revenue; state which one the analysis uses.
Preserve both event and ingestion timestamps where integrations delay updates. Use a consistent time zone and include a rule for account-level journeys with several contacts.
Track cohorts through maturation
Group records by the same start period and calculate elapsed time to the selected revenue event. Show the share that has converted and the share still open at each age.
Recent cohorts are incomplete. Avoid comparing their observed time-to-revenue with mature cohorts without a censoring or maturity method.
Segment only with sufficient evidence
Compare channels, customer sizes, product lines, or regions when the differences can change a decision and the cohorts are large enough to interpret.
Use medians or percentile ranges when time is skewed. An average can be pulled by a small number of exceptionally long cycles.
Use the metric for planning, not blame
Apply observed lag ranges to budget and capacity plans, but label them as historical estimates. Pair timing with margin, conversion quality, and delivery cost.
Our guide to lead-to-revenue lag explains how to handle incomplete cohorts.
Related reading: data delay and sales maturity.
Practical checklist
- State the date basis, definitions, and assumptions behind each measure.
- Separate observed outcomes from estimates and movement in existing records.
- Use the report to name a decision, owner, and next review date.
How did this article land?
Choose one reaction. You can change it anytime.