Software spend due diligence that turns a target's licensing and SaaS run rate into a defensible number you can price into the deal, not a surprise that lands after close.
Software spend due diligence measures the one number standard diligence leaves blurred: what the target will actually pay for software once contracts, license metrics, and deployed usage are tested against each other. The figure a target reports today is rarely the figure a buyer inherits. Renewals reprice, true ups land, and a change of ownership can trigger consent or repricing clauses that lift the run rate the moment the deal closes.
We start with the contracts and the invoices, then go where the quality of earnings work stops. We reconcile every material agreement against deployed usage, because deployment against entitlement is the only measurement a publisher uses when it audits. We map the renewal calendar so the buyer knows which agreements reprice in year one and year two. We test the license metrics that are easy to breach quietly, such as processor counts, named users, and indirect or digital access. And we read the change of control and anti assignment terms that decide whether a deal structure preserves the target's pricing or hands the publisher a reset.
Inherited software licensing exposure is usually latent and unquantified in standard due diligence, and it lands as a publisher audit after close. Public reporting shows how large that tail can be. As of June 2026, SAP was reported to have pursued AB InBev for a figure in the region of 600 million dollars, and the Diageo Great Britain Ltd v SAP UK Ltd judgment, [2017] EWHC 189 (TCC), established that indirect access to SAP through a connected system can itself require licensing. A buyer who has not measured this exposure is pricing the deal blind to its largest software variable.
Spend diligence is only useful if it arrives in time to act on. We work to the deal calendar and deliver in stages. An early read flags the publishers and contracts that carry the most risk, so the deal team knows within days where the exposure concentrates. A full read follows with a quantified range by publisher, the renewal and true up events that will move the run rate, and the deal structure questions that change which clauses bite. Because we are independent and paid only by the acquirer, every figure is built to survive the investment committee rather than to justify a vendor relationship.
| Area reviewed | What we test | Why it moves the number |
|---|---|---|
| Deployed usage | Installs and consumption against entitlement | Closes the gap a publisher audits on |
| Renewal calendar | Reprice dates and uplift terms | Reveals year one and year two cost rises |
| License metrics | Processors, named users, indirect access | Surfaces quiet breaches before they compound |
| Change of control | Consent, termination, and reprice triggers | Shows which deal structures protect pricing |
| SaaS portfolio | Overlap, autorenewal, and seat utilisation | Finds duplicate tools and stranded seats |
The figure a target carries in its accounts reflects what it has negotiated and consumed to date. It does not reflect what the next renewal will cost, what an audit would find, or what a change of ownership will trigger. Each of those is a forward event that a financial review is not built to price, and each one tends to move the run rate in the publisher direction rather than the buyer direction. A target that has under invested in software asset management is almost always carrying latent exposure it cannot see, and that exposure becomes the buyer problem the day the deal closes.
The pattern repeats across publishers. Oracle audits processor counts and options usage that grew quietly over years. SAP tests named users and indirect access through connected systems. Microsoft reconciles enterprise agreements against actual deployment and cloud consumption. IBM measures sub capacity that was never properly reported. Broadcom has reshaped VMware pricing in ways that punish unprepared renewals. None of this appears on an invoice, which is exactly why it has to be measured before the buyer commits a price.
A quantified spend baseline does three things for the buyer. It lets you price the forward run rate into the model rather than discovering it in year one. It gives you a specific basis to negotiate the offer or to seek reps, warranties, or an indemnity for licensing exposure. And it builds the first hundred day plan, so the integration team starts with a map of which renewals to prepare for and which publishers to expect contact from. We provide commercial and licensing advisory, not legal advice, and we recommend your own counsel for the interpretation of any contract term or claim.
A reseller earns more when your spend grows, and a vendor aligned advisor protects the publisher relationship. Neither can hand an acquirer a clean read. We hold no affiliation with any software publisher or reseller and are paid only by the buyer, so the spend figure we produce is the figure that holds up under scrutiny when the deal is challenged.
Software spend diligence sits alongside our software due diligence service and feeds the method in our software due diligence guide and software in deal valuation pillars. See it work in practice: diligence reprices a deal by 6 million dollars, SAP risk quantified before signing, and latent VMware exposure found pre deal. Or review the full range of services.
We turn a target's licensing and SaaS run rate into a defensible number before you sign. Tell us about the deal and we respond within one business day.
Book a confidential call