April 2025•4 min read•Dr. Shashwat Bishwen

The Due Diligence Lie: Why Documentation Doesn't Tell You How a Platform Behaves

Most failing platforms do not look broken on paper. Architecture diagrams look clean, Jira tickets are closed, and compliance checklists are green. But platforms behave according to runtime physics, not executive slide decks.

The Due Diligence Lie: Why Documentation Doesn't Tell You How a Platform Behaves
Dr. Shashwat Bishwen: The Due Diligence Lie: Why Documentation Doesn't Tell You How a Platform Behaves

During corporate acquisitions and private equity buyouts, technical diligence is frequently reduced to a paper audit. Checklists are ticked: Does the target company have SOC2 compliance? Are there architecture diagrams in Confluence? Is code coverage above 80%?

This process is an elaborate corporate ritual that conceals ground truth.

Documentation reflects how the engineering team hopes the platform works. Runtime telemetry reveals how the platform actually behaves when subjected to operational friction.

In my forensic diligence practice, we bypass documentation entirely during the first 48 hours. Instead, we inspect live APM traces, git commit histories, deployment rollback frequencies, and on-call paging frequency.

When you look at production telemetry, the truth cannot hide: you see the unindexed database queries, the silent micro-outages covered up by automated retries, and the exhausted engineers firefighting at 3 AM.

Never acquire or invest in a platform based on documentation. Inspect the runtime physics.

Frequently Asked

Why is documentation review not enough for technical due diligence?

Documentation reflects how a team hopes the platform works; it says nothing about how it actually behaves under load. Clean architecture diagrams and green compliance checklists coexist routinely with unindexed queries and 3 AM firefighting.

What do you inspect instead of documentation during a forensic diligence audit?

Live APM traces, git commit history, deployment rollback frequency, and on-call paging frequency, bypassing documentation entirely for the first 48 hours to see runtime reality before reading any slide deck.

Also relevant to:limitations of documentation based due diligencetechnical due diligence red flagssoftware audit before acquisitiontribal knowledge dependency audit
Read & DiscussThis piece lives at shashwat.si. Join the conversation on LinkedIn.
Discuss on LinkedIn→
Executive Newsletter

The Solution Assembler Dispatch

Architectural teardowns, platform stabilization forensics, and cloud FinOps unit economics for founders, CTOs, and board members. Delivered directly to your inbox.

Curated by Dr. Shashwat Bishwen•No spam, strictly engineering physics