01 / What gets checked
Seven areas, one question each.
02 / Red flags
What slows a deal down.
- Nobody can explain how the system works without opening the code.
- The product was built by an agency and nobody in the company can change it.
- One person holds all the knowledge, and all the passwords.
- Every new customer needs custom engineering work.
- Costs that nobody has looked at since launch.
- "We'll rewrite it after the round."
None of these kill a deal on their own. Hiding them does.
03 / How founders should prepare
Five things to have ready before the data room opens.
Write down how it's built and why
A short architecture overview and the big decisions behind it.
Name your risks before they do
Your three biggest technical risks, and the plan for each.
Clean up ownership
Code, domains, cloud accounts and IP in the company's name. Contracts with freelancers and agencies that transfer the rights.
Know your numbers
Running costs, uptime, release frequency, and how they change with growth.
Have someone who can explain it in business terms
Investors don't buy code. They buy what it does for revenue, margin and risk.
04 / Why a CTO who has built companies
Not a checklist score. A read on whether it carries the business.
I've been on the side that builds the product and has to answer for it: scaling Cloudyfox to 50+ engineers, building PartnerValue, an enterprise SaaS AI platform, at Aximpro, and serving as CTO of NYALA, a regulated fintech platform.
05 / Questions
Questions people ask
What is the difference between technical due diligence and IT due diligence?
Technical due diligence looks at the product a company sells: its architecture, code, team and ability to scale. IT due diligence usually looks at the internal systems a company runs on, such as ERP, networks and licences, and is common in acquisitions of traditional businesses. A software company usually needs the first.
Who asks for technical due diligence?
Investors before a funding round, buyers before an acquisition, and sometimes enterprise customers before they sign a large contract. Founders also commission one before a raise, to find the problems before an investor does.
How should a startup prepare for technical due diligence?
Write down how the system is built and why, know your biggest technical risks and your plan for them, make sure code and IP ownership are clean, and have someone who can explain all of it in business terms. Surprises cost more than known problems.
Do you work outside Munich?
Yes. I am based in the Munich region and work on-site in Munich and remotely across Germany and Europe. I work in English.