Where the back-office work goes after a bolt-on acquisition
The work an add-on brings arrives on day one, and the team it lands on is the same size it was the week before. The capacity to absorb it is something you build ahead of the close, once, so it is standing when the next deal closes.
An add-on brings work with it immediately. A second set of books to consolidate, a second AP process, a second payroll calendar, vendor contracts someone has to read before anyone can renegotiate them, and a reporting pack that has to speak for two companies by the end of the month.
None of that work sat on anyone's job description the week before the close. The team it lands on is the same size it was that week, and it will be the same size for at least a quarter after. The question of where the work goes has usually been answered by then, quietly, and rarely on purpose.
Where the work actually goes
It goes upward, to the people closest to it and most able to absorb it. The controller picks up the consolidation. The FP&A lead rebuilds the reporting to carry a second entity. The COO takes the vendor calls because nobody else has the context yet. That is the fastest available answer, and in the first weeks after a close, fast is the right instinct.
That absorption is why the first close after the deal still lands on time. It is capable people holding two companies together by hand while the org chart catches up, and it is the reason the integration reads as smooth from the board seat. It also means the cost of the integration never appears anywhere you can see it. It gets paid in senior attention, which arrives on no invoice and shows up in no variance report.
Why the strain shows up a quarter later
The absorption works at first, which is exactly why the strain arrives late. Nothing is missed in month one. The reports go out, the payables clear, the numbers reconcile, and the integration checklist keeps moving.
What gets displaced is the discretionary work, and discretionary work is silent. The forecast that was going to be rebuilt. The margin analysis by branch that would have informed pricing. The process cleanup on the acquired side that everyone agreed to do once things settled. None of it has a deadline, so none of it raises a flag. By the time someone notices, the shape of the problem has changed. It is no longer an integration question. It is a team that has run at full capacity for two quarters with the improvement work still sitting in a folder, which is a pattern with a name and a shape worth knowing: why capable teams end up firefighting.
Adding headcount is the slowest answer available
Hiring answers a permanent increase in work well. It answers the first ninety days after a close poorly, because the timelines do not meet. A search, a notice period, and a ramp are measured in quarters. Integration work is front-loaded and wants the capacity now.
Sizing the hire is the second problem. The work an add-on generates is heaviest early and then settles into something smaller and steadier: the recurring reconciliation, reporting, and coordination the combined company now carries permanently. A headcount plan built for the peak is overbuilt for the steady state. A plan built for the steady state leaves the peak uncovered. Both are reasonable readings of the same number, and neither one covers the year.
The distinction that matters is between capacity you go out and acquire each time a deal closes, and capacity that is already standing when it does. Which of these streams belongs inside the company at all is a separate sort, and the Own vs. Rent rule settles it: own what recurs and is tied to your operating rhythm. Integration work is unusual in that it arrives as a spike and leaves a recurring stream behind it. The spike is what makes it urgent. The stream is what makes it worth owning.
The capacity question belongs before the close
The best time to answer it is while the deal is still in diligence. An integration plan already names the systems to be merged, the reporting to be aligned, and the owner of each workstream. It rarely names who does the additional volume those workstreams generate, because that volume is assumed to be absorbed. Writing the assumption down is most of the fix, and two questions do it. Which recurring streams get heavier when this company joins ours, and who holds them in month one.
The work arrives on the day the deal closes. The capacity arrives whenever someone thought to build it.
Teams that answer those two questions before the close usually find the answer is not exotic. It is a modest amount of designed capacity sitting on the recurring streams: reconciliation, reporting, AP and AR follow-up, vendor coordination, data cleanup on the acquired side. Work that is clear, that repeats weekly, and that today lands on the people whose judgment is the scarcest thing the company owns.
Capacity built once absorbs the next deal too
The strongest argument for building it ahead of the deal is that it is almost never one deal. PitchBook's data on US private equity has add-on acquisitions running at roughly three quarters of all buyout activity, which puts the second deal closer to a certainty than a possibility inside a portfolio company.
Capacity built for the first add-on is already standing for the second, and the second integration costs less than the first for reasons that compound. The reconciliation is defined. The reporting template already carries multiple entities. The people doing the work have done it before, on a real close, with your chart of accounts. That is the difference between absorbing a deal and being built to absorb deals.
What we build
Large enterprises answered this a long time ago. When acquired volume kept landing on the same teams, they built Global Capability Centers: embedded operating teams offshore that hold the recurring work and the context that comes with it. The entity, the real estate, and the multi-year build put that out of reach for a $75M company. The same architecture, sized for the middle market, is the Mini-GCC model, and it is what Kayana builds. Seats designed around your recurring streams, running inside your cadence and your tools, grown one at a time. One of the companies we work with grew its embedded team to 10+ seats exactly that way. Voluntary turnover across the teams we build runs 3–5% in year one, which matters more here than it looks. The people who carried the last integration are the people who carry the next one.
Quick answers
Where does the back-office work go after a bolt-on acquisition?
It goes upward, onto the senior people closest to it. The consolidation, the second reporting entity, the vendor coordination, and the AP and AR volume have no designed home on day one, so the controller, the finance lead, and the COO absorb them. That absorption is why the first close after the deal still lands on time, and it is also why the cost of the integration never appears on an invoice.
How do you integrate an acquisition without adding headcount?
By having designed capacity already sitting on the recurring streams before the deal closes. Hiring is a poor fit for the first ninety days after a close, because a search, a notice period, and a ramp run in quarters while integration work is front-loaded. The work that can be held without a new hire is the recurring reconciliation, reporting, follow-up, and coordination work, which is exactly the work that lands on senior people by default.
Why does the finance team break after an add-on deal?
It usually does not break. It absorbs, and the absorption works, which is why nothing looks wrong in month one. The consolidation gets done, the reports go out, and the payables clear, because senior people take on the new volume personally. What gets displaced is the discretionary work: the forecast rebuild, the margin analysis, the process cleanup on the acquired side. None of it has a deadline, so nothing raises a flag until a quarter or two later, when the team has been running at full capacity with the improvement work still sitting in a folder.
What capacity should be in place before the next acquisition closes?
Enough designed capacity on the recurring streams to absorb the increase without moving it onto the leadership team. Two questions in diligence settle the size of it. Which recurring streams get heavier when this company joins ours, and who holds them in month one. Capacity built for the first add-on is already standing for the second, which is the point of building it once rather than negotiating it deal by deal.
The design principles behind an operating layer that compounds are the subject of the book. Operational Alpha →
Keep reading
About the author
Chris Nolte
Founder of Kayana and author of Operational Alpha. He builds Mini-GCCs — embedded operating teams of senior remote professionals — for middle-market, PE-backed companies.