Technical due diligence that tells you what the technology is really worth.
Technical due diligence (tech DD) is an independent review of a target's software, architecture, engineering team and delivery, done before you sign, so the price and the 100-day plan reflect what is actually there. We read the code and the infrastructure, interview the team one by one, test the roadmap against the evidence and cost every material finding in pounds. You get a red-flag call inside the first week and a report written for the investment committee, not for engineers.
What a management presentation won't tell you
Most technology problems that cost money after completion were visible before it. They were in the commit history, the cloud bill or the one engineer who holds every password.
Two engineers wrote most of the code, and one has resigned.
The "platform" is three products held together by manual work.
Hosting costs grow faster than revenue as customers are added.
Security findings from the last penetration test are still open.
Open-source licences in the codebase conflict with how the product is sold.
The roadmap in the model needs twice the team the business has.
of 947 commercial codebases audited had open-source licence conflicts, the highest on record. Black Duck OSSRA, 2026
of PE firms increased their diligence on AI disruption, and many are combining commercial and technical diligence to test it. EY PE Pulse, Q1 2026
of PE firms had a portfolio company suffer a serious cyber incident in the previous three years. S-RM, 2025
Two formats
Start with a red-flag review if you're still deciding whether to proceed. Its fee is credited in full if you go on to the full review.
Should we keep going?
Code and infrastructure walkthrough, a CTO interview, the cloud bill and the security basics. A short written note and a call with the deal team on anything that could move price, structure or the decision to proceed.
What are we buying, and what will it cost?
Architecture, code quality, scalability, security and data protection, third-party and open-source dependency, product and roadmap, the engineering team and how it ships. Every material finding is rated and costed, with SPA protections and 100-day actions.
Is the AI real, and theirs?
If the equity story leans on AI, add a test of the AI claims, the model and provider dependency and the data rights, plus a view on AI disruption risk to the business.
What we look at
Weighted to the deal. A founder-led SaaS business needs most of the time on code and team; a services business on its systems and data.
Architecture and scalability
How the system is put together, where it will break at three times the volume, and what the next stage of growth costs in engineering and hosting.
Team interviews
Separate, structured interviews with the CTO, senior engineers and product. We test what people say against the repository, the tickets and the incident log.
Code quality and technical debt
Maintainability, test coverage, how releases happen, and the debt that matters, sized in engineer-months and pounds rather than adjectives.
Key-person risk
Who wrote what, who holds the keys, and what happens to delivery if one person leaves. Mitigations priced into the deal.
Security and data protection
Access control, secrets, penetration test history, UK GDPR posture and incident handling. Specialist partners for full cyber or code scanning when the target needs it.
IP, open source and dependencies
IP assignment from staff and contractors, open-source licence conflicts, and reliance on suppliers or APIs that could change their terms.
Product and roadmap
Whether the roadmap in the model can be built by this team, in this time, on this platform, and what is really used by customers.
Cost to run
Cloud and licence spend against revenue, how it scales, and the quick savings a new owner can take in the first quarter.
How it runs
Built around your exclusivity window. Data room access and a management contact are all we need to start.
Scope and quote
Evidence and interviews
Red-flag call
Report and IC session
Technical, IT, cyber or AI due diligence?
The terms overlap. This is how we use them, and which your deal needs.
Technical due diligence
The product the business sells: its code, architecture, engineering team and roadmap. Essential for any software or tech-enabled target.
IT due diligence
The internal systems the business runs on: infrastructure, licences, support contracts and back-office software. Matters most for services, distribution and manufacturing targets, and usually sits inside our review.
Cyber due diligence
A focused security assessment, often with external scanning and penetration testing. We cover the security basics and bring in an accredited partner when the target holds sensitive data.
AI due diligence
Whether the target's AI claims are real, whether the AI is defensible, and whether AI is a threat to the business model. Bought alongside technical due diligence or on its own.
Our evidence checklist is in the technology due diligence checklist for private equity.
Fixed price, quoted in 48 hours
A red-flag review is £8k to £12k over five to seven working days, credited in full against a full review. Full technical due diligence is £15k to £30k over two to three weeks, depending on the size of the target, the number of products and codebases, and the strands commissioned.
Selling a business instead? Exit readiness and vendor technical due diligence finds the same issues early enough to fix them. Investing at seed or Series A? See technical due diligence for VCs.
All prices are fixed and agreed before work starts. The full list is on how we work and pricing.
Led by an operator who has been diligenced, and has bought
Brannan Coady co-founded and ran Netsells, a York software consultancy whose clients included Trainline, Uber and the BBC, through its merger with BGF-backed hedgehog lab. He was Chief Product Officer, COO and then CEO of YourParkingSpace, and sat on the Flowbird Group executive committee through its sale to EasyPark. He has been on both sides of technical due diligence, as the founder being examined and as the investor asking the questions. Specialist security and code-scanning partners join where a target needs them.
About Brannan →Questions about technical due diligence
What is technical due diligence?
Technical due diligence is an independent review of a target company's technology before an investment or acquisition. It covers the software and architecture, code quality and technical debt, security and data protection, IP and open-source licences, the engineering team and key-person risk, the product roadmap and the cost of running the platform. The aim is to price what is really there and plan the first 100 days.
How much does technical due diligence cost in the UK?
Our red-flag review is £8k to £12k over five to seven working days, credited in full against a full review. Full technical due diligence is £15k to £30k over two to three weeks, depending on the size of the target, the number of products and codebases, and the strands commissioned. Large consultancies typically charge considerably more; small code-audit firms often less, with a narrower scope.
How long does technical due diligence take?
A red-flag review takes five to seven working days. A full review of a lower mid-market target takes two to three weeks, built around the exclusivity window. Anything that could change the price or the decision to proceed is raised with the deal team at the end of the first week, not saved for the final report.
What happens in the technical team interviews?
We interview the CTO, senior engineers and the product lead separately, usually for 45 to 90 minutes each. Questions cover how the system is built, how releases happen, what breaks, who knows what, and what they would fix with more time. We compare the answers with each other and with the repository, the tickets and the incident history. Consistency matters more than polish.
Do you need access to the source code?
Read access to the main repositories makes the review much better and is normal on a serious process. Where a seller won't allow it, we work from a guided walkthrough with the CTO, screen shares, architecture documents and automated reports, and say clearly in the report what could not be verified.
What is the difference between technical due diligence and IT due diligence?
Technical due diligence looks at the product a business sells: its code, architecture, engineering team and roadmap. IT due diligence looks at the internal systems the business runs on, such as infrastructure, licences and back-office software. Software companies need mostly technical due diligence; services and distribution businesses need more IT. Our review covers both, weighted to the deal.
An original analysis of UK parking built from public data: eight years of DVLA keeper requests broken down by operator, council parking finances, appeals, the 2026 private parking code's impact assessment, payments and the National Parking Platform, EV charging and every verifiable deal since 2019. With a data appendix, a list of what nobody publishes, and what it all means for investors and operators.
Twelve areas, 107 numbered data-room requests, an interview plan by role and a costing method that turns findings into price, SPA protection, conditions or a 100-day plan. Built for deal teams who need to know which two answers out of fifty change the number.