01 · Deal size
Which technical due diligence firm fits your deal size?
Match the firm's usual deal to yours.
- 01
A large platform deal for a private equity fund may need a big advisory firm whose name an investment committee or lender recognizes. A small software acquisition is often better served by a specialist who can start within days and quote a fixed fee.
- 02
Our own technical due diligence work suits the second case, and we say so plainly on that page. For named firms and their stated focus, see technical due diligence firms compared.
02 · The questions
What should you ask a technical due diligence provider?
| # | Question | A good answer sounds like |
|---|---|---|
| 1 | Who does the work and who signs the report? | Named senior engineers, not a pool |
| 2 | Will you read the code, or only interview management? | Read-only repository access is a condition |
| 3 | Who else are you working for on this deal? | A clear no, or a stated way of handling it |
| 4 | Do you sign an NDA before access? | Yes, before any code or data is shared |
| 5 | How is the price set? | Fixed fee once scope is agreed |
| 6 | What does the report contain? | Evidence, severity and a cost to fix for each finding |
| 7 | What if our closing date is close? | A plain yes or no on feasibility, with what gets cut |
| 8 | How do you treat generated and AI-written code? | Reviewed like any other code, with tests checked |
| 9 | What will you not cover? | A short list: legal opinion, financial audit, penetration testing |
03 · Independence
How do you check for conflicts of interest?
Ask directly whether the firm has worked for the seller, the target or a competing bidder, and whether it sells fix-it or staffing work that benefits from bad findings.
- 01
A reviewer who earns more from a worse report has a conflict.
- 02
Ace8 does take follow-on audit and modernization work, so we say which side we are working for before we start and tell you if we have worked with the other party. Separate the review from any later project in the contract.
04 · Confidentiality
What NDA terms should you expect?
Expect a signed NDA before any code, data or interviews.
- 01
Check three things: who may see the code inside the firm, whether the code is copied off the seller's systems, and how long the firm keeps working files after the report.
- 02
Sellers often prefer read-only access in their own environment. A good firm accepts that and works within it.
05 · Price
How should you compare prices?
Compare what each quote includes, not the total.
- 01
Published prices from firms that show them vary widely; see technical due diligence cost. Ask whether interviews, a cost-to-fix estimate and a re-check after seller answers are included.
06 · Warning signs
What are the warning signs in a proposal?
07 · Deliverable
What should the report look like?
It should open with a one-page verdict a non-engineer can act on, then give evidence for every finding.
- 01
Each finding needs a severity, the place in the code or the document that shows it, and an effort range to fix.
- 02
Ask for a sample or an outline before you sign. A firm that cannot show the shape of its report probably has no fixed format. Our checklist lists the areas a complete report covers.
08 · Proof
How do you check a firm's references?
Ask for two references from deals of your size, and ask them what the firm missed, not only what it found.
- 01
Treat counts of deals or deal value on a firm's site as its own claims unless a source backs them.
- 02
Ace8 has no published case studies for this service yet. We would rather say so than quote a number we cannot show.
09 · Next step
How do you start?
Send the closing date, the number of repositories and which side you are on.
- 01
Ace8 is the modernization practice of AceMQ, and AceMQ engineers do the work. Read how we scope it on technical due diligence, or if you need a deeper look at one asset, a code audit. Quote on request.