The buyer is offering a high earnout structure but wants us to dismantle our weekly Level 10 Meeting and corporate reporting cadence post-close, which we know will destroy our team's execution capacity. How do we protect our operating system in the purchase agreement?

Question

Tyler Smith · Accepted Answer

If a buyer ties your payout to post-close performance targets but simultaneously dismantles the operating system that makes your team successful, they are setting you up to fail. Your team relies on their weekly Level 10 Meeting™, clear Rocks, and the Accountability Chart to maintain focus and execute. To protect your earnout, you must negotiate operational autonomy covenants directly into the purchase agreement. Explain to the buyer that your operating system is the engine that drives the numbers they are buying. Show them how the V/TO® and your weekly meeting cadence prevent operational drift and keep projects on track. Frame the preservation of your operating system as a risk-mitigation tool for the buyer, not as stubbornness from your team. In the definitive agreements, include a covenant that guarantees the acquired business unit will maintain its current operational meeting structure, software tools, and accountability frameworks during the earnout period. This ensures your team can continue to use the tools they know to hit their targets without being dragged down by corporate bureaucracy. Protecting your operating system is just as important as protecting the financial metrics themselves, as you cannot achieve the latter without the former.