Services · Technical due diligence

Know what you are buying before you sign

For investors, buyers and banks that need an independent technical view of the software and team before an investment, acquisition or refinancing.

Free initial consultation How it works

What you are dealing with

The pitch deck looks great, but what is underneath?

The founders talk about their platform and technology. You need to know whether the software can support growth or will have to be rewritten.

You have no way to price technical risk

You know how to do financial and legal due diligence. For code, architecture and the team, you lack someone who can name the risks and estimate their impact.

Time is short and everything must stay confidential

The deal has a deadline and only a few people may know about it. The review must not disrupt operations or reveal what is going on.

What we assess

The review answers one question: can the software and the team support the plans you are investing in? We focus on five areas:

Area	What we look at
Code	Readability, tests, technical debt, dependence on outdated libraries
Architecture	Whether the system can handle more users, data and features without a rewrite
Security	Access management, data protection, updates, backups
Operations	Deployment, monitoring, outages, infrastructure costs
Team and processes	Knowledge held by individuals, development practices, documentation

Technical debt means shortcuts in development that save time today but slow down every change later. For an investor, it matters how much of it the system carries and what it will cost to pay it down.

How the report is used

The report is written so that both an investor and an engineer can follow it. A short executive summary sets out the main risks and what they mean for the transaction. The detailed section serves the target company’s team or your technical advisers as a basis for fixing issues. Risks are ranked by severity, and each comes with a recommendation: what to fix before the deal, what to address in the contract terms and what can wait.

Confidentiality

We receive documents only after the NDA is signed. We work with code and documents only in the agreed environment, and after the engagement ends we return or delete them as agreed with you. We do not talk about the engagement and never list it as a reference.

What you get

Written report with an executive summary and a detailed technical section
Assessment of code quality and technical debt
Assessment of the architecture and the system's ability to grow
Security overview and identified risks
Assessment of the team, processes and dependence on key people
List of risks by severity, with recommendations
Final presentation and answers to your questions

How it works

days 1–3
Brief and NDA
We sign the NDA and clarify the goal of the review, its scope and the transaction timeline.
week 1
Documents and access
We get access to the code, documentation and infrastructure, and schedule interviews with key people.
weeks 2–3
Analysis
We review the code, architecture, security and processes, and interview the team.
weeks 3–4
Report and presentation
We deliver the report with risks and recommendations and walk you through it in a meeting.

Who it is for

Investors before entering a technology company
Buyers of a company whose value rests on software
Banks and lenders before refinancing
Company management that wants an independent view of its own IT

Who it is not for

Formal standards-based audits ending with a certification
Penetration tests that require a specialised security team
Situations where the target company refuses to give access to its code

Why work with us

A view across the full SDLC

Michal Czerník manages development from analysis to operations. He assesses code, architecture, operations and processes in context, not each area in isolation.

Experience in the CTO role

Experience as a CTO and leading teams helps assess not only the technology, but also whether the team can deliver the plans you are investing in.

AI helps cover more code

With an AI-assisted approach in Claude Code we find our way around a large codebase faster. The conclusions are always verified and signed off by a person.

Frequently asked questions

How long does technical due diligence take?

Typically two to four weeks, depending on the size of the system and the availability of documents. We fit the timeline to the transaction schedule.

Will you sign an NDA?

Yes, we sign an NDA (non-disclosure agreement) before receiving any documents. We can also use your own template.

What exactly is in the report?

An executive summary and a detailed technical section. It covers risks by severity, code quality, architecture, security, the team and recommendations.

Will you comment on the company's valuation?

No, we do not prepare company valuations. We name the technical risks and their possible impact so your financial advisers can take them into account.

Does the whole team at the target company need to know about the review?

No, you and the target company's management decide who is involved. We interview only the agreed people.

Does due diligence replace a security audit?

No, it includes a security overview but not a penetration test. If we find serious risks, we recommend a specialised follow-up test.

Services

Fractional CTO / AI lead

Part-time technology leadership for companies that need a CTO, but not a full-time one. Strategy, team, vendors and AI.