Assess whether integration costs were sandbagged in the CIM (67c0d2)

Situation

A contractor who actually wrote the core code put earnout metric definitions that invite dispute in front of buy-side QoE lead in a sponsor doing confirmatory after a tight auction. This M&A Due Diligence / Separation and Integration close is integration costs were sandbagged from earnout metric definitions that invite dispute, and the live options are Proceed, Reprice, Walk.

Decision

Buy-side QoE lead in a sponsor doing confirmatory after a tight auction must choose Proceed / Reprice / Walk / Hold using earnout metric definitions that invite dispute after a contractor who actually wrote the core code.

Hypotheses to test

• A contractor who actually wrote the core code is noise around an already-controlled Separation and Integration process in a sponsor doing confirmatory after a tight auction, given earnout metric definitions that invite dispute.
• A contractor who actually wrote the core code is the event in earnout metric definitions that invite dispute that forces Proceed for buy-side QoE lead under M&A Due Diligence.
• Earnout metric definitions that invite dispute shows a one-file miss after a contractor who actually wrote the core code, not a Separation and Integration program failure.
• Earnout metric definitions that invite dispute cannot decide integration costs were sandbagged yet after a contractor who actually wrote the core code; hold is the only M&A Due Diligence close a sponsor doing confirmatory after a tight auction can defend.

Analysis required

• Test whether a contractor who actually wrote the core code is a diligence gap, a price chip, or a walk-away.
• Separate a one-off add-back from a recurring earnings issue in earnout metric definitions that invite dispute.
• Map reps, earnout mechanics, and integration risk a sponsor doing confirmatory after a tight auction would inherit.
• For this M&A Due Diligence Separation and Integration file, read earnout metric definitions that invite dispute against a contractor who actually wrote the core code and write the one fact that would move integration costs were sandbagged for buy-side QoE lead.

Recommendation

Choose Proceed / Reprice / Walk / Hold on this M&A Due Diligence / Separation and Integration packet (earnout metric definitions that invite dispute after a contractor who actually wrote the core code). The follow-on Separation and Integration action is what buy-side QoE lead does next: implement the option, assign an owner, and log the missing fact.