Due diligence
·
10 min read

Commercial Due Diligence: Test the Revenue Story

A practical commercial due diligence guide to market demand, customer evidence, retention, pricing and forecast assumptions, with a usable review checklist.

Published byVDR Directory Editorial Team
On this page (12 sections)▼

Commercial Due Diligence: Test the Revenue Story

A practical commercial due diligence guide to market demand, customer evidence, retention, pricing and forecast assumptions, with a usable review checklist.

Professionals comparing charts and information

Commercial due diligence tests whether a business can sustain and grow demand for its products. The central question is not simply whether last year's revenue was recorded correctly. It is whether customers will keep buying, why they choose the business and which assumptions support the proposed growth plan.

This guide helps acquisition and investment teams organize that investigation around market, customer and revenue evidence. It explains how to request useful data, challenge a forecast and record uncertainty without treating a neat data room as proof of a strong business.

Separate the commercial question from the accounting question

Financial diligence examines accounting, earnings and financial exposures within its agreed scope. Commercial diligence investigates demand, competitive position and the route to future revenue. The workstreams overlap, but they answer different questions and need a shared definition of the numbers they use.

For example, a financial review might reconcile reported sales to accounting records. A commercial review might examine whether a large customer's purchasing pattern is likely to continue. Neither question is answered fully by the other. Link the findings rather than treating one review as a substitute.

Begin with the deal thesis. If the price assumes expansion into a new customer segment, make that segment a specific research question. If the thesis relies on price increases, investigate buying alternatives and contract constraints. Do not spend most of the review on general industry background while the actual value assumption remains untested.

Bain's primary description of commercial diligence emphasizes market outlook, competitive position and customer advocacy. The working process below is our editorial framework for connecting those broad questions to evidence; it is not a reproduction of a proprietary consulting methodology. Bain: Private Equity Due Diligence, commercial review scope

Charts and notebook beside a laptop

Translate the investment thesis into requests

Create a hypothesis list with evidence needed to support or challenge each proposition. Identify the owner, period and expected output. A useful request asks for the customer cohort definition and underlying reconciliation, not just a slide labelled strong retention.

Commercial hypothesisEvidence to requestWhat could challenge it
Existing customers are durableRenewals, churn reasons and cohortsGrowth hides losses in older cohorts
Prices can riseContracts, discounts and buyer interviewsBuyers have substitutes or capped terms
New segment is reachableSegment pipeline and sales historyInterest has not become paid demand
Product wins consistentlyWin/loss records and customer reasonsWins depend on unusual discounts
Market expansion is realisticDefined buyer universe and spend assumptionsHeadline market includes irrelevant buyers
Sales capacity supports the planRep productivity, ramp time and cycle dataHiring assumptions exceed observed output

Start with the few questions most likely to change the investment view. Expand the review when evidence suggests a material issue. A larger request list is not automatically a better investigation; it may consume management time without changing the decision.

Explain evidence gaps. If reliable win/loss records do not exist, use a clearly scoped interview sample and describe its limitations. Do not present a reconstructed anecdotal sample as a complete historical dataset.

Define the market from the customer's buying task

Describe the customer, the problem, the buying trigger and the budget that funds the purchase. A business selling compliance software to regional lenders does not address every dollar spent on enterprise software. The relevant market boundary should reflect who could actually buy the product.

Build a bottom-up model where possible. Specify the number of eligible buyers, realistic annual spending, geographic scope and assumptions about adoption. Keep sources, dates and exclusions visible. Distinguish the total possible opportunity from what the company can reach with its current product and sales channel.

Compare the model with external evidence, but do not average inconsistent market reports into an apparently precise answer. Different reports may include different products, geographies or revenue categories. Explain the difference before using their numbers.

Ask what must happen for the market to become accessible. A new certification, integration, distribution relationship or buying process can be a meaningful dependency. A large buyer universe provides little near-term support if the company cannot yet serve it or pass procurement requirements.

Examine customers as cohorts, not only a total

Agree a consistent period and customer identifier. Separate new sales, expansion, contraction and lost customers. Keep one-time work apart from recurring revenue. Where currencies or acquisitions affect comparisons, disclose the adjustment rather than mixing different bases.

Inspect retention by segment and entry cohort. A single aggregate can hide very different patterns between small customers and large enterprises. Review the reason for losses alongside the amount, because product fit, budget pressure and temporary project completion suggest different future outcomes.

Assess concentration beyond a top-ten table. Ask which accounts share a parent, channel, geography or use case. Ten contracts can still depend on one distributor or one regulatory driver. Investigate relevant renewal dates and contractual terms with the appropriate advisers.

Use identifiable customer data only through an approved handling process. For early analysis, aggregated or suitably minimized schedules may be sufficient. If buyer and seller compete, detailed prices and customer information need a specific competition-law assessment rather than automatic release after an LOI.

Person reviewing charts on a laptop

Interview buyers without selecting only supporters

Agree who can be contacted, how consent or authorization is handled and what the interviewer may disclose. Include a spread of customer sizes, tenures and use cases where the process permits it. A list of management's happiest references is useful but has obvious selection limits.

Use open questions: what task did you buy the product for, what alternatives did you consider, what would make you leave and how is the next renewal decided? Follow the customer's explanation before offering suggested answers. Asking whether service is excellent encourages a different response from asking about the last issue they encountered.

Separate stated intention from observed behavior. A customer may say they love a product while reducing usage or delaying renewal. Conversely, a critical user may continue buying because the product solves an important problem. Capture both the interview and the relevant operating evidence.

Do not turn a small interview sample into a statistically representative market claim. Explain selection, sample size and missing groups. The report should state what the interviews suggest and what needs further testing, not imply that a few calls measure every buyer's opinion.

Test pricing and sales execution together

Review realized pricing rather than list prices alone. Understand discounts, bundled services, implementation work and renewal terms. A proposed price increase can look attractive in a model while changing conversion, churn or service expectations.

Follow the pipeline through defined stages. Check when opportunities were created, what qualification means and whether close dates repeatedly move. Keep booked contracts separate from unsigned proposals. Apply conversion assumptions by comparable segment when reliable data supports the approach.

Assess the hiring plan against observed ramp time and productivity. If an established salesperson carries important customer relationships, a new hire may not reproduce the same output immediately. Include onboarding, management capacity and lead supply instead of treating headcount as a direct revenue multiplier.

Review loss reasons and stalled deals. If customers consistently ask for an integration the company lacks, the sales forecast may depend on a product milestone. Connect that issue to technical diligence and the product plan rather than counting the same dependency as solved in both workstreams.

Worked example: a forecast needs two corrections

This is a fictional analytical exercise. A target reports $10 million of revenue and forecasts $13 million next year. Review shows that $2 million of the historical total came from one-time projects, leaving an $8 million recurring baseline under the agreed definition.

Management's recurring forecast assumes $1.6 million of customer expansion and $2 million of new recurring sales without losses, producing $11.6 million. The team models a scenario with $800,000 of contraction and churn: $8 million minus $800,000 plus $1.6 million plus $2 million equals $10.8 million. It separately models one-time projects instead of calling them recurring growth.

Customer review also shows that one account contributes $2 million of the $8 million recurring baseline, or 25%. Its renewal is not yet decided. A sensitivity excluding that entire amount would reduce the recurring scenario to $8.8 million, before any related cost response. This is an illustrative stress test, not a prediction that the account will leave.

The team now asks for renewal evidence, project pipeline support and the resources needed for expansion. The conclusion is not simply that the forecast is wrong. It is that the original presentation combined different revenue types and omitted losses, so the growth case needs clearer support and a visible downside.

Colleagues pointing to charts on a laptop

Structure the report around decision impact

Use findings that a deal lead can act on. Each should identify the tested proposition, evidence, limitation and implication for the thesis. Avoid pages of descriptive research without explaining whether the evidence strengthens or weakens the case.

FindingEvidence or gapDecision implicationNext step
Revenue types mixedProjects included in recurring totalReset growth baselineReconcile with finance
New segment unprovenFew paid wins in proposed segmentExpansion remains an assumptionValidate buyer demand
Large renewal unresolvedConcentration and renewal date identifiedDownside sensitivity neededApproved customer review
Price growth uncertainInterviews mixed, contracts not fully reviewedAvoid single-point upsideExamine constraints
Sales hiring aggressiveRamp assumptions exceed available historyTiming risk to forecastStage the capacity plan

Keep fact, interpretation and recommendation distinct. A contract renewal date is a fact from reviewed evidence. A concern about renewal is an interpretation. A decision to reduce a growth assumption is a modeling recommendation. Readers should be able to trace one to the other.

Keep evidence usable in the data room

Use folders for market evidence, customer analysis, pricing, pipeline and business-plan assumptions. Provide a data dictionary for schedules and a short explanation of calculations. The room should support rechecking the analysis without requiring a new call for every column.

Preserve snapshot dates and approved versions. If management changes a churn definition, explain the effect on comparisons. Record the question and response that produced the correction. Quiet replacements can make a careful reviewer appear inconsistent when the underlying source has changed.

Do not assume watermarking prevents misuse or viewing activity proves acceptance. Use permissions, approved handling instructions and appropriate professional protocols. Treat platform analytics as delivery context rather than commercial evidence about customer demand.

Colleagues reviewing charts together

Record limitations and carry findings into the deal plan

Commercial diligence cannot guarantee future demand or a successful acquisition. Markets change, customers can behave differently and access to evidence may be incomplete. State the most material limits: restricted interviews, short operating history, poor data quality or a segment without comparable sales.

Carry accepted assumptions into the post-deal plan with an owner and a test. If expansion depends on a new channel, identify the milestone that would confirm or challenge it. The review becomes useful after closing when its hypotheses remain measurable rather than disappearing into an archived presentation.

Frequently asked questions

Commercial diligence tests demand, customers, competition and future revenue assumptions. Financial diligence examines accounting and financial exposures within its agreed scope. Reconcile shared numbers and exchange findings, but do not assume either workstream replaces the other.

There is no universal number. Match the sample to the customer base and questions, then disclose selection limits and missing segments. A handful of positive references should not be described as statistically representative research.

No. Release what the review needs through the approved process. Customer identities, pricing and competitive plans can require restricted handling, especially with a competing buyer. Professional advice determines the appropriate protocol.

Before you proceed

Test the revenue story one assumption at a time. A commercial report is strongest when its conclusions can be traced to customer and market evidence, and its unresolved questions remain visible in the investment decision.

Sources and editorial disclosure

Primary documentation reviewed October 11, 2026. The operational templates and worked examples are editorial recommendations, not claims of completed transactions or product testing.

VDR Directory is published by the team behind SendNow. This ownership is relevant when considering product recommendations. Stock photos illustrate general workflows. Legal, tax, regulatory and security decisions depend on the transaction and applicable requirements; involve the responsible specialist. No platform can guarantee confidentiality, transaction success or search rankings.

Related Guides & Research

Recommended next reading for deal teams and transaction leaders.

View all →