How Much Should You Budget for Post-Merger Integration Support?

By the time a deal closes, most of the budget conversation has already happened — diligence fees, legal fees, financing costs. Integration budget is often an afterthought, sketched in late and under-resourced relative to how much it actually determines whether the deal delivers on its thesis.

That's a mistake. Integration is where deal value is either captured or quietly lost. Here's a practical way to think about what to budget, and why.

Start With Percentage-of-Deal-Value Benchmarks

A common industry rule of thumb is budgeting somewhere between 1% and 3% of total deal value for integration support, inclusive of internal team time, external consulting fees, and one-time integration costs (systems migration, rebranding, facility consolidation, etc.). Where a specific deal lands in that range depends heavily on complexity:

• Simple tuck-ins (target absorbed into existing platform, minimal standalone infrastructure): closer to the lower end

• Complex carve-outs or mergers of equals (standalone systems, TSA dependencies, significant org overlap): closer to the upper end, sometimes exceeding it

Break the Budget Into Its Real Components

Rather than treating "PMI budget" as one line item, it helps to separate it into distinct buckets:

1. External consulting / advisory fees Covers the IMO setup, workstream planning, synergy tracking, change management, and communications support. This is typically the most controllable and negotiable line, and where boutique vs. large-firm pricing differences matter most.

2. Internal team time Often underestimated. Integration pulls real hours from finance, HR, IT, and operations leaders who still have a day job to do. Budgeting backfill or temporary support for stretched internal teams is frequently the difference between an integration that stays on schedule and one that quietly stalls.

3. One-time integration costs Systems consolidation or migration, rebranding, facility or lease consolidation, severance and retention bonuses, and TSA exit costs. These are deal-specific but should be modeled early, ideally during diligence, not discovered mid-integration.

4. Contingency Integrations rarely go exactly to plan. A 10–15% contingency on top of the modeled budget is a reasonable buffer for the unexpected — a key system dependency that surfaces late, a retention risk that requires an off-cycle bonus, a TSA extension.

What Changes the Number Most

• Timeline compression. A board-mandated fast close (60–90 day Day One readiness) costs more per month than a measured 6–12 month integration, because it requires more concentrated senior resourcing up front.

• Number of active workstreams. Full-scope integrations spanning org design, systems, financial reporting, customer retention, and culture cost meaningfully more than a narrowly scoped engagement.

• Whether it's a repeatable platform. Serial acquirers running multiple integrations off a repeatable playbook typically see per-deal costs decrease over time, since the IMO structure, templates, and lessons learned carry forward.

A Word on Underinvesting

The instinct to keep integration budget lean is understandable — it's a cost center on top of an already expensive transaction. But underfunding integration is one of the more common ways deals fail to hit their business case. Synergies that were modeled in diligence but never actively tracked tend to quietly evaporate. Culture and retention issues that go unmanaged in the first 100 days often surface as attrition six months later, well after the window to address them cheaply has closed.

Budgeting adequately for integration isn't overhead — it's protecting the return on the deal itself.

How Stonehill Helps Clients Budget Realistically

Stonehill works with PE-backed and founder-led middle-market companies ($50M–$1B revenue) to scope integration budgets that match the actual complexity of the deal — not a templated retainer or an inflated Big Four rate card. That typically includes:

• Early-stage budget modeling during or shortly after diligence, so integration costs aren't a surprise post-close

• Scoped, milestone-based fee structures tied to Day One readiness, 100-day plans, and synergy capture

• Senior operators leading the engagement directly, which tends to compress both cost and timeline compared to junior-staffed alternatives

If you're heading into a close and haven't yet scoped what integration will actually cost, that conversation is worth having now — while there's still time to build it into the deal model.

Planning integration budget for an upcoming deal? Stonehill can help you scope a realistic number before you close — not after.