Software due diligence is the buyer side review that maps and quantifies a target software licensing position and audit exposure before a transaction closes.
What is software due diligence? It is the part of buy side diligence that examines a target software estate to find the licensing and audit exposure that standard financial and legal review usually miss. It looks at what the target is licensed to run, what it actually runs, and the gap between the two. That gap is where inherited liability lives, and it is almost always latent and unquantified until a publisher audit surfaces it after close.
Software due diligence builds an effective license position for the publishers that audit hardest, tests it against real deployment, and sizes the worst case and likely settlement for any shortfall. It also reads the contracts themselves for change of control and assignment terms that the transaction can trigger, because deal structure decides which clauses bite. The output is a quantified exposure the deal team can price, allocate to the seller, or remediate before signing rather than inherit silently.
The licensing position of an acquired company is a liability nobody has mapped. It sits off the balance sheet, outside the quality of earnings analysis, and unowned by the deal team until it surfaces. A change of ownership resets the audit clock at the major publishers, so acquired companies are routine audit targets in the first year or two after close. SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million over disputed and inherited licensing, the latter confirmed in the English High Court in SAP UK Ltd v Diageo Great Britain Ltd in 2017 (as of June 2026). Diligence is how a buyer sizes that risk before a vendor prices it instead.
Oracle, SAP, Microsoft and IBM are the long standing audit leaders, with Broadcom owned VMware, Salesforce and ServiceNow increasingly active as of June 2026. A competent review prioritises these names, reconstructs entitlement against usage, and scales the depth to the deal timeline. The floor is always a quantified exposure for the tier one publishers, because that is what moves price or supports a protection.
| Deliverable | What it answers | How the deal team uses it |
|---|---|---|
| Effective license position | Entitlement against usage | Sizes the compliance gap |
| Cost to cure | What fixing the gap costs | Supports a price chip or holdback |
| Change of control review | Which clauses the deal triggers | Plans consent and timing |
| Audit risk ranking | Which publishers will test | Sequences post close work |
Related reading: see the M&A software glossary hub, plus effective license position and latent licensing liability.
Map and quantify the licensing exposure in your target or portfolio before it becomes a post close audit. Independent, buyer side, paid only by the acquirer.
Talk to a software M&A advisor