Corporate Governance, Board Management & M&A ExitsPlaybook3 min readUpdated September 2026

Auditing Change-of-Control Clauses in Customer Contracts

An acquisition can close cleanly on paper and still cost you your three largest customers if their contracts require consent before they transfer to a new owner. Assignability clauses get almost no attention during the sales cycle and then become the thing everyone's scrambling over in the final weeks of diligence.

The fix isn't complicated, but it has to start early: read every material customer contract for how it treats a change of control, not just whether it technically allows assignment.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

What is the difference between anti-assignment and change-of-control clauses?

An anti-assignment clause blocks a party from transferring the contract to someone else without consent, which usually isn't triggered by a straight stock sale since the contracting entity doesn't change. A change-of-control clause is broader: it's triggered when ownership of the contracting party itself changes hands, which is exactly what happens in most acquisitions, even ones structured as stock deals.

Many founders assume a stock sale avoids assignment problems entirely. It avoids anti-assignment problems, but a change-of-control clause will still require notice or consent, and missing that distinction is how deals get delayed at the last minute.

Reading these clauses also means checking who counts as a "change of control." Some contracts only trigger on a sale of substantially all assets or a majority equity transfer; others trip on much smaller changes, like a new investor crossing a stated ownership percentage. Two contracts that look similar on the surface can behave completely differently once a specific deal structure is applied to them.

Running the Contract Audit Before You're Under Deal Pressure

Pull every contract above a meaningful revenue threshold, plus any master services agreement with a strategic account regardless of size, and sort them into three buckets: silent on change of control, requires notice only, and requires affirmative consent. Consent-required contracts are the ones that can actually block or delay a closing.

Doing this audit before a buyer is at the table means you can start the consent conversations on your own timeline, not the deal's. Waiting until diligence starts means every consent request looks, to the customer, like news about an acquisition they weren't supposed to know about yet.

Keep the audit as a living document rather than a one-time exercise. New enterprise contracts should get the same change-of-control review at signing that older contracts get retroactively, so the list never goes stale between the time you build it and the time a buyer actually shows up.

Pull every material contract, then sort each one into these buckets:

  • Silent on change of control: no notice or consent is required, though counsel should still confirm the wording.
  • Requires notice only: the customer must be told, but cannot block the transaction.
  • Requires affirmative consent: these are the contracts that can actually block or delay the deal, so they get priority.
  • Strategic accounts: include any master services agreement with a strategic customer regardless of its revenue size.

How do you ask customers for consent without alarming them?

How you ask matters as much as whether you ask. Framing the request as "we're exploring strategic options" days before a signing tends to alarm procurement teams; framing it as "we've entered into an agreement to strengthen our capabilities, here's what stays the same for you" after signing, timed carefully with the buyer's input, lands much better.

For your largest accounts, a short call from a senior executive, not a form email from legal, is usually worth the time. Customers who feel informed rather than notified are far less likely to use the moment to renegotiate pricing.

What Buyers Actually Do With This Risk

A buyer's counsel will flag every consent-required contract as a closing condition, an indemnity item, or a purchase price adjustment, depending on how much revenue is at risk. The bigger the concentration in a handful of accounts, the more likely the buyer asks for a holdback tied to those consents actually being obtained.

Sellers who've already mapped this risk and started consent conversations early are negotiating from a position of "here's our plan and status," not "we didn't know this was an issue," which noticeably changes how the buyer prices the risk.

The revenue concentration question matters more than the raw count of consent-required contracts. Ten small consent-required accounts spread across an industry are a manageable, almost routine part of diligence; two or three accounts that together represent a large share of revenue are a genuine deal risk, and buyers will treat them very differently in how they structure price and holdbacks.

Executive Capability Standard

What Good Looks Like

Before running a sale process, every material customer contract has been sorted by how it treats a change of control, consent-required accounts have an outreach plan, and the concentration of revenue sitting behind consent requirements is known well before a buyer asks.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Read your top twenty customer contracts by revenue specifically for their assignment and change-of-control language, not just their pricing and term.
2. Do Manually:Build the three-bucket audit (silent, notice-only, consent-required) yourself in a spreadsheet, flagging revenue exposure next to each contract.
3. Delegate:Have your general counsel or outside counsel run the full contract audit and draft the consent request templates for your largest accounts.
4. Automate:Use contract review software to flag assignment and change-of-control clauses across your full contract set rather than reading each one manually.
5. Buy:Bring in M&A counsel early to run consent strategy and negotiate holdback terms with the buyer for any accounts that can't get pre-signing consent.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Frequently Asked Questions

Does an asset sale avoid change-of-control assignment problems entirely?

No, often the opposite. An asset sale is a direct assignment of each contract to a new legal entity, so anti-assignment clauses that a stock sale might not trigger will almost always require consent in an asset deal. This is one reason deal structure and contract review need to happen together.

What if a key customer refuses to consent?

The parties usually negotiate a workaround rather than abandon the deal. The seller may keep servicing that contract under a short transition agreement while a new contract is negotiated directly with the buyer, or the purchase price is adjusted to reflect the revenue at risk if the account can't be retained.

Should this audit happen before or after signing a letter of intent?

Before, if possible. Knowing your consent-required contracts and their approximate revenue exposure lets you address the biggest risks, or at least raise them proactively, rather than have a buyer's diligence team discover them and use them to push down price in negotiations.

Do vendor and supplier contracts need the same review as customer contracts?

Yes, though usually with less urgency. A supplier that won't assign a favorable pricing agreement can hurt margins post-close the same way a lost customer hurts revenue, so it belongs in the same audit, just typically lower on the priority list.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides