What strategic buyers actually diligence in a B2B software business

Strategic acquirers of software businesses tend to arrive with a thesis: a product gap to fill, a customer base to cross-sell into, a vertical or geography to enter. The thesis gets them to the table. What determines price and structure is whether the target’s data supports that thesis once the acquirer’s corporate development team, product leaders and accountants have spent several weeks inside the business.

Sellers often prepare for diligence by polishing the growth story. Experienced acquirers spend less time on the story and more on a handful of measures and documents that reveal how durable the revenue is and how expensive the product will be to own. What follows is where we see them focus, roughly in the order it tends to matter.

Net revenue retention, calculated their way

Net revenue retention is usually the first number a strategic buyer recomputes. It captures expansion, contraction and churn within the existing customer base, and it is the best single indicator of whether the product is becoming more valuable to the customers who already use it. For B2B software serving mid-market and enterprise customers, retention above 110 percent is generally viewed as strong; below 100 percent, the business must replace lost revenue before it can grow at all.

The difficulty is definitional. Sellers sometimes calculate the figure on a blended basis, exclude customers who churned in their first year, or count price increases and new-product cross-sells in ways that flatter it. Buyers will rebuild it from the billing system, customer by customer, on a trailing twelve-month basis. Presenting the methodology alongside the number, and reconciling it to the subscription ledger, avoids an awkward discovery later.

Gross margin and what sits in cost of revenue

Software is valued on the assumption of high gross margins, and buyers test that assumption carefully. Hosting, third-party licenses embedded in the product, customer support, onboarding and implementation staff all belong in cost of revenue. A business that reports 85 percent gross margin with support and implementation booked as operating expense may look closer to 70 percent once restated.

Strategic buyers also separate subscription gross margin from services gross margin. Professional services that run at a loss to support software sales are common and acceptable, but the acquirer will want to know whether services are a temporary onboarding cost or a permanent feature of every deployment. Heavy per-customer customization suggests a product that does not yet scale.

Cohort data

Aggregate metrics can conceal a great deal. Cohort analysis, which groups customers by the quarter or year they were acquired and tracks each group’s revenue over time, shows whether recent customers behave like older ones. Buyers look for a few patterns in particular:

• Whether newer cohorts retain and expand at rates similar to older ones, or whether product fit is weakening as the company moves into new segments.
• How long a typical cohort takes to recover its acquisition cost.
• Whether a small number of large customers in one cohort are carrying the overall retention figure.
• How logo churn compares with dollar churn, which reveals whether smaller customers are leaving quietly.

Companies that have never built cohort reporting should do so before a process, not during one. The data almost always exists in the billing system; it simply has not been organized.

Contract terms, not just contract values

A strategic buyer’s legal team will read the customer contracts, at least for the largest accounts and a representative sample of the rest. They are looking for terms that affect the value of the revenue after closing:

• Change-of-control or assignment provisions that allow customers to terminate or renegotiate on acquisition.
• Termination for convenience, which turns a multi-year contract into something closer to month-to-month.
• Most-favored-customer pricing, caps on annual price increases, and uncapped liability or unusual indemnities.
• Source code escrow arrangements and service level commitments with meaningful credits.
• Data processing terms and restrictions on where customer data may be hosted, which bear directly on integration plans.

The value of recurring revenue depends on how enforceable it is. Three-year contracts with termination for convenience are worth less than they appear, and buyers will adjust accordingly.

The value of recurring revenue depends on how enforceable it is.

Technical debt and the cost of integration

Strategic buyers typically send product and engineering leaders to assess the codebase and architecture. They are rarely looking for perfection. They want to estimate what it will cost to bring the product up to their standards for security, scalability and integration with their own platform, and that estimate finds its way into the price.

The common findings are familiar: an aging framework that needs replacing, single-tenant deployments that make upgrades expensive, limited automated testing, undocumented infrastructure, and open-source components under licenses that conflict with the buyer’s policies. Security posture receives particular attention. A recent penetration test, a SOC 2 report where the customer base expects one, and a clean open-source license scan go a long way toward narrowing the range of outcomes.

Sellers should resist the temptation to minimize these issues. An honest technical overview that identifies known debt and the plan to address it is far more credible than one claiming none exists, and it keeps the discussion focused on the size of the problem rather than on whether management understands it.

Key-person risk

In smaller software companies, architectural knowledge, product direction and the most important customer relationships often sit with two or three people, frequently including a founder. Buyers will map who knows what. They will ask who can deploy to production, who understands the oldest parts of the codebase, and whom customers call when something breaks.

Strategic acquirers address this through retention packages, employment agreements and, at times, earn-outs tied to continued involvement. Sellers can reduce the discount by documenting systems, spreading knowledge across the engineering team, and confirming that every key employee and contractor has assigned their intellectual property to the company. The buyer is acquiring not only a product but the team’s ability to keep improving it.

Preparing for the questions you will be asked

None of these areas is a surprise to an experienced acquirer, and none should be a surprise to the seller. The companies that achieve the strongest outcomes have already run the analysis buyers will run, know where their numbers are weak, and can explain why. A buyer who arrives at the same answer the seller presented gains confidence in everything else. A buyer who arrives at a different answer starts to wonder what else is wrong.