The difference between legal and commercial software diligence is the difference between asking whether a contract is enforceable and asking what it will cost the buyer to live with. Legal diligence reads the words on the page and tells the deal team what the target is contractually bound to. Commercial software diligence reads the estate behind the words and tells the deal team what the buyer will actually pay, true up, or defend after close. A buyer that runs one without the other inherits a clean legal opinion and an eight figure surprise, or a tidy spend model and a clause that reprices on signing.
This page sets out where each discipline looks, what each one reliably misses, and how to sequence them so nothing falls between the two. It sits under the broader software due diligence method and feeds the commercial findings into post close license reconciliation. For the contract level mechanics, pair it with reading a target software contracts in due diligence.
What legal software diligence covers
Legal software diligence is the work most deal lawyers recognise. It confirms that the target owns or has the right to use the software it runs the business on, that intellectual property in any proprietary code is properly assigned, that open source obligations are disclosed, and that the contracts can survive the transaction. It is concerned with title, enforceability, assignment, and warranty. The output is a legal opinion and a schedule of issues that could impair the deal or sit in the disclosure letter.
That work is necessary and it is good at what it does. A skilled deal lawyer will find the anti assignment clause, the change of control trigger, and the missing intellectual property assignment from a contractor. What the lawyer will not do, because it is not the job, is price the consequence. A clause that lets a publisher reprice on a change of control is a legal finding. The number that repricing produces against this specific estate is a commercial one.
What commercial software diligence covers and why a buyer needs both
Commercial software diligence starts where the contract ends. It reconstructs the deployed estate, compares it against the entitlements the target actually holds, and quantifies the gap as money. It looks at how many seats are deployed against how many are licensed, how processor and core counts map to metric definitions, how virtualisation and cloud hosting change what a publisher can claim, and how usage has drifted since the last true up. The output is not an opinion. It is a number, expressed as a range, that the deal model can absorb as a price adjustment, an escrow, or a post close work plan.
The reason a buyer needs both is that the expensive risks live in the seam between them. Latent licensing exposure is usually compliant on paper and non compliant in practice. The contract permits the software, but the deployment exceeds the entitlement, and that gap is invisible to a pure legal read and invisible to a finance model that trusts the current invoice. It surfaces as a publisher audit after close, which is exactly how inherited exposure tends to land.
Where the difference between legal and commercial software diligence costs you
The handover between legal and commercial work is where value leaks. A lawyer flags a metric definition as unusual but does not model the deployment against it. A finance lead builds a run rate from invoices but never sees the clause that voids the discount on a change of control. Neither party is at fault. The gap is structural, and it closes only when one team reads the contract and the estate together. The table below maps the common findings that each discipline tends to surface, and the ones that only appear when both run in parallel.
Key takeaways
- Legal software diligence confirms title, assignment, and enforceability. Commercial software diligence prices what the estate will actually cost the buyer.
- The expensive risks live in the seam: a deployment that is compliant on paper but exceeds entitlement in practice is invisible to either discipline alone.
- A clause is a legal finding. The money that clause produces against this estate is a commercial finding. A buyer needs both, sequenced together.
- Change of control and anti assignment terms must be read and priced before the deal structure is fixed, because structure decides which clauses bite.
How the split plays out by deal structure
Deal structure decides which clauses bite and therefore how much commercial work the legal findings demand. In a stock purchase the legal entity survives and most contracts ride through untouched, so the commercial focus is on deployment gaps and forward run rate. In an asset purchase or a carve out, contracts have to be assigned or replaced, which is when anti assignment and change of control clauses turn from theoretical into immediate cost. The legal team identifies which agreements need consent. The commercial team prices what consent will cost and what happens if a publisher refuses. Read the structural detail in software due diligence for stock versus asset purchases.
A useful proof point sits in the public record. SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million over disputed and inherited licensing, as reported in coverage of those disputes and as of June 2026. Those are reminders that a clause read but not priced is a clause that can produce a nine figure claim once the estate behind it grows. Always confirm current figures and outcomes with primary sources, since published numbers are point in time.
Recommendations for buyers
- Commission legal and commercial software diligence to run in parallel, with a single point where contract findings and estate findings are reconciled.
- Ask the legal team to flag every metric definition, change of control trigger, and assignment restriction, then hand each one to the commercial team to price.
- Lock the deal structure only after the commercial team has priced the clauses that structure activates, especially in an asset purchase or carve out.
- Carry the priced exposures, not just the legal schedule, into the negotiation and into the first post close reconciliation.
Sequencing the two workstreams in a live deal
The two disciplines fail most often not because either is weak but because they run on separate tracks and meet only at the data room deadline. The sequence that works puts a single reconciliation point in the middle of the timeline. Legal reads the contracts first and produces a clause schedule. The commercial team takes that schedule and, for every flagged metric, change of control trigger, and assignment restriction, runs the deployment against it and attaches a number and a range. The two outputs are then reconciled in one session so that no clause is left unpriced and no priced gap is left without its governing contract. That single reconciliation is the deliverable the deal team actually needs, because it turns a legal opinion and a spend model into one defensible exposure statement.
Time pressure makes this harder, not optional. In a compressed timetable the temptation is to accept the legal schedule as the answer and move on. The discipline is to insist that the highest value clauses, the ones tied to the largest publishers and the largest deployments, are priced before signing even when the long tail is left for the post close work plan. A buyer that prices the top five exposures before signing rarely meets a surprise large enough to move the deal after close.
Why an independent buyer side advisor closes the gap
The commercial read has to come from a party with no incentive to understate the exposure. The target will not surface its own gaps, and a reseller earns on the spend it would otherwise have to shrink. An independent, buyer side advisor reads the contracts the legal team has flagged, maps them against the deployed estate, and hands the deal team a number it can defend in front of an investment committee. That is the difference between a diligence that produces a legal opinion and one that protects value, both before signing and into the reconciliation that follows close.