Change of control clauses that let a strategic vendor renegotiate on close were the single most material recurring finding, and the ones a sampling review most often never opened
A clause that sat dormant for years activates on close. Whether you found it depends entirely on whether anybody opened that particular agreement.
Prepared by Redress Compliance · August 19, 2026 · Acquisition diligence supported, 2024 and 2025.
Executive summary
Change of control clauses that let a strategic vendor renegotiate on close were the single most material recurring finding. They belong in the model before the deal is priced.
Renewal cliffs, large agreements auto renewing inside the integration window, created post close surprises the model had not priced. Structural, common, and invisible without reading the paper.
Sampling based reviews reliably missed risk in the contracts they did not open, which on a large target is most of them.
The output that matters is a cited risk register, not a memo. A negotiator can price a register line by line; nobody can act on impressions.
Why do software contracts matter in a deal?
Because a change of ownership triggers rights the target never had to worry about. Clauses dormant for years activate on close, and each one can move the value of the deal or the cost of integrating it.
The clause that matters most
A change of control provision can let a vendor terminate, renegotiate or reprice an agreement when the target is acquired. On a critical system that is leverage handed to a supplier at the worst possible moment.
Assignment restrictions and renewal cliffs
Assignment restrictions decide whether contracts can move to the acquirer or the new structure at all. Renewal cliffs create cost the deal team never budgeted. Both are structural, both are common, and both are invisible without reading the actual paper.
The vendors whose clauses matter most are the strategic ones, from the major platform vendors to the major database vendors, because losing or repricing those agreements on close reshapes the whole integration plan.
Where does the asymmetry come from?
From the order of work. Deal teams price the target's revenue, people and technology with care, then read a sample of its software contracts in whatever time is left.
| Diligence step | Traditional approach | Whole set approach | What changes |
|---|---|---|---|
| Coverage | A sample, time permitting | The entire contract set | Risk stops depending on which files were opened |
| Change of control scan | Manual, per contract | Flagged across every agreement | The material clause cannot hide in the tail |
| Assignment and renewal review | Associate reading | Extracted with page anchors | Findings are citable, not remembered |
| Risk register | A memo of impressions | A cited, structured register | The output is priceable line by line |
| Timeline | Associate weeks | Days, inside the window | The work finishes before the deal does |
Sampling is a tractability choice, not a risk judgment
The sample is chosen because it fits the hours available, not because the excluded contracts are less risky. On a large target, most of the estate sits outside it.
Illustrative timelines, not a quote
A traditional sample only review runs roughly 21 days and still covers a fraction. Reading the whole set runs closer to 3 days and covers all of it. Those are benchmark scenarios rather than a proposal.
Read one contract before you commit to a method
Upload a single agreement and see the clause level read the whole set approach produces.
Open the decoder →What the acquisition diligence showed
In the acquisition diligence Morten Andersen supported in 2024 and 2025, the software contract set was almost always larger and riskier than the deal team expected. Three findings recur.
- Change of control clauses that let a strategic vendor renegotiate on close were the single most material recurring finding.
- Renewal cliffs, large agreements auto renewing inside the integration window, created post close surprises the model had not priced.
- Sampling based reviews reliably missed risk in the contracts they did not open, which on a large target is most of them.
A software estate can hide a change of control clause that lets a vendor reprice on close, and a sampling review may never open the agreement it lives in.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What should the output actually be?
A structured risk register rather than a memo. Every material clause, the contract and page it sits in, and its deal impact, exportable for the deal team.
A register is priceable; a memo is not
A negotiator can take a register to the table and raise it line by line. A narrative of impressions cannot be acted on, priced, or handed to somebody else to work.
Page anchors are what make it survive challenge
A finding without a citation is an assertion. A finding with the contract name and the page is a position, and the difference matters most when the counterparty disputes it.
The wider extraction discipline is covered in the contract management reference and the executive frame in the CIO guide.
How do you keep the target's contracts secure?
Inside a controlled room, because diligence handles another company's most sensitive commercial data under a confidentiality agreement. Containment is not optional.
What the room has to provide
- Access controls and private share links rather than distributed copies.
- Audit logs on every document view.
- Encrypted storage with no training on the data.
- A clean deletion path on deal close.
The expectations are already codified
They mirror what enterprise buyers demand of any system handling contracts, and they are written down in the risk management framework and the European regulatory framework.
Where the common advice on diligence is wrong
The common advice is to sample the largest contracts by value and accept the rest as immaterial. We disagree.
Materiality is set by the clause, not by the contract value
A change of control provision on a mid sized agreement covering a critical system moves more value than a large agreement with clean assignment terms. Sorting by contract value sorts by the wrong variable.
The buyer side move is to read the whole set, flag the clause types that activate on close, and produce a cited register the deal team can price. The invoice side of integration is covered in the reconciliation guide.
What the diligence work measured, 2024 and 2025
Two findings that recurred across the deals supported, and one is the reason the other kept happening.
Change of control clauses letting a strategic vendor renegotiate or reprice at the moment the transaction closes.
Reading the entire contract set rather than a sample, because the material clause sits wherever it sits.
The finding is only material if somebody opened the agreement. That is the whole argument for coverage over sampling.
Your first five moves
- Scope the whole software contract set before the diligence clock starts, because sampling misses risk in the files it never opens.
- Flag every change of control and assignment clause across the set, since those were the single most material recurring finding in the deals supported.
- Map renewal dates against the integration window, as large agreements auto renewing inside it created costs the model had not priced.
- Produce a cited risk register rather than a memo, with the contract and page behind every finding so the deal team can price it line by line.
- Run the whole thing inside a controlled room with a deletion path. The advisory practice runs the extraction before the deal is priced rather than after it closes.
Frequently asked questions
Why do software contracts matter in a deal?
Because a change of ownership triggers rights the target never had to worry about. Clauses dormant for years activate on close and can move deal value or integration cost.
What is the most material finding?
Change of control clauses that let a strategic vendor terminate, renegotiate or reprice an agreement when the target is acquired.
Why is that so damaging?
Because on a critical system it hands leverage to a supplier at the worst possible moment, and it belongs in the model before the deal is priced rather than after.
What is a renewal cliff?
A large agreement auto renewing inside the integration window. It creates cost the deal team never budgeted, and it is invisible without reading the paper.
Why does sampling fail?
Because the sample is chosen to fit the hours available, not because the excluded contracts are less risky. On a large target most of the estate sits outside it.
Does contract value predict risk?
No. A change of control clause on a mid sized agreement covering a critical system moves more value than a large agreement with clean assignment terms.
What should the output be?
A structured risk register: every material clause, the contract and page it sits in, and its deal impact, exportable for the deal team.
Why not a memo?
Because a register is priceable line by line and a narrative of impressions is not. A finding without a citation is an assertion rather than a position.
How is the data kept secure?
Inside a controlled room with access controls, private share links, audit logs on every view, encrypted storage, no training on the data, and a deletion path on close.
How long should it take?
Days rather than weeks when the whole set is read at once, against roughly three weeks for a sample only review that still covers a fraction of the estate.