Technical due diligence for investors and founders.
An independent read on whether a company's technology can carry the plan being sold. One to two weeks, ending in a written report and a verdict, not a hedge.
Commissioned from either side of the table.
Investor-side
You are funding or acquiring, and the technology is the part of the story you cannot verify from a deck. We assess what exists, what it would cost to keep, and what the plan assumes that the codebase does not support.
Founder-side
You are raising, and would rather find the problems before an investor's reviewer does. Same assessment, run for you, with time to fix what is fixable and prepare an answer for what is not.
What we assess.
Architecture and its ceiling
How the system is put together, and the load or scale at which its current shape stops working. Where the ceiling is, not whether one exists.
Technical debt, costed
What is genuinely load-bearing debt versus untidiness that does not matter. Remediation sized in engineer-months so it can go into a model.
Team and key-person risk
Who understands which parts, what is written down, and what happens to delivery if any one person leaves. Usually the finding that changes the deal.
Security and compliance posture
Data handling, access control, dependency and supply-chain exposure, and readiness for the obligations the business is claiming to meet.
Delivery capability
Whether this team can ship the roadmap being presented, judged on how they have actually shipped rather than on process documents.
A plain verdict
Whether the technology supports the business plan, with the reasoning and the assumptions written down so you can disagree with them specifically.
One to two weeks.
Scope and access
Code and architecture review
Team interviews
Report and walkthrough
Length depends on codebase size and how quickly access is granted. We will tell you at scoping which of the two it is, and what we would need to see. If access is too limited for an honest assessment, we will say so rather than write a report with holes in it.
We have nothing to sell you afterwards.
The value of an assessment is that it is not a pitch. So we will not take remediation work on a company we performed investor-side diligence on for six months following the report. That rule costs us the follow-on engagement, which is the point: a reviewer who is hoping to win the rebuild is not a reviewer.
₹1,50,000 – ₹4,00,000.
Scoped on codebase size and the depth required, fixed before we begin. Priced well below what a failed deal or an unbudgeted rewrite costs, which is the only comparison that matters.
Tell us about the company.
Stage, rough team size, and what you are trying to find out. We will tell you whether diligence is worth commissioning and what it would take.
Discuss a diligence engagement →