Technical Due Diligence
An independent view of the technology, the team and the risks, before you sign.
- How long1 to 3 weeks
- How we workFixed package
What you receive
Before you invest in or buy a software business, an independent engineer tells you what you are really getting, and what it will cost to fix.
Is the product built to last?
You receiveArchitecture and code quality review
A product that is hard to change slows every plan after the deal.
What it is. An independent read of how the product is designed and written, and how easy it will be to change and grow.
Why it matters. A product that is hard to change slows every plan after the deal. You find out before you sign, not after.
Will it cope with the growth in the plan?
You receiveScalability and hosting review
Growth plans assume the technology can keep up.
What it is. A look at how the product is hosted, what limits it has, and what it would take to serve many more customers.
Why it matters. Growth plans assume the technology can keep up. This checks that assumption against the real system.
Are there security or data problems we would inherit?
You receiveSecurity and data protection review
A breach or a data protection failure after the deal becomes your problem.
What it is. Checks on how the product protects customer data, who has access, and how well it meets GDPR and the privacy laws that apply to you.
Why it matters. A breach or a data protection failure after the deal becomes your problem. It is cheaper to price it in now.
Could a licence stop us using our own product?
You receiveOpen-source licence check
Licence problems are rare but serious.
What it is. A scan of the open-source code inside the product, with any licences that could force code to be shared or limit commercial use.
Why it matters. Licence problems are rare but serious. They are much easier to fix before the deal than after.
What happens if one person leaves?
You receiveTeam, process and key-person risks
The team is often the real asset.
What it is. A view of who builds and runs the product, how they work, and where knowledge sits with one person.
Why it matters. The team is often the real asset. You learn where it is fragile and what to protect in the deal terms.
What could hurt us after we sign?
You receiveA list of red flags and how serious each is
You can negotiate, add conditions or walk away with clear reasons.
What it is. Every serious issue we found, ranked by how much it matters to the deal.
Why it matters. You can negotiate, add conditions or walk away with clear reasons.
What will the fixes cost?
You receiveAn estimate of the work to fix them
You can price the fixes into the valuation instead of discovering them in the first year.
What it is. A rough range of time and cost to deal with each red flag.
Why it matters. You can price the fixes into the valuation instead of discovering them in the first year.
Can you explain it to the deal team?
You receiveA written report and a call
Non-technical decision makers get a straight answer they can act on.
What it is. A clear report written for investors and buyers, and a call to answer questions.
Why it matters. Non-technical decision makers get a straight answer they can act on.
From brief to done
- 1
Days 1 to 2
Scope and access
We agree the questions that matter for the deal and get access to the code and systems.
- 2
Week 1 to 2
Review
Code, hosting, security, licences and conversations with the team.
- 3
Final days
Report
Red flags, fix estimates and a call with the deal team.
Is this idea worth building, and where do we start?
Idea to first step. A one-page brief for your idea: the problem, who it is for, the smallest useful first release and the risks.
- A 30-minute call about the idea and the people it is for
- A one-page brief you can share with a co-founder, a board or another supplier
- It is free. There is nothing to pay and nothing to sign.
- The report is yours to keep and share, whatever you decide.
- No sales call unless you ask for one.
Questions people ask
How much does it cost?
We send a written quote after your request: what it covers and what it does not. The tier, scope and timing set the price.
Could I just use AI for this?
AI drafts code and prototypes quickly, and we use it every day. It cannot decide what to build, prove that it is secure, or answer for it when real people rely on it. That is the part you are hiring us for.
Who owns the work?
You do. Code, designs, files and documents are yours, and the quote says so in writing.
Can we change the scope?
Yes. If something needs adding or removing, we agree it in writing before we do it.
What happens after?
You keep everything we made, and we are here if you need more.