A SaaS business can grow while quietly leaking value if new sales hide weak renewals. Retention shows whether customers keep receiving enough value to stay and, in stronger businesses, expand. Bessemer and Stripe both treat gross/net retention as core SaaS health measures. The capital-readiness standard is not one NRR number; it is cohort evidence with consistent definitions and a clear bridge from beginning recurring revenue to ending recurring revenue.
Know what weak and strong look like
| Readiness area | Weak / diligence risk | Strong / investor-ready |
|---|---|---|
| Logo churn | Cancels ÷ end-of-month customers or inconsistent denominator. | Lost customers ÷ beginning customers for a defined cohort/period. |
| GRR | Not tracked because NRR “looks good.” | Measures retained recurring revenue before expansion; exposes core leakage. |
| NRR | Expansion counted without churn/contraction bridge. | Beginning ARR + expansion − contraction − churn, divided by beginning ARR. |
| Cohorts | All customers blended together. | Retention by start month/quarter, segment, channel, contract size and product. |
| Renewals | Bookings or signed multi-year TCV treated as ARR. | Renewable recurring value separated from services, usage variability and nonrecurring fees. |
Build the recurring-revenue bridge
For each month start with recurring revenue from the opening customer set. Identify churned revenue, contraction, expansion and ending retained revenue. New-logo revenue is excluded from NRR because NRR asks what happened to the starting base.
Calculate GRR and NRR together
GRR prevents expansion from masking a weak core. NRR adds expansion to show whether the installed base compounds. A company with 125% NRR and 78% GRR may still have a severe churn problem hidden by a few large expansions.
Read cohorts instead of averages
Group customers by start period and show percentage of logos/revenue retained over time. Then cut by customer size, acquisition channel, use case and onboarding path. If paid acquisition cohorts retain worse than founder-led referrals, CAC alone is not the acquisition problem.
Separate voluntary and involuntary churn
Cancellation, failed payment, downgrade, customer shutdown and product migration have different remedies. Create churn reason codes with evidence instead of letting customer success choose “other.”
Tie retention to product value
Identify leading usage/implementation signals that predict renewal. A good retention program does not start 60 days before renewal; it starts with activation, time-to-value and the recurring workflow the customer hired the product to perform.
Run the diligence stress test before investors do
Do not rehearse an answer. Rehearse the evidence. Give yourself a short diligence window and try to produce the underlying records without rebuilding the story from memory. A clean result is reproducible, tied to a source system or signed document, and consistent with the numbers elsewhere in the company.
- Logo churn: Put the underlying records on screen and prove this standard: Lost customers ÷ beginning customers for a defined cohort/period. If the evidence still looks like this weak state—Cancels ÷ end-of-month customers or inconsistent denominator.—record the gap, name an owner and give it a due date instead of explaining it away.
- GRR: Put the underlying records on screen and prove this standard: Measures retained recurring revenue before expansion; exposes core leakage. If the evidence still looks like this weak state—Not tracked because NRR “looks good.”—record the gap, name an owner and give it a due date instead of explaining it away.
- NRR: Put the underlying records on screen and prove this standard: Beginning ARR + expansion − contraction − churn, divided by beginning ARR. If the evidence still looks like this weak state—Expansion counted without churn/contraction bridge.—record the gap, name an owner and give it a due date instead of explaining it away.
- Cohorts: Put the underlying records on screen and prove this standard: Retention by start month/quarter, segment, channel, contract size and product. If the evidence still looks like this weak state—All customers blended together.—record the gap, name an owner and give it a due date instead of explaining it away.
- Renewals: Put the underlying records on screen and prove this standard: Renewable recurring value separated from services, usage variability and nonrecurring fees. If the evidence still looks like this weak state—Bookings or signed multi-year TCV treated as ARR.—record the gap, name an owner and give it a due date instead of explaining it away.
Do the math investors will do
Formulas: GRR = (Beginning recurring revenue − churn − contraction) ÷ beginning recurring revenue. NRR = (Beginning recurring revenue − churn − contraction + expansion) ÷ beginning recurring revenue. Example: start with $100k MRR, lose $7k to churn, $3k to contraction and gain $15k expansion. GRR = 90%; NRR = 105%. New customer MRR is not included in either calculation for that starting cohort.
Build the evidence investors can verify
- Monthly logo and revenue retention bridge
- GRR/NRR by segment and contract size
- 12+ month cohort tables
- Renewal calendar and renewal outcomes
- Churn/contraction reason taxonomy
- Expansion sources and concentration
- Activation/value-event indicators correlated with retention
Questions an investor may ask
- Show me the cohort table, not just blended NRR.
- What percentage of NRR comes from the top five expanding accounts?
- What is GRR by SMB versus enterprise?
- When do customers that later churn first show weak usage?
- How do services or one-time fees affect the ARR definition?
30-day repair sprint
- Days 1–5: lock ARR/MRR, churn, contraction and expansion definitions.
- Days 6–10: build monthly customer/revenue bridge from source systems.
- Days 11–15: produce cohorts by start period and segment.
- Days 16–20: clean churn reasons and connect to product/CS events.
- Days 21–25: identify the two largest retention leaks.
- Days 26–30: launch remediation experiments and publish one investor-ready retention pack.
Research behind this guide
Use the primary and authoritative sources below to verify current rules, market conditions and technical guidance. Terms and regulations can change.