We agreed to a three-year earnout based on gross margin, but the buyer wants to integrate their own untested AI tools into our operations immediately post-close. How do we prevent this operational disruption from tanking our performance and destroying our earnout targets?
An earnout tied to financial performance requires operational control. If a buyer forces you to implement untested AI tools post-close, they are introducing system risk that could destroy your margins and eliminate your payout. To protect your earnout, you must negotiate strict operational covenants in the purchase agreement.
First, establish an operational quarantine. Insist on a clause that prevents any mandatory changes to your core technology stack or delivery processes during the first eighteen months of the earnout period, unless your leadership team formally approves the change. This protects your delivery team and keeps them focused on their Rocks.
Second, structure a protection clause for your margins. If the buyer insists on deploying their AI tools and those tools cause client churn or operational delays, the purchase agreement must state that your gross margin targets will be adjusted downward to neutralize the impact. Alternatively, you can negotiate that the costs of integrating, training, and troubleshooting the new AI systems are fully excluded from your earnout calculations.
Third, maintain your EOS operating cadence. Keep running your weekly Level 10 Meetings to track performance issues in real time. If the buyer's systems cause operational friction, document these issues in your weekly meeting notes as clear evidence. This data gives you the leverage needed to show that any dip in performance was caused by their technological intervention rather than your team's execution. Protecting your operational autonomy is the only way to secure your earnout.
Category: Valuation & Deal Structure