Technical due diligence before you build on a platform or invest in it.
An independent code audit and technology review. We assess platforms at code level for security, scalability and stability, then explain what we found in terms a founder, board or investor can act on.
Building your own technology
A second opinion from people who build software.
Many businesses build their own platform without a senior technical leader. The product works and customers are using it, but nobody inside the business can say whether the code underneath is sound, or what it will take to grow.
We read the code, talk to the people who wrote it and tell you where the risks are, which ones matter now, and which can wait.
Investing in a business
Know what the technology is worth before you sign.
- Whether the platform can carry the growth in the business plan.
- Security and data protection gaps that could become liabilities.
- How much of the product depends on one developer or one supplier.
- Technical debt that will need budget after the deal closes.
- A review independent of any build work, so there is nothing to sell you afterwards.
What a technical due diligence review covers
We rate the risk in every area, so you can compare the findings and decide what to fix first.
What you receive
Written for the people who run the business and the people who will fix the code.
- A written report with a red, amber or green rating for each area.
- An executive summary for non-technical readers.
- A prioritised list of fixes, most urgent first.
- A presentation of the findings to your board or investors.
How a review runs
Two to six weeks, depending on the size and complexity of the platform.
-
Stage 1: Scoping call
We agree what is in scope, who needs the findings and any deal deadline. We sign an NDA before you share anything.
-
Stage 2: Access
You give us read-only access to the code repository. We don't change anything.
-
Stage 3: Review
We work through the code and architecture area by area, and check each finding before it goes into the report.
-
Stage 4: Sessions
We talk to the lead developer or product owner to understand the decisions behind the code.
-
Stage 5: Report and presentation
You receive the report, then we take your board or investors through it and answer their questions.
Before you start
What a review needs from you, and how we handle your code.
Access to the code
Read-only access to the repository is the main requirement. Documentation helps, but we do not expect it to be complete.
Time from your team
A few sessions with the lead developer or product owner. We do the rest of the work without them.
Confidentiality
We sign an NDA before any code is shared, and we share the findings only with the people you name.
Deal deadlines
If an investment decision is waiting on the review, we can fast-track it and agree a reporting date at the scoping call.
Reviews we have carried out
Investors and businesses we have reviewed technology for.
-
Knife Capital
Pre-investment review of a fintech platform.
-
Glynt Group
Pre-investment review of a fintech platform.
-
Angelhub
Pre-investment review of an edtech platform.
-
Snapplify
Pre-investment review of an edtech platform.
-
Yue Diligence
Pre-investment audit of an edtech and fintech platform.
-
Allan Gray
A technology audit of scalability and stability before the application was extended.
After the review
Some clients keep us on a retainer to advise on technical decisions. Where fixes are needed, our software team can also take them on.
-
Architecture sign-off
We review proposed changes before they are built, so major decisions fit the platform as a whole.
-
Quarterly health checks
We measure progress against the original findings and flag new risks as the platform changes.
-
On-call advice
A technical adviser the founder or board can call before a decision, rather than after it.
-
Developer hiring
We help write the brief, assess candidates and check that new hires can work on the existing code.
-
Investor reporting
Regular, plain-language updates on technical progress for investors who need to track the platform.
Technical due diligence FAQs
What is technical due diligence?
It is an independent review of a software platform, covering its code, architecture, security and the team behind it. Investors use it before a deal, and businesses use it before they build further on a platform.
How much does technical due diligence cost?
It depends on the size and complexity of the platform. We agree the scope at the scoping call and quote before any work starts.
Is the review independent?
Yes. The review is a separate engagement and is not tied to any build work, so what might come next has no bearing on the findings.
Do you need to change our code?
No. We only need read access, and we don't alter anything in your repository.
Our platform was built by an outside agency. Can you still review it?
Yes. We often review platforms built by a third party. We may ask for a session with their lead developer.
Can the report be shared with investors?
Yes. We write the executive summary for that purpose, and we can present it to them directly.
Which technologies can you review?
Most modern web, mobile and cloud stacks. We confirm at the scoping call that we have the right people for yours.
What happens if you find something serious?
We raise it with you straight away rather than waiting for the final report, so you can decide what to do while the review continues.
Latest insights
Tell us about the platform you need reviewed.
Let us know what it does, who built it and whether a deal is waiting on the answer. We'll set up a short scoping call.