Skip to content

What Buyers and Investors Will Ask About Your Technology

Raising money, selling the company, or passing a big customer's review: the technology questions are much the same, and so are the answers that change the price. Better to find them yourself, while there's time to fix or explain them.

Comment
What Buyers and Investors Will Ask About Your Technology

Due diligence finds the shortcuts.

The system nobody upgraded. The contractor who never signed over the code. The one person who holds every password. The breach that was handled quietly and never written down. None of them felt urgent while you were busy growing. All of them become urgent the moment someone else is deciding what your company is worth.

Who asks, and why it's the same questions

Three kinds of people will look hard at your technology:

  • Investors, before a funding round.
  • Buyers, before an acquisition.
  • Big customers, before they trust you with their data or their operations.

They want different things from the deal, but they ask much the same technology questions, because they're worried about the same thing: what could go wrong after they've committed, and what it would cost to put right.

What they look at

Most technology diligence covers the same ground:

  • Systems: what runs the business, where it runs, and whether any of it is past its end of support.
  • Security: multi-factor login, admin access, tested backups, any past incidents, and any independent assessment like SOC 2 or a penetration test.
  • Data and privacy: what personal data you hold, where, and whether you meet the laws that apply.
  • People: who the key people are, and what happens if one of them leaves.
  • Software and IP: whether you own the code you rely on, and what open-source licenses and AI-written code are in it.
  • Contracts and costs: what you spend, what renews when, and what changes if the company is sold.
  • Technical debt: what's been deferred, and what it would cost to fix.
  • Resilience: whether you could recover from losing a key system, and how fast.

The red flags that change deals

A few gaps are normal. Every company has some. But some findings change the price, delay the close, or end the conversation:

  • You don't own your code. A contractor or agency built something important and the contract never assigned the rights to you.
  • An undisclosed breach. Something happened, it wasn't written down, and it comes out during the review.
  • One person holds everything. The knowledge, the passwords and the vendor relationships, all in one head.
  • A key contract ends on a sale. A critical vendor or customer can walk away on a change of control.
  • Core systems past end of support, with no plan or budget to replace them.

What these have in common: they're expensive to fix in a hurry, and they make the reviewer wonder what else they haven't found.

Surprises cost more than gaps

The biggest mistake isn't having gaps. It's being surprised by them, or worse, letting the reviewer find them first.

A gap you've found, priced and explained, with a plan, is a negotiation point. The same gap discovered by the other side is a trust problem, and trust problems get priced in too.

Getting ready: start three months out

If you can see a funding round, a sale or a big customer review coming, give yourself time:

  1. Three to two months out: find out. Work through the questions honestly. List every gap, with an owner. Get IP assignments signed with everyone who has written code for you, and write down what systems you run.
  2. Two to one months out: fix the quick ones. Multi-factor login everywhere, admin access cleaned up, shared passwords in a vault, a backup restore tested, contracts and renewal dates gathered. These are cheap, and they show.
  3. The last month: explain the rest. For each remaining gap, write down what it is, what it would cost to fix, and the plan. Build the data room - the documents they'll ask to see - and brief whoever will answer the questions.

In the room

  • Answer the question asked, plainly. If you don't know, say you'll find out, and do.
  • Volunteer the known gaps, with the plan. Nothing builds trust faster.
  • Keep the answers consistent, with each other and with the documents.
  • Have one person coordinate, so nothing is said twice in two different ways.

Reviewers don't expect perfection. They want to see that you know where you stand: here's what we have, here's what we know isn't right yet, here's what it would cost, and here's the plan.

The bottom line

The gaps diligence finds usually come from the same place: decisions deferred, knowledge held by one person, and contracts nobody re-read. Fixing them is good for the business whether or not the deal happens.

Find them first.

Getting ready? The Tech Due Diligence Checklist has the 33 questions they'll ask, what good answers look like, the red flags, the data room list and a three-month plan to get ready.

Free guide: The 45-Minute Tech Spend Checkup - a one-page meeting agenda for finding out whether your technology spending is working.

Related reading

Facing a funding round, a sale or a big customer's review? Let's talk. An honest look at your technology a few months ahead is much cheaper than surprises during the deal.

Comments

No comments yet - start the conversation.

Leadership

What Your Board Actually Needs to Hear About Technology

Most technology reports to the board are too long, too technical, and always green. Boards don't need the technology. They need the decisions, the risks in business terms, the money, and the truth - in a few minutes' reading.