James Hobbs Discuss an engagement

Investors, acquirers and their boards

Technical due diligence for investors

In short

Before you write the cheque, it is worth knowing what you are buying. I give investors and acquirers an independent view of a company’s technology, engineering team and risks, in plain commercial terms, drawing on leading technology through funding rounds and advising a CEO through an exit. I also help founders prepare for diligence.

You might recognise this

  • You are about to invest, and nobody on your side can judge the technology.
  • The product demos well, but you cannot tell what sits underneath it.
  • You are acquiring a company and need to know what its technology will cost to own.
  • A portfolio company’s technology is worrying you after the investment.

What technical due diligence looks at

Product and architecture
Whether the platform can support the plan you are investing in, and what would have to change.
Engineering team
Leadership, key-person risk, hiring and how the team actually delivers.
Security and compliance
The controls, evidence and obligations customers and regulators will expect.
Costs
Cloud and vendor spend against revenue, and what it will cost to scale.
AI claims
Whether AI features are real, evaluated and dependable, or a demo.

Diligence reduces risk; it cannot remove it. I report what I found, what it means commercially and what I could not check. The investment decision stays yours.

How we might work together

Examples, not packages. They often overlap within one relationship, and we shape the work together.

See the examples
Before you invest
A short, focused look before you commit, with the risks and their likely cost explained plainly.
Before an acquisition
Deeper work on what the technology will cost to own, integrate and scale after the deal.
After the investment
An independent view, or hands-on help, when a portfolio company’s technology needs attention.
Preparing founders
Helping a company get ready for diligence, so the evidence is to hand and nothing is a surprise.

Relevant experience

Remo homepage: transform boring virtual meetings into real-life events
remo.co
  • Led Remo’s technology organisation through contraction, and advised the CEO on an exit strategy Read the case study
  • Led Festicket’s technology through Series B and C funding Read the case study
  • Served on the BBC’s internal TED (Technology, Engineering and Design) board, one of approximately 12–15 members overseeing digital standards and strategy across the CTPO’s department Read the case study
  • Regularly presented Puregeneration’s hydrogen fuel technology to the boards of publicly listed companies

How we start

We start with a focused look at what you’re trying to achieve, what’s getting in the way, and how I could help. From there, we agree whether there’s a useful role for me and what it should involve.

  • Understanding the business and what you are trying to achieve
  • Meeting the people who matter to the work
  • Looking at enough evidence to see where I could be useful
  • Deciding together whether an ongoing role makes sense, and what it should be

Questions

Do you work for the investor or the company?

For whoever commissions the work, and never for both sides of the same deal. Founders can use the same approach to prepare before investors look.

Will you tell us not to invest?

I tell you what I found, what it means commercially and what I could not check. The decision is yours.

How are scope and fees agreed?

Privately, once I understand the company, the deal and the depth you need. For an early-stage investment it is usually a small fraction of the cheque.

Further reading

What is technical due diligence?

Technical due diligence is an independent assessment of a company’s technology, carried out for investors or acquirers before a deal. It covers architecture and scalability, code quality, security and compliance, the engineering team and key-person risk, and the cost of fixing what it finds. Founders can run the same review beforehand to close gaps. Read the full answer

How do I know whether my engineering team is performing well?

Look at whether engineering helps customers and the business achieve their goals, delivers changes predictably and keeps the product dependable. Combine outcome measures with delivery and operational evidence, then discuss the constraints with the team. Commit counts, hours worked and a busy roadmap cannot establish performance on their own. Read the full answer

Should investors pay for technical due diligence before an early-stage investment?

Usually, yes. A few days of independent technical due diligence costs a small fraction of a typical early-stage cheque. It shows whether the product can support the plan, whether the team can deliver it and which risks you are taking on. It will not guarantee a good investment, but it prevents avoidable surprises. Read the full answer