The Acquisition Closed. The Integration Is Where the Deal Is Won or Lost.

Every acquisition comes with a number. Synergies, cost takeout, a combined run rate the board signed off on. That number does not live in the purchase agreement. It lives in the integration.

The deal team moves on the day it closes. The integration team inherits the promise. And the gap between what was modeled and what happens gets decided in places the deal model never mentioned: the tenant strategy, the data that does not map, the month-end close that has to run clean the first time with two companies in one system.

I have run more than 15 acquisition integrations. The financial case is won or lost long after the handshake, in the program work nobody puts in the press release.

So let me put a frame around that. The base rates on acquisitions are bad and have been bad for a long time. Industry estimates put the share of deals that fail to create the value expected at somewhere between 70 and 90%. KPMG's synergy work lands inside that range with a sharper number: 83% of deals underperform the case that justified them.

Read those two figures together and a pattern shows up. The deals close. That was never the problem. They are failing to deliver. The model was approved, the price was paid, and then the value the model promised did not arrive. The price was usually fine. What broke was execution, and execution is the integration.

1 The synergy number is a promise with a delivery address

When the board approves a deal, they are not approving a price. They are approving a value case. So many dollars of cost taken out, so many dollars of revenue added, on a schedule that pays back the premium inside a defined window.

That case has a delivery address, and the address is the integration program. Cost synergies show up when you consolidate two finance organizations into one system, retire duplicate licenses, and close the books once instead of twice. Revenue synergies show up when the front office can sell the combined product, which means the CRM, the order data, and the service layer have to come together first.

None of that is in the purchase agreement. All of it is in the program plan. The deal model assumes the integration will happen on time and clean. The integration is where you find out whether that assumption was free or expensive.

The model is a forecast of what the integration will deliver. When people say the synergies did not materialize, what they usually mean is the integration did not.

2 Cost synergies show up. Revenue synergies mostly do not.

Here is the number that should change how a deal team thinks about its own model. McKinsey's work on synergy realization finds that cost synergies typically capture 70 to 85% of the announced value within about 18 months. Revenue synergies capture only 25 to 35%, and they take 18 to 36 months to get even that far.

That is a large gap, and it sits right inside most value cases. Deal models love revenue synergies because they make the math work. Cross-sell, expanded footprint, the combined company selling more than the two did apart. On the model they look as solid as the cost line. In delivery the two drift far apart.

The reason is mechanical. A cost synergy is something you do to your own organization. You control the timeline, the headcount, the system consolidation. A revenue synergy depends on customers behaving the way the model assumed, and customers were not in the room when the model was built.

The integration cannot conjure revenue that the market does not want. What it can do is protect the part that was always achievable. The cost case is the part you can deliver, and it is the part that lives or dies in the systems work. A clean consolidation onto one finance platform is a cost synergy made real. A consolidation that slips 2 quarters is a cost synergy you announced and did not bank.

3 Diligence priced the deal. It rarely planned the capture.

There is a quiet handoff failure built into how most deals run. Diligence is set up to validate the price. It was built to price the deal, not to plan the capture.

McKinsey found that 42% of the time, due diligence failed to produce an adequate roadmap for capturing the synergies it had credited. Same body of work, diligence can overlook up to 50% of the potential value entirely. So the number that goes to the board is built on an analysis that often did not check whether the number was deliverable.

I see the result of this on the integration side. The model assumes a system consolidation that the technical reality will not support on the modeled timeline. It assumes the acquired company's data maps cleanly to yours when it does not. It assumes a Day 1 that the tenant strategy cannot hit. None of that was wrong at the price. It was just never converted into a plan.

When diligence hands the integration team a value case with no capture roadmap, the team is reverse-engineering the plan from the answer. That is slow, and slow is where synergy value leaks.

4 The gap has a named cause, and it is not the market

It is tempting to blame a missed synergy case on conditions. The market softened, a key customer churned, integration was harder than expected. KPMG asked the question directly and got a cleaner answer. 74 percentage point to underestimation of integration costs or overestimation of growth as the main driver of the gap between projected and actual synergies.

Read that as two failures of the model, not two failures of the world. The cost of doing the integration was modeled too low. The growth the integration would deliver was modeled too high. Both are estimation errors made before close, and both come due during the program.

The integration team does not get to renegotiate either one. They inherit a budget that was set too thin and a growth target that was set too rich, and they are measured against both. This is why I push deal teams to involve integration leadership before signing, not after. The people who will have to deliver the number are the best check on whether the number is real.

5 The technology nobody planned is the value nobody captured

The systems are where this gets concrete. Industry analyses trace roughly 47% of failed deals to IT problems. The same analyses find that around 80% of value-losing deals went into signing with no coherent technology integration plan at all.

Sit with that second figure. Four out of five deals that destroyed value had no plan at signing for the thing that was going to deliver the value. The board approved a synergy case that depended on combining two companies' systems, and nobody had worked out how the systems would combine.

On the program side this shows up as a list of decisions the deal model deferred and the integration cannot:

• Tenant strategy. Consolidate the acquired company into your environment, hold them separately for a period, or build a new unified one. The choice sets the entire timeline, and the timeline is the synergy schedule.
• Data harmonization. Cost centers, job profiles, and financial dimensions that encode years of the other company's decisions. Whose business logic wins is a negotiation, and it is on the critical path to every cost synergy that runs through finance.
• The first combined close. The books have to close clean the first time with two companies in one system. Miss it and the cost synergy you announced becomes a control weakness you have to explain.

None of these are exotic. They are the standard work of an integration. What makes them dangerous is that the deal model assumed them away, so the budget and the schedule were built as if they were free. They carry a real cost. They are where the value either lands or leaks.

A synergy with no systems plan behind it is a press release, not a number you can bank.

6 What this means for the deal team

I am not arguing that deal teams should build worse models. I am arguing that the model is a hypothesis about the integration, and the integration is where it gets tested. A few things follow from that.

Bring integration leadership in before you sign. The cost line and the timeline in the model are claims about a program that does not exist yet. The people who run those programs can tell you, before the price is set, which parts of the case are deliverable and which parts are hope. That conversation is cheap before close and expensive after.

Fund the technology plan as part of the value case, not as a cost center bolted on afterward. If 80% of value-losing deals had no technology plan at signing, the plan stops looking like overhead. It is the delivery mechanism for the number on the board slide.

Weight the model toward what the integration can protect. The cost synergies are the part you control, and McKinsey's own numbers say they are the part that mostly gets captured. Build the case so the payback survives even if the revenue synergies come in at the low end of the range, because more often than not they will.

Then treat the integration like the place the deal gets decided, because it is. The deal team gets a closing dinner. The integration team gets the number. Resource the second group like the value depends on them, and it does.

The deal closes in a day. The value lands over the year that follows.

The acquisition closes on a single day. The integration runs for a year or more, and that is the period the value case is settled in. The base rates are unforgiving. Most deals do not deliver what the model promised, and the firms that measured the gap keep pointing back at the same causes: costs underestimated, growth overestimated, no real plan for the systems that were supposed to deliver the synergies.

Those are integration problems wearing the costume of a missed financial case. The deal is won long after the handshake. It is won in the program work that comes after, when the tenant goes live clean, the data maps, and the first combined close runs on time. That is where the number on the board slide turns into money, or quietly does not.

I have run this play across more than 15 acquisitions, Workday to Workday, legacy ERP to Workday, and platform migrations on their own. The full approach is here: how I run an acquisition integration. If you have one coming, book a call or find me on LinkedIn.

Sources: McKinsey, Where mergers go wrong and synergy-realization research; KPMG synergy-realization survey. The IT and technology-plan figures are drawn from aggregated industry analyses. Figures are industry benchmarks, included to frame the pattern, not to model any one deal.

Related: What Workday really costs, the pricing, benchmarks, and TCO guide.