Technical due diligence in the UK costs roughly £7,500 to £15,000 for a red-flag review lasting a few days, and £15,000 to £35,000 for a full review of a lower mid-market software business over two to three weeks. Deep dives on large or multi-product targets start at about £90,000 at the firms that publish them, and the Big Four don't publish fees at all. The price moves mainly with the number of codebases and engineers, the strands you commission, and how fast you need the answer.
Those ranges come from the prices firms put on their own websites, which are listed below. They are what vendors publish, not audited market data. They are still more useful than the "it depends" most guides offer, and they are close to what I see quoted on real deals.
You are paying for judgement about money, and the hours are only how the judgement gets formed.
How much does technical due diligence cost in the UK?
A small number of UK and US firms now publish fixed fees. Here is what they say, as of October 2026, excluding VAT.
| Provider | Shorter review | Full review | Larger scopes |
|---|---|---|---|
| Rocking Tech (UK) | Technical Review, £15,000, 10 working days | £35,000, 15 working days | Multiple codebases scoped separately |
| Intelance (UK) | Red flag screen from £15,000, 5 days | Core diligence from £35,000, two to three weeks | Deep dive from £90,000, four to six weeks; vendor DD from £45,000 |
| Deadsimple Computing (UK) | Deal Scan, £7,500, three to five days | From £18,000, about 10 working days | Sell-side IT readiness from £12,000 |
| Kolonell (London pricing) | €8,000 to €12,000 for a small single-app SME, about two weeks | €12,000 to €18,000 for a SaaS business with 5 to 15 developers | €18,000 to €25,000 for multi-product platforms |
| AKF Partners (US) | Documents-only, $10,000 to $25,000 | Standard, $25,000 to $40,000 | Expanded $40,000 to $75,000; enterprise from $50,000 |
| Reyem (US) | Standard, $7,500, one product and up to 10 engineers | Extended from $15,000, 11 to 40 engineers | Hourly beyond tier caps |
A few things stand out. The UK specialists cluster around £15,000 for a short review and £35,000 for a full one. The shorter review is credited against the full one at Rocking Tech, Intelance and Deadsimple, which is now close to standard practice. And the scope behind the same label varies a lot. Deadsimple's offer leans towards infrastructure, security and licensing, which suits a services business with an IT estate. Rocking Tech and Intelance are pitched at software products, with code, team and key-person risk in scope.
ACG's July 2026 piece on diligence for technology deals used AKF's tiers as the published benchmark and put full PE-grade work at up to $150,000 on practitioner estimates. That matches the top of the UK lists once you allow for currency and scope.
What drives the cost of technology due diligence?
Six things account for nearly all of the variance. In rough order of how much they move the number:
The size and shape of the target
The single biggest driver is how much there is to read. One product, one repository and eight engineers is a different job from three products, an acquired codebase nobody has merged, a mobile app and an outsourced team in another time zone. Kolonell's London tiers are explicit about this, stepping up by lines of code and developer count. Headcount is a fair proxy, because more engineers means more code, more process and more people to interview.
How many strands you commission
Technical due diligence can mean a code and architecture review only, or it can add a security assessment, a penetration test, an infrastructure and cloud cost review, open source licence scanning, product and roadmap analysis, and AI diligence. Each strand adds days. Kolonell, for example, prices a web and API penetration test as a separate add-on at €5,000 to €12,000. Be deliberate. A pen test on a target that had a clean one three months ago, from a reputable firm, is often money you don't need to spend.
Red-flag review or full review
A red-flag review answers one question: is there anything here that should stop the deal or change the price? It is short, it relies on interviews and a fast read of the code, and it does not try to be comprehensive. A full review documents every material area, costs each finding and produces something your lawyers, lenders and insurer can rely on. I'd always start with the red-flag stage if the deal is still uncertain, because it costs a fraction of the full review and kills bad deals early.
The timeline
Compressed timelines cost more because they need more people working in parallel. Asking for a full review in five working days, rather than fifteen, usually means two or three reviewers instead of one, and a premium for clearing diaries. The cheaper fix is to start earlier. Tech diligence is often scoped after financial and legal, which is backwards.
Buy-side or vendor due diligence
Vendor technical due diligence, commissioned by the seller before a sale, tends to cost more than a buy-side review of the same business. Intelance's vendor DD starts at £45,000 against £35,000 for core buy-side diligence. The extra covers a report written for several unknown readers, reliance letters to the eventual buyer, and often a remediation phase before the process starts. I cover when it pays for itself in vendor technical due diligence.
Whether there is code access
Documents-only diligence is cheaper and less reliable. AKF prices it at $10,000 to $25,000, well below its standard tier. If the seller will not give read-only repository access, you save on the fee and pay for it in what you don't find out.
Big Four vs specialist vs boutique
There are three kinds of provider, and they suit different deals.
The Big Four and the large consultancies (Deloitte, PwC, EY, KPMG, plus Bain, McKinsey and similar on the strategy side) do not publish technical due diligence fees. On large deals they bring a big bench, sector benchmarks, integration planning and a name the lenders and investment committee recognise. On a £15m enterprise value software business, most of that is overhead. You will often be paying for a partner who sells the work and a team who learns your target's stack on the job.
Specialist tech diligence firms (AKF, Crosslake, Rocking Tech, Intelance and similar) do nothing else. They have templates, a method and a stock of comparable targets in their heads. For most lower mid-market and mid-market deals this is where the value sits.
Boutiques and independents, usually a former CTO or two, are the cheapest and the most variable. The best of them are very good, because the person you talk to is the person who reads the code. The weakest produce a long questionnaire answered by management and a red, amber and green grid. Ask who will do the work, ask to see a redacted report, and ask what the last three findings they raised were worth in pounds.
| Provider type | Typical fit | Strength | Watch for |
|---|---|---|---|
| Big Four or large consultancy | Large deals, carve-outs, regulated targets, lender-driven processes | Bench, brand, integration planning | Junior staffing, long reports, unpublished fees |
| Specialist tech DD firm | Lower mid-market and mid-market software and tech-enabled deals | Method, speed, comparables | Templated reports that miss the one thing specific to this target |
| Boutique or independent former CTO | Smaller deals, VC rounds, single-product targets | Senior person doing the work, low cost | Capacity, insurance cover, consistency |
For a fuller comparison, including when a fund's own operating partner or in-house engineers are the better choice and the questions to ask before you sign, see how to choose a technical due diligence provider.
What you should get for the money
A technical due diligence report is worth paying for only if it changes a decision. So, whatever you pay, insist on four things.
First, every material finding should be costed in pounds, with a range and the assumptions behind it. "Moderate technical debt" is not a finding. "£180k to £260k and six to nine months to move off an unsupported framework before the new product line can start" is.
Second, every finding should be routed. Does it go to price, to the SPA as a warranty, indemnity or condition of completion, to the 100-day plan, or into a note for the file? Your lawyers and your model need that mapping, and the reviewer is the person best placed to make it. I set out what a good report looks like, section by section, in what a technical due diligence report should contain.
Third, there should be a red-flag readout early, ideally by the end of the first week, in plain language. Findings that move price take time to negotiate. A perfect report delivered the day before signing is worth less than a rough note on day five.
Fourth, the person presenting the findings should be the person who did the work. You want to ask "how sure are you?" and get an answer from someone who read the code.
I'd add a fifth for software targets: the team should have interviewed the engineers, separately from the CTO. You learn more about key person risk in a 45-minute call with the second engineer than from any org chart. The interview questions I use are in technical due diligence questions.
You are paying for judgement about money, and the hours are only how the judgement gets formed. A provider who prices by the day and describes the output by page count is selling you the wrong thing.
Our technical due diligence prices
Here is what we charge, fixed in writing before work starts and excluding VAT.
| Engagement | Price | Timeline | What it is for |
|---|---|---|---|
| Red-flag review | £8,000 to £12,000 | Five to seven working days | A go, renegotiate or walk view before you commit to full diligence. Credited in full against a full review |
| Full technical due diligence | £15,000 to £30,000 | Two to three weeks | Architecture, code, delivery, team and key-person risk, security, IP and open source, cost to run and technical debt, with every finding costed and routed |
| AI due diligence add-on | Quoted with the main scope | Runs in parallel | Testing AI claims, AI disruption exposure and the cost of AI in the margin |
Where a target sits in each range depends on the number of codebases and engineers and on whether a security test or cloud cost review is needed. I lead every engagement personally and present the findings myself. I have been diligenced as a founder and CEO in a sale and in a merger, and I have commissioned diligence as an investor, so I know which findings get used and which get filed. The details are on the technical due diligence page, and the AI strand is described on AI due diligence.
How to scope a technical due diligence quote
The fastest way to get an accurate fixed price is to send the provider a short brief before the first call. Six pieces of information are enough:
- What the target sells, its revenue, and the rough enterprise value.
- The number of products, codebases and mobile apps, and the main languages and cloud.
- Engineering headcount, split between employees, contractors and any outsourced agency.
- Your deadline, and when access to the data room, the code and the team can realistically start.
- The questions the investment committee is actually asking. "Can the platform carry the growth in the plan?" scopes a different job from "is the AI real?"
- What has already been done: recent pen tests, SOC 2 or ISO 27001 reports, any earlier diligence.
Then ask each provider the same things. What exactly is in and out of scope? Who will do the work, and what share of it? Is the shorter stage credited, and for how long? Will you give a red-flag readout by a fixed day? Does the price include reliance for lenders or a W&I insurer? What happens to the fee if the deal dies halfway through?
The last question matters more than people think. Many deals fall over in diligence. A provider who stops work and bills only for the days used is worth more than a slightly lower headline fee with no exit.
Is technical due diligence worth the cost?
On a software deal, almost always. Take an illustrative £15m enterprise value acquisition with a £20,000 full review: that is 0.13% of the price. A single costed finding on a missing IP assignment, an unsupported framework or an unretained lead engineer usually outweighs the fee several times over, either in price or in a protection the seller would not otherwise have given.
The case for doing it is weaker when software is a small part of what you are buying. For a distribution or services business whose systems are off-the-shelf, a lighter IT review plus an AI disruption check is usually the better spend. For a software business, the question to ask is which provider will find the two things that matter in the first week, not whether to commission diligence at all.
If you have a deal approaching exclusivity and want a fixed quote within 48 hours, the technical due diligence page sets out how we scope it.
Questions
Who pays for technical due diligence?
On a buy-side deal the buyer pays, and the fee usually sits in the deal costs alongside legal and financial diligence. If the deal completes, many funds recharge it to the acquisition vehicle. On vendor due diligence the seller pays and the report is addressed to buyers, normally with a reliance letter for the eventual winner. Ask about reliance at the quote stage, because some firms charge extra for it.
Is VAT charged on technical due diligence fees?
Yes, for a VAT-registered UK provider, at the standard rate. Almost every UK firm that publishes a technical due diligence price quotes it excluding VAT, so add 20% when comparing against a budget. Whether a fund or acquisition vehicle can recover that VAT depends on its own position, which is a question for your tax adviser rather than the diligence provider.
Can technical due diligence be done without access to the code?
It can, but you get less for the money. Some firms sell a documents-only tier at a lower fee, built from the data room, interviews and the target's public footprint. That suits early screening. For a deal heading to completion, read-only repository access is worth insisting on, because the code, the commit history and the deployment logs are where the evidence is. A refusal to grant it is itself a finding.
Is the cost of a red-flag review credited against full due diligence?
At most specialist firms, yes. Rocking Tech, Intelance and Deadsimple Computing all publish that their shorter review is credited in full against the larger one, and ours is too. Check the window: some credits expire after a set period, such as 90 days. If a provider will not credit the first stage, you are paying twice for the same reading of the code.
How long does technical due diligence take?
A red-flag review takes three to ten working days at the firms that publish timelines. A full review of a lower mid-market software business takes two to three weeks. Large or multi-product targets take four to six weeks. The clock usually starts when access is granted, not when the engagement letter is signed, so the speed of the data room matters as much as the speed of the reviewer.