Recurring Revenue Analysis in Due Diligence: Beyond the ARR Number

Recurring revenue businesses, particularly SaaS and subscription models, dominate M&A deal flow. PE funds and strategic acquirers prize predictable revenue streams. But the headline ARR or MRR figure often masks important quality issues that only surface through detailed analysis.

Transaction Services teams conducting diligence on recurring revenue businesses need analytical frameworks that go beyond what the target's management dashboard shows.

Why Standard Revenue Analysis Falls Short

A standard QoE revenue analysis examines growth trends, customer concentration, and revenue recognition. For recurring revenue businesses, this is necessary but insufficient.

The key questions are about sustainability and quality:

How much of the recurring revenue is truly locked in by contract vs. month-to-month?
What does the churn profile look like across customer cohorts?
Is the growth driven by new customer acquisition, expansion of existing customers, or price increases?
How much revenue is at risk from upcoming renewals?

These questions require data that goes beyond the GL. Contract databases, billing system extracts, and customer-level revenue data are essential inputs.

Core Analytical Components

Revenue Decomposition

Break total revenue into its component streams:

Contracted recurring revenue: Revenue under multi-year or annual contracts with defined terms
Non-contracted recurring: Revenue from customers who pay regularly but without long-term commitments (month-to-month subscriptions)
Usage-based revenue: Variable revenue tied to consumption metrics
Professional services: Implementation, customization, and consulting revenue (typically non-recurring)
One-time revenue: Setup fees, license fees, hardware

Each category has different quality characteristics. Contracted multi-year revenue is the highest quality. Usage-based revenue carries volume risk. Professional services revenue requires continued sales effort.

Cohort Analysis

Cohort analysis groups customers by their start date and tracks their revenue over time. This reveals:

Gross retention: What percentage of revenue from a cohort is retained in subsequent periods (excluding expansion)?
Net retention: What is the combined effect of churn, contraction, and expansion on cohort revenue?
Time-to-churn patterns: Do customers churn after the first year? After contract renewal? Gradually?

Net retention above 100 percent indicates that existing customers are generating more revenue over time (through upsell and expansion) than is lost to churn. This is a powerful signal of product-market fit and revenue quality.

Churn Analysis

Churn is the most scrutinized metric in recurring revenue diligence. Key analyses include:

Logo churn: Percentage of customers lost per period
Revenue churn: Percentage of revenue lost per period (including downgrades)
Churn by segment: Does churn concentrate in specific customer segments, contract types, or product lines?
Churn drivers: Why are customers leaving? Product, price, competition, or business failure?

Elevated churn in a specific segment may be manageable. Accelerating churn across all segments is a deal risk.

Bookings and Pipeline

Forward-looking revenue analysis requires bookings data:

New bookings trend: Is the sales engine maintaining or growing new customer acquisition?
Renewal rates: What percentage of contracts up for renewal are actually renewed?
Pipeline quality: How reliable is the sales pipeline as a predictor of future revenue?
Contract duration trend: Are average contract lengths increasing (customer confidence) or decreasing (market pressure)?

Data Requirements

Recurring revenue analysis demands data that TS teams do not always find in the data room:

Customer-level revenue by month for the full analysis period
Contract details (start date, end date, annual value, auto-renewal terms)
Billing system exports with invoice-level detail
CRM data for bookings and pipeline analysis
GL detail mapped to customer or contract level where possible

When customer-level data is only available in the billing system and not the GL, reconciliation between the two becomes a critical step. Any difference between billing system revenue and GL-reported revenue must be explained.

Common Pitfalls

Conflating ARR and revenue. ARR is an annualized run-rate metric, not a GAAP revenue figure. It may include revenue not yet recognized, exclude deferred revenue amortization, and differ from the P&L revenue used in the QoE. Always reconcile ARR to GAAP revenue.

Ignoring contract terms. A customer on a multi-year contract with a termination-for-convenience clause is not truly locked in. Contract-level review is necessary for the top 20 to 50 customers.

Overlooking revenue recognition. SaaS companies sometimes recognize revenue at booking rather than ratably over the service period. This inflates near-term revenue at the expense of future periods. The QoE analysis must assess whether revenue recognition practices comply with the applicable accounting standard.

Using averages to mask cohort variation. An overall net retention rate of 110 percent can hide the fact that enterprise customers retain at 130 percent while SMB customers retain at 80 percent. Segment-level analysis is essential.

Integration with QoE

Recurring revenue analysis feeds directly into the EBITDA bridge. Adjustments specific to recurring revenue businesses include:

Capitalized implementation costs that should be expensed
Commission expense timing (ASC 606 / IFRS 15 treatment)
Customer acquisition cost amortization
Deferred revenue fair value adjustments in purchase accounting

The TS team should present recurring revenue quality as a distinct section of the QoE, with the decomposition, cohort analysis, and churn metrics supporting the overall earnings sustainability assessment.

For teams handling multiple SaaS due diligence deals, building reusable analytical templates for recurring revenue analysis standardizes the approach and accelerates delivery.