The buyer is proposing an earnout tied to post-merger integration milestones like system migrations and cross-selling targets rather than straight EBITDA. How do we structure this so we do not lose our payout due to their integration failures?

Question

Tyler Smith · Accepted Answer

Integration-based earnouts are incredibly risky because you are tying your payout to processes you no longer control. To protect yourself, you must shift the operational risk back to the buyer. Start by defining the integration milestones with extreme specificity. If a milestone is a system migration, define the exact software, data mapping standards, and completion criteria. Next, establish a reciprocal covenant in the purchase agreement. This clause must obligate the buyer to provide specific resources, including IT staff, budget, and executive sign-off, by designated dates. If the buyer fails to deliver these resources, the milestone must be legally deemed completed, triggering your payout automatically. From an EOS® perspective, these integration milestones should be treated as shared Rocks. Bring these issues to the table early using the IDS® process during negotiations. You must document who does what on a transition-specific Accountability Chart. This ensures the buyer cannot starve your team of the tools they need to succeed and then claim you missed the target. Finally, include a clause that allows your leadership team to retain operational veto power over any integration decisions that directly impact the earnout metrics. If they change the game, they pay the price.