← Blog
Fractional CTO21.04.20262 min

Technical due diligence: the questions I always ask

Before investing in a software product, or buying one, a few well-chosen questions surface more than a month-long audit.

Anyone assessing a software product before an investment or an acquisition usually doesn’t have time to read the code, and often that isn’t the right thing to do anyway. What you need is to understand how much the product depends on people, how fragile it is and what it will cost to keep running. These are the questions I always start from.

About the product

  1. Who is the one person who knows how to keep the system running in production?
  2. How long does it take a new developer to ship something?
  3. When was the last restore from a backup, and did it work?
  4. Which components are out of support or without security updates?
  5. What does the infrastructure cost today, and what will it cost if users double?

The answers matter less than how they arrive. If a question is answered with a glance at a colleague, the answer is already a data point. If there’s a document to show, that’s a good sign. If the answer is “only he knows”, I’ve found the first risk.

About the team

I ask how technical decisions are made, who makes them and where they’re written down. I ask how releases happen: how many times a month, how nervously, with what chance of going back. A team that releases often and without drama almost always has a product in good health.

About technical debt

Technical debt isn’t a flaw: it’s a loan, and like any loan it has to be looked at for its terms. I want to know whether it’s known, whether anyone has measured it, whether there’s a plan to repay it. Declared debt is manageable.

Declared technical debt is a loan. The kind nobody knows about is a risk.

What I deliver

A short report, not a list of two hundred points. For each risk I state how likely it is, what impact it would have and what it would cost to fix. At the end there’s a twelve-month plan, with the two or three things to do now and those that can wait. Whoever decides should be able to read it all in one evening and know what to do the next morning.

Gaetano Del Prete Fractional CTO and developer for over twenty-five years. I help startups, SMEs and agencies make fewer technical decisions, but better ones. Book a call →