The buyer wants an earnout tied to revenue milestones, but their post-close integration plan involves sunsetting our core legacy software and migrating clients to their proprietary platform. How do we structure the earnout terms so their operational changes do not wipe out our earnout?
When a buyer sunsets your product or migrates your customer base onto their infrastructure, a conventional top-line earnout tied to your specific product SKU is guaranteed to fail. You lose control over customer retention, technical implementation schedules, and client satisfaction the moment migration begins.
To preserve the value of your earnout under these conditions, demand one of three structural protections in the purchase agreement:
- Deemed achievement clause: Insert language stating that if the buyer sunsets, deprecates, or materially alters your primary offering prior to the end of the earnout period, all remaining earnout tranches immediately vest and become payable in full.
- Successor revenue credit: Stipulate that revenue generated from any migrated customer, regardless of which product or software tier they are transitioned into inside the buyer portfolio, counts 100 percent toward your earnout targets.
- Gross revenue floor: Establish a minimum guaranteed payment threshold that protects you against integration delays or platform failures caused by the buyer engineering team.
Within your EOS® framework, use the Accountability Chart during negotiations to define who has operational authority over customer migrations post-close. If the buyer insists on operational autonomy, they must assume the financial risk of that integration. Never accept an earnout where achievement hinges on technical milestones managed by personnel outside your direct chain of command. If they refuse deemed achievement language, remove the earnout entirely and convert the disputed sum into a guaranteed deferred payment structure.
Category: Valuation & Deal Structure