What Due Diligence Reports Don't Say Out Loud
A due diligence report is written to survive a lawsuit, not to warn a buyer. Those are different documents, and most buyers only ever get the first one.
Due diligence reports are long, dense, and heavily caveated by design. Every finding is hedged, every conclusion qualified, and the whole structure is built as much to protect the advisor who wrote it as to inform the buyer who commissioned it. That's not a criticism of the advisors — it's a rational response to the liability environment they work in. But it means the document a buyer receives isn't optimised for the buyer's actual decision. It's optimised to be defensible later.
The result is a predictable gap between what a report technically discloses and what actually kills deals in year two. The report will note, in a subordinate clause on page 140, that key-person dependency is elevated in operations. It will not say, in plain language, that if this person leaves in the first year — which is likely, given the compensation structure being proposed — the business you're buying will stop running the way it ran during diligence. Both statements are consistent with the same facts. Only one of them changes a buyer's behaviour.
The gaps that recur most often
Culture and complexity gaps rarely get quantified, because most firms have no clean way to do it — the report notes "differing operating philosophies" without attempting to count what that will actually cost in the first eighteen months. If the target runs on twenty exception-based processes that live only in one person's head, that's a number, not an adjective, and it should be reported as one.
Customer concentration gets disclosed accurately but is rarely stress-tested against the specific event of an ownership change. Many customers who tolerate a founder-led relationship won't automatically extend the same patience to a financial sponsor or a strategic acquirer — a prediction the report is well placed to make and usually doesn't.
Management retention gets treated as a legal question — are there employment agreements — rather than a motivational one: will these specific people actually want to work for this specific buyer, given what they've watched happen to their own founder in the deal. The legal question is answerable from documents. The motivational one requires someone to ask, honestly, off the record, and most diligence processes are structured so that conversation never happens before signing.
Integration cost is almost always underestimated, because it's estimated by people with no accountability for the integration once it actually happens. The diligence team hands off to an integration team that inherits assumptions it had no part in building, and every incentive to quietly revise once the deal is done and nobody is checking anymore.
Beyond the report, ask for one short conversation instead: sit the lead advisor down after delivery and ask them, directly, off the record, what they wouldn't put in writing. Most experienced advisors have an honest answer. Almost none volunteer it unprompted, because the report is the deliverable, and the deliverable is what gets reviewed for liability. The honest answer is the one that actually protects you.