14 companies, one operating model.

A roll-up moving faster than its instrumentation

Kaseya was executing an aggressive acquisition strategy under private equity ownership, buying companies and folding them into a consolidating IT management portfolio. In May 2019 it closed a $500M+ growth financing round from TPG and Insight Partners.

The strategy was working. What it was outrunning was the executive team's ability to see what they now owned.

Fourteen companies, fourteen versions of the truth

Every acquisition arrived with its own internal systems, its own KPI definitions, its own reporting structures, its own planning calendar, and its own conventions for what job titles and processes meant.

Individually, none of that was a crisis. Collectively it meant leadership could not compare anything to anything. A KPI from one acquired company did not mean what the same KPI meant elsewhere. Departmental P&Ls did not reconcile. Forecasts assembled from inconsistent inputs produced a number nobody fully trusted.

You cannot allocate capital across a portfolio you cannot compare.

Give leadership one way to see the whole thing

I was brought in to Strategic Finance and Business Operations and worked directly with the C-suite through the scale-up, across budgets, forecasts, P&Ls, KPIs, resource allocation and scenario analysis.

The choice everyone frames wrongly

Roll-ups usually get framed as a speed question. Absorb acquisitions quickly and you destroy what you paid for. Leave them alone and you get a holding company with a shared logo.

I did not think that was the real decision. The question was not how much to integrate, it was which layer to integrate.

Acquired companies kept their names and their products, because that was the thing customers valued and the thing the acquisition was actually buying. What got unified was the layer underneath: the systems, the metrics, the reporting, the planning cycle, the operating procedures. Leadership did not need every company to look identical. Leadership needed a consistent way to understand a portfolio that was consolidating rapidly.

That framing is what made the work tractable. It also meant the integration never finished and never needed to. Each new acquisition plugged into an operating model that already existed.

The post-close operating layer

Underneath that sat the cadence the company actually ran on: annual planning and budgeting, quarterly planning with forecast adjustments, monthly financial forecasting, KPI reviews, QBRs, acquisition integration reviews, scenario planning, board preparation, and the weekly C-suite meeting.

I also did the unglamorous work that makes the rest of it real. Departmental P&Ls were cleaned up so leadership was reading from a consistent financial picture. Departmental actuals were aligned to budgets, which is what turned resource allocation from an argument into a decision. Quarterly forecast adjustments were worked through directly with the C-suite.

The acquisition that did not happen

The clearest test of whether decision infrastructure is working is not whether it produces reports. It is whether leadership ever does something different because of it.

During one acquisition evaluation, I built and analyzed the underlying financial and operational picture: current and projected KPIs, the short and long-term benefits, the risks, and the expected operating implications of bringing the company in. I worked directly with the C-suite through that review.

Leadership decided not to proceed.

In a company that had completed 14 acquisitions, the ability to say no to the next one is not a small thing. It is the entire argument for building the infrastructure in the first place.

Integrate the layer, not the company

The thing I took from Kaseya is the framing, not the artifacts.

Fourteen acquisitions is not a reporting problem, and treating it as one produces a company that can describe itself accurately and still cannot decide anything. What leadership needed was not more visibility. It was a common basis for comparison, which is a different thing and has to be built deliberately at the layer underneath the businesses rather than on top of them.

Get that layer right and the portfolio can absorb almost anything. Get it wrong and every acquisition makes the company harder to run than the one before it.