Services
Technical due diligence
An independent view of the technology behind a deal — before the money is committed.
When investors call
Technology due diligence is most useful before a decision becomes hard to reverse. These are the usual moments.
A short review to confirm the technology supports the story being sold.
A full assessment of code, architecture, security, IP, and the team behind them.
An independent check when a portfolio company's technology stops matching its reporting.
Evidence that the platform can carry the next stage of growth.
What you receive
A written report in plain English. Risk ratings a deal team can act on. A briefing call with the partners, and answers to the questions the report raises.
A full report typically takes two to three weeks. A rapid red-flag review takes five to seven days. Every engagement runs under NDA.
What gets examined
The review covers the whole platform, not just the code. Six areas, each reported with evidence.
How well the software is built, where the debt sits, and what it would cost to fix — in terms a deal team can use.
Vulnerabilities, data handling, access control, and the security practices behind the product.
Whether AI claims are real — model architecture, training data, inference costs, telemetry, and genuine capability against marketing.
Knowledge concentration, documentation, and how dependent the technology is on individual people.
Whether the architecture supports the growth plan, and how cloud spend behaves as the business scales.
Whether the technology genuinely supports the story being sold — differentiation, IP, data, and platform risk.
Intellectual property & code ownership
In a software deal, the intellectual property is the asset. Every engagement checks whether the company owns what it is selling — and whether anything in the codebase could weaken the IP position after completion.
Whether contractors, employees, and past collaborators have properly assigned their intellectual property — so the company actually owns the code it depends on.
Which open-source licences sit in the codebase, and whether copyleft obligations (GPL, AGPL) create disclosure or commercial risk.
The provenance of third-party components and AI-generated code, and whether their terms are compatible with how the software is licensed and sold.
Findings lawyers and deal teams can use to support IP warranties, indemnities, and disclosure before transaction terms are finalised.
Guides
Longer reading on how the work is done.
Before you invest, sign, or build — talk it through.
Book a confidential call. Bring the decision. Daniel will say how he can help — or tell you plainly if he cannot.
Book a call