There is a pattern in lower-middle-market rollups that repeats across industries. A platform company gets PE backing. The thesis is consolidation. The team is energized. The first add-on closes within six months and integrates well. The second closes three months later. The third closes two months after that. By month eighteen, the platform has acquired six or seven companies, and revenue has tripled.

And then something starts to break.

The most common version of the break is operational. Integration debt accumulates faster than the operations team can pay it down. Acquired systems remain bolted on rather than absorbed. The acquired companies' people continue to operate on their original processes, because the platform's processes haven't actually been documented in a way that lets new sites adopt them. Reporting becomes unreliable because the data lives in too many systems. Cash management becomes harder because the AR cycles don't align. Staffing decisions get made reactively because no one knows what the actual labor model should be at scale.

The platform doesn't fail in this scenario. Worse -- it stalls. Acquisitions halt while the team tries to fix what they've built. The pause sometimes lasts a few months. Sometimes it lasts more than a year. By the time the platform is ready to acquire again, the market has moved, the team has changed, and the thesis is harder to execute.

I watched this play out at Lookout Pest Control during my time there. The platform grew from roughly $7M topline to over $60M in about six months -- extraordinary growth, real value creation, and a thesis that worked. But the integration capacity didn't scale at the same rate. Eventually the team had to halt all acquisition activity to focus on fixing what had been built. The pause was long. By the time acquisitions resumed, the role I had been hired to do had largely been worked out of existence.

This is not a story about a bad platform or a bad sponsor. Both were good. It's a story about a pattern that is structural to how PE rollups are typically built -- acquisition is funded and resourced before integration is, and the asymmetry compounds.

The pattern shows up in behavioral health for the same reasons, and with additional complications specific to the sector.

In behavioral health, integration involves clinical systems, payer contracts, credentialing files, electronic health records, regulatory licenses, staffing models, and quality reporting. Each of these is more complex than its equivalent in a non-healthcare services business. EHR migrations alone can consume six months of operations leadership attention. Payer contract integration requires careful sequencing to avoid disrupting cash flow during transition. Credentialing has to be maintained continuously or the new sites cannot bill. State licenses are not transferable in many states, so post-acquisition restructuring has to be planned in advance.

A behavioral health platform that acquires faster than its operations leadership can absorb the work will reliably produce one of three outcomes. Quality degrades because operational discipline thins out across more sites than the leadership team can attend to. Cash flow becomes unstable because billing and collections lag during integration. Or the platform halts acquisitions while the team catches up, with the consequences described earlier.

The implication for acquirers is not that consolidation is the wrong strategy in behavioral health. It is the right strategy in many segments. The implication is that integration capacity has to be funded and built in advance of acquisition velocity, not in response to it.

This is harder than it sounds, because the deployment pressure on PE-backed platforms is structural. LPs expect capital to be deployed. Sponsors expect acquisition activity. Platform CEOs are evaluated on growth. The pressure to acquire is greater than the pressure to integrate, in the short term -- and the consequences of failing to integrate are delayed by quarters.

The platforms that succeed in this market are the ones whose sponsors and operators have the discipline to slow acquisition velocity when integration capacity is at its limit, even at the cost of short-term deployment metrics. The platforms that fail are the ones who continue to acquire while integration debt accumulates, until something breaks.

For acquirers planning a behavioral health rollup, a few things matter.

Build the operations function before you need it, not after. A platform's first hires should include a head of integration and an operations leader at a level of seniority typically reserved for later stages.

Choose targets that fit the integration model you can actually execute. A target that operates on systems and processes radically different from the platform's will consume more integration capacity than a target that is operationally adjacent. Operational fit is a real diligence dimension, not a soft one.

Sequence acquisitions to allow each one to be substantially integrated before the next one closes. This is unromantic, but it produces compounding outcomes rather than stalls.

Maintain origination discipline during integration phases. The single worst pattern is to acquire fast, hit the integration wall, halt origination, and then have to rebuild pipeline from scratch when the platform is ready to acquire again. Origination should continue at a steady cadence even when acquisition execution is paused, so that the pipeline is full when execution resumes.

This is the kind of strategic patience that is hard to maintain under deployment pressure. It is also what separates the platforms that compound from the platforms that stall.