← All Insights

M&A Technology

The Acquisition Integration Mistake That Costs You Six Months

In an acquisition, the most expensive technology mistake is rarely the system you pick. It is the order you integrate in. Here is the question that should set the sequence.

After over a dozen acquisitions. The most expensive technology mistake I saw was almost never the system anyone picked. It was the order they integrated in.

The pull is always to start with the visible systems. Email, identity, directory. The work that makes it feel like two companies are becoming one. It reads well in a status update and it is satisfying to finish.

But the integrations that actually move the deal are the ones that touch revenue or risk. Financial systems. Customer data. Security tooling. Lead with the cosmetic work and you can burn three to six months of trust and political capital before you have touched anything that changes the business. By the time you reach the integration that mattered, the goodwill you needed to push it through is already spent.

Slow on the cosmetic. Fast on the consequential.

Sequence backward from the deal economics

The teams that get this right start from a sharper question. Not what the two companies look like merged, but what is the one integration that, if we get it wrong, breaks the deal economics. Then they sequence backward from that.

That question reorders everything. The integration nobody wanted to start with, because it is messy and politically expensive, is usually the one holding up the value the deal was built on. Doing it first, while attention and authority are at their peak, is what protects the thesis. The cosmetic work can wait, and waiting on it costs almost nothing.

Slow on the cosmetic, fast on the consequential

This is one of the few places in an integration where moving slowly on the visible work and fast on the consequential work is exactly right. It feels backward, because the visible work is what people ask about first. But the visible work rarely decides whether the acquisition pays off, and the consequential work almost always does.

The discipline is to resist the urge to show early motion, and instead spend the first weeks, when you hold the most leverage, on the integration that carries the most risk. That is the difference between an integration that quietly delivers the thesis and one that spends two quarters looking busy.

How to set the order

Inventory every integration on the table first. Do not sequence anything yet. Just list it all, from the customer database down to the email domain. Then sort each one into three tiers.

Tier one, consequential. Anything that touches live revenue, customer or regulated data, or security exposure. Billing and financial systems, the customer database, identity where it gates security, anything sitting under HIPAA, SOC 2, or a contractual security obligation. Get one of these wrong and it shows up as lost revenue, a breach, or a failed audit. These set the timeline. Everything else sequences around them.

Tier two, value-driving. The integrations the deal was actually priced on. Reporting consolidation, vendor and license rationalization, the shared platform that was supposed to produce the synergy. These do not break the deal if they slip a quarter, but they are the reason the deal existed. They come once tier one is stable.

Tier three, cosmetic. The “we are one company now” work. Email domains, directory, branding, the unified intranet. Real, expected, and almost always the wrong place to start. None of it changes whether the acquisition pays off. It can wait ninety days at close to zero cost.

The instinct is to run that list in the order things feel urgent, which floats tier three to the top because it is the most visible. The discipline is to invert it.

Before you lock the order, run a short checklist:

1. Which single integration, done wrong, breaks the economics this deal was priced on?
2. Which integrations touch live revenue, and can that revenue tolerate downtime while you cut over?
3. Where does customer or regulated data move, and is the receiving side secure enough to hold it on day one?
4. What becomes irreversible once you start, and what is the rollback if you are wrong?
5. Which integrations are cosmetic, and what is the real business cost of letting them wait a quarter?
6. Who owns each integration, and are they accountable for the outcome or just the activity?
7. What does done look like for each, stated in business terms instead of technical ones?

Start with the answer to the first question, while your authority and everyone’s attention are at their peak, and sequence backward from there. Most of the time it is a tier one item nobody volunteered for, because it is messy and politically expensive. That is the one to take first.

I have made this call across a dozen integrations, on the side that had to live with the sequence. The order is not an implementation detail. It is one of the first decisions that determines whether the deal works.

Related: The technology diligence that decides whether an acquisition pays off