Technology Due Diligence in Acquisitions: What I Check Before Close
I’ve led the technology workstream on roughly ten acquisitions, mostly in commercial print. Some were large, some were small tuck-ins, and one of them required moving a primary data center in under a month. The details changed every time. The pattern did not.
Technology is rarely the reason a deal gets done, but it is often the reason the first year after close goes badly. The finance team models revenue, synergies, and headcount. The technology picture usually arrives late, in partial form, and with more optimism than evidence behind it. That gap is where most of the integration pain comes from.
Here is what I look at, and what I’ve learned to watch for.
Start with the business, not the server room
The first question in diligence is not “what do they run?” It is “what does the business depend on to make money next Monday?” That means order intake, production, shipping, billing, and whatever the clients touch directly.
In a lot of mid-market companies, the systems that matter most are not the ones on the inventory spreadsheet. They are the client portal someone built years ago, the nightly file transfer that feeds a customer’s purchasing system, or the controller software on a piece of production equipment that only one person knows how to restart. If you only evaluate the ERP and the email platform, you will miss the things that actually stop revenue.
The checklist I actually use
The scope is broad, and I try to cover all of it even when the timeline is short:
- Hardware and infrastructure. Age, support status, where it physically lives, and what happens if it has to move.
- Software and licensing. What is licensed, what is merely installed, and whether the licenses transfer with the company.
- Core business systems. ERP, accounting, CRM, and ecommerce, plus how well they are actually used rather than how well they are described.
- Equipment control systems. Industry-specific software that runs production machinery, often old and often unsupported.
- Vendors and contracts. Terms, renewal dates, termination clauses, and any agreement that does not survive a change of ownership.
- Client dependencies. Portals, integrations, data feeds, and workflows that a client relies on, whether or not anyone wrote them down.
- The roadmap. What was planned, what was promised to clients, and what was quietly deferred.
- Opportunities. What the acquired client base could gain from capabilities the buyer already has.
That last item is easy to skip because diligence is framed as risk. It shouldn’t be skipped. Some of the best outcomes I’ve seen came from giving an acquired company’s clients access to better ecommerce, integrations, or services than they had before.
Where the surprises hide
Three problems came up again and again.
Incomplete disclosure. Sellers are not always eager to share the level of detail a real technology assessment needs. Sometimes that is caution, sometimes it is a small team that simply does not know, and occasionally it is a hope that a problem will not be noticed until after close. Whatever the reason, the answer is the same: ask specific questions, ask for evidence rather than descriptions, and treat “we’ll get that to you” as an open risk until it arrives.
Hidden client dependencies. The most expensive surprises were almost never infrastructure. They were a client’s integration or a custom workflow that nobody mentioned because it had worked quietly for years. These are the dependencies that cause attrition if you break them during consolidation, so I try to find them by talking to the people who handle client issues, not just the people who manage systems.
Legacy systems and change resistance. Long-established industries tend to run long-established software. Moving people onto a standardized platform is a real learning curve, and it lands on employees who are already uncertain because their company was just sold. Underestimating that is a reliable way to lose good people.
Integrate on purpose, not by default
The easy integration plan is to move everything onto the buyer’s systems as fast as possible. I don’t think that is usually right.
The order I follow is:
- Stabilize first. Keep the acquired business running. Nothing else matters if orders stop shipping.
- Evaluate both environments honestly. The acquired company sometimes has the better system or the better process.
- Keep what is better. If their tool or workflow is stronger, adopt it rather than replace it out of habit.
- Consolidate where standardization pays. Overlapping systems should merge when it improves reliability, supportability, cost, or scale.
- Train people and reduce disruption. Budget real time for training and support. Adoption is the work, not an afterthought.
- Use the combined capabilities to grow. Extend what the buyer does well to the acquired clients.
In my experience it takes a little longer up front, and it keeps more of the clients you paid for.
When the timeline is short
The hardest integration I worked on was the first one. Every core system was on premises, and the primary data center had to move with less than a month for diligence, planning, and execution. Servers, storage, networking, and telecommunications all had to be physically relocated and reconfigured.
The move was completed in a single Saturday without a critical failure. What I took from it is that a compressed timeline does not remove the need for diligence. It makes the diligence you can do more important, and it forces you to put the things that would stop the business ahead of the things that would merely be inconvenient. That first move also set the template for the integrations that followed.
The measure that matters
Nearly every acquisition I supported increased revenue, although some client attrition is normal during consolidation. The difference between a deal that grows and one that shrinks is usually decided early: whether the technology team found the dependencies that mattered, protected them through the transition, and then gave the new clients something better than what they had.
If you are a CIO heading into a deal, push to be involved before the letter of intent turns into a closing date. Diligence done late is still useful. Diligence done early can change the price, the plan, and the first year.