Last updated: October 31, 2026
An integration management office (IMO) is the temporary team that runs a post-merger integration for 6 to 18 months, usually a lead, a PMO, finance and IT integration leads, and a synergy tracker. Keep the decisions with your own people and put the tracking, coordinating, and backfill seats on contract, so your best operators stay on the business.
Every deal team draws the same chart. Steering committee on top, office in the middle, workstreams underneath. Then somebody starts filling in names, and the names are the controller, the head of IT, and the VP of operations who hit their number last year.
All three already have full jobs. Nobody took those away.
So this piece is about the names. What the office is for, how it’s built, which seats you should never hand to an outsider, and which ones you’d be foolish to staff from your own bench. You should know we bill for those seats. KORE1 supplies M&A integration staffing through our contract staffing desk, and we’ve been the buyer ourselves twice, with Kranect in Denver and Technical Connections in Los Angeles. Some of these seats shouldn’t be contract. I’ll tell you which.

What Does an Integration Management Office Actually Do?
An integration management office is a temporary, cross-functional team that sits between the steering committee and the integration workstreams. It keeps the master plan, tracks decisions and dependencies, escalates what’s stuck, and reports progress against the deal model. It coordinates the integration. The workstreams do the integration.
L.E.K. Consulting calls the IMO the central nervous system of the program, carrying guidance from the steering committee down to the workstreams and progress back up. Consultants sell this work, so discount the enthusiasm a little, although the advice tends to hold up once you’ve watched a deal run without an office and then spent a quarter rebuilding the numbers. They’re still right.
The thing it replaces is a controller’s spreadsheet and a Thursday call that keeps moving. I’ve seen versions of that hold up for a tuck-in. Somewhere around the second system, the third benefits plan, and the first question from the board about where the savings went, the spreadsheet stops being true and nobody can say which week it stopped.
IMO vs PMO trips people up. Your PMO runs a portfolio of projects under the rules your company already has, and it stays open. An IMO exists for one deal, spans two companies whose rules don’t match yet, answers for a number somebody promised a board, and closes. Same skills. Different job.
How an IMO Is Structured
Three layers, and most of the arguments are about the middle one. The rhythm column is what we’d suggest, not a standard anyone enforces.
| Layer | Who sits there | What it decides | Rhythm |
|---|---|---|---|
| Steering committee | CEO or sponsor, CFO, CHRO, the acquired company’s senior leader | Org design, synergy targets, anything that changes the deal thesis | Every two weeks through day 100, then monthly |
| IMO | IMO lead, PMO lead, synergy tracker, coordinator | Pace, sequencing, what gets escalated | Weekly workstream meeting, daily in the two weeks around close |
| Workstreams | Finance, IT, HR, sales and customer, operations, procurement, legal | How the work gets done inside each function | Weekly at least, owned by the lead |
L.E.K. has two pieces of advice in that same article that I’d underline. Line the workstreams up with your existing functions, so ownership follows the reporting lines people already respect. And fold synergy targets into those functional workstreams instead of building a separate synergy team, unless the number is big enough to justify one.
They also warn that co-leads, one from each company, buy goodwill and blur accountability. True. Use co-leads anyway when the acquired team is what you paid for. Then write down who breaks the tie.
The Seats Inside the Office, and Who Should Fill Each One
The lengths below are our planning ranges. Your deal will move them.
| Seat | What it owns | Yours or contract? | Typical length |
|---|---|---|---|
| Executive sponsor | Breaks ties, answers to the CEO and board | Yours. Always. | The whole program, part time |
| IMO lead | The plan, the pace, the escalations | Yours if you have one to spare. Contract under a named sponsor if you don’t. | 12 to 18 months |
| PMO lead | Master plan, decision log, dependency tracking, the weekly meeting | Contract | 12 to 18 months |
| Finance integration lead | Chart of accounts mapping, the combined close, opening balance sheet support | Contract for the volume. Your controller keeps the judgment calls. | 6 to 12 months |
| IT integration lead | Day-one access, application inventory, the plan to exit seller systems | Contract. Your CIO keeps the architecture decisions. | 9 to 18 months |
| Synergy tracker | Baseline, initiative owners, where each saving lands in the P&L | Contract, reporting into your finance team | 12 to 18 months |
| People integration lead | Org charts, two payrolls, two benefit plans | Your CHRO decides. Contract specialists carry it. | 6 to 12 months |
| Coordinator | Calendars, minutes, chasing the overdue items | Contract | 6 to 12 months |
The synergy tracker gets underrated. Junior people end up with it because it looks like a spreadsheet job, and for about ninety days it is. Then a procurement saving shows up in a cost center nobody baselined, a headcount reduction gets counted by both HR and finance, and the CFO asks for one number the auditors won’t laugh at. L.E.K. says finance should be closely aligned with the IMO on how targets get set and where savings land in the P&L. Hire someone who has sat in FP&A and argued about a budget.
Which IMO Seats Should Be Contract?
Two questions sort almost all of it. Does this seat make a call the business will live with for five years? Keep it. Does the seat mostly carry volume against a deadline that ends? Contract.
Executive sponsor fails the second test on day one. So does anyone deciding which company’s ERP survives, who runs the combined sales team, or whether a plant stays open. You don’t rent those.
The less obvious move is the backfill.
Plenty of integrations don’t need a contractor in the office at all. They need one behind it. Your controller is the right finance integration lead, because your controller is the only person who can make the calls, knows the auditors, and won’t get pushed around by the acquired company’s finance chief. Fine. So who closes the books in month two? A Bain survey of 250 executives involved in M&A found two of the top three reasons for disappointing acquisitions came down to integration, and its authors said a small team, 10 percent or fewer of employees in any function, should drive it while the rest stay on the business. That paper is about twenty years old. Nothing’s changed except the software.
L.E.K.’s version is more specific. On a complex program the IMO lead should ideally be full time, and at minimum half time for the opening months. Half of whose job? That’s the question nobody writes into the plan. Half time on integration means someone else is doing the other half, or nobody is, and if it’s nobody you’ll find out when the quarter closes late and the two people who could’ve caught it were in a Day 30 readout.
So there are really two contract plays, and they cost about the same.
One: your operator stays put and decides, and a contract integration lead carries the mapping, testing, and reconciliations under them. Two: your operator moves into the office full time, and a contractor runs the day job, through something like a month-end close contract team or a contract controller. I lean toward the second when the acquired company’s books are a mess and the decisions will come fast. I lean toward the first when your own team is the fragile part, because a contractor who’s been in your close for six days is not who you want facing the audit committee.
Don’t apply any of this to the people you bought. L.E.K. calls finding the target’s subject matter experts and initiative owners a critical early step, and they’re right. A contractor can’t replace the person who knows why that spreadsheet feeds that report. A contractor can free up that person’s week, which is also how you keep them past the month-four attrition wave.

When to Stand It Up, and the Trap in Starting Early
Start at signing. The office needs weeks of planning before close, and the first hard work is deciding what has to be true on day one, meaning which accounts have to reconcile, who can sign what, and which customer gets a call from whom before the press release goes out. Waiting for close means you spend your first month writing the plan you should’ve arrived with.
Careful, though. Until the deal closes you’re still two companies, and the rules treat you that way. The FTC’s guidance on pre-merger information sharing says what you exchange should be narrowly tailored to a specific diligence or integration planning issue, that sensitive material can call for a clean team, and that clean teams shouldn’t include anyone responsible for competitive planning, pricing, or strategy. In January 2025 the agency announced a record $5.6 million gun-jumping penalty, which is the kind of thing that wakes a general counsel up.
This is an underrated reason to use contractors before close. An analyst with no pricing role, who leaves when the job ends, is a lot easier to wall off than your head of sales operations. Your antitrust counsel picks who goes on the clean team. Not you, and certainly not us.
After close, a few clocks start that don’t care how your plan looks.
- Workforce changes. Under the WARN Act, notice of a covered layoff or plant closing falls to the seller up to the sale’s effective date and to the buyer after it.
- The opening balance sheet, because ASC 805’s measurement period ends no more than a year after the acquisition date.
- Public buyer? The SEC staff gives you a limited pass on assessing the acquired company’s internal controls, good for one annual report and gone by the deal’s first anniversary.
We laid out how those run against each seat on the integration staffing page, and if systems are the main event, post-acquisition systems integration is a separate team on a separate clock.
What the Contract Seats Cost
Here’s the bench priced out. These are bill rates, meaning what you’d pay per hour, with payroll taxes, workers’ comp, insurance, and benefits already inside.
| IMO seat | Closest index role (national) | Bill rate range | Median | 3 months | 6 months |
|---|---|---|---|---|---|
| PMO lead | Senior IT project or program manager | $93 to $114 | $106 | $54,900 | $109,800 |
| Finance integration lead | Senior controller | $145 to $178 | $165 | $85,900 | $171,900 |
| IT integration lead | Senior ERP or business systems consultant | $95 to $115 | $106 | $55,300 | $110,600 |
| Synergy tracker | Mid-level financial analyst or FP&A | $72 to $94 | $82 | $42,400 | $84,800 |
| People integration lead | Senior HR generalist | $70 to $85 | $79 | $41,000 | $82,000 |
| Coordinator | Junior project coordinator | $56 to $70 | $61 | $31,700 | $63,400 |
Source: KORE1 Contract Rate Index 2026-Q4, effective October 16, 2026. All cells are modeled from BLS wage data for May 2025, a 24% employer burden, and the bill bands we observe on our own placements. Costs assume 40 hours a week. The IMO seat names are ours, mapped to the closest role in the index.
One real number to check that against. Our own placed project and program managers, 21 of them, billed a $116 median with a $105 to $124 range, though most of those were in Southern California. Metro matters. So does the title you put on the req, which is why we keep a full contract rate card and a salary benchmark tool if you’re also pricing permanent seats.
Nobody needs all of these for the whole program, and this is where most budgets go wrong. Take five seats. Hold every one of them for 12 months at those medians and you’ve spent about $1,081,000. That’s real money. Now end each seat when its work ends: the PMO lead and tracker at 12 months, the IT lead at 9, the finance lead and coordinator at 6. That’s about $790,400, a difference of $290,600, with nobody doing less of the work that mattered. It’s arithmetic on the index, not a quote, and your deal will have its own shape.
Write the end date into each seat on day one. No exceptions.
Here’s why. Across 1,887 contract assignments that KORE1 tracked to their end, the median ran 116 days and a quarter ran past 227. A 12-month IMO seat outlasts most of what we place. Long seats drift. Nobody cancels them, the work gets vaguer, and in month fourteen a program manager is still chairing a meeting that has run out of agenda. It happens.
Closing the Office
IMOs are easy to open and strangely hard to close. People get attached to the status report.
Set the exit test before you need it. The combined company has closed its books on one calendar at least twice. Synergy numbers now live in the normal budget and FP&A owns them, so the tracker has nothing left that finance can’t do. Seller services under the transition agreement have ended, or there’s a dated plan and a named owner for the last few. And the decision log has stopped growing, which you’ll notice about a month before anyone says so out loud.
Then hand each leftover item to a person with a permanent job. Not a committee.
Some seats will turn into people you want to keep. Good. As our partner Devin Hornick puts it, “If this person completes 1,040 hours, then they are eligible to convert over to full time with that particular company at no additional charge from KORE1.” That’s about six months full time. There’s no replacement guarantee on contract, and I’d rather say that here than in month three. If you already know the combined company needs a permanent controller or HR director, skip the contract seat and go straight to direct hire, then let that person build what they’ll run.

When You Don’t Need an IMO at All
Small tuck-in, one location, one payroll, the seller’s systems going away on a date you already know. You need a good project manager and a controller with some breathing room. Call it a project. Drawing a three-layer org chart for that deal will cost you more in meetings than it saves.
And if what you actually need is somebody to write the integration thesis, hire an advisory firm. Really. Devin’s description of the line is the right one: “generally staffing firms don’t get into that. That’s a professional services thing.” We bill by the hour and you manage the person. If you’re a sponsor with several of these running at once, our portfolio company contract staffing page covers how that changes things, and the engineering version of this problem has its own 100-day playbook.
Things People Ask Before Standing Up an IMO
So who actually runs the IMO, and can that person be a contractor?
A senior internal leader should run it whenever you can spare one, because the job depends on credibility across functions and access to the top.
L.E.K. treats it as a step-up assignment for rising talent, and that’s a fine use of the role. Mid-market buyers often don’t have that person free. A contract IMO lead can work, but only under a named executive who owns the decisions. Without that sponsor, you’ve hired somebody to chase people who don’t report to them.
IMO vs PMO, does the gap actually matter?
Yes, because an IMO closes when the deal is integrated, while a PMO stays open and runs your normal project portfolio under rules your company already has.
Your PMO can supply people. It shouldn’t become the IMO by default, or its regular projects will quietly stop.
Realistically, how long does the office stay open?
6 to 18 months is the range we plan on, longer when the deal is large or systems consolidation runs late.
Can a contract synergy tracker see the deal numbers?
Under an NDA and your normal access controls, a contractor can see what the job requires, the same way an outside accountant would.
Before close it’s a different conversation. Sensitive data belongs behind whatever clean team rules your antitrust counsel sets, and those rules apply to contractors exactly as they apply to employees. After close, keep access tied to the seat and shut it off the day the seat ends. Somebody should own that last step by name, because it’s the one that gets forgotten.
How fast can these seats start?
17 days is KORE1’s average time to hire for IT roles, and that’s the figure we can stand behind.
We don’t publish one for finance or HR contract seats. Start the search at signing, not at close, and you won’t have to care much.
If you’ve just signed, or you can see a signature coming, talk to our team about the seats before the org chart hardens. We’ll tell you which ones are worth filling and which should stay with your own people. Want numbers first? Get a bill rate quote for the roles and metros you’re working with.

