Skip to content
Contact Us
Technical Due Diligence

Nothing looks wrongLook again

In technical due diligence, the codebase that ships every day is the one hiding the most.The risk only has your name on it after the deal closes.

  • Codebase health
  • Bus factor
  • Hidden coupling
  • EOL & lock-in
Inherited risk

You're buying more than the code

A codebase that ships every day can still carry years of risk that only surfaces once the people who knew it have gone

The signs it won't survive contact with production

  1. 01One name on every critical filegit blame on the payment, auth and billing paths keeps returning the same person while everything still ships on time
  2. 02Green CI, thin assertionsCoverage numbers climb while the suite mostly proves that code ran, not that the critical paths are correct
  3. 03The changelog goes quietThe riskiest modules stop changing – not because they're finished, but because nobody left dares touch them
  4. 04Runbook that points to a personIncident notes resolve with “asked X” instead of a documented step, long before X ever leaves
  5. 05Dependencies pinned and frozenLockfiles haven't moved in years and upgrade branches are opened, stalled and abandoned