SaaS Due Diligence Metrics: The Complete Framework

Every acquisition checklist names the same ten SaaS metrics. None of them explain what "good" looks like at $2M ARR vs. $20M ARR, how to verify the number against billing data, or which specific pattern in a metric trend should stop a deal outright. This is the framework PE deal teams and growth investors use to evaluate SaaS acquisitions — per-metric formulas, stage-adjusted benchmarks, red flags with hard thresholds, and the billing-system verification methods that separate self-reported numbers from investor-grade data.

What SaaS metrics should you check before acquiring a company?

Due diligence checklists are easy to find. The problem is that most of them are flat — ten metrics listed alphabetically with a single "healthy range" that applies identically to a seed-stage company and a $50M ARR platform. That framing is worse than useless because it creates false confidence. A deal team that sees 3% monthly churn and marks it "within range" without checking stage, segment, or pricing model has validated nothing.

The metrics that matter in SaaS due diligence cluster into three groups: revenue metrics (what the company earns and how durable it is), retention metrics (what happens after acquisition), and efficiency metrics (how expensive growth is). Within each cluster, the question is never "what is this number?" — it's "what should this number be given the company's stage, and can we verify it from billing data?"

Stage context changes everything. A 5% monthly logo churn rate is a crisis at $10M ARR. It's expected at $500K ARR where the customer base is still mostly early adopters on monthly plans. An LTV:CAC of 2:1 is alarming at scale but rational for a company investing heavily in a land-and-expand motion with proven expansion revenue. Every metric in this framework is paired with stage-specific benchmarks because a number without context is a number without meaning.

The second gap in most checklists is verification. A target company reports $3.2M ARR. Is that billing-system-verified or spreadsheet- computed? Does it include annual contracts at their full value or normalized monthly? Are one-time setup fees or services revenue mixed in? The gap between self-reported and billing-verified revenue in SaaS companies runs 8–15% on average — wide enough to change a valuation multiple. This framework treats verification as a required step, not an optional audit.

Revenue metrics — verifying what the company claims

Revenue is the first cluster because it's the one most likely to be misstated. Not through fraud — through inconsistent definitions. "MRR" means something different at every SaaS company depending on how they handle annual contracts, discounts, usage-based components, and multi-currency conversions. Diligence starts by aligning on the definition, then verifying it from the billing system.

MRR/ARR — definition alignment and billing verification

MRR is the atomic unit. ARR is MRR multiplied by 12. The simplicity of that statement obscures the complexity underneath. A company with annual contracts, quarterly billing, and usage overages has at least three normalization decisions baked into its MRR figure — and those decisions are rarely documented.

Billing verification means reconstructing MRR from subscription objects in the billing system (Stripe, Chargebee, Recurly) rather than accepting the company's spreadsheet. The reconstruction process is mechanical: sum all active subscription line items, normalize non-monthly intervals to their monthly equivalent, exclude one-time charges, and convert multi-currency amounts at consistent rates. The resulting number is the billing-verified MRR.

The gap between self-reported and billing-verified MRR typically runs 8–15%. Common causes: counting annual contracts at full annual value instead of dividing by 12, including one-time onboarding fees, counting churned subscriptions with future end dates as active, or using stale FX rates. None of these are malicious — they're the natural result of metrics computed in spreadsheets rather than derived from billing objects.

Revenue concentration — customer and plan-tier risk

Revenue concentration measures how much revenue depends on a small number of customers or a single plan tier. The standard threshold is customer concentration: if the top 10% of customers account for more than 40% of revenue, the revenue base is fragile. Losing one or two large accounts can move the MRR number by 5–10% in a single month.

Plan-tier concentration is less commonly checked but equally important. A company where 80% of revenue comes from a single pricing tier has a single-product risk — if that tier's value proposition weakens, there's no diversification buffer. Healthy SaaS companies have 40–60% of revenue on the mid-tier plan, with meaningful contributions from both the entry and enterprise tiers.

Revenue quality — recurring vs one-time vs services

Not all revenue deserves a SaaS multiple. Recurring subscription revenue gets 8–15x ARR multiples because it's predictable. One-time implementation fees, training revenue, and services income are valued at 1–2x because they require marginal effort for every dollar. The mix matters enormously for valuation.

In diligence, separate the revenue stream into three buckets: recurring subscription revenue, recurring usage/consumption revenue, and non-recurring revenue (services, setup fees, one-time charges). The subscription percentage should be above 85% for a company positioned as a SaaS business. Below 70%, the company has meaningful services exposure and should be valued accordingly.

Retention metrics — the most predictive cluster

Revenue tells you what the company earns today. Retention tells you what it will earn in 12 months. Of the three metric clusters in SaaS due diligence, retention has the highest predictive value for post-acquisition performance — and it's the cluster most commonly misrepresented, not through intent but through definitional inconsistency.

Net Revenue Retention — the single best predictor

Net revenue retention (NRR) captures the full lifecycle of existing customer revenue: expansion (upgrades, seat additions, usage growth), contraction (downgrades), and churn (cancellations). An NRR of 110% means the existing customer base generates 10% more revenue this period than last period, before any new customer acquisition.

NRR above 100% is the single strongest signal of product-market fit and long-term compounding. Companies with NRR above 120% can literally stop acquiring new customers and still grow. In diligence, NRR is the number that most directly predicts whether the acquired revenue base will hold, grow, or erode post-close.

Stage benchmarks for NRR: early-stage ($0–$3M ARR) targets 90–100%, growth-stage ($3M–$15M ARR) targets 100–115%, and scale-stage ($15M+ ARR) targets 110–130%. The increasing target reflects that larger companies should have more expansion levers (upsell tiers, seat-based growth, usage expansion) driving NRR above the retention floor.

Gross Revenue Retention — the floor

Gross revenue retention (GRR) strips out expansion and measures only what the company keeps. It has a maximum of 100% and reveals the baseline retention quality without the offsetting effect of expansion revenue. A company with 115% NRR and 75% GRR has a retention problem masked by aggressive upselling — the expansion engine is compensating for a leaky bucket.

GRR below 85% is a red flag in diligence at any stage. It means the company loses more than 15% of its existing revenue base annually before expansion. For acquisition targets, GRR is often more revealing than NRR because it shows what happens if expansion slows post-acquisition — a common pattern when new ownership changes pricing, packaging, or GTM priorities.

Logo churn — customer count trends

Logo churn measures customer count, not revenue. A company can have low revenue churn (large customers stay) and high logo churn (small customers leave) simultaneously. This pattern is common in enterprise SaaS where SMB customers adopted the product early and churn as the company moves upmarket.

In diligence, logo churn reveals customer satisfaction independent of revenue weighting. Healthy monthly logo churn runs 2–3% for SMB SaaS, 1–2% for mid-market, and below 1% for enterprise. But the trend matters more than the absolute number — improving logo churn signals product-market fit strengthening; worsening logo churn over three or more months signals a problem that revenue retention may be temporarily masking.

Growth efficiency metrics

Revenue and retention describe the current state. Efficiency metrics describe the cost of maintaining and extending it. In due diligence, efficiency answers the capital allocation question: how much investment does this company need to sustain its growth rate, and what return does each dollar of investment produce?

LTV:CAC — by GTM motion

The ratio of customer lifetime value to customer acquisition cost is the unit economics acid test. The formula is straightforward — (ARPA / monthly churn rate) / CAC — but the inputs vary dramatically by GTM motion, and using a single benchmark across motions produces misleading conclusions.

Self-serve SaaS should target LTV:CAC of 3:1 or higher. The acquisition cost is low (primarily marketing spend), so a 3:1 return is achievable. Sales-led SaaS can operate at 2.5:1 because the higher ACV justifies higher acquisition cost. PLG-to-sales hybrid motions should target 4:1+ because the product-led funnel is supposed to reduce CAC below pure sales-led levels — if it's not producing better unit economics, the PLG motion isn't working.

In diligence, LTV:CAC below 2:1 signals that the company is spending more to acquire customers than those customers are worth. Above 5:1 usually means the company is under-investing in growth — capturing less market than it could. Both extremes warrant investigation.

CAC payback — the cash flow lens

LTV:CAC measures total return. CAC payback measures speed: how many months of gross margin does it take to recover the cost of acquiring a customer? This is the cash flow metric — a company with strong LTV:CAC but 24-month payback needs significant working capital to fund growth.

Healthy CAC payback is under 12 months for self-serve, under 18 months for sales-assisted, and under 24 months for enterprise. Beyond those thresholds, the company is effectively financing customer acquisition from future revenue — which works during a funding cycle but becomes fragile when capital tightens. For PE-backed acquisitions where leverage is involved, CAC payback above 18 months creates a cash flow timing mismatch with debt service.

Quick ratio — growth quality

The SaaS quick ratio measures the quality of MRR growth: (new MRR + expansion MRR) / (churned MRR + contraction MRR). A quick ratio of 4 means the company adds $4 of new and expansion revenue for every $1 it loses. A quick ratio of 1.5 means growth is real but the company is running hard to stay in place.

In diligence, quick ratio distinguishes efficient growers from treadmill growers. A company growing MRR 8% month-over-month with a quick ratio of 4 is adding durable revenue. The same growth rate with a quick ratio of 1.5 means the company is churning almost as fast as it acquires — that growth rate collapses the moment acquisition spend declines. Target: above 4 for healthy growth, above 2 as a floor for sustainable economics.

Red flags that should stop a deal

Not every weak metric is a deal-breaker. A company with 2:1 LTV:CAC might simply need a pricing adjustment. Low GRR might reflect a fixable onboarding gap. Due diligence is about distinguishing between problems you can fix post-acquisition and structural issues that no operational improvement will resolve.

Customer concentration above 30%.When a single customer or a small cluster accounts for more than 30% of revenue, the business has key-person risk at the customer level. If that customer leaves, the revenue hit exceeds any reasonable contingency buffer. This is structural — you can't diversify a customer base fast enough post-close to mitigate the risk window.

Declining NRR for three or more quarters.A single quarter of NRR decline can reflect seasonality or a large customer contraction. Three consecutive quarters of decline indicates a retention trend that will compound into a revenue erosion problem. The math is unforgiving: NRR declining from 110% to 95% over three quarters means the existing customer base will shrink by 5% annually even before accounting for churn — and that trajectory is accelerating.

Involuntary churn exceeding 40% of total churn. Involuntary churn (failed payments, expired cards, billing errors) should be a minority of total churn in a well-run SaaS business. When it exceeds 40% of total churn, the company has a billing infrastructure problem. Failed payment recovery is operationally solvable, but a company that hasn't solved it at scale likely has other operational gaps that diligence should probe.

Revenue recognition mismatches. When the gap between self-reported ARR and billing-verified ARR exceeds 15%, something is wrong with how the company counts revenue. The mismatch could be definitional (mixing in services revenue), temporal (counting booked but not yet activated contracts), or structural (counting revenue from paused or cancelled subscriptions). Any of these mismatches reduces confidence in every other number the company reports.

How to verify metrics from billing data

Self-reported metrics are a starting point, not a conclusion. Verification means reconstructing the key metrics directly from billing-system objects — subscriptions, invoices, charges, refunds — and comparing the result to what the company reports. The gap between those two numbers is itself a data point in diligence.

Stripe billing objects as source of truth

For Stripe-billed SaaS companies (the majority of the market below $50M ARR), the subscription object is the source of truth for MRR. Each active subscription has a plan, quantity, interval, and status. Normalizing these to a monthly cadence produces billing-verified MRR that is independent of how the company internally tracks revenue.

The verification process is specific. Pull all active subscriptions. Exclude subscriptions in trial, paused, or past-due status beyond a grace period. Normalize annual plans by dividing by 12 and quarterly plans by 3. Exclude one-time invoice items and metered billing overages that aren't recurring. Apply consistent FX rates for multi-currency subscriptions. The result is a clean MRR figure that can be compared directly to the company's self-reported number.

Churn verification follows a similar pattern. Rather than accepting the company's churn figure, reconstruct it from subscription state changes: subscriptions that moved from active to cancelled in each period. Separate voluntary cancellations (customer-initiated) from involuntary failures (payment failures that exceeded the retry window). The voluntary/involuntary split is critical because the two types have different causes and different remediation paths.

What verified data changes in the diligence timeline

Billing-verified metrics don't just produce more accurate numbers — they compress the diligence timeline. Traditional SaaS due diligence spends 2–4 weeks reconciling self-reported metrics with financial statements and billing data. Automated billing verification can produce the same reconciliation in hours, shifting diligence time from data collection to analysis.

The timeline compression matters because it changes the deal dynamic. A deal team that can verify revenue within 48 hours of accessing the billing system moves faster to term sheet. In competitive processes, speed to conviction is a structural advantage. The team that validates the numbers first sets the terms of the conversation.

The due diligence metrics dashboard — what investors should see

The output of metric verification should be a single view that gives the deal team the complete diligence picture: revenue quality, retention trajectory, growth efficiency, and red-flag alerts. The dashboard isn't a replacement for deep analysis — it's the entry point that tells the team where to focus.

A diligence dashboard should surface five layers. First, headline metrics: billing-verified MRR/ARR, NRR, GRR, and quick ratio with their trailing 12-month trends. Second, the verification delta: the percentage gap between self-reported and billing-verified figures for each headline metric. Third, concentration analysis: top-10 customer revenue share, plan-tier distribution, and cohort retention curves. Fourth, efficiency metrics: LTV:CAC by acquisition channel, CAC payback period, and gross margin trend. Fifth, red-flag alerts: automated detection of the four deal-stopping patterns described above.

The dashboard should update from billing data, not from spreadsheets the target company maintains. Every metric should trace back to a billing-system object — a subscription, an invoice, a charge — with an audit trail that the deal team can verify independently. Self-reported data belongs in the comparison column, not the source-of-truth column.

For PE firms running multiple portfolio companies, the diligence dashboard becomes a portfolio monitoring tool post-close. The same metrics that validated the acquisition become the operating metrics that track value creation. This continuity — same definitions, same data source, same benchmarks from diligence through ownership — eliminates the data-quality reset that typically happens in the first 90 days after close.

North Metric builds this continuity by default. Connect a target's Stripe account during diligence, verify the metrics against billing data, then keep the same connection running post-close for ongoing portfolio monitoring — no re-implementation required.