Buyer guide
What does technical due diligence cover, and what decides its price?
In short
Technical due diligence is an independent review of a software product and the team and practices behind it, usually before an investment or purchase. The price depends on the size and age of the system, how deep the review goes, how much access you give and how fast you need the answer. Compare quotes by scope and by what the report will contain.
Who is this guide for?
Investors, buyers and founders who are about to put money into, buy or sell a software product and need an independent view of its technical risk.
What it is for
The aim is to answer one question: how much technical risk comes with this product? A buyer wants to know what they are really getting. A seller prepares so that surprises do not appear mid-deal. An investor wants to know if the product can grow.
It is a review, not a rebuild. The result is a written assessment of findings and risks, ranked by how much they matter.
What a review usually looks at
Typical areas are the architecture and the code, how the software is built, tested and released, how data and users are protected, who owns what, the third-party components and their licences, the infrastructure and its running costs, and the people who know how it works.
For security and process there are public references. NIST publishes a Secure Software Development Framework that organises practices into preparing the organisation, protecting the software, producing well-secured software and responding to vulnerabilities, and it describes the framework as outcome-based and meant to be adapted to an organisation's risk. OWASP's Application Security Verification Standard lists security requirements for web applications and services, and says it can be used to test security controls and as a benchmark of how much confidence an application deserves.
What moves the price
Size and age of the system: a small, recent product is quicker to read than a large one with years of changes. Number of products, services and repositories in scope.
Depth: a light review of documents and a few conversations is much smaller than reading the code, running the tests and probing security. Access also matters. Reviews are faster and cheaper when the reviewer can see the repository, the cloud account and the team, and slower when everything is shown on a call.
Urgency and the format of the report. A short summary for a deal meeting and a detailed written report for a lawyer are different jobs.
How reviewers differ
Some reviewers are large firms that cover legal, financial and technical review together. Some are independent senior engineers who focus on the technical part. Neither is better in principle. Ask who will actually do the reading, what they have run themselves and whether they are independent of the seller.
Check for conflicts: a reviewer who also wants to be hired to fix the problems has a reason to find many.
How to compare quotes
Put each quote into the same shape: what is in scope, what access is needed, what you receive, how long it takes and what is not covered. A quote without a list of deliverables is not comparable.
Ask for a sample of the report format with details removed. It shows whether findings are ranked and explained in words you can use.
Prepare to make it cheaper and better
Have the repository, the architecture notes, the list of accounts and the people available. Reviewers spend less time chasing, and you get a clearer result.
How do the options compare?
| Factor | Smaller review | Larger review |
|---|---|---|
| System | One small, recent product | Several services with a long history |
| Depth | Documents and conversations | Code, tests and security probing |
| Access | Repository, cloud and team available | Everything shown on a call |
| Output | Short summary of key risks | Detailed ranked written report |
| Timing | A normal schedule | A rush before a deal closes |
What should I check before I sign?
- The scope lists the products, repositories and areas covered.
- You know what the report will contain, and have seen a sample.
- Findings are ranked by importance.
- The reviewer is independent of the seller.
- The reviewer will read the code, not only attend calls.
- Access needs are agreed before the work starts.
- Confidentiality is in the agreement.
How pricing works
I quote in writing after a short discovery call, against a written scope. Building an app from scratch? The app cost calculator gives a first range in two minutes.
What else do people ask?
How long does technical due diligence take?
It depends on the size of the system and the access you give. Ask for a schedule in the quote and note what it assumes.
Do I need it for a small product?
A lighter review can still be worth it before a purchase or an investment, as the money at risk is what matters.
Who should pay for it?
Usually the party that needs the answer. A seller may also commission one to prepare for questions.
Will the review find everything?
No review can promise that. It reduces the chance of unpleasant surprises, and it should state what it did not cover.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.