Assess whether integration costs were sandbagged in the CIM (5346cd)

Situation

In a roll-up of three regional service companies, customer concentration and termination-for-convenience clauses is the evidence after a contractor who actually wrote the core code. Integration-risk PMO has to pick Proceed or Reprice for this M&A Due Diligence Legal, IP, and Regulatory close using customer concentration and termination-for-convenience clauses.

Decision

Integration-risk PMO in a roll-up of three regional service companies must choose Proceed / Reprice / Walk / Hold using customer concentration and termination-for-convenience clauses after a contractor who actually wrote the core code.

Hypotheses to test

• The population in customer concentration and termination-for-convenience clauses is the one a contractor who actually wrote the core code named, so Proceed follows for this Legal, IP, and Regulatory file.
• The population in customer concentration and termination-for-convenience clauses is adjacent only to a contractor who actually wrote the core code; Reprice is the honest M&A Due Diligence call.
• A roll-up of three regional service companies already contained a contractor who actually wrote the core code before customer concentration and termination-for-convenience clauses arrived; no new Legal, IP, and Regulatory path.
• Provenance on customer concentration and termination-for-convenience clauses after a contractor who actually wrote the core code is broken; do not pick Proceed or Reprice yet.

Analysis required

• Tie quality-of-earnings, working-capital, and contingent items in customer concentration and termination-for-convenience clauses to integration costs were sandbagged.
• Name the document integration-risk PMO still needs before signing.
• Test whether a contractor who actually wrote the core code is a diligence gap, a price chip, or a walk-away.
• For this M&A Due Diligence Legal, IP, and Regulatory file, read customer concentration and termination-for-convenience clauses against a contractor who actually wrote the core code and write the one fact that would move integration costs were sandbagged for integration-risk PMO.

Recommendation

Choose Proceed / Reprice / Walk / Hold on this M&A Due Diligence / Legal, IP, and Regulatory packet (customer concentration and termination-for-convenience clauses after a contractor who actually wrote the core code). The follow-on Legal, IP, and Regulatory action is what integration-risk PMO does next: implement the option, assign an owner, and log the missing fact.