By Mario Peshev, DevriX
Most integration plans I have reviewed fail before the first 100 days start. Not because the operating team is weak, and not because the synergy model was wrong on the spreadsheet. They fail because nobody decided who owned the integration, what it was supposed to protect, and how the deal partner would know it was drifting until the value was already gone.
I have sat on both sides of this. I have advised sponsors on the buy side, and I have run the operating work inside portfolio companies where the integration thesis met reality. The pattern is consistent: the diligence gets funded and staffed properly, the closing gets lawyered properly, and then the integration gets treated as a project management exercise handed to whoever is available. That is a category error. Integration is where the return actually gets made or lost, and it is a set of decisions the deal partner and operating partner own, not a Gantt chart they approve.
This piece lays out what those decisions are, a framework for making them, and how to judge an integration plan before you commit capital and attention to it.
1. Why integration is a return problem, not a project
The financial case for an acquisition rarely survives contact with the combined entity untouched. Bain’s annual Global Private Equity Report has tracked for years how much of PE returns now depend on operational improvement rather than multiple expansion or leverage. When entry multiples are high and debt is expensive, the integration is not a supporting workstream. It is the value creation plan.
Here is the operator translation. When you underwrite an add-on or a platform combination, you are booking value in three buckets: revenue synergies, cost synergies, and risk reduction. Every one of those is a claim about something that has not happened yet. The integration plan is the mechanism that converts the claim into a realized number. If the plan is a schedule of activities rather than a schedule of value, you have no way to tell whether the thesis is being delivered or quietly eroded.
This is the same distinction I keep returning to in the difference between value creation consultants and operators. Advice describes what should happen. Accountability owns whether it did. Integration lives entirely on the accountability side.
McKinsey’s private capital research and HBR’s long body of work on mergers and acquisitions both land on a version of the same finding: the majority of deals that disappoint do so on execution, not on thesis. The thesis was often right. The integration was under-owned.
2. The four decisions the deal partner cannot delegate
Before anyone builds a plan, four decisions have to be made by the people who own the return. These are not project decisions. They set the frame everything else runs inside.
Integration depth
Full absorption, or standalone with shared services, or something between? This is the single most consequential decision, and it is a value decision, not an org-chart preference. Full absorption unlocks cost synergies faster and exposes revenue and culture risk sooner. A standalone hold protects the acquired business’s momentum and defers the synergy capture. You are trading integration risk against synergy speed, and only the deal partner can price that trade against the hold period and exit thesis.
Sequence
What gets integrated first, and what is deliberately left alone? Revenue-touching systems that risk customer disruption are handled differently from back-office consolidation that customers never see. Sequencing is where most plans quietly go wrong, because teams default to whatever is technically easiest rather than whatever protects the thesis.
Ownership and authority
Who runs the integration day to day, and what can they decide without escalating? An integration lead with responsibility but no authority is a status-report generator. This is exactly the case I made in why PE value creation needs embedded partners rather than advisory firms: someone has to be inside the business with the mandate to move, not outside it producing recommendations.
The value tracker
How will realized synergies be measured against the deal model, and on what cadence will the deal partner see it? If the answer is “we’ll know at the next board meeting,” the plan has no feedback loop and drift is guaranteed.
3. A framework for the plan itself, four tiers
Once the four decisions are made, the plan needs structure. I organize integration plans into four tiers, worst-first in terms of how much they get skipped. Each tier answers a different question and is judged differently.
Tier 1, protect the base
Before any synergy capture, what could the integration break? Customer relationships, key employees, revenue continuity, and the systems that keep cash moving. This tier is about downside, and its measure is simple: nothing that was working before should stop working because of us. Attrition of top customers and top talent in the first two quarters is the leading indicator here.
Tier 2, capture the committed synergies
These are the numbers in the model that justified the price. They are the promises you made to your own investment committee. Each one needs an owner, a baseline, a target, and a date. Cost synergies belong here mostly, and they are the most defensible because they are within your control.
Tier 3, unlock the revenue synergies
Cross-sell, pricing alignment, expanded distribution. These are real but they are forecast value, not realized value, and they behave that way. They take longer, depend on customer behavior, and miss more often. I treat Tier 3 numbers with the same skepticism I apply to any revenue theory, which is why a fractional CRO working win rate and CAC is often worth more here than a slide of projected cross-sell.
Tier 4, build the platform
The capabilities the combined entity needs for the next add-on or for exit readiness. Shared data, a common commercial motion, clean reporting. This tier is enabled value. It rarely shows up in this deal’s model but it is what makes the next deal cheaper to integrate and the platform more valuable at exit.
4. How to tell realized value from wishful value
The most common failure in integration reporting is that everything gets counted as if it already happened. A signed contract, a projected cross-sell, and a headcount plan get lumped into one synergy number, and the deal partner cannot see the difference between money in the bank and money in a slide.
Discipline here matters more than optimism. I classify every synergy claim into one of a few states:
- Realized: it has hit the P&L, you can point to the line item.
- Run-rate: the change is in place and will annualize, even if the trailing twelve months do not show it yet.
- Forecast: modeled, dependent on future behavior, not yet locked.
- Risk avoided: a cost or loss you prevented, which is real but easy to overstate.
This matters at exit as much as during the hold. When you present adjusted EBITDA to a buyer, the quality of your add-backs is under scrutiny, and I have written separately about the art of add-backs and how a sloppy integration synergy story becomes a quality-of-earnings problem.AICPA and CIMA’s guidance on financial reporting standards, is the reference point any credible operating review will hold your synergy claims against.
5. The revenue leakage that integration creates
Integrations do not just capture value, they leak it, and the leaks are usually invisible until a quarter is missed. When you merge two commercial organizations, you disrupt pipelines, confuse account ownership, retire products customers still want, and change pricing in ways the sales team cannot explain. Every one of those is a hole in the boat.
I run a revenue leakage diagnostic as part of integration planning, not after, precisely because the integration is where fresh leaks get created. The Tier 1 mandate to protect the base is enforced here. If your integration plan has a detailed cost synergy schedule and a vague paragraph on “commercial continuity,” you are planning to lose revenue you have not budgeted for.
The connective tissue is a real commercial plan for the acquired entity, which is why I usually pair integration planning with a 100-day go-to-market plan. Integration decides the structure. The GTM plan decides how revenue keeps moving through it.
6. An applied example, a two-company platform build
Let me make this concrete with a composite drawn from work I have seen, not a specific client result. A sponsor acquires a platform B2B services business and, six months later, a smaller regional add-on. The model books three synergy sources: consolidated overhead, cross-sell of the platform’s premium tier into the add-on’s base, and a shared delivery team.
The four decisions. Depth is set to full absorption on back office, standalone on customer-facing brand for twelve months to protect the add-on’s local relationships. Sequence puts finance and reporting consolidation first, sales integration last. Ownership goes to an integration lead embedded in the add-on with authority over anything under a set threshold. The value tracker reports monthly against the model, split by realized, run-rate, and forecast.
The four tiers in motion. Tier 1 flags that two of the add-on’s top five accounts are relationship-dependent on a founder who is exiting; those get a retention plan before anything else moves. Tier 2 consolidated overhead is on track and mostly run-rate by month four. Tier 3 cross-sell, the number the deal partner was most excited about, is running at roughly half the modeled pace because the add-on’s customers buy on a different cycle. Tier 4 quietly builds the shared reporting layer that will make the third acquisition faster.
The point of the example is the reporting, not the outcome. Because the value tracker separates the tiers, the deal partner can see in month four that the deal is safe, most committed synergies are landing, and the revenue synergy is the risk to manage, not a surprise waiting at month eighteen. That visibility is the whole product of good integration planning.
7. How to judge an integration plan before you fund it
When a plan lands on your desk, here is how I read it. These are the questions that separate a real plan from a schedule.
- Does every synergy have an owner, a baseline, and a date? A synergy without a named owner is a hope. A synergy without a baseline cannot be measured, which means it cannot be proven at exit.
- Is Tier 1 explicit and funded? If protecting the base is assumed rather than resourced, the plan is optimistic about the one thing that kills returns fastest.
- Are revenue synergies discounted relative to cost synergies? A plan that treats Tier 3 cross-sell with the same confidence as Tier 2 headcount reduction is not being honest with itself.
- Does the integration lead have authority, not just responsibility? Check the decision threshold. If everything escalates, nothing moves.
- Is the reporting cadence monthly and classified? Quarterly board-level reporting is a lagging indicator. By the time drift shows up there, a quarter is gone.
These questions overlap heavily with the commercial due diligence red flags I look for pre-close. The same discipline that surfaces a fragile customer base in diligence should carry straight into the integration plan, because a fragile base is exactly what a bad integration accelerates.
8. Who is reading the plan changes what it should say
An integration plan is read by different stakeholders who want different things, and a plan written for all of them at once serves none.
The deal partner wants the thesis intact, the risk visible, and the exit path preserved. Show them value by tier and the two or three things that could break the return. The operating partner wants speed, adoption, and a playbook that works on the next add-on. Show them ownership, decision rights, and sequence. The CFO wants the synergy numbers to reconcile to the model and to survive a quality-of-earnings review. Show them classification, baselines, and reporting cadence.
I have watched integration plans get rejected not because they were wrong but because they answered the operating partner’s question when the deal partner was in the room. The financial framing has to lead. Guidance from the Harvard Law School Forum on Corporate Governance on board oversight, and the market context tracked by PitchBook, S&P Global Market Intelligence, and BCG, all point the same way: in a tighter deal environment, the integration is where the diligence promise gets tested, and it gets tested in the numbers.
9. What good looks like across a hold period
The integration plan should not evaporate after 100 days. The best ones become the operating rhythm of the platform. Tier 4 is the reason. If your integration builds a repeatable playbook, clean reporting, and a common commercial motion, the second and third add-ons integrate faster and cheaper, and the platform tells a cleaner growth story at exit. That is enabled value compounding, and it is the difference between a portfolio company that is expensive to grow and one that is built to absorb.
I made a broader version of this argument in lessons on future-proofing organizations, and it connects directly to avoiding the go-to-market traps I covered in the PE go-to-market pitfalls piece. Integration done as a one-time event captures this deal’s synergies. Integration done as a capability captures every deal after it.
Conclusion
Merger integration planning is not a project the deal partner approves. It is a set of value decisions the deal partner owns: how deep to integrate, in what order, who has authority, and how realized value gets separated from wishful value. The four-tier plan protects the base first, captures committed synergies second, treats revenue synergies as the forecast they are, and builds the platform for what comes next. Judge any plan by whether every synergy has an owner and a baseline, whether Tier 1 is funded, and whether the reporting is monthly and honestly classified.
If you are integrating an acquisition and want the plan pressure-tested by someone who has run the operating work, not just diagrammed it, that is exactly the conversation I have with sponsors and operating partners. Start an advisory exploration with me here, or see how the DevriX team plugs into portfolio execution through our services. The integration is where the return is made. Plan it like it.
