SaaS metrics due diligence tests whether churn, net revenue retention, cohort retention and product usage evidence support the growth story behind a SaaS deal. It verifies definitions, reconciles dashboards to source data, and translates metric quality into product risk, valuation risk and post-close priorities.
Recurring revenue can make a target look predictable. The diligence risk is that the recurring-revenue story is cleaner than the operating reality. ARR can include services work, churn can be softened by annual contracts, expansion can depend on exceptional account management, and cohort curves can hide segment problems that will matter after investment.
FoundationState's product due diligence service treats SaaS metrics as product evidence, not only finance evidence. In our diligence engagements we typically move from scoping, to data room review, to evidence evaluation, to leadership and product interviews, to findings calibration and readout. The goal is to understand whether the product creates durable customer value at the scale the deal model assumes.
Which SaaS metrics due diligence should verify first?
SaaS metrics due diligence should start with definitions. The question is not whether the target has a dashboard. It is whether each metric means what the deal team thinks it means, whether it reconciles to source evidence, and whether the same definition is used across finance, sales, product and board reporting.
David Skok's SaaS Metrics 2.0 is a useful reference because it frames SaaS performance around acquiring customers, retaining customers and monetising customers. In diligence, those three areas become a practical evidence map: revenue quality, retention quality and product engagement quality.
| Metric or evidence area | What to verify | What it can reveal |
|---|---|---|
| ARR and MRR | Recurring revenue definitions, exclusions, discounts, renewals, services separation and customer-level reconciliation | Whether the revenue base is truly recurring and comparable over time |
| Logo churn vs revenue churn | Lost customers, lost revenue, cancellation reasons and segment patterns | Whether churn is concentrated in low-value accounts or in strategically important customers |
| Net revenue retention | Expansion, contraction, downgrades, price increases and account-management effort | Whether growth comes from product value or from exceptional commercial intervention |
| Cohort retention | Customer cohorts by start date, segment, plan and acquisition channel | Whether retention improves, decays or varies sharply by market segment |
| Activation and engagement | Product usage metrics, activation rate assessment and depth of workflow adoption | Whether customers are using the product in a way that supports renewal confidence |
| CAC payback period | Cost allocation, channel mix, sales cycle and segment economics | Whether the growth engine can scale without consuming disproportionate capital |
| Customer concentration risk | Revenue, expansion and support load by customer | Whether headline NRR depends on a small number of accounts |
This table is not a replacement for financial due diligence. It is the product diligence lens on the same numbers. A metric can reconcile financially and still raise product risk if the behaviour underneath it is weak.
How do churn, NRR and cohorts change the investment case?
Churn analysis due diligence should explain who leaves, why they leave and what their departure says about product-market fit. A single churn percentage rarely gives enough signal. Investors need to compare logo churn vs revenue churn, customer size, tenure, use case, implementation quality and support history.
Net revenue retention assessment asks a related question: do retained customers expand because the product becomes more valuable, or because the company applies heavy commercial effort? NRR above 100% can be attractive because expansion offsets contraction, but it is not automatically healthy. It may be carried by price increases, one enterprise account, paid services, or a small upsell motion that is hard to repeat.
Cohort analysis acquisition work is especially useful because it shows behaviour over time. Stronger cohorts normally retain value, deepen usage and show explainable differences by segment. Weaker cohorts decay quickly, depend on discounting, or look healthy only after excluding failed implementations. In a product review, cohorts help test whether the growth story is becoming more durable or simply larger.
The commercial implication is direct. If retention quality is strong, the buyer may have more confidence in the revenue base and roadmap investment. If retention quality is weak, the issue may affect valuation, warranties, post-close operating support or the first 100-day product priorities.
How can SaaS metrics be flattered before a deal?
Metric flattering is not always deliberate. Many targets report the numbers they needed as a growing company, not the numbers an acquirer needs to underwrite a deal. The risk is that board dashboards, investor decks and product analytics use different definitions.
Common issues include annual contracts masking churn until renewal, non-recurring implementation fees included in ARR, free months treated as retained revenue, customer downgrades excluded from churn, paused accounts left in the active base, expansion counted before it is contractually committed, and services-heavy work described as product adoption.
ARR quality assessment should therefore compare reported ARR with contract data, billing data, CRM stages and customer movement schedules. Product analytics due diligence should then test whether usage data supports the revenue story. If a cohort appears retained but active users have dropped, support tickets are rising and core feature usage is thin, the renewal risk may be larger than finance reporting implies.
The same applies to benchmark language. Management may refer to NRR benchmarks, gross retention benchmarks or SaaS benchmark data, but benchmarks only help when definitions and segments match. A target selling to very small businesses should not be judged by the same retention pattern as an enterprise workflow platform without adjusting for customer type, contract length and implementation depth.
How do metrics connect to product reality?
SaaS metrics are most valuable when they are read alongside product behaviour. Product usage metrics due diligence looks at the habits behind revenue: which users activate, which workflows repeat, which features correlate with renewal, and whether engagement depth is increasing in the segments the growth plan prioritises.
This is where assessing product-market fit in due diligence matters. Product-market fit is not proven by a high-level ARR chart. It is evidenced by retention, usage depth, clear differentiation, willingness to renew, and a roadmap that solves real customer problems rather than chasing every sales objection.
Engagement metrics assessment should be specific to the product. Daily active users may matter for a collaboration tool, while monthly workflow completion may matter more for finance, compliance or HR software. A diligence review should avoid generic vanity metrics and ask what behaviour would make the product hard to replace.
The SaaS due diligence guide covers the wider platform, cloud and security context. Metrics and platform evidence should be read together. Churn may be caused by product fit, but it may also be caused by reliability problems, onboarding friction, weak integrations, slow support or configuration complexity.
What evidence should be requested in the data room?
The data room should make recurring revenue verification possible without relying on a polished dashboard. Deal teams should request enough source evidence to reconcile metric definitions, customer movements and product usage patterns.
Useful evidence includes ARR and MRR definitions, customer-level revenue schedules, churn and downgrade logs, renewal outcomes, expansion history, product usage exports, activation measures, feature adoption, support themes, onboarding data, customer feedback, cohort views, pricing and packaging history, and sales-to-product handoff evidence.
For product diligence, the most useful artefacts are often the ones that connect teams. A roadmap item should be traceable to customer evidence, usage data or strategic rationale. A churn reason should be visible in customer success notes, support history or product analytics. A retention claim should match actual usage behaviour.
The review should also test whether product, finance and customer success teams use the same language. Inconsistent metric definitions can be a maturity issue, but they can also create valuation risk if the buyer cannot compare performance over time.
FoundationState's work with River Consulting reflects the same principle: product evidence becomes more valuable when it helps leadership make clear prioritisation decisions rather than simply collecting more data.
How should findings affect valuation and Day-1 planning?
SaaS metrics findings should be translated into deal decisions. Some findings are normal maturity gaps. Others affect software valuation because they change the confidence investors can place in retention, expansion, margin or roadmap feasibility.
A practical readout should separate findings into four categories. First, definition issues that need clarification before signing. Second, revenue-quality issues that may affect price or warranties. Third, product issues that explain churn, weak activation or limited expansion. Fourth, operating issues that should become Day-1 or 100-day priorities.
Examples include tightening ARR definitions, separating services revenue, rebuilding the board metrics pack, improving onboarding, instrumenting product analytics, focusing roadmap work on retention drivers, reviewing pricing and packaging, or investigating customer concentration before underwriting aggressive expansion.
The strongest diligence output does not say "churn is high" and stop there. It explains why churn is high, whether it is segment-specific, whether the product team can address it, how long remediation may take, and whether the investment thesis still works after that evidence is considered.
Get an independent view of the SaaS metrics behind the growth story. Contact FoundationState to scope product due diligence around churn, NRR, cohorts, product usage and roadmap evidence before your next SaaS investment or acquisition.
Frequently Asked Questions
What SaaS metrics should due diligence verify?
Due diligence should verify ARR, MRR, churn, net revenue retention, cohort retention, activation, engagement, CAC payback, expansion, contraction and customer concentration. The important step is definition testing: each metric should reconcile to source evidence and be segmented enough to show whether the product is retaining the customers the growth plan depends on.
How can churn be hidden in SaaS reporting?
Churn can be hidden by annual contracts, paused accounts, delayed renewals, downgrade exclusions, discounting, services revenue, or reporting revenue churn without logo churn. A target may also show stable ARR while product usage weakens. Diligence should compare contracts, billing, CRM movement, customer success notes and product usage data.
What is a good NRR for a SaaS acquisition?
A good NRR depends on segment, pricing model, contract length and expansion motion. For acquisition diligence, the key question is whether expansion is repeatable, contractually supported and linked to product value. NRR above 100% can be attractive, but only if it is not carried by one account, price rises or services work.
