Technology due diligence
You’re about to value a company partly on its technology, and the pitch deck won’t tell you whether that technology is an asset or a liability. Technology due diligence is where I go and find out, the state of the code, the people who built it, the infrastructure it runs on and the debt they’ve left, and report back to you as the buyer in terms of risk and money.
What this is
This is an independent technical assessment, done for the person writing the cheque, not the person receiving it. I go into the codebase, the architecture, the infrastructure, the development practices, and the team, and I come back with a clear read on what’s solid, what’s fragile, what’s missing, and what it’ll cost to fix — translated into the language of risk and money, not engineering.
What I’m really answering is a short list of questions that decide the deal: Will this thing scale, or will it fall over the moment you grow it? Is the codebase maintainable, or is it held together by one person who’s about to leave? How much undeclared technical debt are you inheriting? Are there security or compliance time bombs? Is the team that built it the reason it works, or the reason it barely does? Could this be rebuilt cleanly if it came to that, and what would that take?
It’s deliberately not a rubber stamp. I’ve seen due diligence done as a box-ticking exercise that exists to make everyone comfortable. That’s worse than nothing — it launders risk into confidence. My report is the version I’d want if it were my money: the things that should give you pause, stated plainly, with a sense of how serious each one is.
When you need this
You need this when a meaningful part of what you’re paying for is software, and you can’t independently verify that the software is what it’s claimed to be. The obvious cases:
- You’re an investor about to fund or buy a company whose value rests on its technology.
- You’re acquiring a business and the product is the asset — and you want to know what you’re inheriting before close.
- You’re a board or fund partner who needs an independent technical opinion you can act on, not the founder’s own account of how great the build is.
The cost of getting this wrong is the entire deal. A platform that can’t scale, a codebase only its author understands, or a pile of hidden rebuild work can turn a good price into a bad one overnight. Due diligence is the cheapest insurance in the whole transaction.
How working with me goes
I work to the questions that actually move your valuation, not a generic checklist. We start by agreeing what matters most for this deal — scalability, team risk, security, the cost to take it forward — so the assessment is pointed at your real exposure rather than producing a hundred pages nobody reads.
Then I go in: the code, the architecture, the infrastructure, the deployment and development practices, and conversations with the people who built it. I read what’s there and, just as importantly, what isn’t — the tests that don’t exist, the documentation that’s all in one person’s head, the single points of failure. You get one senior person forming a coherent view, not a junior running automated scanners and pasting the output. I come back with a report written for a decision-maker: the headline risks first, each weighted, each with what it means for the deal.
What you walk away with
- A plain-English read on whether the technology is an asset or a liability, and how confident I am in that.
- A prioritised risk register — the things that should affect the price, the terms, or the decision to proceed at all.
- A realistic view of the technical debt you’re inheriting and what it’ll cost to service or clear.
- An honest assessment of team and key-person risk: is this resilient, or is it one resignation away from trouble.
- A sense of what it would take to rebuild or replace the thing if you ever had to — your walk-away position, quantified.
Who this isn’t for
If you want a report that confirms the deal so everyone can relax, I’m the wrong person — I’ll tell you what I find, including the parts you’d rather not hear before you sign. This is for buyers who’d genuinely rather know now.
When you need a team instead
Due diligence is a one-person, senior judgement job — that’s the whole value of it. But if the deal closes and you’ve inherited software that needs to be rebuilt, stabilised, or scaled, that’s ongoing delivery, and it’s a team’s job, not mine. That’s what my agency, Digital Royalty, is for: taking the thing you’ve just bought and making it sound, at scale, with a team and a process behind it. I can hand the findings straight across, so whoever fixes it starts from a clear map rather than from scratch.
Talk to me
If you’ve got a deal on the table and the technology is a meaningful part of the price, talk to me before you commit. Tell me about the deal and I’ll tell you what the assessment should focus on and how fast it can be done. If what you actually need is a read on an existing build rather than a company, an architecture review or a software audit is the narrower version, and the other ways I help cover the rest. If you’re trying to decide between a consultant’s view and an agency’s, consultant vs agency lays out the difference.