The short answer. It can, but only when the plan accounts for the engineering work and capacity each synergy requires. Some add-on synergies are commercial and need little engineering. Others depend on product integration: connecting the add-on to the platform’s workflows, data and infrastructure.
The deal model often counts on growth from the existing roadmap and on synergies that need integration in the same year. When both need the same engineers, the company has to decide on capacity, priorities and dates.
Four kinds of synergy and five questions, set out below, show which synergies depend on engineering and whether the plan has the capacity to deliver them.
Research Grounding
FTI Consulting, June 4, 2026. FTI surveyed 555 senior private equity leaders in 14 countries. M&A rose from the lowest-ranked value creation lever in 2025 to the top priority for 2026. It was also the slowest. Only 25% of firms reported M&A results within 12 months. Only 35% described M&A implementation as efficient, the lowest of the nine levers.
PitchBook, June 25, 2026. Platform buyouts fell to 41% of US PE software deal value through May, the lowest share in at least a decade. Add-ons, at roughly $18 billion, rose to about 45% of software deal value, more than double their share a year earlier.
Bain & Company, 2024. In Bain’s surveys of technology M&A practitioners, failure to integrate the product portfolio was the most common reason companies fell short of their revenue synergies. Bain calls product integration the longest-term, and least certain, of the synergy drivers. It also advises acquirers to ring-fence the incremental R&D investment that integration needs.
PwC, September 29, 2026. In PwC’s survey of 530 executives, technology and data enabled at least a quarter of the synergies for nearly nine in ten acquirers. Only 46% had translated their value drivers into initiatives with owners, timelines and dependencies before integration began.
In my experience, the hardest part of executing a software add-on is integrating the products. Bain’s finding points the same way.
The PE Translation
An add-on deal model for a software platform usually includes four kinds of synergy. They depend on different work.
Cross-selling. The add-on is sold to the platform’s customers as a separate product. This depends mostly on sales.
A combined product. Customers use the two products as one, through shared workflows and data. This depends on product integration.
Operating savings. The two companies share hosting, deployment, security tooling and support. This depends on platform integration.
Product consolidation. Customers move to one codebase, and the other is retired. This depends on migration work.
The distinction matters because a missed cross-sell target is not always an engineering problem. McKinsey found that fewer than 20 percent of the organizations it polled achieved their cross-selling goals. It traces most of the shortfall to commercial factors: how well the products complement each other, sales capacity, incentives and leadership commitment.
The combined product is different. Connecting the add-on to the platform’s workflows, moving data between the two through APIs, and moving the add-on onto shared infrastructure are engineering projects. The acquired product often has its own technology stack, release process, data model and security setup.
The same engineers also own the roadmap that the deal model counts on. The model often assumes organic growth from that roadmap and new revenue from the combined product in the same year. Both can be achievable. The engineering plan has to account for the capacity each needs, and if that capacity is already committed, the company must add engineers, change priorities or move dates.
Cost synergies have the same dependency. Suppose a deal model assumes $2 million a year of hosting and support savings from the start of the hold, and all of it depends on the shared platform. If the platform is finished nine months late, about $1.5 million of planned savings does not arrive in that period. The figures are illustrative.
A synergy that depends on product integration is a claim on engineering capacity. If the plan has not assigned that capacity, the synergy has a date and no team behind it.
The same gap affects the exit. A buyer’s technology diligence on a buy-and-build platform checks whether the synergies in the original deal case have been realized. It also estimates the cost, the delivery risk and the capital the remaining integration work will need. Separate products can be a deliberate and profitable choice. Integration that was promised and not finished becomes part of the buyer’s plan and the buyer’s cost.
So the gap affects the investment case in three ways:
Revenue. Combined-product revenue, and the roadmap growth it competes with, start later than planned.
Cost. Two hosting environments, two support desks and two release processes keep running past the date the model removed them.
Valuation. A buyer evaluates the synergies already realized, and weighs the cost, timing and execution risk of the benefits that still depend on integration.
Operator Experience
The hardest part of the add-ons I worked on was building and integrating the products.
At a K-12 analytics and AI company, we acquired multiple companies. We had separate on-premises products for business intelligence, data engineering, the data warehouse and AI. I unified them into one cloud platform. We replaced the old products incrementally, one part at a time, and did not stop to rewrite everything at once.
Before that, I spent 17 years in product lifecycle management software, much of it building an enterprise integration platform that connected separate systems through their own APIs.
That work is why I treat these commitments separately. Selling two products together is a commercial commitment. Delivering them as one product is an engineering commitment, and it is made alongside the existing roadmap. Merging the two codebases is a third and larger decision, and its business case decides whether it happens during this hold.
Board Question
For each synergy in the add-on’s deal model, what work does it depend on, and has the plan given that work the engineers it needs?
Four Kinds of Add-On Synergy and the Work Behind Each
KIND OF SYNERGY | WHAT IT DEPENDS ON | WHO OWNS THE CRITICAL PATH | THE INVESTMENT DECISION |
|---|---|---|---|
Cross-selling | Sales enablement, incentives and how well the products complement each other | Chief revenue officer | Fund the commercial program |
Combined product | Shared workflows, APIs, data flows and single sign-on | CTO with the head of product | Assign engineering capacity, and decide what the roadmap gives up |
Operating savings | Shared hosting, deployment tooling, security controls, monitoring and support systems | CTO | Check the savings against the migration cost |
Product consolidation | Customer migration, data migration, parallel running and retirement of one codebase | CTO with the head of product | Compare the migration cost with the savings and the reduced risk |
A deal can include all four kinds or only one. Separate products can stay separate for the whole hold. Some savings can also come early, for example from consolidating vendor contracts or combining support teams before any system moves.
Full product consolidation is often the most expensive and disruptive kind. It brings data migration, customer cutover and parallel running, the costs Issue 14 showed modernization estimates most often leave out. The business case has to show that the benefits justify those costs within the hold.
Each additional piece of integration has its own cost, delivery risk and incremental benefit. The operating partner decides where to stop by comparing four things: the expected incremental value, the integration investment, the implementation risk and the time left in the hold.
Five Questions to Ask About Every Add-On Integration Plan
QUESTION | WHO ANSWERS | WHAT A WEAK ANSWER SOUNDS LIKE |
|---|---|---|
1. Which synergies in the deal model are commercial, and which depend on product or platform integration? | Operating partner with the CTO and the chief revenue officer | They all come from the integration. |
2. For each integration-dependent synergy, what engineering work is on the critical path, and who is building it? | CTO with the head of product | The acquired team will build it once the roadmap allows. |
3. Has engineering estimated the capacity the roadmap and the integration each need, and reconciled both against the engineers available? | CTO | We will do both with the current team. |
4. Which integration work can be delivered independently, and which depends on other work finishing first? | CTO with the lead architect | The teams will work out the dependencies as they go. |
5. Which integration will this add-on deliberately not get during this hold, and why? | CTO with the operating partner | Eventually everything moves onto one platform. |
The third weak answer means the plan may be counting the same engineers twice. Ask for the capacity plan, not a verbal commitment. The fourth means the schedule may depend on an API or a shared sign-in that nobody has sequenced, however many engineers are assigned.
The fifth question ends in a decision. A company that never decides where an add-on stops tends to start the most expensive integration by default.
Three Decisions
1. Classify every synergy by the work it depends on before the 100-day plan is approved
Ask the operating partner, the CTO and the chief revenue officer to label each synergy line as commercial, combined product, operating savings or consolidation. Next to it, write the owner, the date the work will finish and the date the model starts counting. Where the work finishes later, move the synergy or fund the work.
2. Ring-fence the engineering capacity on the critical path
Give the integration work that the synergies depend on its own line in the operating plan, with named engineers and a budget sized to the value case. It does not have to be a separate team. It does have to be capacity that the roadmap cannot take back.
3. Decide in writing where each add-on stops
For each add-on, decide which integration it will get during this hold. Stopping short of a single product is often the right decision. Record the reasoning in the board minutes, so a buyer can see the choice was deliberate.
One Number for the Next Operating Review
Execution-ready synergy share: the percentage of modeled synergy dollars for which all the required commercial, product and operational work is complete and validated.
A $3 million combined-product line may need shared workflows, combined provisioning and sales enablement. It counts as ready only when all of them are done.
Report two more shares beside it. The execution-funded share covers synergies whose unfinished work has an approved owner, budget, allocated capacity, documented dependencies and a credible delivery schedule. The uncommitted share covers the remaining synergies, whose execution plans are incomplete or unfunded. The forecast should not count on those.
Classify each synergy only once, so the three shares add up to 100%. If a synergy can be delivered in phases that are measured separately, split those amounts before classifying them.
Execution readiness does not mean the financial benefit has been realized. Track actual revenue and cost savings separately against the deal model.
Board Takeaway
Synergies that depend on product integration compete for the engineering capacity needed to deliver the existing roadmap.
Before approving the next add-on’s 100-day plan, ask which synergies need engineering, what capacity and dependencies that work involves, and whether the company has funded a plan that can deliver both.
Portco Brief is a weekly briefing for PE operating partners and portfolio company executives focused on technology, AI, and value creation. If this was forwarded to you, subscribe at portcobrief.com.
Sources
FTI Consulting, AI Speeds Up Returns in Private Equity as M&A Becomes Top Value Generator for Firms, June 4, 2026, and the full report, Private Equity Value Creation Index 2026: The Value Creation Edge.
PitchBook, PE pivots as platform buyouts in software fall to decade low, June 25, 2026.
Bain & Company, Tech M&A: The New Rules for Scope Deals, Technology Report 2024, and M&A in Technology: Getting Serious about Product Synergies, M&A Report 2024.
PwC, PwC’s 2026 M&A Integration Survey, September 29, 2026.
McKinsey & Company, Capturing cross-selling synergies in M&A.