The buyer is offering a revenue-based earnout, but they plan to merge our service delivery team with their existing operations immediately after closing. How do we structure operational service level agreements and resource guarantees in the definitive agreement to ensure their legacy team does not bottleneck our fulfillment and kill our earnout targets?

Question

Tyler Smith · Accepted Answer

A revenue-based earnout sounds simple, but if the buyer immediately merges your service delivery team with theirs, you lose control of the capacity needed to hit your targets. If their team is slow, inefficient, or prioritized on other accounts, your revenue drops and your earnout is ruined. You must protect your capacity by writing operational service level agreements and resource guarantees directly into the purchase agreement. First, define the baseline resource capacity required to service your sales pipeline. This capacity must be maintained by the merged organization. Write specific headcount or operational capacity minimums into the deal terms. For example, specify that the delivery team must maintain a maximum response time of four hours and a minimum of five dedicated full-time equivalents assigned to your accounts. Second, establish a dispute resolution process that escalates fulfillment bottlenecks directly to a joint operational committee before they impact your earnout calculations. If the buyer fails to meet these resource levels, the agreement should state that your earnout targets are automatically adjusted downward or deemed fully achieved for that period. By securing these operational guards, you ensure that the buyer's post-close integration decisions cannot starve your business of the operational capacity needed to win your payout.