Whether a top customer is actually sticky from QoE add-backs the seller
August 31, 2026 · SmartSolo
Situation
Earnings and Revenue Quality work in a sponsor doing confirmatory after a tight auction now turns on a top customer is actually sticky because add-backs that are just delayed opex put QoE add-backs the seller marked 'normalized' in play. Integration-risk PMO should say what QoE add-backs the seller marked 'normalized' proves.
Decision
Integration-risk PMO in a sponsor doing confirmatory after a tight auction must choose Proceed / Reprice / Walk / Hold using QoE add-backs the seller marked 'normalized' after add-backs that are just delayed opex.
Hypotheses to test
- Integration-risk PMO can defend Proceed from QoE add-backs the seller marked 'normalized' after add-backs that are just delayed opex in a M&A Due Diligence challenge.
- Integration-risk PMO cannot defend Proceed from QoE add-backs the seller marked 'normalized'; Reprice is what the extract actually supports after add-backs that are just delayed opex.
- Add-backs that are just delayed opex never reached the population in QoE add-backs the seller marked 'normalized' — reopen intake, do not close a top customer is actually sticky.
- Two facts in QoE add-backs the seller marked 'normalized' after add-backs that are just delayed opex conflict for integration-risk PMO; hold this Earnings and Revenue Quality file.
Analysis required
- Tie quality-of-earnings, working-capital, and contingent items in QoE add-backs the seller marked 'normalized' to a top customer is actually sticky.
- Name the document integration-risk PMO still needs before signing.
- Test whether add-backs that are just delayed opex is a diligence gap, a price chip, or a walk-away.
- For this M&A Due Diligence Earnings and Revenue Quality file, read QoE add-backs the seller marked 'normalized' against add-backs that are just delayed opex and write the one fact that would move a top customer is actually sticky for integration-risk PMO.
Recommendation
Choose Proceed / Reprice / Walk / Hold on this M&A Due Diligence / Earnings and Revenue Quality packet (QoE add-backs the seller marked 'normalized' after add-backs that are just delayed opex). The follow-on Earnings and Revenue Quality action is what integration-risk PMO does next: implement the option, assign an owner, and log the missing fact.
Explore more
More M&A Due Diligence prompts
- Customer-contract risk reviewer must resolve whether integration costs were
- Whether environmental liability is capped or open-ended from post-merger
- Assess whether environmental liability is capped or open-ended from carve-out
- Integration-risk PMO must resolve whether the carve-out is operable on day one
- Assess whether regulatory approval is a timing risk or a deal risk (113e71)
Explore related decision areas
- Assess whether umbrella attachment is too thin for the hazard from renewalInsurance Underwriting
- Whether cyber controls claimed are actually in force from product-liabilityInsurance Underwriting
- Assess whether the SBIR data-rights assertions are too aggressive from SBIRGovernment RFP
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.

