Most acquirers spend months on the deal and days on the integration plan. By the time someone asks “should we hire a post-merger integration consultant?” the deal has usually already closed, the first stakeholder meeting has been a mess, and the internal team is realising that running an integration is a different discipline from running the business.
This piece covers what a PMI consultant actually does, when to bring one in, how to tell a good one from a bad one, and what the engagement looks like in practice. I’ve led these programmes — what follows is what I’ve learned about what makes the hiring decision work.
What a post-merger integration consultant does
A PMI consultant owns the operational coordination of combining two organisations. Not the strategy — that’s the deal team’s work. Not the commercial decisions — that’s the internal IMO lead’s responsibility. The operating layer in between: the workstreams, the dependencies, the cadence, the artefacts, and the cross-functional friction that accumulates when Finance needs something from IT that depends on a Legal decision that hasn’t been made yet.
In practice, that means:
- Day-1 readiness. Making sure nothing visible breaks when the deal closes — legal entities, customer comms, IT access, payroll, contracts.
- Integration planning. The post-merger integration plan that decides what happens when, who owns it, and how success is measured.
- Workstream coordination. Running the cadence across all functional tracks — finance, legal, IT, HR, brand, operations — so they stay sequenced and dependencies don’t become surprises.
- Issue resolution. The cross-functional problems that fall between workstreams and have no natural owner.
- Governance. Steering committee structure, escalation paths, decision rights — the architecture that makes sure the right people are making decisions at the right altitude.
The common confusion: people assume a PMI consultant replaces the internal integration lead. They don’t. The internal IMO lead — usually a senior executive from the acquiring side — owns the commercial calls and the stakeholder management. The consultant owns the coordination machinery. Trying to run both through one person is the most common shape of integration failure I’ve seen.
When to hire a PMI consultant
The honest answer is before you think you need one. The three windows, in order of value:
During diligence. This is the highest-leverage window. Integration assumptions get baked into the deal model during diligence, and they’re expensive to fix later. A PMI consultant at this stage can pressure-test synergy estimates, flag integration risks the deal team hasn’t considered, and build the Day-1 readiness plan before close.
At signing. The second-best option. You can’t execute much before close for legal and confidentiality reasons, but the critical structural decisions — naming the integration lead, agreeing the deal thesis, building the Day-1 plan — all happen between signing and close. Starting here means Day 1 is controlled rather than improvised.
Post-close. The most common but least efficient. I’ve walked into engagements at three months post-close where the integration was already off track. It’s recoverable, but more expensive: you’re paying once for the gap and again to undo decisions that were made without integration context.
The signal that you’ve waited too long: the first steering committee meeting ends with more questions than decisions, and nobody can name who owns the integration.
How to evaluate a PMI consultant
The market is full of advisors who can build impressive slide decks about integration methodology. What matters is whether they’ve actually run one. Here’s what to look for:
Operating experience, not advisory experience
Ask them to describe a specific integration they led — not advised on, not consulted to, but ran. The answer should include concrete details: how many workstreams, what the governance cadence was, what went wrong and how they handled it. Advisors give you frameworks. Operating PMs give you stories about the Wednesday when the legal entity registration was rejected and the customer migration was scheduled for Friday.
Cross-functional range
Integration work crosses every function. A consultant who’s only done IT integrations will struggle with the brand consolidation. Someone who’s only done brand work won’t anticipate the legal entity complications. Look for breadth — someone who’s touched finance, legal, IT, brand, and operations across at least two or three deals.
The IMO lead vs. operating PM distinction
A good PMI consultant will explain this distinction unprompted. If they claim they’ll “run the whole integration,” be cautious — that usually means they haven’t run one where the politics were real. The best ones understand that they’re there to support the internal leadership, not replace it.
Cultural fit and operating style
Integration is high-pressure, politically charged work. The consultant will be in rooms with executives from both sides who have competing interests and bruised egos. Ask about how they’ve handled resistance, how they run difficult conversations, and how they manage upward without becoming a bottleneck.
Red flags
- No specific deal experience. “I’ve worked in M&A” is not the same as “I led the integration of Company X into Company Y.”
- Methodology-first. If the first thing they show you is a proprietary framework with a trademarked name, be wary. Integration is messy; methodologies are clean. The best practitioners adapt their approach to the deal, not the other way around.
- No reference to Day-1 readiness. If they jump straight to “100-day plan” without discussing what happens on the actual first day, they may not have run a close before.
- Solo-operator positioning. Integration programmes need a team. A consultant who positions themselves as a one-person solution either hasn’t run a complex deal or is planning to staff it with juniors.
Engagement models
PMI consulting engagements typically take one of three shapes:
Full-time embedded (most common)
The consultant works full-time inside the acquiring organisation for the duration of the integration — typically three to twelve months. They attend every steering meeting, run the daily standup, and own the integration artefacts. This is the model I use most often. It’s the most effective because integration problems don’t wait for your next consulting visit.
Part-time / fractional
The consultant works two to three days a week, usually suitable for smaller bolt-on acquisitions where the internal team has capacity but needs the methodology and experience. Less effective for complex deals — the seams between workstreams need someone present every day to catch issues early.
Advisory / oversight
The consultant reviews progress, attends steering meetings, and provides strategic guidance but doesn’t own the day-to-day coordination. This works when the internal team has integration experience and needs a sounding board, not an operator. It doesn’t work when the integration needs someone to build the machinery from scratch.
For what this costs in practice, I’ve broken down the rate ranges and engagement economics separately.
What to agree before the engagement starts
Five things to get right in the scoping conversation:
- Authority. The consultant needs enough authority to convene cross-functional meetings, request information, and escalate blockers without going through three layers of approval. Define this explicitly.
- Reporting line. They should report to the IMO lead or a board-level sponsor, not to a functional head. Integration work crosses functions — if the consultant reports to the CTO, the brand work suffers; if they report to the CMO, the systems work stalls.
- Scope boundaries. What workstreams are in scope? What’s explicitly out? A consultant who tries to own everything will burn out; one who doesn’t know the boundaries will step on internal toes.
- Governance cadence. Weekly steering, daily standups, fortnightly board updates — agree the rhythm before Day 1 so the consultant can build the artefacts to match.
- Exit criteria. What does “done” look like? The answer is usually when the integration programme transitions to business-as-usual operations, but define the specific milestones that signal that transition.
The bottom line
Hiring a post-merger integration consultant is a risk-mitigation decision, not a luxury. The cost of a good one is a rounding error compared to the cost of a stalled integration — lost synergies, churned customers, departed talent, and a deal model that never delivers.
The best time to hire one is before close. The second-best time is now. If you’re weighing the decision, the post-merger integration checklist gives you a sense of the scope, and the 100-day framework shows what the plan looks like in practice.
If you want to talk about a specific deal, reach out. I’ve run these programmes and I’m happy to discuss whether your situation needs a full engagement or just a sanity check.
Frequently asked
What does a post-merger integration consultant do?
They own the operational coordination of turning two organisations into one — workstream planning, dependency mapping, governance cadence, Day-1 readiness, and cross-functional issue resolution. They sit alongside the internal IMO lead, who handles the commercial and stakeholder decisions.
When should we hire a PMI consultant?
Ideally during diligence, at minimum by signing. The cost of waiting until close is paying twice — once for the gap and once to undo decisions made without integration context.
What's the difference between a PMI consultant and a PMI advisor?
An advisor gives strategic guidance and reviews progress. A consultant (or operating PM) owns the day-to-day coordination — the artefacts, the cadence, the cross-functional friction. Most integrations need the latter.
How long does a PMI engagement typically last?
Three to twelve months, depending on deal complexity. Simple bolt-on acquisitions can be shorter. Multi-entity, multi-geography mergers with brand consolidation and system migration typically run nine to twelve months.