How to Hire and Judge a Post-Merger Integration Consultant When You’re Backing the Deal

How to Hire and Judge a Post-Merger Integration Consultant When You're Backing the Deal

Short answer. Hire a post-merger integration consultant before you sign if the thesis depends on combining systems, teams or customer bases, and no later than the week after close if it does not. Pick the type of help by what the integration puts at risk: a firm with an integration management office for a large, multi-workstream merger, one senior integrator for a mid-market add-on, a functional specialist when one workstream carries the risk. Pay for named people and dated outcomes, never for a methodology. Judge the consultant on how they diagnose your deal in the first meeting, before you read any plan they bring.

The rest of this guide is how I make that call when I am on the buy side, written for operating partners, deal partners and portfolio CEOs who have to hire someone for the first 100 days and live with the result for the hold. I have done more than forty acquisitions as an operator and individual buyer, and the integration decisions that cost money were rarely the ones in the integration plan. They were the hiring decisions made before the plan existed.

When to bring in a post-merger integration consultant

The most common question I get is when: before the deal, during it, or after. The answer depends on which part of the value creation plan needs the integration to work.

Moment Bring someone in if What you are buying
Before LOI or during confirmatory diligence The price assumes synergies from merging platforms, CRMs, billing or teams A view on whether the synergy case survives contact with the systems and the org chart, and what it costs to get there
Between signing and close Day 1 has customer, payroll, billing or access risk A Day 1 plan, a short list of decisions that cannot wait, and owners for each
First week after close The add-on is small, the platform team is stretched, and nobody owns the integration full time An operating cadence, a risk register and someone who chases the dependencies weekly
Months 3 to 6 The integration stalled, the synergy number is slipping, or two systems still run in parallel A reset: what is behind, why, and what to cut from scope to land the rest

If you are reading this after close and nothing has been planned, you have not missed the window. You have lost the cheapest part of it. Pre-close work costs a few weeks of one person; a rescue at month five costs a quarter of management attention plus whatever the delay did to customers.

For the deal partner’s side of that timing call, I wrote a separate piece on what a deal partner decides in a PMI and how to judge it.

Four kinds of integration help, and which one your deal needs

“Post-merger integration consultant” covers very different products. Most bad hires come from buying the wrong one.

Type Best for Typical fee model Main risk
Integration management office from a large firm Platform mergers, carve-outs with standalone systems, many workstreams in parallel Fixed fee per phase or a monthly team rate Process overhead that the management team ends up serving
Independent senior integrator Mid-market add-ons where the platform team does the work and needs someone to run the cadence Monthly retainer for a fixed period One person’s bandwidth; needs a clear owner on the company side
Functional specialist One workstream carries the risk: CRM and revenue data, ERP, HR and payroll, security Fixed scope project Optimises their workstream while the others drift
Embedded delivery team The plan is clear and the gap is hands: migrations, integrations, reporting rebuilds Monthly team retainer or fixed project Builds what it is told to build, so the plan has to be right first

A $75M add-on folding into an existing platform rarely needs an integration office. A carve-out that needs its own ERP, payroll and finance stack usually does. Stonehill makes the same point in its breakdown of what a post-merger integration consultant costs, contrasting a $75M add-on with a $500M carve-out.

What it costs to hire a post-merger integration expert

There is no honest single number, because the scope varies by an order of magnitude. What you can control is the fee structure, and the structure tells you a lot about the firm.

  • Fixed fee per phase. Common for Day 1 readiness and the first 100 days. Good when the scope is clear. Ask what happens when a dependency outside their control slips, because that is where change orders come from.
  • Monthly retainer. Common for an independent integrator or an outsourced integration office. Good for add-ons, where the work is steady and the risk is drift. Put an end date and an exit criterion in the contract.
  • Fixed scope plus a performance component. Some firms tie part of the fee to realised synergies. Useful only if you agree up front how a synergy is measured and who reports it. Otherwise you will argue about the number at month nine.

For complex integrations run by the large firms, Stonehill puts fees in the high six figures to seven figures. An independent integrator on a mid-market add-on costs a fraction of that, and should, because the platform team does most of the work. The expensive mistake is paying large-firm fees for an add-on, or independent-integrator fees for a carve-out.

The cost that does not show up on the invoice is management time. Every status meeting, template and steering committee the consultant adds is time your CEO and CFO are not running the business. Ask for the weekly time commitment the engagement expects from your team, in hours, before you sign.

Judge the diagnosis before you judge the plan

Every integration consultant has a plan template. Most of them are fine. What separates a good one is how they read your deal before they show you anything, so the first meeting is the real interview.

Give them the thesis, the rough org charts, the systems list and the synergy case, then listen for three things:

  1. Do they find the dependency you were worried about without being told? On most add-ons it is customer data: two CRMs, two definitions of an active customer, and a revenue synergy that assumes a cross-sell motion neither sales team has run.
  2. Do they put a date and an owner on it? “We will assess the CRM landscape” is a sentence that can survive six months. “Customer master and pipeline definitions agreed by day 30, owned by the platform’s RevOps lead” is a sentence you can check.
  3. Do they tell you what to leave alone? A good integrator cuts scope. Integrating everything is how the first 100 days turn into the first 300.

The scorecard I use to compare post-merger integration consultants

Criterion What good looks like Red flag
Who does the work The people in the pitch are named in the contract with their time allocation Partners pitch, a junior team arrives in week two
Scope language Written in the terms the CFO’s model uses: revenue, margin, cost lines, dates Written in workstreams and activities with no link to the model
Commercial engine Customer, pipeline and pricing risks are a named workstream from day 1 Sales and marketing appear as “change management”
Systems view A sequenced decision on which CRM, ERP and data model survive, and when “Tool rationalisation” with no order or owner
Reporting One page a week: decisions made, decisions blocked, risks with owners A 40-page status pack
Exit A handover date and the internal owner who takes the cadence over No end date, or one that depends on “phase 2”
References Sponsors or CEOs from deals of a similar size you can call Logos only

Score each criterion 1 to 3 across two or three candidates. The total matters less than the gaps: a firm that scores 1 on “who does the work” will lose you more than a strong process wins back.

Questions to ask before you hire a PMI consultant

  1. Which three decisions in our integration have to be made in the first 30 days, and who should own each?
  2. Which synergy in our case do you trust least, and what would you test first?
  3. What will you not integrate in the first 100 days, and why?
  4. How many hours a week will our CEO, CFO and functional leads spend on this?
  5. Who on your side is in the weekly meeting in month three?
  6. How do you track customer churn and pipeline during the integration, and from which system?
  7. What happens to your fee if a dependency on our side slips?
  8. When do you hand the cadence over to us, and what does the handover contain?
  9. Which of your last integrations did not go to plan, and what did you change?
  10. Can I call the operating partner or CEO from that deal?

The ninth question does more work than the rest. Someone who has run real integrations has a specific answer. Someone selling a method gives you a general one.

Common mistakes a PMI consultant should help you avoid

These are the failure patterns that show up across mid-market integrations, and a good consultant names most of them in the first meeting:

  • Customer communication left to the end. Customers hear about the deal from a competitor’s sales rep. Plan the Day 1 message per segment, with an owner for the top accounts.
  • Merging CRMs before agreeing definitions. Two companies rarely define an opportunity, a customer or churn the same way. Migrate before you agree and the board pack is wrong for two quarters. My post-merger integration checklist for revenue, data and customer systems covers that sequence.
  • Counting the same synergy twice. The procurement saving appears in the cost case and again in the margin case. One owner per synergy, one line in the tracker.
  • Losing the people who hold the knowledge. The engineer who knows the billing system and the account manager with the top ten customers are retention decisions for week one.
  • Running two systems in parallel indefinitely. Every month of dual running is double licence cost and double reporting. Put a retirement date on the losing system when you pick the winner.
  • Integration theatre. Steering committees and templates that produce activity reports instead of decisions. Count decisions per week, not meetings.
  • Treating the commercial engine as soft. Pipeline coverage and win rates drop during integrations because sales teams spend time on internal changes. Watch them weekly from day 1. The 100-day go-to-market plan for a newly acquired B2B business is where I start.

Protect the number the CFO reports

The CFO’s model is the contract between the deal team and the integration. If the integration changes how revenue, margin or headcount is counted, the board sees a variance that has nothing to do with performance. Ask the consultant to show, before they start, which reported numbers their work will touch and how they will keep the before and after comparable. A consultant who has not thought about this will produce a better process and a worse board meeting.

This is also why I prefer integrators who can read the commercial and technical sides together. Most integration value in mid-market B2B deals sits in the revenue systems: CRM, billing, pricing, customer success. Those are the places where a process consultant and an engineering team each see half the problem. It is one of the reasons I wrote about value creation consultants versus operators.

What to keep in-house

Some parts of an integration should never be outsourced, whoever you hire:

  • The decision on which leader runs the combined function.
  • The message to the top 20 customers, delivered by someone they already know.
  • The synergy owner for each line in the tracker.
  • The retention conversations with key people.

A consultant can prepare all four. If they own them, the organisation learns that the integration belongs to someone who is leaving.

What good looks like at each review

Review You should be able to see
Day 1 Customers, employees and suppliers told; payroll, access and billing working; the decision list for the first 30 days with owners
Day 30 Leadership of each combined function decided; customer and pipeline definitions agreed; system decisions made with retirement dates
Day 100 Synergy tracker reconciled to the CFO’s model; churn and pipeline compared to the pre-close baseline; first systems retired; handover plan for the cadence
Month 6 The integration office closed or reduced to a monthly check; remaining items owned by line management

If a review shows activity without one of these outcomes, the integration is drifting, whatever the status colour says.

Where I fit

I advise sponsors and portfolio CEOs on the technical and commercial side of integrations: which systems survive, how the revenue data is merged, and what the first 100 days have to deliver for the value creation plan to hold. When the plan needs engineering capacity, that comes from DevriX’s post-merger integration practice. For the broader picture of how I work with sponsors, see value creation advisory.

For the market context, Bain’s Global Private Equity Report tracks how hold periods and exit pressure have changed what sponsors expect from the first year, and McKinsey’s private equity research covers integration practice at the large end.

Mario Peshev

About Mario Peshev

Digital value creation advisor to PE-backed and mid-market companies. Founder of DevriX and Growth Shuttle, 40+ acquisitions as an operator, author of MBA Disrupted.