IT Due Diligence Checklist for Private Equity: 12 Questions That Can Change a Deal

Contents
- A £1 million lesson from a healthcare acquisition
- Why management's technology reports aren't always reliable
- IT due diligence checklist: 12 questions investors should ask
- What are the biggest technology red flags in M&A?
- Can technology due diligence reveal opportunities to increase enterprise value?
- What should an IT due diligence report include?
- What happens after technology due diligence?
- Frequently asked questions
- Buying a business without understanding its technology
IT due diligence helps private equity investors understand the technology they're acquiring, the risks they'll inherit and the investment needed to deliver their business plan. A proper assessment examines software, infrastructure, cybersecurity, engineering capability and operating costs. It should also establish what it will cost to fix existing problems and where technology could create additional value.
I've seen what happens when this work gets overlooked.
In one acquisition we became involved with, the buyer faced more than £1 million in additional technology expenditure and an eight-month delay to the product launch.
The financial due diligence had been completed. The technology hadn't been properly examined.
A £1 million lesson from a healthcare acquisition
- £1M+ additional technology expenditure
- 8 months delay to the product launch
- 40 → 2 engineering team
- 50% migration to AWS complete
The transaction involved a distressed healthcare technology business.
The buyer knew the company had experienced significant layoffs. Its engineering team had fallen from approximately 40 people to just two.
What hadn't been properly assessed was how much technical knowledge had disappeared with those people.
The software was already being used by clinics. It had serious bugs, a complicated architecture and dependencies across several technologies.
A migration from a European hosting provider to AWS was only about 50% complete.
Most of the original developers were gone. Nobody remaining had a complete understanding of how everything worked.
And shutting down the product wasn't an option. Clinics were already using it, with patients depending on services supported by the system.
Our engineers had to reverse-engineer the architecture, fix critical issues and complete the infrastructure migration while keeping both environments running. We also continued developing the product.
After approximately six months of engineering work, we delivered an updated product that began generating revenue.
The broader launch had been delayed by eight months, and the technology budget had increased by more than £1 million.
The buyer had acquired a functioning product without fully understanding what it would cost to maintain, repair and develop.
A technical assessment before the acquisition could have identified many of those dependencies.
The investor could then have considered the additional expenditure, implementation timeline and operational risks before committing capital.
A company can look financially attractive while carrying technology liabilities that materially change the investment case.
Why management's technology reports aren't always reliable
One of the most common problems I encounter during technical assessments is the difference between what companies say they've built and what's actually operating.
Smaller engineering teams sometimes present the processes and standards of much larger organisations.
You receive documents describing automated testing, sophisticated architecture, security frameworks, disaster-recovery procedures and ambitious development roadmaps.
Everything looks convincing.
Then you start checking.
Automated testing turns out to be largely manual. The recovery plan has never been tested. A supposedly completed infrastructure migration still has critical dependencies in the old environment.
Sometimes the documentation describes what the company intends to implement rather than what exists today.
I've also encountered situations where a CTO's reports to management were contradicted by the technical evidence.
This can become particularly dangerous when the CEO doesn't have a technical background.
A CEO may genuinely believe the company has capabilities it doesn't possess because they've trusted the person responsible for engineering.
Investors can inherit that same misunderstanding.
That's why we verify material technical claims against evidence.
If management says the infrastructure can support significant growth, we examine the architecture, performance and capacity constraints.
If the company claims to have automated deployments, we inspect the delivery pipeline.
If the CTO promises an ambitious roadmap, we compare those commitments with the team's actual capacity and delivery history.
We document what management reported, what we verified and how any discrepancies could affect the business.
The findings need to be supported by evidence that another qualified professional can independently examine.
The engineering team often tells a different story
An organisation chart doesn't necessarily show who understands the technology.
I've seen situations where a Head of Engineering lacked the expertise required for important technical decisions and was relying heavily on junior developers for complex work.
During an assessment, I want to understand who makes architecture decisions, who maintains critical systems and who gets called when something breaks.
I also want to know what happens if those people leave.
But getting reliable answers requires trust.
Internal engineers sometimes see external specialists as inspectors or competitors. We've experienced this even when joining a company to help deliver a project.
People become defensive and stop sharing information.
We try to establish a shared purpose. Whether the business is raising capital, preparing for a sale or implementing a post-acquisition plan, engineers need to understand how their work contributes to that objective.
We remain independent in our assessments, but we don't treat the existing team as an adversary.
A conversation with someone who knows the system can reveal problems that won't appear in any management presentation.
IT due diligence checklist: 12 questions investors should ask
The depth of technical due diligence depends on the business. A software company, healthcare operator and buy-and-build platform have different requirements.
However, these are the questions I would want answered before acquiring most technology-dependent businesses.
| Question | What to verify | Why it matters |
|---|---|---|
| 1. Which systems keep the business running? | Critical applications, dependencies and business processes | Revenue and operational continuity |
| 2. Does the product do what management claims? | Working functionality and production evidence | Validity of the investment thesis |
| 3. Who actually understands the technology? | Engineering interviews and technical ownership | Key-person and leadership risks |
| 4. Can the team deliver the roadmap? | Capacity, release history and outstanding work | Execution and growth assumptions |
| 5. How much technical debt exists? | Architecture, code quality and maintenance requirements | Future remediation costs |
| 6. Are major technology projects complete? | Migration status and outstanding dependencies | Hidden expenditure and delays |
| 7. Are the systems secure and resilient? | Security controls, incidents and recovery tests | Operational and cybersecurity exposure |
| 8. Does the company control its technology? | Source code, IP rights, licences and vendor contracts | Ownership and third-party dependencies |
| 9. What does technology actually cost? | Cloud bills, SaaS licences and engineering expenditure | Recurring costs and inefficiencies |
| 10. Are the company's AI claims credible? | Architecture, model dependencies and proprietary capabilities | Technology differentiation |
| 11. Can the platform support future acquisitions? | APIs, integration architecture and data quality | Buy-and-build feasibility |
| 12. What will it cost to improve the business? | Engineering estimates, implementation options and resources | Impact on the investment model |
The checklist is a starting point.
Not every company needs microservices, sophisticated automation or the engineering infrastructure of a large technology business.
What matters is whether the technology supports the company's current operations and the investor's future plans.
A relatively simple, well-maintained system can be a better asset than an elaborate architecture that's expensive to operate and difficult to change.
What are the biggest technology red flags in M&A?
From my experience, several findings deserve particular attention.
Critical knowledge has left the company. The product may still work, but maintaining it requires substantial reverse engineering.
Major infrastructure projects remain unfinished. Partial cloud migrations and incomplete integrations can create duplicated costs and operational risks.
Engineering capabilities don't match management's commitments. The roadmap may be unrealistic for the existing team.
Technical debt makes ordinary changes expensive. A working product can still be difficult to develop, scale or maintain.
Technology spending hasn't been reviewed properly. Unused infrastructure and duplicated software subscriptions quietly reduce profitability.
None of these automatically makes an acquisition unattractive.
The investor needs to understand what addressing each problem will cost, how long it will take and what happens if nothing changes.
What about companies claiming to be AI-native?
This is becoming an increasingly important question.
I've seen businesses describe themselves as AI-native when the product is largely a conventional application connected to OpenAI, Anthropic or another provider through an API.
Using external models is perfectly legitimate. Many valuable AI products are built that way.
But investors should understand where the differentiation actually exists.
Does the company own valuable proprietary data? Has it developed specialised workflows or integrations? Does it have production-ready engineering and a meaningful competitive advantage?
What happens if competitors can reproduce similar features?
An AI label doesn't establish technological defensibility. The underlying capabilities and economics need to be examined.
Can technology due diligence reveal opportunities to increase enterprise value?
Absolutely. Sometimes we find opportunities before we've even opened the codebase.
I've seen companies paying for more than 100 software subscriptions while actively using only around 20% of them.
Departments purchase overlapping tools. Contracts renew automatically. Employees leave, but their licences remain active.
Cloud infrastructure develops similar problems.
Companies continue paying for oversized servers, unused environments and resources that no longer serve their original purpose.
In one engagement, just two meetings helped us identify approximately £150,000 in potential annual infrastructure savings.
That was an estimated opportunity requiring further validation and implementation, rather than a realised saving.
But it demonstrated how quickly a technical review can reveal expenditure that has gone unquestioned.
Financial due diligence can establish how much a business spends on technology.
Technical due diligence can help establish whether those costs are necessary and what it would take to reduce them.
How do we calculate ROI?
For each material opportunity, we examine the expected benefit, implementation expenditure, remaining operating costs and delivery risks.
For a standalone business, we generally begin with a 12-month financial view.
For buy-and-build platforms, we typically consider a three-to-five-year horizon.
That longer period matters because the economics of technology change with each acquisition.
An integration platform might require considerable investment initially but reduce the cost of onboarding subsequent businesses.
On the other hand, a poor architectural decision can become increasingly expensive as more companies join the group.
The financial analysis should reflect the acquisition strategy, realistic implementation costs and the timing of expected benefits.
Potential savings remain estimates until they've been validated and realised.
What should an IT due diligence report include?
I think of our role at Bearskin Group in much the same way as a doctor examining a patient.
First, we establish a diagnosis based on evidence. Then we explain the available treatments, their costs, risks and expected outcomes.
Sometimes a business needs urgent intervention. Sometimes it needs a longer-term improvement programme.
Sometimes the examination reveals opportunities to improve performance and create value.
Our reports aim to give investors a clear view of the available choices.
| Stage | What the investor needs to understand |
|---|---|
| Claim | What has management said about the technology? |
| Evidence | What have we independently verified? |
| Exposure | What financial or operational consequences could follow? |
| Options | What are the realistic ways to address the issue? |
| Cost | What will each option require in money, time and resources? |
| Return | What financial benefit or risk reduction can reasonably be expected? |
For material findings, we also identify the required engineering capabilities, implementation dependencies and degree of uncertainty.
Some issues need attention before completion. Others belong in the first 100-day plan or a longer-term value-creation programme.
The investor should understand the technical condition of the business, what improvement will cost and what the available options could deliver.
Our job is to establish the facts and provide realistic choices. The investment decision remains with the investor.
What happens after technology due diligence?
A useful technical assessment should inform the operating plan after the acquisition.
In our healthcare engagement, the immediate priorities were to maintain operational continuity, fix critical software issues, recover technical knowledge and complete the unfinished infrastructure migration.
That required engineers working directly with the existing systems.
A report alone couldn't resolve those problems.
This is why Bearskin Group also provides forward-deployed engineering.
Our engineers work alongside client teams to implement technical improvements, modernise infrastructure and deliver changes in production.
For investors and portfolio companies, our post-acquisition technology services connect due diligence findings with practical engineering delivery.
The diagnosis should lead to a plan that the business can actually execute.
Frequently asked questions
When should private equity firms conduct IT due diligence?
Ideally, before completing an acquisition, while material findings can still inform transaction decisions. The depth of assessment should reflect the target's technology complexity, operating dependencies and investment thesis.
Is IT due diligence necessary for non-technology companies?
It can be particularly important when operations depend on software, data or critical digital infrastructure. Healthcare, logistics, manufacturing and business services businesses may have substantial technology dependencies even when they aren't considered software companies.
Can technical due diligence affect the purchase price?
Yes. Material findings may change assumptions about future investment, operating costs, implementation timelines and financial performance. Investors and their transaction advisers determine how those findings should affect valuation or deal terms.
Buying a business without understanding its technology
Looking back at the healthcare acquisition, many of the problems were discoverable before the transaction.
The engineering team had fallen from approximately 40 people to two. A major infrastructure migration was only halfway complete. The product had serious technical issues and depended on an architecture that few people still understood.
Those facts didn't automatically make the business a bad investment.
But they should have been part of the decision.
More than £1 million in additional technology expenditure and an eight-month launch delay are substantial consequences of discovering technical problems too late.
Buying a technology-dependent business without assessing its technology leaves too much of the investment outcome to chance.
You may underestimate the costs you're inheriting, overestimate what the existing team can deliver or overlook opportunities to improve profitability.
At Bearskin Group, we approach technology due diligence as a diagnosis supported by evidence, followed by practical options and an assessment of their financial implications.
Our responsibility is to explain what's actually happening inside the technology, what can be done about it and what the available choices may cost or deliver.
The investment decision remains yours.
Technology due diligence with Bearskin Group
Bearskin Group works with private equity firms, family offices, acquisition-led businesses and M&A advisers on independent technology assessments, technical risk evaluation and post-acquisition engineering.
Explore our Technology Due Diligence services
Contact: hello@bearskingroup.com
This article is for general information only. It is not investment, legal, tax or accounting advice, and it is not a recommendation to buy, sell or hold any security or to enter into any transaction. Bearskin Group provides technology advisory and engineering services only.


