By Mario Peshev, DevriX
Most integration consulting engagements fail the only test that matters: they cannot tell you, in dollars, whether the deal you paid for is on track. You get a workstream tracker with 340 tasks, a color-coded RAG status, and a steering committee deck that says “Day 100 milestones 82% complete.” None of that answers the question a deal partner is actually holding, which is whether the synergies underwritten in the investment committee memo are going to show up in the P&L before the hold period runs out.
I have sat on both sides of this. I run DevriX, which does hands-on commercial and technical work inside portfolio companies, and I have watched integration budgets get spent on choreography while the value case quietly slipped. This piece is about what you should actually be buying when you buy M&A integration consulting, and how to judge whether you are getting it.
The decision you are actually making
When a PE deal partner or operating partner brings in integration help, the framing is usually “we need someone to run the integration.” That framing is already wrong. Running integration is table stakes. The real decision is narrower and harder: which pieces of the value creation thesis require an external hand, and what is the smallest amount of that hand you can buy while still protecting the deal.
The thesis is not “combine two companies.” The thesis is a specific set of numbers your firm underwrote. Cross-sell revenue at a stated attach rate. Procurement savings at a stated run-rate. A consolidated tech stack that removes duplicate licensing and headcount. A shorter path to the next add-on. Each of those is a line you can measure, and integration consulting is worth its fee only to the extent it moves those lines.
Bain’s annual private equity report has tracked how much of returns now depend on operational improvement rather than multiple expansion or leverage, and that shift is the whole reason integration quality matters more than it did a decade ago. You can read the running series in the Bain Global Private Equity Report. When entry multiples are high and cheap debt is gone, the deal has to earn its return from the operating plan. A botched integration does not just cost money. It removes the mechanism by which the return was supposed to happen.
Three questions that separate a real engagement from theater
Before you sign anything, put the potential provider against three questions. Their answers tell you almost everything.
Can they name the value case in numbers?
A strong integration partner reads your IC memo, or reconstructs its logic, and can state the synergy targets back to you as a small set of quantified lines with owners and dates. A weak one talks about “aligning cultures” and “establishing governance.” Governance matters, but it is a means. If the first conversation is about workstreams and not about the run-rate EBITDA the deal was priced on, you are buying process for its own sake.
Do they attach to the P&L or to a slide?
This is the line I care about most. There is a real difference between advice and accountability, and I have written about it at length in Value Creation Consultants vs. Operators. Ask a simple question: at the end of this engagement, what number do you own? A firm that answers “the plan was delivered” owns activity. A firm that answers “the $4.2M cross-sell run-rate” owns an outcome. The second answer is rare, and it is the one worth paying for.
Will they still be there on Day 200?
Integration value does not land on Day 100. Day 100 is when the systems are cut over and the org chart is signed. The synergy realization happens over the following twelve to eighteen months, and that is exactly when most consulting engagements have already invoiced and left. The embedded model, which I argue for in PE Value Creation Requires Embedded Partners, Not Advisory Firms, exists precisely because the advisory model checks out before the value shows up.
What integration consulting is actually for
Strip away the deck and there are only a handful of jobs an integration engagement genuinely does. It is worth being explicit about them, because the fee should map to the job.
- Sequencing the value case. Deciding what to integrate now, what to leave alone, and what to actively separate. Not everything should be combined, and integrating the wrong thing early destroys more value than it captures.
- Protecting revenue through the transition. The single most expensive integration failure is customer and rep churn during the disruption. Commercial continuity is where the money leaks first.
- Capturing the cost synergies you underwrote. Duplicate systems, overlapping vendors, redundant roles. These are the easiest to model and the ones most often left half-done because nobody owned the last mile.
- Standing up management visibility. A combined reporting spine so the CFO and the board can see the combined business in one number set, on time, every month.
- Setting up the platform for the next add-on. If the thesis is a buy-and-build, the first integration is a template. Get it repeatable or you pay the full price every time.
Notice that none of these is “manage the project.” Project management is the container. The value is in the choices about sequence and the discipline about the last mile.
Where the money actually leaks
The failure modes are predictable, which is a gift, because predictable failures can be underwritten against.
Commercial disruption nobody priced
When two go-to-market motions get combined, accounts get reassigned, comp plans change, and the best reps start taking recruiter calls. Revenue that was in the base case walks out the door, and it does not show up in the integration tracker because the tracker measures tasks, not pipeline. This is the leak I watch first, and it is the reason I lean on a proper diagnostic early. The approach I use is laid out in the B2B Portfolio Revenue Leakage Diagnostic. If the integration plan does not have a named owner for commercial continuity, revenue leakage is already priced into your future, you just have not seen the invoice yet.
Synergies that were never real
Some of the synergies in the memo were optimistic to begin with. A good integration partner will tell you which ones, early, rather than spending eighteen months chasing a cross-sell number that the customer base was never going to support. This is where honest diligence earups its keep. The patterns that predict trouble are the same ones I flag in Commercial Due Diligence Red Flags in B2B Businesses: concentrated revenue, soft retention dressed up as growth, and pipeline that lives in one person’s head.
Add-backs that do not survive contact with the buyer’s QoE
Integration cost synergies frequently get booked as adjusted EBITDA before they are realized, and that inflates the number the next buyer or lender will scrutinize. The discipline around what counts and what does not is something I covered in Adjusted EBITDA and the Art of Add-Backs. If you let forecast synergies read as realized EBITDA, you are borrowing credibility from your own exit.
Judging the provider on realized versus forecast value
Here is a discipline I apply to every value claim, whether it comes from my own team or an outside firm. Classify every dollar of impact into one of five buckets: realized, run-rate, forecast, enabled, or risk avoided. Realized has hit the P&L. Run-rate is contracted and recurring but not yet cumulative. Forecast is modeled. Enabled means the capability now exists but the value depends on someone acting on it. Risk avoided is a loss that did not happen.
A provider who blends these into one big “value created” figure is either sloppy or selling. When you force the distinction, the conversation gets honest fast. Most integration synergies at Day 100 are run-rate or enabled at best. That is fine, as long as nobody presents them as realized to the board. I would rather see a provider claim $1.8M realized and $3M run-rate than a single vague $6M “impact” number that collapses the moment your CFO opens the cash flow.
This is also the right frame for the CFO in the room. A CFO cares about forecast reliability, covenant headroom, and cash conversion. An integration partner who speaks in that language, rather than in milestones, is speaking to the person who will actually judge the outcome. The KPIs worth putting in front of that audience are the ones I lay out in Portfolio Company Operating Reviews: The Commercial KPIs That Matter.
The technical integration that finance forgets about
Deal partners tend to treat the systems integration as an IT chore to delegate. That is a mistake, because the tech stack is where a large share of both the cost synergy and the diligence risk lives.
The systems consolidation is a synergy line, not an expense
Two CRMs, two ERPs, three billing systems, overlapping SaaS subscriptions across both entities. Consolidating these is where real recurring savings sit, and it is also where the combined reporting spine gets built. But it is slow, it touches every department, and it is the workstream most often left at 70% done because the last 30% is politically painful. The CTO’s job here is to translate the technical plan into EBITDA impact and diligence risk, because that is the language the deal partner and the CFO respond to.
Integration debt becomes exit friction
If the combined business exits on a patchwork of half-migrated systems and manual reconciliation, the next buyer’s technical diligence will find it, and it will show up as either a price chip or a longer close. The point of doing the integration well is not tidiness. It is that a clean, well-documented combined operation exits faster and at a better multiple. Preqin and PitchBook both track how hold periods have stretched, and you can follow that data at Preqin and PitchBook. In a market where holds are longer, integration debt compounds. It does not stay flat.
What a repeatable playbook looks like in a buy-and-build
If your thesis is platform-plus-add-ons, the first integration is not just an integration. It is a template you will run four or six more times. Judge your provider on whether they build that template or just get through the first deal.
The operating partner in a buy-and-build wants speed, adoption, and a repeatable playbook, not a bespoke heroics effort each time. The first 100 days set the pattern, and I have written out that sequence in The 100-Day Go-to-Market Plan for a Newly Acquired B2B Business. The commercial side of that playbook, especially win rate and customer acquisition cost, is often where a fractional operator earns the fee, a point I make in Fractional CROs in PE Fix Win Rate and CAC, Not Revenue Theory.
A repeatable playbook has a few visible signs: a standard Day 1 checklist, a fixed reporting template that every acquired entity adopts, a defined owner for commercial continuity, and a synergy tracker that classifies value into the five buckets I described. The Harvard Law School Forum on Corporate Governance publishes useful practitioner writing on M&A execution and governance, which you can browse at the HLS Forum, and Harvard Business Review’s M&A collection covers the recurring reasons integrations underdeliver.
How to structure the engagement so incentives point at value
Once you have decided you need help, the shape of the contract determines whether you get outcomes or activity. A few structural choices matter more than the day rate.
- Tie a meaningful portion of fees to realized synergy, not to milestone completion. If the provider gets paid the same whether or not the value lands, they will optimize for the deliverable, not the dollar.
- Name the owner for every synergy line inside the portfolio company, not inside the consultancy. Consultants leave. The value has to be owned by someone who stays.
- Insist on the five-bucket classification in every report. This one discipline prevents the most common self-deception, which is reading forecast as realized.
- Extend the accountability window past Day 100. Structure a check at Day 200 and Day 365 against the same numbers, or accept that you will never know whether the engagement worked.
The broader GTM pitfalls that undermine value creation, including the tendency to fund activity over outcome, are ones I collected in Private Equity GTM: Avoid Value Creation Pitfalls. And if you are thinking about how the combined organization stays durable past the integration itself, the longer view is in Future-Proofing Organizations.
The uncomfortable conclusion
Most M&A integration consulting is priced and judged on the wrong thing. It is sold as project management and bought as reassurance, and both parties agree to measure completion instead of value because completion is easy to see and value is not. The result is a well-run process that ends exactly when the money was supposed to start showing up, and a deal partner who cannot say whether the thesis is intact.
The fix is not more sophisticated. It is more honest. Name the value case in dollars. Buy accountability for those dollars, not activity around them. Classify every claimed impact so forecast never masquerades as realized. Keep someone on the number past Day 100, because that is when the synergies actually land or die. Judge the provider on whether they attach to your P&L or to a slide.
Integration done this way is not a cost center you tolerate. It is the mechanism that converts the operating thesis into the return you underwrote, and in a market where multiple expansion and cheap leverage are no longer doing the work, that mechanism is most of the deal.
Where to take this next
If you are staring at an integration where the workstream tracker is green but you cannot say whether the synergies are real, that gap is exactly what I help portfolio companies close. I work embedded, on the number, past Day 100. If you want a direct conversation about a specific deal or portfolio situation, start with a business advisory session. For teams that need hands-on commercial and technical execution across the integration itself, the DevriX services hub lays out how we do the work.
