Assess whether integration costs were sandbagged in the CIM (d75cbb)
August 31, 2026 · SmartSolo
Situation
A PE platform evaluating a founder-led SaaS add-on cannot treat a customer who just sent a non-renewal as color commentary on post-merger systems-integration risk register. Integration-risk PMO must close integration costs were sandbagged from that extract under M&A Due Diligence / People and Contracts.
Decision
Integration-risk PMO in a PE platform evaluating a founder-led SaaS add-on must choose Proceed / Reprice / Walk / Hold using post-merger systems-integration risk register after a customer who just sent a non-renewal.
Hypotheses to test
- Authorize Proceed now; post-merger systems-integration risk register already has the discriminator after a customer who just sent a non-renewal.
- Keep Reprice in force until post-merger systems-integration risk register is completed after a customer who just sent a non-renewal for integration-risk PMO.
- Treat post-merger systems-integration risk register as Walk because both readings appear after a customer who just sent a non-renewal.
- Refuse a M&A Due Diligence close: integration-risk PMO does not have the page integration costs were sandbagged turns on in post-merger systems-integration risk register.
Analysis required
- Map reps, earnout mechanics, and integration risk a PE platform evaluating a founder-led SaaS add-on would inherit.
- Tie quality-of-earnings, working-capital, and contingent items in post-merger systems-integration risk register to integration costs were sandbagged.
- Name the document integration-risk PMO still needs before signing.
- For this M&A Due Diligence People and Contracts file, read post-merger systems-integration risk register against a customer who just sent a non-renewal 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 / People and Contracts packet (post-merger systems-integration risk register after a customer who just sent a non-renewal). If post-merger systems-integration risk register cannot force a M&A Due Diligence label under People and Contracts, stop. If post-merger systems-integration risk register after a customer who just sent a non-renewal cannot support Proceed versus Reprice on this M&A Due Diligence People and Contracts close, integration-risk PMO must do not proceed, reprice, or walk on a quality-of-earnings fact the packet does not carry.
Explore more
More M&A Due Diligence prompts
- Assess whether integration costs were sandbagged in the CIM after a QoE that
- Assess whether environmental liability is capped or open-ended (0bed4f)
- Assess whether related-party sales should be backed out of valuation (fda282)
- Assess whether the carve-out is operable on day one (a32b5b)
- Assess whether regulatory approval is a timing risk or a deal risk (041ef8)
Explore related decision areas
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

