For investors, acquirers, and lenders
Technical due diligence. Before you buy, invest, or lend.
You are about to price a company whose main asset is software you have not read, built by a team you have not met. Two weeks closes that gap.
What gets examined
- The code and the architecture. Can it carry the growth in the deck, and what breaks first when it does.
- The team and the key people. Who actually built this, who can maintain it, and how much of the company leaves if one person does.
- The delivery data. What this team really ships per quarter, read from the repositories rather than the roadmap.
- The cloud costs and the contracts. What the platform costs at current and projected traffic, and which supplier or licence terms bite after the deal. The lens from the AWS cost work applies unchanged.
- The debt ledger. The technical debt, priced per month, so it can sit in the model next to the other liabilities.
What you get
A written report inside 2 weeks: the risks priced in euros, the deal-breakers separated from the negotiation points, and a 100-day plan for the technology if the deal goes through. Findings are stated plainly; if the platform will not carry the plan you are paying for, the report says so on page one.
What it costs
A fixed fee from EUR 6 500, set by the size of the target, agreed before the work starts. 5 to 8 working days of my time. Sell-side preparation, getting your own house ready for someone else's diligence, uses the same checklist at the same fee.
Anonymous by design, which cuts both ways: no target ever appears on this site, and references from past diligence work are shared on the intro call, under NDA where needed.