Assess whether management can run this without the founder (0d4756)

Situation

A health-system acquiring a specialty practice cannot treat add-backs that are just delayed opex as color commentary on revenue-quality bridge from bookings to cash. Integration-risk PMO must close management can run this from that extract under M&A Due Diligence / Separation and Integration.

Decision

Integration-risk PMO in a health-system acquiring a specialty practice must choose Proceed / Reprice / Walk / Hold using revenue-quality bridge from bookings to cash after add-backs that are just delayed opex.

Hypotheses to test

• The population in revenue-quality bridge from bookings to cash is the one add-backs that are just delayed opex named, so Proceed follows for this Separation and Integration file.
• The population in revenue-quality bridge from bookings to cash is adjacent only to add-backs that are just delayed opex; Reprice is the honest M&A Due Diligence call.
• A health-system acquiring a specialty practice already contained add-backs that are just delayed opex before revenue-quality bridge from bookings to cash arrived; no new Separation and Integration path.
• Provenance on revenue-quality bridge from bookings to cash after add-backs that are just delayed opex is broken; do not pick Proceed or Reprice yet.

Analysis required

• Separate a one-off add-back from a recurring earnings issue in revenue-quality bridge from bookings to cash.
• Map reps, earnout mechanics, and integration risk a health-system acquiring a specialty practice would inherit.
• Tie quality-of-earnings, working-capital, and contingent items in revenue-quality bridge from bookings to cash to management can run this.
• For this M&A Due Diligence Separation and Integration file, read revenue-quality bridge from bookings to cash against add-backs that are just delayed opex and write the one fact that would move management can run this for integration-risk PMO.

Recommendation

Choose Proceed / Reprice / Walk / Hold on this M&A Due Diligence / Separation and Integration packet (revenue-quality bridge from bookings to cash after add-backs that are just delayed opex). The follow-on Separation and Integration action is what integration-risk PMO does next: implement the option, assign an owner, and log the missing fact.