01 · Why
Why run technical due diligence on your own company?
You run it because a buyer will find the same problems, and a problem you have already explained costs less than one they discover.
- 01
A finding with a plan and an effort estimate reads as managed risk; the same finding unexplained reads as a reason to lower the price.
- 02
Buyers also work against a clock. Exclusivity commonly runs 30 to 90 days according to MEV, so slow answers from you are a cost to the deal. Our technical due diligence work covers both sides.
02 · Prepare
What should you fix before a buyer looks?
| Item | Do before the process? | Why |
|---|---|---|
| Secrets in the repository or its history | Yes, rotate and remove | Easy to find, easy to price badly |
| Dependency and runtime versions | Yes, patch what is cheap | Any scanner shows these |
| A repeatable build and release | Yes, script it | Proves the team is not one laptop |
| Contractor code ownership | Yes, get assignments signed | Ownership gaps can stall a deal |
| Architecture notes and runbooks | Yes, write the short versions | Shows the knowledge is shared |
| Large rewrites and framework moves | No, plan and explain | Too big to finish and risks a regression |
03 · Evidence
What goes into a technical data room?
Put in the material a reviewer asks for first, so questions are answered before they are asked.
An architecture overview and a deployment diagram.
A list of repositories, languages and versions, with owners.
A bill of materials with licences, and the contractor agreements.
Recent scan results and a record of how findings were fixed.
Release history and the last few incident write-ups.
An org chart with tenure, and who covers which system.
04 · Narrative
How do you explain a weakness to a buyer?
Explain it in three lines: what it is, what it costs to fix in effort terms, and when it will be fixed.
- 01
Do not hide a finding; a buyer's reviewer reads the code and will find it. Use the software acquisition red flags list to see which ones buyers price hardest.
05 · Independence
Should the reviewer be independent of your engineers?
Yes.
- 01
Your own team knows where the problems are but cannot easily rate them against what a buyer sees. An outside reviewer works from the buyer's checklist; see the technical due diligence checklist. Ace8 signs an NDA before access, and says which side it is on.
- 02
If the review shows deep problems in one system, a full code audit covers it before the process starts.
06 · Plan
What does a sell-side preparation timeline look like?
Work backwards from the date you open the process. The order below puts the cheap, visible fixes first.
Run the review
An outside reviewer runs the buyer's checklist against your code and reports findings with effort to fix.
Fix the cheap items
Rotate secrets, patch dependencies, script the build and get contractor assignments signed.
Write it down
Architecture notes, runbooks and a short explanation of each open finding.
Build the data room
Collect the evidence list so it is ready before the first request arrives.
07 · Fundraising
Is this different for a raise than for a sale?
The method is the same, but investors in a raise weigh scalability and team more, and acquirers weigh licences, ownership and cost to maintain.
- 01
Prepare both views if you do not yet know which path you will take.
- 02
In either case the buyer's reviewer will read the code. Answer with evidence, not slides.
08 · Next step
How do you start?
Tell us the planned date for the process and the number of repositories.
- 01
Ace8 is the modernization practice of AceMQ, and AceMQ engineers run the review. See technical due diligence. Quote on request.