The deal closed. The synergy case that justified the multiple now lives in a spreadsheet that only three people have read closely, and one of them has already rolled off to the next transaction. Someone has to convert that spreadsheet into sequenced work, owners, and dates, and hold two management teams accountable to it while both companies keep selling. That is the job an integration management office consultant is supposed to do, and it is also the job that most portfolio companies quietly fail at in the first ninety days.

This guide is for the operating partner or portfolio company executive who already knows what a PMI program is and has the budget to run one properly. The question is not whether integration matters. The question is what to actually decide when you engage an integration management office consultant, how to scope the engagement so it produces enterprise value instead of status decks, and how to tell within four weeks whether the person you hired is worth what you are paying.

Why the integration office is where value leaks fastest

The commercial logic of a buy-and-build or platform acquisition rests on synergies that are booked in a model and realized in the field. Bain’s annual Global Private Equity Report has tracked, year over year, how integration execution separates the deals that hit their return case from the ones that quietly underperform. The gap is rarely the thesis. The gap is the eighteen months after close, when the value creation plan meets the reality of two ERP systems, two comp plans, and two sales teams who do not trust each other’s pipeline data.

Left unmanaged, three things happen in sequence. Revenue dips because sales attention shifts inward. Cost synergies slip because nobody owns the decommissioning dates. And management visibility degrades because the two companies report on different definitions of the same metric. The integration management office exists to prevent all three. When it is run by someone competent, it is the single highest-leverage spend in the first year of ownership. When it is run by someone who confuses coordination with control, it becomes an expensive layer of meetings.

McKinsey’s private capital research has made a consistent point across cycles: the discipline of integration, not the size of the synergy target, is what predicts whether the number gets realized. That is the frame every buyer should hold when they scope this engagement. You are not buying a project manager. You are buying the mechanism that converts a forecast into measurable enterprise-value improvement.

Decide what the office is actually for before you hire anyone

The most common scoping mistake is hiring an integration management office consultant to “run the integration” without deciding what integration means for this specific deal. The answer differs sharply by deal type, and it changes what you are buying.

Platform vs. bolt-on

A platform acquisition where you intend to buy five more companies over three years needs a repeatable integration playbook, not a one-off plan. The consultant’s deliverable is a machine: standard workstreams, standard Day 1 checklists, a standard reporting cadence, and a decision-rights matrix that survives the next four deals. A single bolt-on into an existing platform needs the opposite: fast absorption into systems that already exist, minimal net-new process, and a hard finish line.

Full integration vs. hold-separate

If the thesis is to run the target as a standalone until exit, you do not need a full IMO. You need a lighter governance layer and a small set of shared-service consolidations. Paying for a full integration office when the plan is hold-separate is a classic way to burn six figures on org charts nobody will use.

Cost-led vs. revenue-led

A cost-synergy deal (consolidate back office, close facilities, rationalize vendors) is a different engagement from a revenue-synergy deal (cross-sell, combined go-to-market, shared pipeline). The revenue case is harder to manage and easier to overclaim, which is exactly why the RevOps side of integration deserves scrutiny. Before funding any cross-sell synergy line, it is worth reading how to pressure-test those assumptions in RevOps due diligence before you fund the number. Revenue synergies that were assumed in the model and never tested against real pipeline data are the ones that quietly disappear.

Decide these three axes first. The scope of the consultant, the seniority you need, and the price you should pay all follow from that decision, not the other way around.

What an integration management office consultant should own, and what stays with management

An integration office fails when it tries to make operating decisions that belong to the business, and it also fails when it makes no decisions at all. The line has to be drawn explicitly, in writing, before Day 1.

The consultant owns the mechanism: the master integration plan, the workstream structure, the cadence, the risk register, the interdependency map, and the escalation path. They own the truth about actual versus plan. They do not own whether to keep Product A or Product B, whether to retain a regional sales leader, or how to price the combined offering. Those are management and sponsor decisions. The IMO’s job is to force those decisions onto a timeline and to surface the cost of not making them.

Harvard Business Review’s body of work on mergers and acquisitions returns to this repeatedly: the integration that succeeds has clear decision rights and an owner for every dependency. The one that fails has a steering committee that reviews slides and defers the hard calls. When you interview a candidate, ask them to describe a decision they forced a management team to make against its preference. If they cannot, they have been a coordinator, not an integration leader.

The decision-rights test

Before the engagement starts, agree in a one-page RACI who decides, who is consulted, and who merely executes for the ten decisions that will most affect the synergy case. If that page cannot be produced in the first two weeks, the office is not functioning, no matter how good the status deck looks.

Sequence the first hundred days as workstreams with dollar owners

The output of a competent integration management office consultant in the opening phase is not a plan. It is a plan where every workstream has a named owner, a synergy dollar figure attached, a baseline, and a date. The distinction matters because a plan without dollar accountability is a to-do list, and a to-do list does not defend the return case in a board meeting.

A workable sequence for the first phase looks like this:

• Weeks 1-2: Baseline the actuals. Confirm the synergy case line by line against reality. Identify which synergies are realized, which are run-rate, which are forecast, and which were never more than optimistic. This is where a lot of integration budgets quietly get right-sized.
• Weeks 2-4: Stand up the workstreams (finance, systems, commercial, people, operations) with owners and decision rights. Build the interdependency map so the sequencing is real, not aspirational.
• Weeks 4-8: Execute Day 1 and early-win items. Lock the reporting cadence so the sponsor sees actual versus plan every two weeks, not a narrative.
• Weeks 8-12: Reforecast against realized progress and hand the board a defensible view of where synergy capture actually stands.

This is the same discipline that governs a well-run first 100 days program, and the integration office is the vehicle that carries it. The tighter these two are coupled, the less likely the synergy case drifts into anecdote by the first board meeting.

The systems and data workstream is where integrations actually stall

Every integration plan looks clean until it hits the systems layer. Two CRMs, two ERPs, overlapping data models, and duplicate customer records are where timelines slip and where the promised management visibility fails to materialize. An integration management office consultant who cannot speak credibly about the systems and data workstream is going to hand you a plan that breaks on contact with the migration.

The data question is not incidental to the integration. It is the integration for any deal where the synergy case depends on a combined view of customers, pipeline, or cost. Getting this wrong shows up as two sales teams reporting pipeline in incompatible definitions, or a finance function that cannot produce a consolidated forecast for months. If the systems consolidation is significant, the work of scoping it deserves its own treatment, and the trade-offs are laid out well in this guide to data platform implementation in a portfolio company and in the companion piece on data strategy consulting for portfolio companies.

This is also where diligence should have already done half the work. A serious technology due diligence effort before close gives the integration office a head start: it names the system risks, the integration dependencies, and the migration cost that the IMO now has to sequence. When diligence skipped the technical layer, the integration consultant inherits the discovery work, and the timeline extends accordingly. Ask, in the interview, how the candidate uses the diligence output. If they have never read a tech diligence report, they will rediscover its findings on your clock.

How to judge the consultant in the first four weeks

A buyer with budget does not need to wait for the engagement to conclude to know whether it is working. The signals are visible early, and they are concrete.

The evidence signal

By week two, the consultant should have replaced assertions with baselines. “We are on track” is not a status. “Synergy line 4 was modeled at run-rate by Q2, the baseline shows we start collecting in Q3, here is the gap and the owner” is a status. If the reporting is narrative rather than evidence, the office is not doing its job.

The decision-forcing signal

A good integration lead makes management uncomfortable in the first month by forcing decisions the two teams have been avoiding. If everyone is comfortable at week four, the hard calls are being deferred, and they will resurface as slipped dates in month five.

The reporting cadence signal

The sponsor should be receiving a consistent actual-versus-plan view on a fixed cadence, with the same metric definitions every time. A consultant who changes the format or the metrics each cycle is managing the perception, not the integration.

The RevOps competence signal

For any revenue-led deal, the integration office has to be literate in how the combined go-to-market actually works: routing, ownership, pipeline definitions, comp. This is where a lot of otherwise strong integration leads are weak. It is worth judging that capability against the standard set out in a RevOps maturity assessment that survives a board meeting. If the combined revenue engine is left to sort itself out, the cross-sell synergy is the first line to disappear from the reforecast.

Buy-side vs. build-side when engaging a firm rather than an individual

Some buyers hire an individual integration consultant. Others engage a firm that provides the office as a service. Both work, and the choice depends on the volume of integration you expect and the internal capacity you already have.

A single senior operator is right when you have one integration, strong internal management, and a defined finish line. A firm is right when you are running a platform with multiple bolt-ons, when you need the office to persist across deals, or when the integration includes a real systems and data build that a single person cannot execute alone. The “as a service” model is familiar to operating partners from the RevOps side, and the same buying logic applies. The frameworks in how to buy, scope, and judge RevOps as a service and in a data team as a service in private equity transfer almost directly: define the outcome, cap the scope, and tie the fee to milestones you can verify.

Whichever model you choose, the contract should be milestone-based against integration outcomes, not a monthly retainer for presence. A retainer pays for attendance. A milestone structure pays for the plan being built, the workstreams being stood up, Day 1 being executed, and the reforecast being delivered. The difference in incentive is the difference in what you get.

What this should cost, and how to size it

A focused integration management office engagement for a single mid-market deal typically sits in the range of a defined PMI sprint rather than an open-ended program. The right scope for most portfolio companies is a bounded effort, in the region of $25K to $75K for the setup-and-sequence phase, that produces the master plan, the workstream structure, the decision-rights matrix, and the reporting cadence, and then hands ongoing execution to a named internal owner or a milestone-based continuation.

The temptation is to buy a long, open engagement because integration feels open-ended. Resist it. The office should have a defined job, a defined output, and a defined handoff. PitchBook deal and portfolio data, alongside S&P Global Market Intelligence, consistently shows that hold periods and integration timelines vary widely, which is precisely why the engagement should be scoped to a phase you can judge rather than a duration you have to trust. Price the phase, judge the output, then decide whether to extend.

Where cost discipline matters most is in avoiding two failure modes at once: underspending on the office so the synergy case is never sequenced, and overspending on a permanent integration function that outlives its usefulness. BCG’s private equity value creation research and Preqin data both point in the same direction, that the return comes from disciplined execution of a scoped plan, not from the volume of consulting hours applied to it.

The RevOps layer that most integration offices underweight

For revenue-led deals, the part of integration most often treated as a footnote is the combined go-to-market. Two sales teams, two pipeline definitions, two comp plans, and two sets of customer data are not a coordination problem. They are a revenue-realization problem, and they belong inside the integration office with a named owner and a synergy dollar figure.

The pattern to watch: the cost synergies get owned and tracked because they are easy to measure, while the revenue synergies get “assigned to sales” and never sequenced. Six months later the cross-sell line is missing from the reforecast and nobody can say precisely when it evaporated. Building the RevOps workstream into the integration plan from week one is the fix, and the buying logic for that capability is set out in detail in RevOps as a service, what to buy and how to judge it and in how to choose a RevOps agency for portfolio companies. Even simpler competitive-visibility signals matter here, since a combined company inherits a combined reputation footprint, as the analysis of Google versus Yelp competitor rating trends shows.

A checklist to run before you sign

Use this as the gate for engaging an integration management office consultant. If the answers are not clear, the scope is not ready.

• Deal type decided. Platform, bolt-on, or hold-separate, and cost-led or revenue-led, agreed before scoping.
• Ownership line drawn. A one-page RACI naming who decides the ten decisions that most affect the synergy case.
• Synergy case classified. Every line labeled realized, run-rate, forecast, or enabled, with a baseline for each.
• Systems and data scoped. The migration and consolidation work named, sized, and sequenced, ideally off a prior tech diligence report.
• RevOps workstream included. For revenue-led deals, a named owner and a dollar figure on cross-sell and combined go-to-market.
• Reporting cadence fixed. Actual versus plan, same definitions, every two weeks, to the sponsor.
• Milestone-based fee. Payment tied to plan, workstreams, Day 1, and reforecast, not to monthly presence.
• Handoff defined. A named internal owner takes ongoing execution, with a clear finish line for the consultant’s core scope.

Governance discipline of this kind is exactly what the Harvard Law School Forum on Corporate Governance and financial-controls guidance from the AICPA and CIMA point toward: clear ownership, consistent definitions, and evidence over narrative. If the engagement cannot satisfy the checklist, it will produce activity rather than realized value, and the board will notice by the second meeting.

How this connects to the rest of the value creation plan

The integration office does not run alone. It sits between the diligence that named the risks and the operating program that captures the value. When those three are coupled, the synergy case moves from spreadsheet to realized EBITDA on a timeline the board can see. When they are decoupled, each hands the next a set of surprises. The related work on RevOps due diligence, what to decide and how to judge it covers the front end of that chain, and the integration office is where its findings get executed rather than forgotten.

The buyer’s job is not to run the office. It is to scope it correctly, judge it early, and hold it to evidence. Do that, and the integration management office consultant becomes the mechanism that protects the return case. Skip it, and the office becomes the place where the return case quietly leaks away.

If you are scoping the integration office for a live deal and want a bounded PMI sprint that produces the plan, the workstreams, and a defensible reforecast rather than a standing meeting, review the DevriX and GrowthShuttle private equity offer and bring it the specific deal you are integrating.