Tech due diligence: know what you are buying before you sign
A technical due diligence answers three questions: does the technology do what the company says, what will it cost to keep and grow it, and which risks could change the price or the deal. You get a short list of findings, each with its impact on the deal, and a costed plan to fix what matters.
| Red-flag review | 1 week |
|---|---|
| Full review | 2–3 weeks |
| Price | Fixed price, agreed before the review starts |
| Access | code, cloud accounts, bills, architecture and security documents, under NDA |
| You get | findings ranked by impact on the deal, and a costed remediation plan |
- 01Scope
- 02Access
- 03Interviews
- 04Analysis
- 05Report
Scope
What we look at
- Product and architecture. Does the system match the pitch, or is a core feature manual work or a vendor's product behind a thin layer.
- Code and delivery. Tests on the money and data paths, review practice, dependencies, how releases reach production.
- Security. Access control, secrets, encryption, penetration tests and incident history.
- Infrastructure and cost. Cloud setup, backups, monitoring, and cost per customer or per transaction against revenue.
- Scalability. What breaks at ten times the volume, and whether the growth plan needs a rewrite it does not budget for.
- Team, IP and open source. Who holds the knowledge and the access, contractor IP assignment, open-source licences.
Crypto, payments and device companies get extra checks: custody and signing, ledger and reconciliation, firmware updates and the Cyber Resilience Act.
Report
What the report gives you
- A one-page summary a partner or board can read in five minutes.
- Each finding with evidence, its impact on the deal, and the effort to fix it.
- A remediation plan in order for the first 100 days after closing (full review).
- Questions to put in the deal terms: warranties, conditions before closing, retention of key people.
- What is fine, so the real risks stand out.
Fit
When it fits
Use it when you
- are about to invest in or buy a company whose value sits in its software or devices
- need to know before a term sheet or an offer whether anything should change the price
- have no technical partner in the fund who has built payments, wallets or firmware
- need a costed plan for the first 100 days after closing
Skip it when
You need a security penetration test or a legal opinion on its own. We point out where one is needed, but do not replace it.
Why us
We review what we have built
We have built and run the kinds of systems we review: payment and stablecoin platforms, wallet and custody infrastructure, device firmware and AI workflows for regulated teams. Our founders built Stablerail, Transatron and Pitchbreeze.
FAQ
Common questions
Q01Red-flag or full review?
The red-flag review answers one question before a term sheet or an offer: is there anything that should change the price or stop the deal. The full review adds the costed plan for the first 100 days after closing.
Q02What access do you need?
Code, cloud accounts, bills, architecture and security documents, under NDA, and interviews with the CTO, two or three engineers and the person who runs infrastructure.
Q03Will the company see the report?
The report is yours. Before it is final we walk the findings with the company's CTO to correct facts, not to soften conclusions.
Related
Related pages
- Tech due diligence checklist
The ten areas, the red flags that change a deal and what the report should give you.
Guide - How to add stablecoin payouts to a payment platform
For a payments company in the deal: the five parts of a payout flow and what goes wrong.
Guide - CRA readiness sprint
For a device company in the deal: what the Cyber Resilience Act asks of its product.
Offer - Custody models for a fintech
What to check about who can sign.
Guide
Next step
Investing in or buying a software company?
A 30 minute call with Mykhailo about the deal, the questions that matter and the access a review needs.
Mykhailo Tiutin
CTO, Vareger
