Technical due diligence on a SaaS codebase before an acquisition
A buyer needed to know what they would inherit: whether the platform could be maintained by a new team, what the security and licensing exposure looked like, and what the first twelve months of engineering would have to pay for.
Engagement
Role: Technical due diligence, read-only.
Shape: Repository and infrastructure review, then a written report and stakeholder walkthrough.
Duration: Two weeks for the due diligence tier.
Stack: PHP monolith · MySQL · Single-server deployment · Composer dependency audit · Written report.
What was wrong
- No documented deployment path: releases depended on one person's shell history.
- Backups existed but had never been restored, so their usefulness was unproven.
- Several dependencies were unmaintained, and two carried licences that conflicted with the buyer's distribution plans.
- Access control was shared credentials rather than per-person accounts, making offboarding impossible to verify.
What was built
- Read-only review of the repository, dependency tree, deployment path, backup and restore process, and access control.
- Key-person risk assessment: what is documented, what only exists in one person's head, and what would be needed to hand it over.
- Remediation plan split into pre-close blockers, first-90-day work and longer-term architecture decisions, each with an estimate.
- Written report and a walkthrough call with both the technical and non-technical stakeholders.
Architecture after the work
Evidence, not opinion — Every finding cites the file, dependency or configuration it came from, so the seller can respond to it specifically.
Risk tiering — Findings are split into pre-close blockers, first-90-day work and longer-term architecture decisions, each with an engineering estimate.
Key-person mapping — The review records what is documented versus what exists only in one person's head, which is the risk that most often survives a handover.
Two audiences, one report — The report is written so a non-technical buyer can act on it, with an appendix that an engineer can verify line by line.
Trade-offs and what was left out
- The review is read-only: nothing in the codebase is changed during due diligence, and remediation is quoted separately.
- No valuation advice is given — the output is engineering cost and risk, which the buyer's advisors price.
Outcome
The buyer went into the negotiation with a costed engineering plan and a written list of the risks that needed to be priced in.
Frequently asked questions
- What does technical due diligence actually deliver?
- A written report covering the state of the codebase, dependency and licence exposure, deployment and backup reality, access control, key-person risk, and a remediation plan split into pre-close, first-90-day and longer-term work with estimates against each item.
- Can you review a codebase you have never seen before in two weeks?
- Yes, for a single product of this size. The review is structured rather than exhaustive: it follows the paths that carry money, data and access, and states plainly what was and was not examined.