The SaaS Contract Risk Hiding in Every M&A Deal
Diligence scrutinises revenue contracts and IP. Dozens of SaaS agreements, and the escalators inside them, usually pass straight through.
The moment a company gets acquired, nothing changes automatically on the vendor side of its SaaS contracts. The notice period is still the notice period. The auto-renewal clause still fires on schedule. The escalator still applies. Nobody adjusts anything just because ownership changed, and very few acquirers ever ask.
I remember a situation where a company we sold to was acquired mid-contract. The new parent company's finance and integration teams were, understandably, focused on the target's core financials, customer contracts, and technical infrastructure. Our contract with them, along with dozens of other SaaS agreements the target held, was not part of that review. The renewal came due a few months after close, on the exact terms it always would have, with an escalator clause the new owners did not know existed applied without anyone questioning it.
Why this gap is so common
Due diligence is built to scrutinise what looks financially or legally significant: revenue contracts, IP, major liabilities. A target company's SaaS vendor agreements, individually modest in size, rarely rise to that level of scrutiny, even though collectively they represent real recurring spend and real contractual risk that becomes the acquirer's problem the moment the deal closes.
What goes unnoticed until it is a problem
- Renewal dates and notice periods falling inside the post-close integration window
- Escalator clauses that trigger on schedule regardless of the ownership change
- Contracts sized for the target's pre-acquisition scale that no longer fit the combined organisation
- Vendor concentration that was not visible until someone mapped the full portfolio
What year one looks like: a fictional deal, month by month
Consent, change of control and group-wide pricing
An acquisition does not automatically reset a SaaS agreement, but it can activate obligations in the existing terms. Some contracts require notice or vendor consent when ownership changes; others restrict assignment to another legal entity. A share acquisition and a transfer of assets or contracts may be treated differently, so check the wording against the proposed deal structure rather than assuming one rule applies to every agreement.
A change of control clause is the term that decides this. It can require the vendor's written consent before close, give the vendor a right to terminate, or allow pricing to be recalculated for the new group. Reading it for every material vendor, before signing, is what turns an unknown into a line in the deal model.
Also read the definition of "Customer" and "Affiliates", alongside the pricing schedule. Where fees are tied to the headcount of "Customer and its Affiliates", joining a larger group may expand the fee base after close, even if the target's own usage has not changed. Confirm which entities count, when headcount is measured and whether a recalculation is permitted during the term or only at renewal. Record any required consent, notice and pricing clarification before signing, with an owner and deadline, and add every inherited renewal to a shared SaaS renewal tracker. Obtain written confirmation where the commercial effect is unclear.
Why this is entirely avoidable
None of this is hidden information. It sits in contracts the target company already has. It simply is not looked for during a typical diligence process, which is a gap that closes easily once someone deliberately looks.
Common questions
Keep reading
Notice periods, renewal dates and escalators carry forward unchanged through an acquisition. What a deliberate post-close contract review catches.
InsightHow Auto-Renew Clauses Quietly Cost Companies Thousands in SaaS SpendWhat the auto-renewal clause is actually doing for the vendor, why the notice deadline matters more than the renewal date, and how to stay ahead of it.
InsightWhy Nobody Reads SaaS Contracts Until It's Too LateWhy SaaS contracts get signed, filed, and never reread until a renewal forces the issue, and what to track so the notice period never closes unnoticed.