Technical Due Diligence
for Investors and Acquirers
Independent assessment of a software business’s code, architecture, infrastructure and team before you invest or acquire. Fixed fee, written for the deal team.
Fixed fee · From £15,000
What technical due diligence answers
Financial due diligence checks the numbers. Legal due diligence checks the liabilities. Technical due diligence checks the software: whether it works, whether it can support the plan in the investment case, what it costs to run, and who it depends on.
What’s in the report
-
One-page summary of the findings that affect price or terms
-
Architecture and scalability against the growth in the plan
-
Code quality, test coverage and maintainability
-
Infrastructure, security and data exposure
-
Team and key-person risk
-
Delivery track record against the roadmap
-
Third-party dependencies, licences and IP ownership
-
Every finding costed and classified: price adjustment, condition of completion, or reason not to proceed
Pricing
Two fixed-fee engagements. Prices exclude VAT.
Technical Review
£15,000 +VAT
10 working days. For early screening, or where a go / no-go view is needed before full diligence.
-
Codebase, infrastructure and delivery history reviewed
-
Interview with the technical lead
-
Main risks identified and costed
-
Written summary
-
Call with the deal team
-
Credited in full against Full Technical Due Diligence
Full Technical Due Diligence
£35,000 +VAT
15 working days. For deals heading to completion, and where the technology carries the growth case.
-
Everything in the Technical Review
-
Full assessment of architecture, code, infrastructure and security
-
Team, key-person risk and delivery track record
-
Interviews with the technical team
-
Dependency and IP review
-
Every finding costed and classified
-
Full report with summary and technical appendix
-
Presentation to the deal team
Larger transactions or multiple codebases are scoped separately.
Process
Ten working days for a Technical Review, fifteen for Full Technical Due Diligence, from access granted to report delivered.
Scoping call
What the investment case assumes about the technology, the specific concerns, and the timeline. Scope, fee and dates confirmed in writing.
NDA and access
Read-only access to repositories, infrastructure and project tooling. Analysis runs in an isolated environment under our control; working copies are destroyed on delivery and access is revoked.
Codebase analysis
Automated mapping of architecture, dependencies, test coverage and change history across all repositories, so interviews start from evidence. Static and dependency analysis only — target source code is never submitted to third-party AI services.
Interviews and inspection
The technical lead, the people who build and deploy, and anyone holding critical knowledge. Statements are checked against what the analysis found.
Report and presentation
Findings costed and classified. Presented to the deal team, with the technical detail in the appendix.
Who does the work
Anatoly Silko
Founder, Rocking Tech
Building, rescuing and running production software for UK businesses since 2019, most of it side by side with founders - from first prototype to funded platform. That means knowing how startups actually build and ship, what a codebase looks like after three years of pressure, and where what the founders say and what the repository shows tend to part company.
-
MBA, Cranfield School of Management
-
NatWest Accelerator Alumnus 3x
-
Zend & Laravel Certified
-
Association for Competitive Technology - Member
Continuity and cover
I conduct the assessment and write the report. If I am unavailable during an engagement, an associate senior engineer completes it to the agreed timetable. Rocking Tech Ltd carries professional indemnity insurance; cover details are provided on request at scoping.
Technical assessment only. Not financial or legal advice, nor a substitute for either.
Example finding
Illustrative only.
Release process
- Issue
- Releases are manual, run by one engineer from their own machine. No staging environment. Fourteen releases in twelve months; the investment case assumes weekly.
- Evidence
- Commit history, deployment logs, interview with the technical lead, no CI configuration in any repository.
- Cost to fix
- £28,000 and six weeks, plus two weeks of the lead’s time.
- Classification
- Condition of completion: automated deployment and a second engineer able to release. Alternatively a price adjustment if the buyer takes the work on post-completion.
Frequently asked questions
Who commissions it?
The investor or acquirer, or a corporate finance adviser or law firm on their behalf.
What access is required?
Read-only access to source repositories, infrastructure, the issue tracker, and interviews with the technical team. All under NDA. Analysis runs in an isolated environment and nothing is retained after delivery.
What if the target will not grant repository access?
The review proceeds on what is available, and the report states what was and was not inspected.
Which technology stacks are covered?
PHP and Laravel, Node, Python, React and Vue, AWS, Azure and GCP, and AI and LLM-based systems, including platforms built with AI coding tools.
How is this different from the Discovery Sprint?
The Platform Discovery Sprint is for a business planning to build or rebuild a platform: it produces an architecture, a roadmap and a build, buy or don't-build recommendation. Technical due diligence is for an investor or acquirer assessing an existing platform before a transaction.
How soon can you start?
Usually within a week of the scoping call, subject to access.
Book a scoping call
Send the timeline and what the investment case assumes about the technology.
We will confirm scope, fee and dates.