On May 4, Oliver Wyman, the management consulting arm of Marsh & McLennan, announced it was acquiring CR3 Partners, a firm that specializes in turnaround, transition, and distress. Sixty-two professionals. The stated rationale, in Oliver Wyman's own words: CR3's "hands-on turnaround expertise complements our strategic capabilities." The implicit admission: one of the world's best-resourced strategy firms has clients who cannot execute, and it needed to buy the people who fix that.
The acquisition is a useful market signal. Add-on acquisitions now account for approximately 73 percent of all US private equity buyout activity, up from under 50 percent a decade ago. PE platforms are closing more deals faster, which means integration teams are stretched thinner, and the post-acquisition execution gap (the distance between deal close and synergies realized) has become large enough that enterprise consulting firms are reorganizing around it. If Oliver Wyman is buying turnaround operators to serve its enterprise clients, the same gap exists at the LMM scale, just without the budget to hire Oliver Wyman to fill it.
For the $10M to $100M operator that just got acquired into a buy-and-build platform, the execution gap is not a consulting problem. It is an operational one. More than 70 percent of post-acquisition integrations fail to capture planned synergies. The failure is predictable, structural, and happens at the same three points in almost every deal. This post is where those points are, what they cost, and what to do about them before the seller walks out at close.
The buy-and-build math.
The add-on acquisition model is straightforward as a thesis. Acquire a platform at 5 to 6x EBITDA. Add two to four smaller companies at 4 to 5x. Integrate operations, eliminate redundancies, grow revenue on a shared cost base. Exit at 8 to 10x on a larger EBITDA. The multiple arbitrage creates value independent of organic growth.
The execution reality is harder. Add-ons are now 73 percent of US PE buyouts. That concentration means the average PE deal today is not a single standalone acquisition with a clean operating team. It is the third or fourth company being bolted onto a platform that is already running integration work streams on two prior adds. The bandwidth required to execute that integration well is higher than most deals budget for.
More than 70 percent of post-merger integrations fail to capture planned synergies. The synergies were real, modeled correctly, and genuinely available. They were not captured because execution failed. Execution failure in an add-on acquisition is not random. It follows three predictable patterns.
Where integration breaks.
Management bandwidth collapse.
In a buy-and-build platform, the platform CEO runs the acquired company, manages the integration work stream for the new add-on, maintains lender and sponsor relationships, and continues diligence on the next add-on simultaneously. This is four distinct jobs. Most platforms staff for one.
Every significant decision routes through one person. Integration tasks that require CEO authority (org structure changes, supplier contract decisions, system consolidation choices) sit in a queue. The queue grows by several items per week. What was modeled as a 90-day integration becomes a 180-day integration because the decision bandwidth does not exist.
The fix is not a second CEO. It is separating the work. Someone has to own integration execution independently of the platform CEO. That is the specific role a fractional COO fills in an add-on context: the CEO runs the business, the fractional COO owns the integration.
Systems and data fragmentation.
A platform running three acquired companies typically operates three or four accounting systems, two or three CRM instances, and multiple payroll systems simultaneously. The data in each is not compatible. Consolidating it requires manual extraction and reconciliation every time reporting is needed.
The practical impact: board reporting runs 30 to 45 days behind. By the time the sponsor sees the numbers, the quarter that produced them is nearly over. Exceptions that should have been caught in week four are not visible until week ten.
This is not a technology problem. Buying a new ERP does not solve it; it creates a new integration project on top of the existing one. The discipline required is a single reporting layer above whatever systems the acquired companies run: a standardized weekly operating report, in the same format, from every entity. Not a system migration. A reporting template and the operating discipline to fill it every week.
Synergy timing mismatch.
Synergies modeled at close typically realize 12 to 24 months after close. Integration planning delays add 6 to 12 months on top of that. On a three-year hold period, a 12-month synergy delay compresses return profiles materially.
The timing mismatch usually traces to one root cause: the synergy model was built on assumptions about the acquired company's operations that turned out to be wrong. Not dishonestly wrong. Wrong because the diligence focused on financials and not operations. The income statement looked correct. The operating system behind it was not documented and not examined.
The gap in operational due diligence.
Most LMM acquisitions receive thorough financial due diligence and thin operational due diligence. Financial diligence answers the right question for the deal decision: is this a good business to acquire? It answers the wrong question for integration planning: do we understand how this business actually runs?
At most LMM targets, the operating system is in the seller's head. The key processes are tribal knowledge. The supplier relationships are personal relationships held by the owner-operator. The institutional knowledge that produces the acquired business's historical margins is not written down anywhere.
When the seller walks out at close, that knowledge walks out too. The platform can produce the income statement. It cannot produce the business.
| Operating element | Documented at close | Undocumented at close |
|---|---|---|
| Core delivery process | SOP exists; can be handed off | 4 to 8 weeks to map and document post-close |
| Supplier relationships | Contacts, terms, and lead times in writing | Dependent on seller introductions; renegotiation risk |
| Customer service standards | Defined and measurable | Varies by employee; attrition creates inconsistency |
| Reporting cadence | Weekly and monthly cycle documented | Controller builds from scratch; 30 to 60-day delay |
| Org chart and role clarity | Written and current | Reconstructed through observation over 60 to 90 days |
Every undocumented element adds weeks or months to the integration timeline. In a deal where the synergy model assumed a 90-day integration, three undocumented elements push the timeline to 7 or 8 months. That is the timing mismatch, and the operational due diligence gap is where it starts.
The pre-close window. The most valuable operational work in any acquisition happens before the deal closes. If the seller has not documented their processes, that documentation must happen between LOI and close, when the seller still has incentive to cooperate. After close, the incentive is gone and the integration timeline is already running.
What the first 90 days require.
If you are past close without pre-close operational work, the sequence matters. The natural instinct is to integrate systems first because systems produce data. That instinct is usually wrong. Systems integration is a 6 to 18-month project. You need operational visibility in week two.
The correct sequence:
- Install the weekly operating report before anything else. One template, same format for every entity in the platform. Revenue, margins, headcount, open exceptions, cash position. Not a system project; a spreadsheet. Fill it every Monday. This single action reduces board-reporting lag from 30 to 45 days to 7 to 10 days.
- Map the acquired company's primary process before you change it. Walk the process end to end. Write it down. Mark where it breaks. Do not reorganize what you do not understand. Most integration failures trace to a process that looked inefficient on the income statement but was load-bearing in a way not visible from the financials.
- Identify the two or three people who hold institutional knowledge and retain them explicitly. Not a general retention program. Specific individuals, specific roles, specific conversations about what they know and what leaves with them. Assign each a trained backup within 60 days.
- Separate CEO bandwidth from integration bandwidth in week one. Assign one person, internal or fractional, to own the integration work stream. This person escalates only what requires CEO authority. Without this separation, the CEO's queue grows until integration stalls.
- Build the supplier exposure map before consolidating procurement. Know which suppliers are shared across entities, which are single-sourced, and which carry contract terms that prohibit assignment at change of control. Consolidating procurement without this map creates contract violations that cost more than the synergy you were trying to capture.
The Axis Method is built for this specific phase. The Diagnose and Stabilize stages in a post-acquisition engagement produce the operating report format, the process map, and the supplier exposure analysis in the first four to six weeks. On what that looks like in a standard engagement: What We Cut in the First 90 Days. On the operational excellence baseline required before synergies can compound: the acquired company needs to be running predictably before integration overhead lands on top of it.
Oliver Wyman bought operators because its enterprise clients need execution, not just advice. At the LMM scale, the need is identical and the economics are different. A fractional COO engagement at $3,000 to $7,500 per month covers the integration execution capacity that a platform CEO cannot provide for themselves. For a $15M acquisition where a 6-month integration delay costs $400,000 to $600,000 in unrealized synergies, the return calculation is not complicated. If you are inside a buy-and-build platform or approaching a close, book a scoping call. The first conversation is about where you are in the integration timeline and what the highest-cost gap is.
Keep reading.
- Manufacturing Input Costs at a Four-Year High: Three Numbers That Tell You How Exposed You Are, The ISM Prices Index for April 2026 registered 84.6 percent, the highest reading since Apr…
- Replacing the SaaS Stack with $75/mo of Cloudflare, Most small operators run on $500–$3,000/month of SaaS that compounds with every new hire. …
- What We Cut in the First 90 Days, A typical $10M–$50M operator carries 30–40% operational waste. The first 90 days of an Axi…
- How to Read an Operational Waste Audit, Three numbers come out of the Diagnose phase of every Operations Architect (fractional COO…
- How to Actually Move a Team from Storming to Performing, Most LMM teams stop at Norming and the leadership thinks that is success. It is not. This …
- Lean Six Sigma for the Lower-Middle Market, Without the BS, DMAIC, SIPOC, Black Belts, control charts, kaizen events. At enterprise scale these earn t…
Talk through it.
If any of this is applicable to where you are, book a scoping call. No pitch deck.