Home/Services/IT Diligence Licensing
For buyers and deal teams

IT due diligence software licensing done right

IT due diligence software licensing adds the entitlement measurement an architecture and security review leaves out, so the largest hidden software cost is priced before close.

IT due diligence software licensing is the part of the IT diligence workstream that standard reviews treat lightly and publishers treat seriously. An IT diligence team will assess architecture, security, and technical debt, but the licence position underneath those systems is where a target's largest hidden cost usually sits. We add the licensing measurement that turns an IT review into a complete one.

Where software licensing fits in the IT due diligence workstreamTimeline showing software licensing as a distinct stage within the broader IT due diligence process.IT scopesystems andarchitectureSecuritycontrols andriskLicensingusage versusentitlementCostrun rateand renewalsPlanfirst hundreddays
Software licensing as a distinct stage within the broader IT due diligence workstream.

Why IT due diligence software licensing needs its own focus

IT due diligence software licensing is different from the rest of the workstream because it measures entitlement, not function. A system can be well architected, secure, and modern, and still be deployed far beyond what its licences permit. That gap does not show up in an architecture review or a security assessment. It shows up when a publisher audits after a change of ownership, which is a common trigger. We reconcile deployed usage against entitlement for the publishers that matter and quantify the exposure so it joins the rest of the IT diligence findings as a priced item.

Inherited software licensing exposure is usually latent and unquantified in standard due diligence, and it lands as a publisher audit after close. As of June 2026, public reporting shows SAP 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), confirmed indirect access can require licensing. An IT diligence review that skips licensing leaves the largest software variable unpriced.

IT due diligence workstreams and where software licensing exposure lives
IT diligence areaTypical focusLicensing exposure
InfrastructureArchitecture and resilienceProcessor based licence breaches
ApplicationsFit and technical debtNamed user and edition overage
Cloud and SaaSConsumption and toolingAutorenewal and duplicate seats
SecurityControls and postureTooling licensed below deployment
Change of controlContinuity of serviceConsent and reprice triggers

How licensing exposure escapes a standard IT review

A standard IT due diligence review is built around capability and risk. It asks whether the architecture will scale, whether the security posture is sound, and whether technical debt will slow the combined business. Those are the right questions, but none of them measures entitlement. A platform can pass every architectural test and still be deployed far beyond what its licences permit, because the deployment that creates exposure is invisible to a review that looks at how systems are built rather than how they are licensed. The result is that the single largest hidden cost in many estates sits outside the scope of the workstream meant to surface it.

IT due diligence software licensing fixes that by treating entitlement as its own measurement. We take the deployment data the IT review already gathers, such as server inventories, virtualisation maps, and user directories, and we reconcile it against the licence entitlement for each material publisher. Virtualisation is a frequent culprit, because spreading a licensed workload across a cluster can multiply the licensable footprint without anyone changing a contract. The output joins the IT diligence report as a quantified line, so the deal team weighs the licence liability against the other findings and prices it with the same discipline.

How licensing joins the IT diligence report

The licence finding belongs in the IT diligence report as a quantified line, not a footnote. We deliver a range by publisher, the renewal and audit events that will move it, and the change of control terms that depend on deal structure. That lets the deal team weigh the software liability against the other IT findings and price it into the offer. Because we are independent and paid only by the acquirer, the figure is built to survive the investment committee. We provide commercial and licensing advisory, not legal advice, and recommend your own counsel for the interpretation of any contract term.

Key takeaways

  • IT due diligence software licensing measures entitlement, which architecture and security reviews do not.
  • A well built system can still be deployed beyond its licences.
  • A change of ownership commonly triggers a publisher audit after close.
  • Quantifying licensing turns an IT review into a complete, priced assessment.

Recommendations for buyers

  1. Add licensing to the IT diligence scope. Architecture and security do not measure entitlement.
  2. Focus on the publishers that audit. Oracle, SAP, Microsoft, IBM, and Broadcom for VMware carry the exposure.
  3. Price the gap. Bring the licence finding into the IT diligence report as a number.
  4. Build the first hundred day plan. Know which renewals and audits to expect before close.

Pair this with our software due diligence service and the software due diligence guide pillar. In practice: hidden licensing gaps mapped across borders and latent VMware exposure found pre deal.

Frequently asked questions

What is IT due diligence software licensing?
It is the part of IT due diligence that measures a target's deployed software against its licence entitlement and quantifies the inherited exposure, which architecture and security reviews do not cover.
Why does a standard IT review miss licensing exposure?
An IT review assesses how systems are built and secured. It does not measure whether deployment exceeds entitlement, which is the gap a publisher audits and the largest hidden software cost.
Which systems carry the most licensing risk?
Processor based products like Oracle databases and VMware, named user systems like SAP, and enterprise agreements like Microsoft tend to carry the most exposure inside an IT estate.
Does a change of ownership trigger audits?
Yes. A change of control is a common audit trigger, which is why measuring the licence position before close protects the buyer.
Are you affiliated with any vendor?
No. We are paid only by the acquirer and hold no affiliation with any publisher or reseller.

Adding licensing to your IT due diligence?

We measure the licence position underneath the IT estate and price the exposure. Tell us about the deal and we respond within one business day.

Book a confidential call