Somewhere between 70% and 90% of acquisitions fail to deliver the value their deal models promised. That number gets cited often enough in M&A circles that it's started to lose its weight - but spend time inside an actual integration and the reasons behind it stop being abstract. They're specific, repeatable, and almost always avoidable with the right structure in place before close.

The first failure pattern shows up in the synergy line of the deal model itself. A deal gets approved on the strength of a number - cost savings from consolidated vendors, revenue lift from cross-selling, efficiency gains from shared infrastructure. The number is real on paper. What's missing is the operational machinery to turn it into cash. Synergy identification and synergy realization are two different disciplines, and most organizations only build the first one. They know, in principle, where the value should come from. They never assign a named owner to each synergy line, never build a tracking mechanism connecting day-to-day operational decisions to financial outcomes, and never establish a reporting cadence that surfaces slippage while there's still time to fix it. A year and a half later, leadership is still asking where the synergies went - not because they weren't real, but because nobody built the system to capture them.

The second pattern is structural: no one owns integration full-time. Acquirers often assume existing leadership can absorb integration on top of their regular roles - the CFO handles financial integration, the VP of Ops handles operational integration, HR handles people. Each function moves at its own pace, makes its own trade-offs, and reports status differently, if at all. Conflicts between workstreams surface only when they've already cost time: IT discovers mid-migration that finance assumed a different systems timeline; HR finalizes a retention package without knowing operations was about to announce a restructuring that contradicts it. None of this is incompetence. It's the predictable result of asking people with full-time jobs to also run a second, equally demanding job with no shared coordination layer above it.

A third, less obvious pattern: speed gets confused with progress. Leadership, eager to show the deal is working, pushes for visible wins - consolidating logos, announcing org changes, migrating systems - before the underlying decisions are actually settled. Stonehill has seen this play out directly in time-sensitive situations. In one engagement, a private equity-backed client had acquired the assets of a flooring manufacturer following a bankruptcy triggered by legal and operational challenges, and speed genuinely mattered - the business needed to stabilize, integrate, and become operational quickly to preserve customer relationships, retain key talent, and prevent further value erosion. The difference between that kind of urgency working and backfiring is sequencing: knowing which decisions have to be made fast and which ones only look like they do. Rushing the wrong ones - announcing an org structure before leadership roles are actually settled, migrating systems before data integrity is verified - creates a second, more expensive integration to clean up the first one.

A fourth pattern hides in plain sight: growth outpaces infrastructure. Companies that acquire repeatedly, rather than once, often hit a different kind of failure - not a single botched integration, but an accumulation of unaddressed technical and operational debt across several. A national packaging company that had grown rapidly through a string of acquisitions eventually ran into exactly this: rising infrastructure limitations and increasing cybersecurity risk that hadn't been a priority during any single deal, but became a serious exposure across all of them combined. The fix wasn't another acquisition playbook - it was finally building the IT program management structure that should have existed since the second deal, not the sixth.

The fifth pattern is cultural, and it's the one most deal models don't even attempt to quantify. Two organizations develop different norms for how decisions get made, how fast people expect answers, and what "good work" looks like - none of which shows up in a balance sheet, all of which shows up in attrition, productivity, and customer experience within the first year. Leadership from the acquiring company tends to assume its own culture is simply the correct one, and leadership from the acquired company is often too uncertain about their own standing to push back, even when they should. Left unmanaged, this doesn't resolve on its own. It calcifies into two cultures operating uneasily under one name.

What separates the acquisitions that recover their intended value from the ones that don't isn't luck, and it isn't a better deal thesis. It's whether someone built the infrastructure - ownership, tracking, sequencing, and a dedicated team with the authority to coordinate across functions - before the gap between the model and reality had time to widen.

That infrastructure is what Stonehill builds. We lead the Integration Management Office, design the operating model, track synergies against the original deal thesis, and manage the cultural and organizational work that decides whether the people inside the deal actually stay and perform. Talk to our team about your upcoming integration, or see our step-by-step integration guide for how the work actually gets structured.