The acquisition closed. The integration is where the deal is won or lost.
The synergy case the board signed off on lives in the integration, and the purchase agreement never mentions it. After more than 15 of these, here's where the value goes.
Key terms
- The number
- Synergies, cost takeout, a combined run rate
- Approved by
- The board
- Where it lives
- The integration program
- At close
- The deal team moves on. The integration team inherits the promise.
- Settled over
- A year or more of integration
- Decided in
- Tenant strategy, data that doesn't map, the first combined close
- Prepared by
- David Apollon, after more than 15 acquisition integrations
Where the value lands4
- The model as approved, every synergy at full value
- Revenue synergies come in at 25 to 35%
- The finance consolidation slips 2 quarters
- Cost synergies banked at 70 to 85%, and the payback still clears the bid
How much of the case shows up
The dashed line is the full announced case.
Transaction overview
Every acquisition comes with a number: synergies, cost takeout, a combined run rate the board signed off on. That number lives in the integration. The purchase agreement only sets the price.
The deal team moves on the day it closes, and the integration team inherits the promise. The gap between what was modeled and what happens gets decided in places the deal model never mentioned: the tenant strategy, the data that doesn't map, the month-end close that has to run clean the first time with two companies in one system.
I've 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.
The base rates on acquisitions are bad and have been for a long time. Industry estimates put the share of deals that fail to create the value expected 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. Getting the deals closed was never the hard part. They fail on delivery. The model was approved, the price was paid, and then the value the model promised didn't arrive. The price was usually fine. What broke was execution, and execution is the integration.
- McKinsey, Where mergers go wrong, and its synergy-realization research.
- KPMG synergy-realization survey.
- Industry estimates and aggregated industry analyses, including the IT and technology-plan figures.
- Dial positions show direction only. No deal is priced here, so the dial carries no dollar scale.
Figures are industry benchmarks. They frame the pattern and don't model any one deal.
Key consideration 1The value case
The synergy number is a promise with a delivery address
When the board approves a deal, what it's really approving is 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.
| Synergy | Shows up when | Has to be true first |
|---|---|---|
| Cost | Two finance organizations run on one system, duplicate licenses are retired, the books close once | One system, one chart, one close calendar |
| Revenue | The front office sells the combined product | CRM, order data and the service layer brought together, which is a program of its own |
The model is a forecast of what the integration will deliver. When people say the synergies didn't materialize, what they usually mean is the integration didn't.
Key consideration 2Cost against revenue
Cost synergies show up. Revenue synergies mostly don't.
McKinsey's work on synergy realization has the number that should change how a deal team reads its own model. 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.1
That's a large gap, and it sits right inside most value cases. Deal models love revenue synergies because they make the math work: cross-sell, an 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 and the system consolidation. A revenue synergy depends on customers behaving the way the model assumed, and customers weren't in the room when the model was built.
The integration can't conjure revenue the market doesn't want. What it can do is protect the part that was always achievable. The cost case is the part you can deliver, and it 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 didn't bank.
| Cost synergies | Revenue synergies | |
|---|---|---|
| Arrive | Reasonably fast | Mostly don't |
| Trace to | A system consolidation you can point at | Front-office systems nobody sequenced |
| Bankable | Once the second close runs clean | A fraction of the case, 18 to 36 months out |
| Fail by | Slipping, which is visible | Quietly not happening, which isn't |
Source: McKinsey.
Key consideration 3Diligence
Diligence priced the deal. It rarely planned the capture.
There's a handoff failure built into how most deals run. Diligence is set up to validate the price. Planning how the value gets captured usually isn't part of its brief.
McKinsey found that 42% of the time, due diligence failed to produce an adequate roadmap for capturing the synergies it had credited. The same body of work finds diligence can overlook up to 50% of the potential value entirely.1 So the number that goes to the board often rests on an analysis that never checked whether the number was deliverable.
I see the result on the integration side: assumptions that were fine at the price and never got turned 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's slow, and slow is where synergy value leaks.
| The model assumes | On the integration side |
|---|---|
| A system consolidation on the modeled timeline | The technical reality won't support it |
| The acquired company's data maps cleanly to yours | It doesn't |
| A Day 1 date | The tenant strategy can't hit it |
Source: McKinsey.
Key consideration 4The cause
The gap has a named cause, and it sits in the model
It's 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% of respondents point to underestimated integration costs or overestimated growth as the main driver of the gap between projected and actual synergies.2
Both of those are failures of the model. The cost of doing the integration was modeled too low. The growth the integration would deliver was modeled too high. Both estimates were made before close, and both come due during the program.
The integration team doesn't get to renegotiate either one. They inherit a budget set too thin and a growth target set too rich, and they're measured against both. That's why I push deal teams to bring integration leadership in before signing. The people who'll have to deliver the number are the best check on whether the number is real.
| Estimated before close | Inherited by the integration team |
|---|---|
| Integration cost, modeled too low | A budget set too thin |
| Growth, modeled too high | A growth target set too rich |
Source: KPMG.
Key consideration 5Technology
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.3
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 it shows up as a list of decisions the deal model deferred and the integration can't:
- Tenant strategyConsolidate the acquired company into your environment, hold it separately for a period, or build a new unified one. The choice sets the entire timeline, and the timeline is the synergy schedule.
- Data harmonizationCost centers, job profiles and financial dimensions that encode years of the other company's decisions. Whose business logic wins is a negotiation, and it's on the critical path to every cost synergy that runs through finance.
- The first combined closeThe 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're 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, and they're where the value either lands or leaks.
4 in 5 value-losing deals signed with no coherent technology integration plan (around 80%)
Source: aggregated industry analyses.
A synergy with no systems plan behind it is a press release. You can't bank it.
Key consideration 6For the deal team
What this means for the deal team
Keep building the model, but treat it as a hypothesis about the integration. The integration is where it gets tested, and three 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 doesn't 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. If 80% of value-losing deals had no technology plan at signing, the plan stops looking like overhead bolted on afterward. It's the delivery mechanism for the number on the board slide.
- Weight the model toward what the integration can protect. Cost synergies are the part you control, and McKinsey's own numbers say they're the part that mostly gets captured. Build the case so the payback survives even if 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. The deal team gets a closing dinner. The integration team gets the number. Staff and fund that second group like the value depends on them, because it does.
Bottom line
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's the period the value case gets settled in. The base rates are unforgiving. Most deals don't 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, in the program work that follows, when the tenant goes live clean, the data maps and the first combined close runs on time. That's where the number on the board slide turns into money, or doesn't.
I've 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.
Related: What Workday really costs, the pricing, benchmarks and TCO guide.
Pressure-test the synergy case before you sign.
The cost line and the Day 1 timeline in your model are claims about a program that doesn't exist yet. Bring me in early and you'll find out which parts of the value case are deliverable while it's still cheap to know.