Back to blog

IT debt kills deal value before a transaction even starts

•6 min read

Most founders and operating partners prepare carefully for financial and legal due diligence. Technical due diligence tends to get less attention, right up until the acquirer's adviser sends over a questionnaire and a request for read-only access to the Microsoft 365 tenant. That is usually the moment IT debt stops being an internal irritation and becomes a line in the price negotiation.

In my view, IT debt rarely kills a deal outright. What it does is give the buyer leverage: a price chip, a larger retention, a specific indemnity, or a 100-day remediation plan that you end up funding. If you are planning an exit, or you are a PE sponsor preparing a portfolio company for sale, it is far cheaper to find these issues yourself than to have them found for you.

What IT debt looks like to an acquirer

IT debt is the accumulated cost of decisions that were reasonable at the time: the server nobody wanted to touch, the integration built over a weekend, the admin account shared because it was quicker. Individually they look small. Collectively they tell a buyer how well the business is run.

Imagine you are evaluating a target company that has grown quickly over eight years. Revenue looks healthy, but the core line-of-business application runs on a Windows Server version that is out of extended support. It talks to the finance system through a script one contractor wrote, and nobody else knows how it works. Backups exist, but nobody can remember the last restore test. None of this appears in the management accounts, yet every item will appear in the technical due diligence report, and each one carries a remediation cost the buyer will want reflected in the price.

That kind of picture is common. Companies that grow organically without a formal IT strategy tend to end up there by default rather than through negligence.

The signals a technical due diligence adviser looks for

Advisors work from a fairly consistent checklist. If you want to know how your business will read, these are the areas I would check first.

Unpatched systems and end-of-life platforms

Advisors will ask for patch compliance figures and an inventory of operating systems, databases and firewalls, with support end dates. Anything past end of life is a finding, because it means no security fixes and, often, a forced and unplanned migration after completion. Line-of-business applications pinned to old platforms are the usual culprit, because upgrading the platform means upgrading the application too.

Undocumented integrations

Most SMEs have a web of connections between their CRM, finance, payroll and operational systems: scheduled scripts, exported spreadsheets, middleware nobody remembers buying. If you cannot produce a simple diagram showing what connects to what, and who maintains each link, the buyer will assume integration with their own estate will be slow and expensive.

Single points of failure

One internet connection, one domain controller, one firewall, one person with the global admin password. Advisors look for resilience in infrastructure and in access. A business that cannot show tested backups and a credible recovery plan for its critical systems will see that reflected in the risk register attached to the deal.

Licence position

This one catches people out. Software licensing is a real liability, not just an IT matter. Under-licensed Microsoft estates, server software on the wrong licence model, or SaaS subscriptions held on a founder's personal card all create exposure. Advisors will reconcile licence counts against user counts, and any shortfall becomes a quantifiable cost.

Key-person risk in IT

If one internal person, or one small managed service provider, holds all the knowledge and all the credentials, the buyer is acquiring a dependency rather than a capability. Expect questions about documentation, who holds admin rights, and what happens if that person leaves the day after completion.

Security posture and evidence

Buyers increasingly want evidence rather than assurances: multi-factor authentication coverage, endpoint protection status, incident history, Cyber Essentials or equivalent certification, and data protection records. A business that says it takes security seriously but cannot produce a basic risk register or access review gives the adviser little to work with, and they will err on the side of caution.

How to get ahead of it

Most of this can be addressed in the six to twelve months before a process starts, and much of it is about visibility rather than heavy spending.

Run your own technical assessment first

Commission or carry out the same review a buyer would. Build an inventory of systems, owners, support dates and licences. Map your integrations. Test a restore. I would rather you discover the end-of-life server now, with time to plan, than have it surface in week three of exclusivity.

Cost the remediation honestly

For each finding, put a realistic figure and timeline against it. Not every issue needs fixing before a sale. Some are better disclosed with a credible plan and a budget, because a buyer will price a known, costed risk far more generously than an unknown one. Separate what must be fixed, what should be planned, and what can simply be disclosed.

Fix the cheap, high-signal items

Some fixes cost little and change how the whole estate reads: enforcing multi-factor authentication everywhere, removing shared admin accounts, tidying licence allocation, moving subscriptions onto company accounts and writing down how the critical integrations work. These show the business is managed, and that impression carries into how the adviser reads everything else.

Reduce key-person dependency

Document the critical systems, put credentials into a managed vault with named owners, and make sure at least two people can administer anything that matters. If you rely on a managed service provider, check that your contract gives you the documentation and access you would need to move away from them.

Prepare a clear technology narrative

When the questionnaire arrives, you want to answer it from a position of knowledge. A short document covering the current estate, known risks, the remediation plan and the budget behind it changes the conversation from "what else is hiding here?" to "this is a business that knows itself".

Where I can help

If you are a founder planning an exit in the next year or two, or an operating partner preparing a portfolio company for sale, I can run a pre-sale technical readiness review and help you build a remediation plan an acquirer's adviser will take seriously. You can find details on my services page, or get in touch to talk through where your business stands.