Assess whether the carve-out is operable on day one after IT diligence
August 31, 2026
SITUATION A PE platform evaluating a founder-led SaaS add-on cannot treat IT diligence showing two ERPs and no chart of accounts map as incidental context on earnout metric definitions that invite dispute. Buy-side QoE lead must close the carve-out is operable from that extract under M&A Due Diligence / Earnings and Revenue Quality.
DECISION Buy-side QoE lead in a PE platform evaluating a founder-led SaaS add-on must choose Proceed / Reprice / Walk / Hold using earnout metric definitions that invite dispute after IT diligence showing two ERPs and no chart of accounts map.
HYPOTHESES TO TEST 1. Authorize Proceed now; earnout metric definitions that invite dispute already has the discriminator after IT diligence showing two ERPs and no chart of accounts map. 2. Keep Reprice in force until earnout metric definitions that invite dispute is completed after IT diligence showing two ERPs and no chart of accounts map for buy-side QoE lead. 3. Treat earnout metric definitions that invite dispute as Walk because both readings appear after IT diligence showing two ERPs and no chart of accounts map. 4. Refuse a M&A Due Diligence close: buy-side QoE lead does not have the decision the carve-out is operable turns on in earnout metric definitions that invite dispute.
ANALYSIS REQUIRED 1. Tie quality-of-earnings, working-capital, and contingent items in earnout metric definitions that invite dispute to the carve-out is operable. 2. Name the document buy-side QoE lead still needs before signing. 3. Test whether IT diligence showing two ERPs and no chart of accounts map is a diligence gap, a price chip, or a walk-away. 4. For this M&A Due Diligence Earnings and Revenue Quality file, read earnout metric definitions that invite dispute against IT diligence showing two ERPs and no chart of accounts map and write the one fact that would move the carve-out is operable for buy-side QoE lead.
RECOMMENDATION Choose Proceed / Reprice / Walk / Hold on this M&A Due Diligence / Earnings and Revenue Quality packet (earnout metric definitions that invite dispute after IT diligence showing two ERPs and no chart of accounts map). The follow-on Earnings and Revenue Quality action is what buy-side QoE lead does next: implement the option, assign an owner, and log the missing fact.
COMMAND RETURNS - Bottom-line M&A Due Diligence option on the carve-out is operable, then the evidence in earnout metric definitions that invite dispute, then the action for buy-side QoE lead - Hypothesis scorecard against earnout metric definitions that invite dispute: supported / rejected / untestable - Regulatory or exam hook Earnings and Revenue Quality would cite - Earnings and Revenue Quality finding in earnout metric definitions that invite dispute that a second reviewer can re-perform
Explore more
More M&A Due Diligence prompts
- Assess whether earnout definitions will cause a post-close fight after an HSR
- Whether integration costs were sandbagged in the CIM from QoE add-backs
- Assess whether IP is owned or merely licensed from IP ownership vs
- Assess whether earnings quality supports the bid price after add-backs that
- Assess whether management can run this without the founder from post-merger
Explore related decision areas
- Assess whether the S-1 disclosure language is still defensible (09fda3)Forensic Accounting
- Assess whether a warranty should be converted to a condition precedentInsurance Underwriting
- Assess whether telematics improvements offset driver quality (31ad68)Insurance Underwriting
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.

