Assess whether related-party sales should be backed out of valuation (0a7592)
August 31, 2026
SITUATION A cross-border deal with earnout-heavy structure cannot treat a contractor who actually wrote the core code as incidental context on related-party revenue that disappears at close. Commercial-diligence partner must close related-party sales should be from that extract under M&A Due Diligence / Legal, IP, and Regulatory.
DECISION Commercial-diligence partner in a cross-border deal with earnout-heavy structure must choose Proceed / Reprice / Walk / Hold using related-party revenue that disappears at close after a contractor who actually wrote the core code.
HYPOTHESES TO TEST 1. Related-party revenue that disappears at close reads as Proceed once a contractor who actually wrote the core code is lined up to the same M&A Due Diligence population. 2. Related-party revenue that disappears at close is closer to Reprice after a contractor who actually wrote the core code; Proceed would over-claim this Legal, IP, and Regulatory extract. 3. Walk is still live in related-party revenue that disappears at close for commercial-diligence partner in a cross-border deal with earnout-heavy structure. 4. Related-party revenue that disappears at close is missing the fact commercial-diligence partner needs after a contractor who actually wrote the core code; stop this M&A Due Diligence close.
ANALYSIS REQUIRED 1. Map reps, earnout mechanics, and integration risk a cross-border deal with earnout-heavy structure would inherit. 2. Tie quality-of-earnings, working-capital, and contingent items in related-party revenue that disappears at close to related-party sales should be. 3. Name the document commercial-diligence partner still needs before signing. 4. For this M&A Due Diligence Legal, IP, and Regulatory file, read related-party revenue that disappears at close against a contractor who actually wrote the core code and write the one fact that would move related-party sales should be for commercial-diligence partner.
RECOMMENDATION Choose Proceed / Reprice / Walk / Hold on this M&A Due Diligence / Legal, IP, and Regulatory packet (related-party revenue that disappears at close after a contractor who actually wrote the core code). Lead with the M&A Due Diligence option related-party revenue that disappears at close can support after a contractor who actually wrote the core code, then the two facts that force it, then the Monday action for commercial-diligence partner in a cross-border deal with earnout-heavy structure.
COMMAND RETURNS - Bottom-line M&A Due Diligence option on related-party sales should be, then the evidence in related-party revenue that disappears at close, then the action for commercial-diligence partner - Hypothesis scorecard against related-party revenue that disappears at close: supported / rejected / untestable - Regulatory or exam hook Legal, IP, and Regulatory would cite - Legal, IP, and Regulatory finding in related-party revenue that disappears at close that a second reviewer can re-perform
Explore more
More M&A Due Diligence prompts
- Assess whether regulatory approval is a timing risk or a deal risk (5ef513)
- Assess whether environmental liability is capped or open-ended (5511e4)
- Assess whether to re-trade, restructure, or drop (d1fe8a)
- Assess whether to re-trade, restructure, or drop (db8be3)
- Assess whether related-party sales should be backed out of valuation (a68f25)
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.

