Most software acquisitions are sold on a single promise: together, the two companies will be worth more than apart. The deck lists the synergies, the board approves the premium, the deal closes. Then the hard part starts, and it is where most of the promised value quietly disappears. When Broadcom paid $69B for VMware in 2023, or Salesforce $27.7B for Slack in 2021, the price made the headlines; whether the synergies behind that price would ever materialise was the question that actually decided the outcome. Across large software deals, more miss their synergy targets than hit them.

Capturing synergy is the discipline of actually realising those gains once the cheque has cleared. It is less glamorous than deal-making and far more decisive: synergies routinely account for 20 to 30 percent of a large deal's modelled value, yet only 60 to 70 percent of what is modelled is ever booked. This guide breaks down the two kinds of synergy, why software and SaaS deals so often fall short, and what the acquirers who get it right do differently.

What is synergy capture?

Synergy capture is the work of turning the cost and revenue advantages promised in an acquisition into real, measurable results after close. A number on a spreadsheet is only a forecast. The gap between the synergies modelled during due diligence and the ones a company actually books a year later is exactly where deal value is won or lost. Acquirers who treat that gap as an afterthought routinely overpay by 10 to 20 percent; the ones who plan for it from the first week tend to come out ahead. Adobe learned the limit the hard way: its $20B bid for Figma, announced in 2022, was abandoned in late 2023 before a single synergy could be tested, after regulators in the EU and UK pushed back.

Cost synergies versus revenue synergies

The two kinds behave very differently, and confusing them is the first mistake. Cost synergies are the dependable ones: retiring duplicate infrastructure, consolidating cloud contracts, merging back-office functions, shutting down overlapping tools. They sit largely within the acquirer's control, which makes them easier to model and easier to bank. Revenue synergies are the seductive line on the deck and the first to slip. Cross-sell and upsell gains assume customers will behave the way the model says, and customers rarely read the model. A safe rule of thumb: underwrite the deal on cost synergies, treat revenue synergies as upside.

Put rough numbers on it. Say a $50M-ARR acquirer buys a $20M-ARR company at a premium that bakes in $8M of annual synergies. Perhaps $5M of that is cost: overlapping cloud spend, a duplicated finance team, two marketing stacks doing the same job. Those savings land within a year if someone owns them. The remaining $3M is revenue synergy, pencilled in from cross-selling the new product into the existing base. That $3M is the figure that tends to evaporate, because it rests on thousands of customer decisions the acquirer does not control. Price the deal as though the $3M may never show up, and the downside mostly takes care of itself.

Why software and SaaS deals miss the target

A handful of failure modes show up again and again. The first is integration debt: two codebases, two data models, and two billing systems that can take 18 to 24 months to reconcile, burning engineering time that was supposed to fund growth. The second is churn. Customers of the acquired product, unsettled by a change of owner and a shifting roadmap, leave before any cross-sell can land; it is common to see 15 to 25 percent of the acquired base lost in the first 12 months. What looked like overlap to be harvested often turns out to be cannibalisation instead. And then there is the quiet exodus: the people who understood the acquired product, its hidden dependencies and its real roadmap, walk out in the first year and take that knowledge with them.

Scale makes the problem concrete. Folding VMware into Broadcom, or Tableau and Slack into Salesforce, means reconciling billing, identity, and data models across millions of seats, a job measured in years rather than quarters. When IBM paid $34B for Red Hat in 2019, it deliberately kept the company operating at arm's length, precisely to avoid the integration damage that sinks more heavy-handed deals. The bigger the overlap a synergy model assumes, the more of these failure modes it quietly invites.

How the best acquirers capture synergy

Teams that consistently realise their numbers tend to run the same plays. None of them are exotic; the difference is discipline and sequence.

  • Sequence cost before revenue. Bank 60 to 80 percent of the controllable cost savings in the first two quarters, while you still have integration momentum. Let the revenue synergies follow once the combined product actually works.
  • Put retention ahead of cross-sell. A retained customer is worth 5 to 7 times what it costs to win a new one, so a forced upsell that triggers a cancellation is a losing trade. Protect the acquired base before you try to grow it.
  • Name an owner for every synergy line. A number with no name attached is a wish. Each line in the synergy model should have a person, a deadline, and a tracked baseline.
  • Protect the product knowledge. Retention bonuses and clear roles for key engineers and account owners cost far less than rebuilding what they carried in their heads.
  • Track it weekly, not quarterly. Synergy targets drift quietly. A short weekly review against the baseline catches slippage while there is still time to act, rather than explaining the miss at year-end.

What ties these plays together is ownership and tempo. The deals that hit their numbers treat capture as a line-managed program with named owners and a weekly heartbeat, not a slide revisited at the next board meeting. Integration is a project with a deadline, and the teams that win run it like one.

The unit-economics test: is the synergy real?

There is a simple way to tell a genuine revenue synergy from a slide. Track the net revenue retention of the acquired cohort twelve months after close. If that cohort still retains above 90% and expands, the combination is creating value and the cross-sell is real. If retention slips, the synergy was an illusion, and no amount of pipeline reporting will change that. A cohort that drifts from 95% to 80% net retention can erase a third of a revenue-synergy forecast on its own. This is the same lens that decides whether growth spend is worth financing: a customer base only compounds if it stays. An acquisition is, in the end, a very large bet on someone else's retention curve.

Funding the integration

Integration costs money long before it saves any. Migration work, retention bonuses, and parallel systems running side by side can consume 60 to 70 percent of the integration budget in year one, while most of the savings arrive across years two and three. Funding that gap with fresh equity is rarely the cheapest choice for a profitable acquirer. The predictable, recurring revenue of the combined business can often support non-dilutive financing instead, matching the cost of capital to an asset that pays back on a schedule. For the wider picture of why these deals happen and how the market is consolidating, see our overview of major SaaS acquisitions.

Frequently asked questions

What does synergy capture mean in M&A? It is the process of actually realising the cost and revenue benefits promised in an acquisition, after the deal closes. The synergies in the model are forecasts; capture is the execution that turns them into booked results.

Which synergies are most reliable? Cost synergies, because 70 to 80 percent of them sit within the acquirer's control: consolidating infrastructure, vendors, and back-office functions. Revenue synergies from cross-sell are far less certain, often delivering well under half of what the model assumed, and arriving in year two or three if at all.

Why do most software mergers miss their synergy targets? Integration debt between systems, customer churn after the change of owner, overlap that proves to be cannibalisation, and the loss of key people who understood the acquired product. Together these can wipe out 30 to 50 percent of the synergies a deal was priced on.

How do you know a revenue synergy is real? Watch the net revenue retention of the acquired cohort a year out. Retention that holds above 90% and expands signals real value; retention that slips means the synergy existed only on the deck.