Buying an Asset

Standard diligence tells you what you're buying. It doesn't tell you what you're actually underwriting.

Two structural questions determine whether a B2B SaaS asset is infrastructure with a ceiling or something the market hasn't priced correctly. The first is whether the company is solving the right underlying problem — not the question the category inherited, but the actual challenge the category was built to address. The second is whether the product is designed so agents have to operate inside it, or whether it's a workflow they can replicate from outside.

Standard diligence — however rigorous — doesn't reach either question. The gap between 3.7× and 15–25× usually lives there. The buyers who surface it first price these assets differently than the buyers who don't.

Median private SaaS multiple
3.7×
Revenue multiple across 1,325 private software transactions, 2015–2025. Inside the existing category answer, executing well.
Top quartile — same answer, better execution
7.2×
The ceiling for a company answering the existing category question better than its competitors. The gap from 3.7× to 7.2× is execution. The gap above 7× is something else.
Category owners — new ceiling
15–25×
Gong peaked at ~15× ARR on a new conversation. Veeva ~20×. HubSpot ~25×. The gap between 7× and 20× was whether the company owned the category question — or inherited it along with everyone else.
In 2026 there is a second dimension. A company can own the category conversation and still be a workflow AI replaces. The environment question — is this something agents have to operate inside, or a workflow they replicate from outside — is now part of what the multiple is pricing.
The opening

Four workstreams. One that doesn't go far enough.

A rigorous diligence process covers the market, the financials, the technology, and the commercial position with real depth. The gap isn't a missing workstream — it's two dimensions that commercial diligence doesn't reach. Not because it's done poorly, but because it wasn't designed to ask them.

Workstream 01
Financial Diligence
Validates ARR, NRR, churn, cohort quality, revenue recognition, and financial projections. Tells you whether the numbers are real. Doesn't tell you whether the category question those numbers are built on has a ceiling.
Covered
Workstream 02
Legal Diligence
Validates contracts, IP ownership, regulatory exposure, and change-of-control provisions. Tells you what you're legally acquiring. Doesn't tell you what the asset is structurally positioned to become.
Covered
Workstream 03
Technical Diligence
Validates product architecture, scalability, technical debt, and engineering team quality. Tells you whether the product can scale. Doesn't tell you whether it's designed to be the environment agents depend on — or a workflow they automate away.
Covered
Workstream 04
Commercial Diligence
Validates market size and competitive position within the existing category frame. Tells you how the company competes. Doesn't reach the two structural questions that determine what the multiple is actually pricing: whether the company is solving the right underlying challenge, and whether the product is designed so agents have to operate inside it rather than automate around it. Both questions belong in commercial diligence. Neither is currently in the standard scope.
Partially covered — this is the opening
The framework

The two questions that belong in every management presentation.

Both questions surface in the room. Neither is complicated to ask. The answers — and how the management team responds — tell you whether you're pricing infrastructure or something the market has mispriced in your favor.

Move 01 — Question Diagnosis
Is this company solving the right underlying challenge — or the one the category inherited?
Every B2B SaaS category organizes itself around a question. Most companies never examine whether it's the right one. The category's inherited question produces a ceiling — a point where executing better stops producing better outcomes, because the question itself has run out of room. A company that has identified the underlying challenge the category was built to address — and is moving toward it — is not competing inside the same frame as everyone else. That distinction is not in the data room. It is in the management conversation.
The question for the management meeting
"When your product is working perfectly — what are your best customers still worried about?" A team that answers immediately and specifically has named the ceiling. A team that deflects is optimizing inside a frame they haven't examined.
Move 02 — Agentic Positioning
Is this an environment agents will depend on — or a workflow they'll automate away?
Most B2B SaaS products are workflows — sequences of steps agents can replicate by calling APIs and stitching together other systems. The products that compound are environments: places where something irreplaceable has accumulated that agents have to operate inside rather than recreate from outside. What accumulates differs by category. The structural characteristic is the same: it lives here and nowhere else. That accumulation has to be designed for — and it has to be organized around the right underlying challenge, or it compounds the wrong thing.
The question for the management meeting
"If a customer cancelled tomorrow and tried to recreate what they've built here using other tools — what would they lose that they couldn't get back quickly?" Infrastructure answers immediately. Workflows struggle.

Getting Move 1 wrong and Move 2 right builds a moat around a ceiling. The environment is real — switching costs, accumulated data, genuine stickiness — but it's organized around an inherited question AI will automate. The moat doesn't disappear. It just stops expanding.

Getting Move 1 right and Move 2 wrong names the right challenge while remaining structurally replaceable. The company understands what it should become. It hasn't built the thing agents depend on. The insight is correct. The infrastructure isn't there yet.

Getting both right is the only position that compounds without a ceiling. The environment is organized around the right underlying challenge. The question pulls the environment forward. The environment makes the question defensible. At identical ARR, growth, and NRR, an asset in this position is not the same asset as one in either failure mode. Standard diligence will not surface the difference.

The worked example

See the framework applied to a real category.

The buy-side category brief applies both moves to a real category — fifteen vendors assessed on two structural dimensions, quadrant-by-quadrant multiple logic, and the IC-ready language that tells your client what they're actually underwriting. The worked example covers Revenue Intelligence. The underlying framework — the two moves, the matrix, and buyer targeting by quadrant — applies to any B2B SaaS category.

Inside the Buy-Side Category Brief — Revenue Intelligence
Section 01
What standard diligence reaches — and where it stops
  • Four workstreams covered — two structural questions not reached
  • Why these aren't gaps in execution but dimensions CDD was never designed to address
  • The two questions named in plain buy-side language
Section 02
The two-move framework applied to Revenue Intelligence
  • 32 years of the same inherited question — what it produced and where it stopped
  • Move 1: the underlying challenge the category was built to address
  • Move 2: environment vs workflow in an agentic world
  • Why the two moves are connected, not independent
Section 03
Fifteen vendors on two dimensions — the full matrix
  • Every significant vendor placed on both structural dimensions simultaneously
  • Why the category is concentrated in one corner
  • The open position — vacant, and not yet priced by the market
Section 04
Two lenses: PE buyer vs strategic acquirer
  • Quadrant-by-quadrant multiple ranges and value creation thesis
  • Specific risks to underwrite in each quadrant
  • Strategic rationale and what each acquirer type can supply
Section 05
How to use this in a live process
  • Where each tool belongs in the buy-side workflow
  • Thesis definition, CDD scope, IC pre-read, management meetings
Section 06
The forward thesis — three directions, five vendors each
  • Where the category can actually go — D1, D2, D3
  • Five vendors with the most credible path in each direction
  • Acquisition path per vendor — what the acquirer would need to supply
Section 07
The two questions and the IC line
  • The two questions that belong in every management presentation
  • What each answer reveals — and what deflection signals
  • The IC line: what your client can say that nobody else in the room will have said
Get the full brief

The buy-side category brief — Revenue Intelligence.

The actual framework applied to a real category. Fifteen vendors. Two dimensions. IC-ready language. Sent directly to your inbox.

No list. No sequence. One brief, sent once.