Assess whether a top customer is actually sticky (67180c)

Situation

Buy-side QoE lead owns a top customer is actually sticky inside a sponsor doing confirmatory after a tight auction with management-team retention and key-person map as the only packet. An HSR second-request rumor is what changed the clock for this M&A Due Diligence Separation and Integration file.

Decision

Buy-side QoE lead in a sponsor doing confirmatory after a tight auction must choose Proceed / Reprice / Walk / Hold using management-team retention and key-person map after an HSR second-request rumor.

Hypotheses to test

• Buy-side QoE lead can defend Proceed from management-team retention and key-person map after an HSR second-request rumor in a M&A Due Diligence challenge.
• Buy-side QoE lead cannot defend Proceed from management-team retention and key-person map; Reprice is what the extract actually supports after an HSR second-request rumor.
• An HSR second-request rumor never reached the population in management-team retention and key-person map — reopen intake, do not close a top customer is actually sticky.
• Two facts in management-team retention and key-person map after an HSR second-request rumor conflict for buy-side QoE lead; hold this Separation and Integration file.

Analysis required

• Test whether an HSR second-request rumor is a diligence gap, a price chip, or a walk-away.
• Separate a one-off add-back from a recurring earnings issue in management-team retention and key-person map.
• 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 management-team retention and key-person map against an HSR second-request rumor and write the one fact that would move a top customer is actually sticky for buy-side QoE lead.

Recommendation

Choose Proceed / Reprice / Walk / Hold on this M&A Due Diligence / Separation and Integration packet (management-team retention and key-person map after an HSR second-request rumor). If management-team retention and key-person map cannot force a M&A Due Diligence label under Separation and Integration, stop. If management-team retention and key-person map after an HSR second-request rumor cannot support Proceed versus Reprice on this M&A Due Diligence Separation and Integration close, buy-side QoE lead must do not proceed, reprice, or walk on a quality-of-earnings fact the packet does not carry.