Reading a target software contracts in due diligence is where the deal team turns a folder of agreements into a map of risk, and it rewards a trained eye. The contracts hold the clauses that decide whether the deal triggers a consent, whether a license can move to the buyer, how exposed the estate is to an audit, and how the next renewal will price. None of that is visible from a spend summary or a system diagram. It is read out of the agreements themselves, clause by clause, which is why contract reading is a core part of software due diligence.
The work is not a legal opinion, which the buyer counsel provides, but a commercial read of where the risk and the leverage sit. A clause that requires consent on a change of control is a negotiating point. A vague license metric is a place where deployment and entitlement can drift apart unnoticed. An audit rights clause tells the buyer how exposed it is the moment it owns the estate. Reading for these is a discipline, and the sections below set out what to look for.
Reading a target's software contracts in due diligence
Reading a target software contracts in due diligence means working through every material agreement for a fixed set of clauses, not skimming for the headline price. The priority clauses are change of control, assignment, audit rights, the license metric and its definitions, and the renewal and price mechanics. Each one answers a specific deal question, and together they describe both the risk the buyer inherits and the leverage the publisher holds. The aim is a clause level map the deal team can act on, not a summary of what the target spends.
The change of control clause sits at the top of the list because it can hand the publisher a lever at the worst possible moment. Depending on the wording, a change of ownership can require consent, allow the publisher to terminate, or trigger a repricing of the agreement. Which of those applies depends on the deal structure, as explained in software due diligence for stock vs asset purchases. Reading the clause closely is the only way to know whether the deal is a formality or a trigger.
Why the license metric deserves the closest read
The least glamorous clause, the license metric and its definitions, is often where the largest exposure hides. A metric defined loosely, or defined in a way the target has not actually followed, is where deployment and entitlement drift apart. An Oracle processor metric that does not match how the target virtualises, or an SAP named user definition the target has not applied consistently, can each carry seven figure exposure. Reading the metric against how the software is actually deployed is the bridge between the contract and the measurement, and it feeds directly into building a software license position during diligence.
What audit rights tell the buyer
The audit rights clause is the publisher route into the buyer estate after close, so it deserves a careful read. It sets how often the publisher can audit, what notice it must give, and what it can inspect. A broad audit right with short notice is a standing risk the buyer should price, because the publisher can exercise it at will once the deal completes. As of mid 2025, SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million in disputes tied to indirect and inherited licensing, the kind of claim that begins with an audit right being exercised. Knowing the audit terms before close lets the buyer prepare rather than react.
Key takeaways
- Reading contracts turns a folder of agreements into a clause level map of risk and leverage.
- Prioritise change of control, assignment, audit rights, the license metric, and renewal and price.
- The change of control clause can require consent, allow termination, or trigger repricing on the deal.
- The license metric is the least glamorous clause and often where the largest exposure hides.
- Audit rights define how exposed the buyer is to a publisher audit the moment it owns the estate.
How contract reading connects to measurement
Contract reading and license measurement are two halves of one exercise. The contracts define the metric and the entitlement; the measurement counts the deployment. Reading the contracts without measuring leaves the buyer with terms but no exposure number. Measuring without reading the contracts leaves the buyer with a count but no basis to interpret it. Done together, they produce an effective license position the deal team can price. The data needed to complete the measurement is requested from the target as described in how to request software data from a target.
What a good contract read produces
A good contract read produces a register: every material agreement, its key clauses, the deal questions each one raises, and the action required. The register flags the agreements that need consent, the metrics that need measuring, the audit rights that need pricing, and the renewals that carry uplift risk. It becomes a working document for the negotiation, not a static summary, and it feeds the deal team conditions, indemnities and price adjustments. That register is one of the core deliverables described in software due diligence deliverables.
Recommendations for buyers
- Read every material agreement for a fixed clause set rather than skimming for the headline price.
- Put change of control first, and confirm whether the deal structure makes it a formality or a trigger.
- Read each license metric against how the software is actually deployed, not how the contract assumes.
- Price the audit rights as a standing exposure the buyer carries from the day it owns the estate.
- Produce a contract register that links each clause to a deal action: consent, measurement, condition or indemnity.
A disciplined contract read is what turns the paperwork into leverage, and it is a core step in the software due diligence method. The full workstream is delivered through our software due diligence service.