Buying an Asset

Standard diligence tells you a lot. This lens helps isolate two structural questions that may not be tested explicitly enough.

A rigorous commercial diligence process covers the market, the competition, the customers, and the management team with real analytical depth. What it may not isolate explicitly are two structural questions that can change how an asset is understood, valued, and assessed.

The first is whether the product is organized around the right underlying challenge — or the inherited one the category has been answering for years. The second is whether, in an agentic AI environment, the product is something agents will have to operate inside — because data, history, and decision records accumulate here and nowhere else — or a workflow they can replicate from outside.

Both questions are often inferred indirectly through customer calls, product diligence, and management interviews. This framework isolates them explicitly so they can be discussed, tested, and factored into the investment view.

Best fit
  • —PE principals and VPs
  • —Corp dev leaders
  • —Operating partners
  • —Boutique M&A advisors on buy-side mandates
Best use
  • —IC pre-read
  • —Management meeting prep
  • —Commercial diligence sharpening
  • —Value-creation hypothesis testing
Practical application

What this lens can change in a live process.

Three specific places where isolating these two questions explicitly can sharpen the investment view.

01
Management conversation sharpening. Two specific questions belong in every management presentation for a B2B SaaS asset. One surfaces whether the CEO has genuinely identified a different underlying challenge or is fluent in the category's existing language. The other surfaces whether the product is accumulating something agents would have to operate inside. The difference between a borrowed answer and a real one is testable in the room. This framework makes the test explicit.
02
Diligence scope adjustment. If the framework suggests the asset may be approaching a category departure — or is more embedded in the inherited question than the positioning implies — that changes which customer conversations matter most, what product diligence should focus on, and where agentic substitution risk should be stress-tested in the model.
03
Conviction and value-creation calibration. Two assets at identical ARR, growth, and NRR can be in structurally different positions relative to these two questions. The framework can help sharpen where conviction may be too high or too low relative to the evidence — and what the value-creation thesis needs to be if the asset is in the workflow cluster rather than approaching the open position.
The context

What standard diligence covers — and the two structural questions this lens isolates.

Standard commercial diligence is well-designed for what it measures. These two structural questions are often inferred indirectly through customer calls, product diligence, and management interviews — rather than isolated as named questions. That is where this lens adds something.

Workstream 01
Financial Diligence
Validates ARR, NRR, churn, cohort quality, revenue recognition, and financial projections. Tells you whether the numbers are real. Less likely to surface 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. Scope does not typically extend to 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. Less likely to assess 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. The two structural questions — whether the product is organized around the right underlying challenge, and whether agents will depend on it or route around it — are often inferred indirectly here. This framework isolates them explicitly so they can be discussed and tested.
Often inferred — not yet isolated explicitly
The framework

The two structural questions — and how to test them.

Both questions are often inferred indirectly in a standard process. Isolating them explicitly — and testing them in the management meeting — surfaces the structural picture more cleanly and can sharpen conviction and underwriting discussion.

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 may be assessed very differently from one in either failure mode — and standard diligence may not surface that difference cleanly enough to price it.

Scope and role

What this is. What this isn't.

This framework is designed to sharpen specific dimensions of the investment view — not to replace the process it sits inside.

What this is
  • —A structural category lens applied to a specific asset
  • —A way to sharpen management questions and underwriting discussion
  • —A framework for thinking about category ceilings, agentic defensibility, and value-creation logic
What this isn't
  • —A replacement for full commercial, financial, legal, or technical diligence
  • —A technical audit of product architecture
  • —A market study pretending to be live-deal certainty
The worked example

See the framework applied to a real category.

The Revenue Intelligence buy-side brief applies this framework to a specific category — fifteen vendors placed on two structural dimensions, management questions written, diligence implications mapped by quadrant. It is a working example of what the lens produces when applied to a real asset class. The framework — the two moves, the matrix, and the conviction logic by quadrant — applies to any B2B SaaS category.

Inside the Buy-Side Category Brief — Revenue Intelligence
Section 01
What standard diligence covers — and the two structural questions this lens isolates
  • Four workstreams covered — two structural questions often inferred rather than named
  • Why these dimensions are typically assessed indirectly rather than isolated explicitly
  • 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
How the category clusters today — and where the most interesting position may be emerging
  • Every significant vendor placed on both structural dimensions simultaneously
  • Why the category is concentrated in one corner
  • The open position — appears unoccupied based on public positioning, with pricing consequence still emerging
Section 04
How the framework can change diligence focus, conviction, and value-creation logic
  • Quadrant-by-quadrant thesis, diligence implications, and value-creation logic (ranges directional)
  • 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
What strong answers reveal — and how the framework sharpens the investment view
  • The two questions that belong in every management presentation
  • What each answer reveals — and what deflection signals
  • The IC framing: how isolating these questions can sharpen how the investment view is communicated
Two ways to engage
Option 01
Request the RI buy-side brief — the framework applied to a real category, with vendor placements, management questions, and diligence implications.
Option 02
Talk with Mike directly — if you have a live situation and want to discuss whether the framework is relevant before requesting anything.
Talk with Mike →
or request the brief below

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