Set the start date and retention measure together
This note uses a hypothetical diligence setting. Contract signature, go-live, and first billing create different cohorts. A long implementation period makes signature-based retention a poor measure of early product behavior.
I would first decide whether the table is meant to examine acquisition quality, adoption after launch, or contract-value development. The cohort anchor follows that decision.
Logo retention counts the relationships that remain. Revenue retention measures the contract value that survives and expands. Growth in a large account can conceal churn among smaller customers, while a stable logo count may still contain downsells.
- Show logo and revenue retention together.
- Separate new business, renewal, expansion, contraction, and churn.
- Document entity changes, migrations, and contract rewrites.
Sample the customer-level record
When the aggregate curve changes, return to contracts and account histories. Compare contract dates, product packages, seats or usage, renewal status, and sales notes. Common definition breaks include splitting one customer into several entities or counting a multi-year rewrite as a new logo.
Carry limitations into the conclusion
Recent cohorts may not have completed a renewal cycle. A concentrated customer base can also let one account dominate the curve. The memo should state those limits instead of presenting an early signal as a durable pattern.