Assess whether integration costs were sandbagged in the CIM (4a3647)
August 31, 2026 · SmartSolo
Situation
Legal, IP, and Regulatory work in a family-office reviewing a manufacturing target now turns on integration costs were sandbagged because IT diligence showing two ERPs and no chart of accounts map put working-capital peg versus seasonal reality in play. Customer-contract risk reviewer should say what working-capital peg versus seasonal reality proves.
Decision
Customer-contract risk reviewer in a family-office reviewing a manufacturing target must choose Proceed / Reprice / Walk / Hold using working-capital peg versus seasonal reality after IT diligence showing two ERPs and no chart of accounts map.
Hypotheses to test
- Working-capital peg versus seasonal reality reads as Proceed once IT diligence showing two ERPs and no chart of accounts map is lined up to the same M&A Due Diligence population.
- Working-capital peg versus seasonal reality is closer to Reprice after IT diligence showing two ERPs and no chart of accounts map; Proceed would over-claim this Legal, IP, and Regulatory extract.
- Walk is still live in working-capital peg versus seasonal reality for customer-contract risk reviewer in a family-office reviewing a manufacturing target.
- Working-capital peg versus seasonal reality is missing the fact customer-contract risk reviewer needs after IT diligence showing two ERPs and no chart of accounts map; stop this M&A Due Diligence close.
Analysis required
- Tie quality-of-earnings, working-capital, and contingent items in working-capital peg versus seasonal reality to integration costs were sandbagged.
- Name the document customer-contract risk reviewer still needs before signing.
- Test whether IT diligence showing two ERPs and no chart of accounts map is a diligence gap, a price chip, or a walk-away.
- For this M&A Due Diligence Legal, IP, and Regulatory file, read working-capital peg versus seasonal reality against IT diligence showing two ERPs and no chart of accounts map and write the one fact that would move integration costs were sandbagged for customer-contract risk reviewer.
Recommendation
Choose Proceed / Reprice / Walk / Hold on this M&A Due Diligence / Legal, IP, and Regulatory packet (working-capital peg versus seasonal reality after IT diligence showing two ERPs and no chart of accounts map). The follow-on Legal, IP, and Regulatory action is what customer-contract risk reviewer does next: implement the option, assign an owner, and log the missing fact.
Explore more
More M&A Due Diligence prompts
- Assess whether related-party sales should be backed out of valuation (5ca709)
- Assess whether regulatory approval is a timing risk or a deal risk (b023d3)
- Assess whether regulatory approval is a timing risk or a deal risk (136838)
- Assess whether environmental liability is capped or open-ended (0be910)
- Assess whether earnings quality supports the bid price (c33494)
Explore related decision areas
- Assess whether product recall exposure is priced or excluded (2387fa)Insurance Underwriting
- Assess whether telematics improvements offset driver quality (223273)Insurance Underwriting
- Assess whether related-party revenue is arm's-length (81bf0e)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.

