Assess whether integration costs were sandbagged in the CIM (420d1e)
August 31, 2026 · SmartSolo
Situation
After a peg set at a seasonal high, related-party revenue that disappears at close is what commercial-diligence partner can touch in a public acquirer facing HSR and sector regulators. M&A Due Diligence will live with Proceed versus Reprice on this Separation and Integration file.
Decision
Commercial-diligence partner in a public acquirer facing HSR and sector regulators must choose Proceed / Reprice / Walk / Hold using related-party revenue that disappears at close after a peg set at a seasonal high.
Hypotheses to test
- The population in related-party revenue that disappears at close is the one a peg set at a seasonal high named, so Proceed follows for this Separation and Integration file.
- The population in related-party revenue that disappears at close is adjacent only to a peg set at a seasonal high; Reprice is the honest M&A Due Diligence call.
- A public acquirer facing HSR and sector regulators already contained a peg set at a seasonal high before related-party revenue that disappears at close arrived; no new Separation and Integration path.
- Provenance on related-party revenue that disappears at close after a peg set at a seasonal high is broken; do not pick Proceed or Reprice yet.
Analysis required
- Tie quality-of-earnings, working-capital, and contingent items in related-party revenue that disappears at close to integration costs were sandbagged.
- Name the document commercial-diligence partner still needs before signing.
- Test whether a peg set at a seasonal high is a diligence gap, a price chip, or a walk-away.
- For this M&A Due Diligence Separation and Integration file, read related-party revenue that disappears at close against a peg set at a seasonal high and write the one fact that would move integration costs were sandbagged for commercial-diligence partner.
Recommendation
Choose Proceed / Reprice / Walk / Hold on this M&A Due Diligence / Separation and Integration packet (related-party revenue that disappears at close after a peg set at a seasonal high). If related-party revenue that disappears at close cannot force a M&A Due Diligence label under Separation and Integration, stop. If related-party revenue that disappears at close after a peg set at a seasonal high cannot support Proceed versus Reprice on this M&A Due Diligence Separation and Integration close, commercial-diligence partner 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 related-party sales should be backed out of valuation (03a527)
- Assess whether IP is owned or merely licensed (4aae07)
- Assess whether environmental liability is capped or open-ended (9b823e)
- Assess whether IP is owned or merely licensed (25bb3a)
- Assess whether the carve-out is operable on day one (bd4a11)
Explore related decision areas
- Assess whether the SBIR data-rights assertions are too aggressive (d479c7)Government RFP
- Assess whether the pattern is timing, error, or scheme (3a5575)Forensic Accounting
- Assess whether SAB 99 qualitative materiality is triggered (eb3b05)Forensic Accounting
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.

