Synergy capture after an acquisition: why deal synergies leak and how to get them back

Every deal model has a synergy line. Cost takeout in year one, revenue synergies in years two and three, a multiple applied to both. It was built by a deal team that will never run the combined company, and it's the number the board will hold the CEO to. By day 180, most of it is still a row in a spreadsheet.

Here's why. Synergy capture isn't a finance exercise. It's an operating one. Synergies leak at the handoffs: from the deal team to the operating team, from the model to the people who have to deliver it, from a target to a weekly decision. You get them back by turning every synergy into an outcome with one owner, a baseline, a date, and a place in the weekly operating cadence, and you do it in the first 30 days, not after the first missed quarter.

I've led or supported more than fifty acquisitions, and the synergies that showed up were never the ones with the best model. They were the ones somebody on the operating side had committed to, by name, with a date, and then reviewed every week until they closed. The rest drifted. Not because anyone was lazy, but because nobody's calendar was organized around them.

The first leak is ownership. The deal team builds the synergy case, closes, and moves to the next deal. The operating leaders inherit targets they never agreed to, built on assumptions they never saw. A target you inherited is a forecast. A target you committed to is an outcome. Until every synergy line has a single owner on the operating side who has signed up for it, the synergy case belongs to nobody, and it shows.

The second leak is language. Synergies are written in deal language: cross-sell, procurement savings, platform consolidation. None of that means anything to the people doing the work until it's defined in operating language: which accounts, which products, whose territory, which comp plan, which system gets retired and on what date. In one KeyDelta engagement, a PE-backed cloud infrastructure company had merged five companies with 1,400 employees across three continents, and each company defined pipeline differently. Reconciling $180 million of reported pipeline to one definition had to come before any revenue synergy could be measured. You can't capture a cross-sell synergy against a pipeline nobody agrees on.

The third leak is sequencing. Cost synergies are visible and fast: overlapping roles, duplicate vendors, two offices in the same city. They get done first because a small group with a spreadsheet can do them. Revenue synergies are slower and harder, because two sales teams, two product groups, and two customer success teams have to work as one. That's exactly the part that stalls. Companies hit the cost number, miss the revenue number, and the deal model quietly shrinks to whatever got cut.

The fourth leak is politics. After a deal, information becomes currency. Leaders on each side hold on to the customer data, the pipeline, and the delivery metrics, because what they know is what makes them hard to replace. We saw this at a PE-backed IT services and cybersecurity platform built from five acquisitions and a carve-out: six entities, six power structures, and no shared view of the business. Making the same operating data visible to everyone at once, then running one weekly review against shared metrics, made hoarding worthless. Six silos became one platform, cross-sell rose 18 percent in the first year, and follow-on integrations ran four times faster because the operating model was already in place.

The fifth leak is the calendar. Most integration teams are built for 100 days, and our 100-day PMI execution playbook covers that window: decision rights, single owners, and a weekly cadence installed before the honeymoon ends. Synergy capture runs longer. Revenue synergies usually land in year two. If synergy tracking lives inside an integration team that disbands at day 100, it disbands with it, and nobody notices until the year-end variance.

So build the synergy register into the operating system, not beside it. Every synergy becomes one line: the outcome in operating language, the baseline it's measured against, the single owner, the date it's due, the leading indicator you'll see first, and the consequence everyone agreed to if it slips. That last column is Commitments Before Scale applied to a deal. Agree on what happens if a synergy misses before anyone starts working on it, not after.

Then review it where decisions already get made. Not a separate PMO meeting with a status slide, but the leadership team's weekly operating cadence, where a slipping synergy gets a decision in the room: more resources, a different owner, or a revised number the board hears about this week instead of next quarter. A tracker that reports and can't decide is a history book.

Settle decision rights before the conflicts arrive. Which CRM survives. Whose pricing wins. Who owns the overlapping accounts. Which product roadmap gets cut. Every one of those is a revenue synergy waiting on a decision, and every week it waits is value you don't get back. Name who decides each one in the first 30 days, and the CEO stops being the escalation path for all of them.

AI belongs here too, in the right order. Once the combined company runs on one data definition and one cadence, AI can do real work on the synergy case: consolidating support, surfacing cross-sell opportunities across the combined customer base, retiring duplicate workflows. Before that, it automates the confusion. Operations first. AI second.

If you're searching for PMI consultants to rescue a synergy case, ask four questions before you hire anyone. Have they held the operating seat, as a CEO, COO, or CRO who had to deliver a synergy number themselves? Will they own outcomes, or report on them? Do they install the register and the cadence in your team, so it runs after they leave? And will they stay through the revenue synergies, or leave after day one and the cost cuts? Then watch for the red flags: an integration plan with no named owners, a PMO that tracks but can't decide, and a junior team doing the work a senior partner sold.

That's the gap KeyDelta was built for. Our operators, a Managing Partner and six Principals who, between them, have held the CEO, COO, and CRO seats, embed with the leadership team, turn the deal model into owned outcomes in the first 30 days, and install the cadence that carries synergy capture past day 100. The first measurable result comes by day 30, and the operating model stays with your team when we step back.

Synergies aren't forecasts. They're commitments, and commitments need owners. Give every synergy a name, a date, and a seat in the weekly cadence, and the deal model becomes the operating plan. Leave it in the spreadsheet, and it stays a spreadsheet. Define it. Measure it. Own it. Close it. Scale it.