01 · Start here
How do you use a technical due diligence checklist?
Send the evidence list to the other side first, then use the questions in interviews.
- 01
Evidence comes before conversation because a claim that no document backs up is the finding. Our technical due diligence service follows this order.
- 02
Read access to the repositories matters more than any presentation. If a seller will not grant read-only access under an NDA, record that as a finding in itself.
02 · The checklist
What should be on the checklist, area by area?
| Area | Evidence to request | Questions to ask |
|---|---|---|
| Code | Read access to all repositories; commit history; test results | Who wrote most of it and are they still here? How much is generated or copied? |
| Architecture | Diagrams, deployment topology, data model | What breaks first at ten times today's load? Which parts nobody dares touch? |
| Technical debt | Dependency and runtime versions; open upgrade tickets | Which frameworks are out of date? What was started and never finished? |
| Security | Dependency scan, secrets scan, last penetration test, incident log | Where are keys stored? Who can reach production data? |
| Licences and open source | Bill of materials, licence list, third-party contracts | Any copyleft code in the shipped product? Who owns work done by contractors? |
| Infrastructure | Cloud accounts and bills, backup and restore records | When was a restore last tested? What does one outage cost? |
| Delivery process | Release history, CI configuration, on-call records | How often does it ship and how often does a release fail? |
| Team | Org chart, tenure, documentation, contractor list | If two named people left, what would stop working? |
03 · Code and debt
How do you check code quality and technical debt?
Check code quality by reading a sample, running the test suite and counting what is out of date, not by reading a metrics dashboard. A coverage number says little if the tests assert nothing.
Run the build from a clean checkout
If nobody has done that recently, expect surprises.
List the runtime, framework and database versions and compare them with what their vendors still patch.
Look for code that is copied between projects, generated by AI tools without review, or commented out in large blocks.
Ask for the three modules the team fears most, then read them.
04 · Risk
What security and licence evidence should you ask for?
Ask for scan output and the history of fixes, because a clean scan today says nothing about how the team handles findings.
- 01
Secrets committed to the repository, unpatched dependencies and missing access reviews are the usual early findings.
- 02
For licences, ask for a bill of materials and the licence of every component that ships to customers. Copyleft terms and unassigned contractor work are the items that can change a deal's terms. This is an engineering check, not legal advice; your lawyers decide what a licence finding means.
05 · Team and process
How do you assess key-person risk and delivery process?
Assess it from the commit history and the release record.
- 01
If one author wrote most of a critical module and has no backup, that is key-person risk whatever the org chart says.
- 02
Release frequency, failed releases and the time to fix a production bug show how the team really works. Ask to see the last three incidents and what changed afterwards.
06 · Output
How do you turn the answers into a decision?
Rate each area red, amber or green, and attach a cost to fix to every red and amber item so the number can enter the deal model.
- 01
See software acquisition red flags for how to price the common ones.
- 02
If the red items are many or the evidence is missing, a deeper code audit of the whole codebase is the next step. Sellers can run the same list on themselves first; see sell-side technical due diligence.
07 · Newer risk
How do you check AI-generated code in a deal?
Treat generated code like any other code and check whether a person reviewed it and a test covers it.
- 01
Large commits with no review, repeated near-identical functions and missing tests are the signs.
- 02
Ask the seller which tools the team uses, which repositories they touched and what the review rule is. The answer tells you more than the code alone, because it shows whether the process catches mistakes.
08 · Timing
When in a deal should you run the checklist?
Run a light version before a letter of intent and the full version after it, inside the exclusivity window.
- 01
The light pass asks only for repository access, versions and the last three incidents, and tells you whether to continue.
- 02
The full pass adds interviews, a clean build and the evidence list above. Send the request on day one, because waiting on documents is the usual cause of delay. See technical due diligence cost for how timing and price relate.
09 · Next step
Who can run this checklist for you?
Ace8 is the modernization practice of AceMQ, and AceMQ engineers run the review.
- 01
We report in plain English, with evidence and a cost to fix, before close. Details are on our technical due diligence page. Quote on request.