Roll-up strategies are usually judged by the quality of the deals: the multiple paid, the fit of the target, the terms of the earn-out. Those things matter, but they are not where most roll-ups actually fail. They fail in the months after closing, when the acquired business has to be absorbed into a platform that turns out not to be ready for it. This note is about that gap, and what has to exist before the acquisition, not after it, to close it.
The day after the deal
On the day a deal closes, the acquired business still has its own bookkeeper, its own bank accounts, its own vendor terms, its own way of running payroll, and its own founder or general manager who has run it a particular way for years. None of that changes automatically because a purchase agreement was signed. It changes only through a deliberate, resourced integration process, and that process depends entirely on what the acquiring platform already has in place. If the platform has shared services for finance, people and procurement, the acquired business joins them. If it does not, the group now runs two of everything with one stretched team trying to hold both together.
The founder becomes the bottleneck
The most common failure pattern is simple to describe: the founder who led the roll-up now personally holds the relationship with the acquired company's team, personally reviews its numbers, and personally makes its exceptions. This works for one acquisition. It does not work for the second, and it collapses under the third. The founder's attention is the actual constraint on the roll-up's growth, and no amount of capital fixes that; only operating cadence and named owners do.
Acquiring before the platform exists
The deeper cause is sequencing. Many roll-ups acquire before the platform's own operating layer, finance function and shared services are built, on the theory that scale will fund the operating layer later. In practice, scale without an operating layer produces complexity faster than revenue, and the operating layer never gets built because everyone is busy running the fires. The sequence that holds up puts growth capital before acquisitions: the platform gets its systems and shared services first, funded deliberately, and only then goes looking for businesses to add. Reversing that order is the single most reliable predictor of a roll-up in trouble.
What integration requires
What has to be true before the first acquisition closes
- 01
A finance function that closes on schedule
The platform's own books close on a fixed day every month before it takes on a second set of books to reconcile.
- 02
Named owners for shared functions
Someone who is not the founder owns finance, people operations and procurement, and can absorb another business into each.
- 03
A documented onboarding sequence
A written plan for migrating an acquired company's banking, payroll, systems and reporting onto the platform, with a realistic timeline.
- 04
A cadence the acquired team can join
Weekly and monthly reviews that already exist and simply add the new business, rather than being invented under pressure after closing.
- 05
Capital set aside for integration
Budget for the systems work, temporary duplicate costs and people time that integration requires, planned before the deal, not found afterward.
The first hundred days
Even a well-prepared platform should expect the first hundred days after an acquisition to be demanding. Systems migrations slip. People who worked for the previous owner test the new arrangement. Customers ask who they should call. None of that is failure; it is the normal cost of integration, and it is manageable when the platform has planned for it. It becomes failure when the platform is discovering, in the middle of the acquired business's problems, that it does not have a finance team, a reporting cadence or a decision-maker of its own to spare. The first hundred days note sets out that sequence in more detail.
Reading the early signs
A roll-up in trouble usually shows the same early signs across its acquisitions: management accounts that arrive later each month, a founder whose calendar has no free time, an integration plan that exists as a slide but not as a set of dates with owners, and a growing gap between the group's reported EBITDA and the cash actually landing in the bank. None of these are dramatic on their own. Together, over two or three acquisitions, they describe a platform that bought growth it could not yet carry.
The remedy is rarely to stop acquiring altogether. It is to pause, build the shared-services layer the current businesses need, and resume once the platform can absorb the next one without the founder personally holding it together. That is a harder discipline than closing the next deal, and it is the one that determines whether the roll-up compounds or stalls. The Portfolios page describes how Opsist sequences platform readiness against acquisition pace, and the apply page is where that conversation starts.