Most synergy estimates presented in an M&A pitch don’t survive the first round of integration planning. The number on slide twelve is rarely the number the combined company delivers — not because the logic was wrong, but because it was never built to withstand scrutiny in the first place.
That gap between the pitched number and the realized number is where deals lose credibility — and where boards start asking why the model didn’t catch it.
Why Synergy Numbers Fall Apart After Signing
The pattern repeats across transactions: a synergy case gets built backward from a target IRR or accretion threshold, then the line items get reverse-engineered to hit it. The model looks complete. Every category — procurement, headcount, cross-sell — has a number next to it. What it lacks is a defensible chain from assumption to driver to cash flow.
When that model meets due diligence, or worse, the first post-close board meeting, the questions are predictable: Where does this number come from? What’s the realization timeline? What happens if it’s wrong? A model built to impress in the pitch rarely has good answers, because impressing and surviving scrutiny are different design goals.
The fix isn’t a bigger synergy number or a longer list of categories. It’s building the case so each component can be traced back to a specific, challengeable driver — and discounted for the realistic probability and timing of capture.
Cost Synergies: The Easier Case, Still Often Overstated
Cost synergies are more defensible than revenue synergies because they rest on things you can observe before close: headcount overlap, duplicate facilities, vendor contracts, overlapping software licenses. That makes them the natural starting point for a credible synergy case.
The error we see most often when reviewing models built for a deal: synergies are estimated at the category level — “G&A reduction: 15%” — rather than at the line-item level. A 15% G&A reduction sounds reasonable until someone asks which fifteen percent. A defensible cost synergy model breaks each category into named drivers: this facility closes in month nine, this vendor contract consolidates at renewal in Q3, these forty-two roles overlap and attrition covers eighteen of them naturally.
That level of granularity does two things. It forces the assumption to confront reality — a facility lease with four years remaining doesn’t close in month nine, no matter what the slide says. And it gives the integration team an actual execution plan instead of a target to reverse-engineer toward.
Revenue Synergies: Why They Deserve More Skepticism
Revenue synergies — cross-sell, pricing power, channel access — get modeled with the same confidence as cost synergies, and they shouldn’t be. Cost synergies depend mostly on internal execution. Revenue synergies depend on customer behavior, competitive response, and sales execution across two organizations that haven’t worked together before. That’s a fundamentally higher-variance assumption, and the model should reflect it.
If we’re deciding how much weight to give a revenue synergy line, the test is straightforward: does the assumption depend primarily on something the combined company controls, or on something a customer has to decide to do? Cross-selling Product A to Company B’s existing customer base depends on B’s customers choosing to buy something new from an unfamiliar vendor relationship — that’s a customer decision, and it should be discounted and phased in far more conservatively than a headcount consolidation.
In practice, this means most defensible models apply a realization-probability haircut to revenue synergies — often 50% or lower in year one, scaling up only as the combined go-to-market motion proves itself — while cost synergies might be modeled closer to 80–90% of stated value in the realistic case.
A Framework for Quantifying Synergies Without Overselling Them
A synergy model that holds up under diligence and post-close scrutiny is structured around three layers, each one auditable independently:
- The driver layer — named, specific assumptions (this contract, this facility, this customer segment), never category-level percentages.
- The probability layer — a realization estimate for each driver based on whether it depends on internal execution or external behavior.
- The timing layer — a phasing schedule that reflects integration sequencing, not a flat run-rate applied from day one.
Run-rate synergies — the steady-state number once everything is fully realized — should always be shown separately from in-year cash impact. Conflating the two is one of the most common ways a synergy case oversells a deal: presenting the year-five run-rate figure as if it were available in year one.
Phasing and the Realization Timeline
Synergy realization isn’t linear, and a model that assumes it is will miss the financing question that actually matters: how much cash does the integration require before synergies start offsetting it? Procurement synergies typically take two to three quarters to show up, once contracts hit renewal and new terms are negotiated. Headcount synergies move faster but carry severance costs that hit the P&L before the savings do. Revenue synergies are usually the slowest — twelve to twenty-four months before cross-sell motions produce measurable pipeline, longer if the sales organizations haven’t been integrated.
A model that shows the J-curve — integration costs and partial realization in years one and two, full run-rate by year three — gives decision-makers a usable picture of financing needs and accretion timing. A model that shows full synergies from close gives them a number that won’t match what the company reports eighteen months later.
How to Present Synergy Numbers So They Survive the Room
Every synergy line in the model should be able to answer three questions on demand: what specifically drives this number, what’s the probability it’s realized at the stated level, and when does it show up in cash flow. If a line can’t answer all three, it isn’t ready to be in the deck — it’s a placeholder dressed as an estimate.
We’re not suggesting smaller numbers. We’re suggesting numbers that hold their value when someone with diligence authority starts asking where they came from. A synergy case built this way is usually less impressive on first read and considerably more credible on the fifth — which is the read that determines whether the deal financing actually closes on the terms assumed.
If you’re working on a transaction where the synergy case needs to withstand external scrutiny — bank financing, board approval, or post-close reporting — let’s talk through what that model architecture looks like.
FAQ
What’s a realistic realization rate for cost synergies in year one? Most defensible models apply 40–60% realization in year one, scaling toward 80–90% by year two as contracts renew and headcount actions complete.
Why do revenue synergies get discounted more than cost synergies? Revenue synergies depend on customer and market behavior, not just internal execution, making the probability of full realization structurally lower and harder to control.
Should synergies be modeled at the category or line-item level? Line-item level. Category-level percentages (such as “10% G&A reduction”) can’t be traced to a specific driver, which is the first thing diligence and bank reviewers test.
How long does it typically take for revenue synergies to show up in cash flow? Twelve to twenty-four months in most cases, depending on how quickly the combined go-to-market motion and sales integration are executed.
If you want to build the kind of synergy models that hold up in a data room — that’s where the methodology gets applied directly to your numbers.