Synergy capture is the post-close work of turning the synergies you modeled into real cash, and it is where most software deals lose value. The gap is rarely the thesis. It is integration that slips, customers who churn during a clumsy transition, and cost cuts that quietly break the product. The first 100 days after close set whether the combined company hits its synergy number or writes it down a year later.
The model that got the deal approved is a promise; capture is delivery. This playbook covers what has to happen in the first 100 days, how to realize cost and revenue synergies without damaging the business you bought, and how to fund the integration without giving away equity.
What is synergy capture, and why do most software deals miss it?
Modeling a synergy and capturing it are different jobs. The model assigns a dollar figure to cost savings and cross-sell revenue; capture is the operational work of making those dollars appear. The synergy model in the deal is the target, not the result.
Most misses trace to three causes. Integration runs behind schedule, so savings arrive quarters late and get discounted to near zero. Cost cuts land on the wrong teams, and the product or the customer experience degrades. And in SaaS the sharpest risk is churn: an acquisition that unsettles the acquired customer base can erase the revenue synergy before a single cross-sell closes. Our breakdown of a $500M enterprise software synergy case shows the same pattern: what separated the win was execution after close, not the spreadsheet before it.
What has to happen in the first 100 days?
Treat the 100 days as four moves, each with an owner and a deadline. The single rule that governs all of them: every synergy gets a dollar, an owner, and a date, or it does not happen.
- Before close (planning). Name an integration lead and build the plan while due diligence is still open, mapping systems, contracts, and the people you cannot afford to lose.
- Days 1 to 30 (stabilize). Keep revenue running. Lock in retention packages for key engineers and account owners, tell customers what stays the same, and change nothing that generates cash yet.
- Days 31 to 70 (consolidate). Merge the back office and the infrastructure that does not touch customers: billing, cloud contracts, duplicate tooling, finance and HR systems.
- Days 71 to 100 (grow). Start the first cross-sell, align pricing and packaging, and stand up a synergy tracker where each line has a name against it and a due date.
The tracker is what keeps capture honest. A synergy without a named owner is a hope, and hopes do not show up in the combined P&L.
How do you capture cost synergies without breaking the product?
Cost synergies are the fastest to bank because they sit in overhead, not in the product. In SaaS the clean cuts are infrastructure and back office: consolidating two cloud contracts into one with better committed-use pricing, removing overlapping tooling subscriptions, and merging finance, legal, and HR functions that no longer need two of everything.
Take two companies each spending $1.2M a year on cloud and another $600K on overlapping software tools. A single negotiated cloud commitment plus a tooling cleanup can save $700K to $900K a year without anyone touching the product. That is real money, and none of it costs you a customer.
The discipline is knowing what not to cut. Core engineering and customer-facing teams are the revenue you just paid for. Trimming them to hit a cost target destroys the asset behind the deal, which is why acquirers who read CAC as a capital expenditure protect the go-to-market engine and take savings from overhead instead.
How do you capture revenue synergies?
Revenue synergies are larger on paper and harder in practice. The three levers are cross-sell into the combined customer base, unified packaging that bundles both products, and pricing alignment across the two books. Each one takes two to four quarters and carries more execution risk than any cost cut.
Cross-sell only works when the two products serve an overlapping ideal customer profile. Sell product B into product A's base and the math is powerful; force a bundle onto a base that never wanted it and you raise churn instead of revenue. Pricing alignment carries the same trap: repricing acquired customers too fast reads as a penalty for being bought, and some of them leave. Move on revenue synergies deliberately, prove the cross-sell with one segment before you roll it across the base, and hold the packaging changes until the two motions actually fit. The related work of financing a serial roll-up depends on getting this sequence right every time.
Which synergies land first, and where does each one break?
Sequence the work by speed and risk. The table below maps common SaaS synergies to their timing and the failure modes that most often destroy them.
| Synergy | SaaS example | Typical timing | Main risk |
|---|---|---|---|
| Cost: infrastructure | Consolidate to one cloud contract, dedup tooling | 1 to 2 quarters | Migration downtime hits customers |
| Cost: back office | Merge finance, HR, and legal; cut duplicate seats | 1 to 2 quarters | Losing institutional knowledge |
| Revenue: cross-sell | Sell product B into product A's base | 2 to 4 quarters | Mismatched profile raises churn |
| Revenue: pricing | Unified bundle and aligned price points | 2 to 4 quarters | Repricing shocks existing customers |
| Financial: capital | Refinance acquired debt into one facility | 1 to 2 quarters | Covenant conflicts across loans |
Bank the cost and financial synergies first because they are fast and low-risk, then use the credibility of hitting those numbers to fund the slower revenue work. Where the acquired company's earnout terms are still live, the sequence matters even more, because the seller's incentives run on the same clock.
How do you fund the integration without dilution?
Integration costs cash before it returns any. Severance, system migration, retention bonuses, and rebranding all land in the first two quarters, ahead of the savings. Paying for that by selling more equity dilutes the exact returns the synergies were supposed to create.
The alternative is to fund both the purchase and an integration reserve with non-dilutive capital. Venture debt or dedicated acquisition financing covers the deal and the transition without touching the cap table, which keeps the upside from a well-run integration with the existing owners. The cleanest post-close signal that the capture worked is a combined business that acquires customers more efficiently than either company did alone, the discipline at the center of non-dilutive financing for SaaS.
FAQ: SaaS synergy capture
How long does synergy capture take? Cost and financial synergies usually land in one to two quarters. Revenue synergies from cross-sell and pricing take two to four quarters or more, because they depend on customer behavior you do not fully control.
What is the most common reason software deals miss their synergies? Customer churn during a rushed transition, paired with integration that runs behind schedule. Both erode the revenue case faster than any cost saving can offset.
Should you cut the acquired team to hit cost targets? Only duplicate and non-core roles. Cutting product or customer-success teams removes the revenue you bought, so take cost synergies from overhead and infrastructure instead.
Synergy capture is a management discipline, not a spreadsheet exercise. Assign every synergy a dollar, an owner, and a date, bank the fast cost and financial wins first, and move on revenue synergies only where the two customer bases actually fit. Fund the whole transition without dilution and the value you modeled stays with the people who built it. Start from the synergy model and check whether non-dilutive financing fits your next acquisition.
