Sorai
Decision-Grade Review
SaaS DD
Mar 27, 2026 · 15 min read · Sorai Editorial · M&A Diligence Research · Updated Mar 30, 2026
SaaS M&A is not just a revenue-multiple exercise. Buyers test whether ARR is durable, whether retention is real, and whether growth economics will still work after close.
Quick answer
SaaS metrics in M&A are a way to test business quality, not just to headline valuation. Buyers focus on ARR composition, gross and net retention, customer concentration, margin profile, sales efficiency, and cohort behavior to understand whether recurring revenue is durable and whether growth will hold up after close. Bain's 2025 M&A work reinforces why that discipline matters in a more selective market, while McKinsey's private-markets research points to the advantage of stronger synthesis and pattern recognition in knowledge-intensive deal work.
SaaS metrics matter in M&A because software businesses can look healthier than they are if buyers focus only on growth and a headline ARR number.
Recurring revenue is powerful, but it is also easy to misread. A target can show growth while quietly replacing churned customers with expensive acquisition spend. It can report strong ARR while embedding services work that does not scale like software. It can look efficient on a blended margin basis while hiding an implementation burden, customer concentration issue, or pricing structure that will become obvious only after close.
That is why sophisticated buyers use SaaS metrics as a way to test business quality rather than as a shortcut to valuation. Bain's 2025 M&A work reinforces the broader point: in a more selective market, better diligence and stronger conviction matter more because there is less tolerance for avoidable mistakes [Bain & Company, "2025 Global M&A Report," 2025]. McKinsey's 2026 private-markets work is useful for the same reason from an operating standpoint. It highlights the value of better synthesis in knowledge-intensive investment processes where teams need to interpret patterns across many data points quickly [McKinsey & Company, "Harnessing the power of gen AI in private markets," January 5, 2026]. SaaS diligence is exactly that kind of pattern-recognition problem.
Traditional diligence can tell you whether revenue is recorded correctly, whether margins reconcile, and whether reported results tie to the underlying accounts. SaaS diligence has to go further because the central question is not only whether the numbers are accurate. It is whether the revenue base will behave the way management implies once the buyer owns it.
That means buyers need to understand:
The strongest SaaS diligence work therefore connects financial, commercial, product, and customer evidence. Metrics are the entry point, not the answer.
Annual recurring revenue is the headline number most buyers start with, but it is rarely the number they trust at face value.
The first question is definitional. What exactly is inside ARR?
A buyer will usually separate:
That decomposition matters because ARR is only useful as a valuation input if it represents revenue that is both recurring and scalable. When implementation work, custom development, or unusually sticky one-off arrangements are mixed into the number, the buyer is not looking at a clean recurring-revenue base anymore.
The second question is durability. Two targets can report similar ARR but have very different quality profiles. One may have broad customer diversification, embedded workflows, and contracts that renew into growing usage. Another may depend on a small number of customers, aggressive discounting, and annual selling pressure to defend the base.
A practical buyer review will test ARR quality by asking:
In other words, ARR is not just a size metric. It is a quality-of-revenue question.
Retention is usually the core lens through which buyers evaluate SaaS resilience.
Gross revenue retention shows how much recurring revenue remains before the benefit of expansion. Net revenue retention adds expansion back in. Both matter, but they answer different questions.
Gross retention asks whether the core base is leaking. Net retention asks whether the installed base becomes more valuable over time.
That distinction matters because a business can post respectable net retention while still having an underlying product problem. Aggressive upsell to a subset of customers can cover up contraction or churn elsewhere. Conversely, a company may have stable gross retention but weaker expansion because the product has limited wallet-share growth even if the customer base is loyal.
Sophisticated buyers therefore do not stop at the single retention headline. They want to see the bridge:
| Retention component | What it shows | Why buyers care |
|---|---|---|
| Beginning-period recurring revenue | Size of the starting base | Establishes the revenue foundation |
| Expansion | Deeper product penetration or price growth | Tests account development quality |
| Contraction | Shrinking spend inside existing accounts | Signals product, pricing, or budget stress |
| Churn | Revenue lost from departing customers | Tests durability of the installed base |
The next step is explaining the pattern. If expansion is strong, what is driving it: seat growth, usage growth, price increases, module adoption, or contract restructuring? If churn is elevated, is it concentrated in one segment, sales channel, product line, geography, or cohort?
Metrics become more meaningful when they can be explained operationally.
SaaS businesses are often described as diversified by default, but that is not always true. Some have one or two anchor accounts, channel dependencies, reseller exposure, or a narrow vertical footprint that creates concentration risk even if the customer count looks healthy.
Buyers usually test concentration in several ways:
Contract structure matters just as much as customer count. A revenue base made up of shorter-term or heavily negotiated contracts is different from one built on deeply embedded renewals with strong product usage and clear procurement support.
Important contract questions include:
Financial workflow
Sorai keeps QoE findings, working capital calls, and evidence-linked review points in one workflow instead of scattered files and memo rebuilds.
This is where SaaS metrics need legal and commercial diligence around them. The metric may look stable, but the contract mechanics may tell a more fragile story.
Gross margin is one of the simplest numbers in the model and one of the easiest to misread.
A strong gross margin profile can signal scalable software economics, but only if the cost structure is classified sensibly and the customer-delivery model is understood. If implementation labor, customer success burden, or custom support is doing more work than management admits, margin quality may be weaker than the headline suggests.
That is why buyers do not just ask, "What is the gross margin?" They ask:
One of the most common diligence corrections in SaaS is separating pure software economics from the broader customer-delivery model. That distinction matters because the buyer is underwriting future scale, not just historical reporting.
Customer acquisition cost and CAC payback are useful only when they are interpreted in context.
At a basic level, buyers want to know whether growth is being purchased at an acceptable cost and whether the company can continue funding expansion without deteriorating returns. But a clean answer requires more than a single payback figure.
A real review looks at:
CAC looks different depending on the go-to-market architecture. A business selling large, complex enterprise contracts may carry a longer selling motion but still be healthy if retention, contract value, and renewal depth are strong. A business with apparently fast payback may still be weak if customers do not stay, expand, or use the product meaningfully.
The metric therefore needs to be tied back to customer outcomes, not read in isolation.
Cohort analysis is where many buyer convictions either strengthen or fall apart.
Headline retention can hide a business whose early customers are weakening while newer customers temporarily keep the blended metrics attractive. Cohorts help a buyer see whether the revenue base matures well or decays after the initial sale.
Useful cohort questions include:
Usage data is especially important in SaaS because revenue and product reality can drift apart for a while before the problem shows up in churn. A customer may keep paying through a contract term while adoption weakens underneath. Buyers want to identify that early.
This is where the SaaS diligence story becomes cross-functional. Revenue metrics, product telemetry, support patterns, and customer behavior should reinforce each other. If they do not, the buyer needs to understand why.
The Rule of 40 remains popular because it compresses a growth-versus-profitability tradeoff into a simple shorthand. That can be useful for fast screening, board conversations, and high-level comparability.
But it is not a substitute for diligence.
A company can present an acceptable Rule of 40 profile while carrying weak retention, fragile concentration, a deteriorating pipeline, or an implementation-heavy delivery model. Another business may miss the shorthand while still being attractive because its revenue quality, product depth, and customer expansion path are stronger than the headline score suggests.
The metric is therefore best used as a summary lens after the buyer understands the building blocks underneath it.
For a serious SaaS review, buyers should be able to answer the following before they underwrite a premium valuation:
When those answers line up, SaaS metrics become powerful evidence. When they do not, the headline valuation story is usually ahead of the underlying business quality.
SaaS metrics for M&A are not about memorizing a benchmark table. They are about understanding whether recurring revenue is durable, whether customer behavior supports the model, and whether growth economics will remain credible after the buyer takes control.
The best buyers treat ARR, retention, efficiency, margins, and cohorts as linked signals. They do not ask which single metric justifies a premium. They ask whether the full metric set tells a coherent story about product value, customer durability, and scalable economics.
Sources cited
Author
Editorial review team for Sorai's public diligence content
The editorial team translates public primary-source research and Sorai's workflow perspective into material designed for private equity, corporate development, and transaction advisory readers.
Frequently asked questions
The most important SaaS metrics in M&A are the ones that explain whether recurring revenue is durable. Buyers usually focus on ARR composition, gross and net retention, customer concentration, gross margin and services mix, sales efficiency, cohort behavior, and how much of growth comes from expansion versus constant new-logo replacement.
Headline ARR can hide weak underlying economics. Buyers want to know whether revenue is concentrated, discounted, bundled with services, dependent on short-term contracts, or inflated by temporary pricing changes. The quality of ARR often matters more than the absolute dollar figure because it determines how much of the revenue base is defendable after close.
Net revenue retention measures how revenue from an existing customer base changes over time before adding any new customers. It is commonly expressed as beginning-period recurring revenue plus expansion, minus contraction and churn, divided by beginning-period recurring revenue. Buyers use it to understand whether the product is deepening inside the installed base or slowly eroding.
The Rule of 40 is a shorthand for balancing growth and profitability. It is useful as a quick signal, but sophisticated buyers do not rely on it alone because it can mask revenue-quality issues, unsustainable cost cuts, or a business that looks efficient only because growth has already slowed.
Common red flags include weak retention hidden by new-logo growth, heavy services revenue presented as software revenue, concentrated customers, deteriorating cohort behavior, rising acquisition costs, and product usage trends that do not support the reported revenue story.
Relevant workflows
Use the linked workflow pages to connect financial findings to adjacent tax, legal, and platform review requirements.
Relevant workflow
Review the core financial diligence workflow in Sorai.
Relevant workflow
Connect financial findings to tax exposure, structuring, and filing review.
Relevant workflow
See how Sorai keeps specialist workstreams aligned under partner review pressure.
Related reading
Quality of Earnings
A buyer-focused guide to quality of earnings analysis in M&A, including what QoE actually tests, which findings change price and terms, and how to run the work under deal pressure.
Financial DD
The EBITDA bridge reconciles reported EBITDA to normalized EBITDA. Every add-back must be validated with evidence — because each dollar of unsupported adjustment multiplied by the deal multiple inflates overpayment.
Due Diligence
Due diligence in M&A is the buyer's systematic investigation of a target company's financial, tax, legal, and operational position before closing. This guide covers every workstream, timeline, and checklist.