Software diligence reprices a deal by USD 6M
How a pre signing software license position moved the purchase price by 6 million dollars and rebalanced the warranty package on a mid market acquisition.
This case study is an anonymised composite drawn from representative engagements. It names no real parties and uses approximate figures to illustrate typical outcomes.
This software diligence reprices a deal by usd 6m case study shows how a deliberate license position, built before signing, became a 6 million dollar lever in the negotiation. License exposure is usually latent and unquantified in standard diligence, then lands as a publisher audit after close, so finding it early changed both the price and the warranty package.
Inside the software diligence reprices a deal by USD 6M case study
| Finding | Quantified | Deal effect |
|---|---|---|
| Deployment over entitlement | Material | Price adjustment |
| Unassignable agreements | Material | Condition to close |
| Residual uncertainty | Bounded | Warranty and indemnity |
| Total price movement | ~$6M | Reflected in terms |
Situation
The target sold software but also ran a heavy internal stack: a tier one ERP, a major database platform, a commercial analytics suite, and a large estate of engineering tools. The corporate development team had a quality of earnings report and a legal review of the contracts. Neither one quantified the licensing position. The assumption baked into the model was that software was a known, recurring cost with no balance sheet surprise.
The deal was moving toward signing at a fixed enterprise value. Our scope was narrow and time boxed: build a defensible license position for the publishers most likely to audit after close, and size any gap in dollars the deal team could act on.
Exposure found
The mapping surfaced three material items. The ERP was licensed by named user, but indirect and digital access from connected systems pulled far more usage into scope than the named user count reflected. The database estate carried the familiar virtualisation scoping problem. And a block of engineering tools had drifted onto more machines than the entitlements covered after years of unmanaged growth.
Sized conservatively, the combined remediation and true up exposure sat near 6 million dollars. This is the pattern the public record keeps showing. SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million over disputed and inherited licensing, both widely reported as of 2017 and 2018. The dollars in this composite were smaller, but the mechanism, latent under licensing surfacing as a post close claim, was identical.
Approach
We presented the exposure as a single, sourced number with the assumptions exposed so the deal team and the seller could both test it. We did not argue law. We quantified commercial risk and handed the legal interpretation of the contracts to the buyer's counsel.
Outcome
The finding moved the deal. Rather than walk, the buyer and seller agreed a 6 million dollar adjustment, split between a headline price reduction and a specific indemnity that ring fenced the licensing exposure for a defined period. The acquirer no longer carried an unpriced liability into ownership, and the seller retained the deal by absorbing a risk that was genuinely theirs.
Post close, the same map became the remediation plan. The buyer closed the engineering tool gap quickly and entered the inevitable ERP conversation from a position of evidence rather than surprise.
Lessons for buyers
- License exposure is usually latent and unquantified in standard diligence.
- A pre signing license position quantified the gap as a credible number.
- The finding moved the purchase price by about 6 million dollars.
- Unassignable agreements became a condition to close.
- Residual uncertainty was covered by the warranty and indemnity package.
- Build the position before signing. Quantify the license gap while the leverage favours the buyer.
- Make it credible. Model the likely settlement so the number holds at the table.
- Use it to reprice. Convert the exposure into a price adjustment and conditions to close.
- Rebalance the warranties. Push residual uncertainty into indemnities, not the buyer.
This outcome is the work of our software due diligence service, applied to the method in the software due diligence guide. For the questions buyers ask most, see the FAQ below.
Frequently asked questions
How does software diligence reprice a deal by USD 6M?
By quantifying licensing and audit exposure the standard file missed, then translating it into deal terms. In this composite the 6 million dollar finding split into a headline price reduction and a specific indemnity ring fencing the licensing risk.
Why does a quality of earnings report miss this?
A quality of earnings report normalises and verifies earnings. It does not build a publisher by publisher license position or measure indirect access. Licensing compliance sits outside its scope, which is why a dedicated software read is needed alongside it.
What is indirect or digital access?
It is usage of licensed software by people or systems that connect to it through other applications, integrations, or bots. Major publishers count this usage even when it does not appear in a named user list, and it is a frequent source of large true up claims.
Can diligence findings really change the purchase price?
Yes, when the finding is specific, sourced, and quantified. A defensible dollar figure gives the deal team something to negotiate. This is why pre signing exposure mapping pays for itself many times over on deals where the estate is material.
Do you provide legal advice on the indemnity?
No. We quantify and frame the commercial exposure. Your own counsel drafts and interprets the indemnity and warranty language. We are an independent, buyer side commercial and licensing advisor only.
Could a license position move your price?
Request a confidential software M&A risk assessment. We quantify the exposure before you sign.