Skip to content

Technical Due Diligence

Know what the software is worth before you buy or invest

Our senior engineers assess the architecture, code, security, infrastructure and delivery practice behind a business you are acquiring or investing in. You get a written report, rated by risk, that you can share with your investors and legal advisers.

Technical due diligence from Talk Think Do is an independent assessment of a business's software before you acquire it, invest in it or come to depend on it. The review typically takes 3-10 working days, works with the limited access usual before a deal completes, and ends in a report rated by risk. It is fixed price, quoted after a short scoping call.

When to commission technical due diligence

Each of these is a point where a decision is hard to reverse once it is made.

Before an acquisition

You are buying a company or a product and need to know what the software is worth, what it will cost to keep, and what could go wrong after completion.

Before an investment

You are investing in a technology business and need to know whether its technical claims stand up, and which risks could affect the valuation.

Before you depend on a system

A system your organisation relies on was built or is run by someone else, and you need an independent view of it before you commit further.

What technical due diligence covers

Six areas, each with findings rated by severity and business impact.

Architecture and code quality

Whether the design suits what the system has to do, and whether competent engineers could maintain and extend the code.

Security posture

Authentication, authorisation, data handling, secret management and vulnerable dependencies, checked against the OWASP Top 10 and rated by severity.

Infrastructure, scale and running cost

Hosting configuration, database design, single points of failure, whether the system can handle growth, and what it costs to run.

Delivery practice

Test coverage, build and release pipelines, rollback, and how AI coding tools are used and whether a person reviews their output.

Knowledge and team risk

Documentation, how much depends on a few people, and whether a new team could take the system on.

Dependency and licence risk

Third-party libraries, end-of-life frameworks and open-source licences, with ownership questions flagged for your legal advisers.
An example of an eight-day technical due diligence review: access is granted in stages, each of the six areas gets a finding, a risk rating and its consequence for the deal, and the report states what could not be checked. Illustrative data for a fictional business.

A code-level review is not a penetration test. If the deal needs one, commission it from a CREST-accredited tester. We also go deeper on architecture on its own, through our architecture assurance service.

Who does what during the review

Most of the work is ours. You set the questions and the timetable, and the business being assessed gives us access.

Who does what in technical due diligence: you set the scope, the business gives access, our engineers review and report
Who does what in technical due diligence, across three lanes: you, the business being assessed, and Talk Think Do. Stage 1, scope: you set out the deal, the questions and the timetable, and Talk Think Do agrees the scope and a fixed price and signs the NDA. Stage 2, access: the business grants read-only access to code, pipelines and configuration. Stage 3, review, highlighted, typically 3-10 working days: senior engineers at Talk Think Do assess all six areas. A gate follows where findings are rated. Stage 4, report: Talk Think Do writes a report with a recommendation for each finding. Stage 5, decision: Talk Think Do walks you through the findings, and you share the report with your advisers and decide.

Due diligence we have carried out

We have carried out technical due diligence for clients before. For CalMac Ferries, operator of the UK's largest ferry network, we carried out independent technical due diligence on another core system alongside our managed support of their integration platform. The work gave CalMac recommendations for improvement and supported decisions on where to invest.

If the deal goes ahead, the findings can become the plan for what comes next. We can fix what the review finds, take on the system under managed support, or hand the findings to the team that will.

Seen enough? Let's talk through your requirements.

Book a free consultation

Frequently asked questions

What is technical due diligence?

Technical due diligence is an independent assessment of a business's software before you buy it, invest in it or come to depend on it. It tells you what the software is worth, what it will cost to maintain, and which risks could affect the deal. We cover architecture, code quality, security, infrastructure, delivery practice, knowledge risk and third-party dependencies.

How is this different from a Maintainability Review?

The review areas overlap, but the audience differs. Technical due diligence answers the questions an acquirer or investor needs settled before a deal, and the report is written to be shared with your advisers. A Maintainability Review is for an organisation that already owns a system and needs to decide what to do with it, such as changing supplier or taking it in-house.

How long does it take?

The review itself typically takes 3-10 working days, depending on the size and complexity of the system. You receive the report within a few days of the review finishing. We fit the scoping call and the walkthrough around your deal timetable.

Can you work with limited access before the deal completes?

Yes. Ideally we have read-only access to the source code, the infrastructure configuration and the build pipelines. Before completion that is often not possible, so we agree on the scoping call what we can see and state in the report what we could not check.

Can you sign an NDA?

Yes. We routinely sign NDAs for due diligence work, and we can use your standard NDA or provide ours.

Do you assess AI-generated code?

Yes. We look at how AI coding tools were used, whether a person reviewed and was accountable for what they produced, and what that means for maintenance and security. We write and review AI-generated code every day in our own delivery, so we know where it tends to go wrong.

Do you advise on intellectual property?

No. We are engineers, not lawyers. We identify the third-party code, open-source licences and authorship questions in a codebase, and flag anything your legal advisers should look at. Our guide to IP licensing and source code handover covers the contractual side.

What does it cost?

Technical due diligence is fixed price, quoted after a short scoping call, because the cost depends on the size of the system and how deep the review needs to go. Book a consultation for a quote.

See how AI is changing how we build software

Our quarterly AI Velocity Report tracks real delivery metrics from live projects: how much of our code is AI-authored, how delivery timelines compare to baseline, and which tools are making a measurable difference. No marketing spin, just honest data from a team that builds software every day.

Read the latest AI Velocity Report

Find out what you are buying

Book a consultation and we will tell you what a review would cover for your deal, how long it would take, and what it would cost.

Book a consultation

or call 01202 006729