The AI MSP Roll-Up: What the Pitch Decks Skip

More than $3B has been deployed into AI-enabled roll-ups, and in December 2025 OpenAI itself took an equity stake in Thrive Holdings, one of the backers funding an MSP consolidation play. An AI MSP roll-up is the strategy behind that money: buy several managed service providers, then deploy AI automation across the combined delivery operation to push service margins toward software economics. It has gone from a niche investor thesis to a category with real capital and a model vendor at the table. The problem is that most of the investor-facing coverage is written by the people raising the money.

I run growth inside a national MSP, and I spent close to a decade across investment banking, a family office, and private equity before that. This is the operator's read, not the fundraiser's. Three things decide whether the thesis holds: why 90% of MSPs are actually stuck under $1M in revenue, what AI genuinely automates in delivery and what it does not, and the one step in the whole model nobody has publicly proven. Get those three right and you can tell a real platform from a slide deck before you sign anything.

Why 90% of MSPs Never Pass $1M: It's the Delivery Model

There are roughly 150,000 MSPs worldwide, and about 90% of them never get past $1M in annual revenue. The standard explanation is that they cannot market themselves. That explanation is wrong.

A friend who spent nearly a decade doing cybersecurity M&A at a large vendor put it better than any analyst report. Big-client managed services work, he said, is like fixing a house: you start at the pipe, and the asks never end for the same price tag. That one line contains the whole diagnosis.

Here is the mechanism, in sequence.

Every large client becomes a custom engagement. You sign a fixed monthly fee, then the out-of-scope requests start, and unless you bound them hard in the contract your margin erodes with every one. This is why project and custom work runs 35% to 45% gross margin while the MSP average sits around 52%. Kaseya's 2026 data shows the squeeze getting worse: the share of MSPs reporting typical customer spend above $25K a year fell from 75% to 41% in a single year.

Revenue then concentrates. A small MSP is usually top-heavy on five to ten accounts. Independent benchmarks treat a single client above 15% of revenue as a concentration risk and above 25% as a structural vulnerability, and when the top three clients pass 40% of revenue, one bad quarter can cascade into a cash crisis. Client concentration is the most common structural weakness in businesses between $500K and $3M in revenue, which is exactly the band these shops live in.

Growth means hiring, because capacity is human. A SOC analyst can triage 50 to 75 alerts a day, and techs spend around 80% of their time on repeatable L1 work. There is no way to add clients without adding people, so revenue and headcount move together and margin never expands. Then the owner burns out, and the loop closes.

Layer on the demand side. Omdia's analysts found that roughly 70% of an MSP's "new" customers are just churn from another MSP, and that headline managed services growth of about 6% is mostly price rises and acquisition effects, not real accretive growth.

So the constraint was never marketing. It is a delivery model where the link between headcount and revenue never breaks. That is why product companies avoid services, and why a third of MSPs run at a loss.

The Multiples Arbitrage Game, and Who It's Really For

Strip the AI story away and the AI MSP roll-up is a multiples-arbitrage trade, the kind I priced for a living. A managed services shop with under $1M in EBITDA trades at roughly 4x. A standardized platform above $5M in EBITDA trades at 12x to 14x. That spread is the entire game.

The trade is simple on a spreadsheet. Buy ten small shops at 4x, staple them into one entity, and the aggregate re-rates to double-digit multiples, provided retention, margins, and integration hold. Solganick's deal tracking counted 466 MSP and MSSP transactions in 2025, up about 27% year over year, with private equity involved in 69% of disclosed deals. The money likes this because fragmentation reads as inefficiency, and IT services reads as sticky recurring revenue from a distance.

What the spreadsheet misses is where the synergies actually come from. They come from back-office consolidation and vendor contract renegotiation. They do not come from delivery.

As Sayantan Sarkar put it in his roll-up thesis, what a technician does on a Tuesday morning looks the same in 2026 as it did in 2014. You can merge ten finance departments. You cannot merge ten custom-scoped delivery models into one and call it a synergy.

The honest exception proves the point. Evergreen Services Group ran more than 150 acquisitions and its Lyra Technology Group platform crossed $1B in ARR, so the classic roll-up clearly can work financially. But its own CEO, Elliott Hyman, says AI is enhancement, not shortcut: the engine in any company has to exist before the technology can accelerate it. He built it on operational discipline and light integration, not on a delivery-automation story.

And the arbitrage is decaying. Top Down Ventures' State of MSP Capital 2025 counts 75-plus platforms chasing the same sub-$10M targets, sellers now price in the re-rating, and median buyout returns had already compressed by 2023 even as revenue grew, which is why the arbitrage era is ending. If this rhymes with anything, it is the Amazon FBA aggregators who raised billions on identical buy-and-centralize logic and then blew up. Buying revenue is not the same as building an operation.

The New Money: Who Is Buying MSPs With an AI Story

The most telling deal in this whole AI MSP roll-up wave is not the acquisition of an MSP. On December 1, 2025, OpenAI took an equity stake in Thrive Holdings, one of the backers behind an MSP roll-up, compensated out of future returns and with access to the portfolio companies' operating data to train models. The model vendor now owns a piece of the consolidator and a pipe into its data. Sit with that for a second.

Here is who is actually buying, and with what. Shield Technology Partners raised two $100M checks from ZBS Partners and Thrive Holdings, reaching $200M by February 2026. It holds controlling interests in at least seven MSPs and reports nine portfolio companies serving more than 1,500 organizations, with portfolio revenue past $100M.

Titan MSP raised $74M from General Catalyst and bought RFA, a well-known New York MSP. General Catalyst's stated model is $100M to $150M per platform over several rounds, seven-to-ten-year holds, and no debt-and-cut playbook. It also screens hard for whether an acquired shop actually wants to change, which is the opposite of a classic cost-cutting buyout.

The punchline is the last column. None of the AI-native platforms has published a post-acquisition delivery result: no margin lift, no ticket automation rate, nothing from inside an acquired shop. What is disclosed sits upstream.

General Catalyst's Marc Bhargava says Titan proved it could automate 38% of what an MSP does, but that was on six pilot clients before the RFA acquisition, not after it. Bhargava also says Titan is well on its way to doubling EBITDA margins, though that is a target, not a reported result. And the Thrive data-access arrangement raises a client-consent question nobody has litigated yet. I mapped who is funding these buyers and where the software money sits separately.

What AI Actually Automates in MSP Delivery (With Numbers)

About half of an MSP's technical labor is routine L1 and L2 work, according to CompTIA: password resets, endpoint provisioning, patch compliance. That is the half AI can touch today, and the numbers are real enough to plan around.

The most credible single number is Titan's 38%, a sponsor-reported pilot benchmark that General Catalyst backed with its own capital. D3's vendor case study, an unnamed MSSP going from 144,000 monthly alerts to 200 needing human review, is directionally exciting but vendor-published, so treat it as the ceiling, not the base case. For a 10-person SOC, D3 frames the same deployment as roughly 7,800 analyst-hours recovered a year, which is the kind of number that moves EBITDA if it survives contact with real data.

Then there is the other half, which stays human: custom scope negotiation, on-site work, and the unsupervised response actions where the liability lives. Trust matters most of all, because in a small MSP the owner is the brand and carries 80-plus personal relationships that do not transfer to a model.

Two walls sit behind the automation. The first is autonomy: Edward Wu, Dropzone's own CEO, says a fully autonomous SOC is still technically impossible, and his system already makes around 100 LLM calls to investigate a single alert. The second is data. Gartner reckons 60% of AI projects fail without AI-ready data infrastructure, and Eric Capuano, an independent detection engineer, says organizations that skipped the last decade of data hygiene find AI cost-prohibitive on messy inputs.

So treat the biggest headline numbers as marketing until you validate them on your own alert data. Torq's 95% Tier-1 auto-investigation figure is a vendor-published claim, not an audited result. The cost model also flips underneath all of this: roughly 100 LLM calls per alert at $1 to $3 per investigation turns a fixed labor cost into a variable compute cost, which becomes a real line item at volume and reshapes how MSPs price AI work. On complex incidents that math gets ugly fast, with one operator reporting agents hitting $300 a day, around $100K a year each, while still covering only 10 to 20% of the task.

The Open-Source Wrinkle: The Best Automation Layer Is Increasingly Free

The automation table above is all commercial vendors, and that hides something the pitch decks hide too. Spend a week inside the two communities where MSP owners actually talk, The Tech Tribe and r/msp, and the most automated shops are not the ones buying AI platforms. They are running free software assembled by an internal champion.

The tool with the most mindshare in the entire channel conversation is not a funded platform. It is CIPP, an open-source multi-tenant Microsoft 365 management portal built by CyberDrain’s Kelvin Tempelman. Around it sits a whole free stack: CISA’s ScubaGear for M365 security baselines, M365DSC for configuration drift, CyberDrain’s Check for token-theft protection, TacticalRMM for shops that want to own their monitoring layer. Technical MSPs assemble their config, drift and detection layer from these parts and pay nobody. When someone on r/msp asked whether “it’s open source” is a valid reason to reject CIPP, the thread resolved the other way: the founder answers support complaints personally within hours, which is more than most funded vendors manage.

The commercial side of MSP automation just demonstrated the risk of betting against this. Rewst, the best-funded automation platform in the channel with $45M raised, went through significant layoffs in early 2026. Within weeks, operators were posting migration threads: one MSP ported its entire production workflow library to n8n, the open-source automation platform, in under two weeks. Others described dropping their RMM entirely, replacing ConnectWise Automate with a combination of workflow automation, CIPP and Microsoft’s native Intune. The stack an acquirer inherits is being unbundled from below while they are still in diligence.

There is also a newer layer forming that the automation table cannot show yet. The agents in those pilot numbers need authenticated access to the PSA, the RMM and the Microsoft tenant before they can close a single ticket. That plumbing is being built by practitioners, not platforms: StackJack, an MCP proxy that gives AI assistants audited access to twenty-plus MSP tools, was built by a HaloPSA specialist and sells for less than a single tech-hour per month. Whoever standardises this agent-access layer owns the next version of the integration moat, and right now it is a cottage industry.

For the roll-up thesis this cuts two ways. It supports the re-platform argument, because the marginal cost of the automation layer is collapsing toward free software plus one AI-fluent operator, which is exactly the internal-champion profile from Sarkar’s interviews. And it undercuts any buyer whose model prices proprietary automation as the moat. If the tooling is free, the moat was never the tooling. It is standardization, change management and the champion, the three things you cannot buy at 4x EBITDA.

The Right Sequence: Re-Platform First, Buy Second

The real question is not whether to roll up MSPs. It is what you fix first, the delivery machine or the client books.

A classic roll-up glues broken delivery models together. Ten shops each doing custom work for five to ten big clients become one shop doing custom work for 50 to 100 big clients, plus integration drag. The 2011 MSPAlliance critique that "there has never been a successful roll-up in managed services" was wrong about the financials, as Evergreen later proved, but its point about forced integration causing client loss and brand damage was never actually answered.

The sequence that works runs the other way.

First, standardize the offer. Kill snowflake scopes and define two or three productized tiers with bounded inclusions. This is the Huntress lesson: one multi-tenant stack and fixed playbooks scaled to $120M ARR growing around 70% a year, with no M&A at all, while the traditional custom-scope MSSP sits near 52% gross margin and adds headcount for every client. Standardization is what breaks the headcount link.

Second, automate the routine half using the tools from the section above. The catch is that tools do not re-platform a business, operators do: Sarkar's owner interviews found MSPs with an internal AI champion hit 60-70% automation, while the ones that bought AI as a checkbox feature got nothing.

Third, instrument the proof. Tickets closed by agents, hours removed, margin recovered. Top Down calls this "proof per dollar," and their data shows verified efficiency gains trade at roughly double the multiple of firms selling potential. A $10M MSP that automates 30% of its Tier-1 workload lifts EBITDA from about 15% to 18%, roughly $300K a year, with no new capital and no top-line growth.

Fourth, and only then, buy MRR and pour it into the re-platformed machine. Structure two-to-three-year retention earnouts so relationships transfer, because post-acquisition churn can hit 75% if the owner walks and drops to single digits when the earnout ties them in.

The kicker is that the smartest finance money already runs this sequence. General Catalyst's Crescendo built call-center software that automated 50-70% of tasks, proved it on about ten pilot clients for a full year, and only then bought a call center, taking 10% EBITDA margins toward 40%. Titan proved its 38% on pilots before touching RFA.

The build-then-buy order is exactly what the on-the-record operators describe. The pitch-deck version is the same story with steps one through three quietly deleted.

The Step Nobody Has Proven: Buy-Then-Re-Platform

Here is the sentence the pitch decks will not print. There is no publicly documented case of buying a legacy MSP or MSSP book and materially cutting delivery headcount with AI tooling. More than $3B raised, 15-plus MSPs bought, and zero disclosed post-acquisition delivery results.

What exists instead is proof from before the acquisition or from outside it. Titan's 38% came from pilots. D3's alert-reduction case is a vendor study on an unnamed customer.

Top Down's margin numbers come from pilot programs run by a fund with a direct interest in the thesis. Every data point sits upstream of the hard part.

Why it might genuinely be hard is baked into everything above. Acquired books are custom-scoped by construction, so there is no standard runbook to automate against. Client contracts encode the old delivery model.

PSA migration is the problem one operator described as easier to solve by selling the business and starting a new one. And change management on acquired staff is a different animal from a pilot run with volunteers who opted in.

Why it might still work is timing. The 2025-26 tooling curve is ahead of any acquisition vintage that has had enough time to report results. It is genuinely possible the first clean case study is eighteen months away.

But the market is already pricing the outcome. In cyber-heavy comps, MDR and XDR specialists trade two to four EBITDA turns above labor-heavy MSSPs, a spread that proxies automation maturity, and buyers pay it before anyone has publicly demonstrated the conversion on an acquired book. Capital Founders notes there are only two to three years of performance data for the entire category.

The diagnosis is proven. The prescription is still a bet.

What This Means If You Own an MSP

If AI MSP roll-up buyers are circling your inbox, the worst move you can make is selling an un-automated book into a thesis that prices automation. You would be handing the buyer the entire upside for free.

The valuation spread is your to-do list. An under-$1M-EBITDA custom shop trades around 4x. Standardized, instrumented delivery gets you into the 8x to 11x band for cyber-heavy MSSP work, and 12x to 14x at real scale. Every point of automation-driven margin is worth roughly double when the buyer prices it, because the market pays the proof camp and discounts the hope camp, which is how MSP valuation works in the AI era.

So do the re-platform work on your own P&L first. Standardize your tiers. Bound scope in the contract so the out-of-scope asks stop eating your margin.

Deploy triage automation on the routine half. Keep the before-and-after metrics, because those become the diligence artifacts that move your multiple. The gains are concrete, not theoretical: one MSP in Top Down's fieldwork replaced three help-desk staff with a dozen autonomous agents billed at $800 each, cut cost 40%, and doubled response speed.

One more thing, and it is a posture, not a tactic. Distrust the urgency. Outbound M&A spam has sellers everywhere on alert, and a recently exited operator I know gets daily "a family office wants to buy you" emails.

A buyer who needs your book more than you need their exit will still be there in twelve months. The re-platform work you do in those twelve months is what changes which side of that table you sit on. The owners who win the next three years are not the ones who sell fastest. They are the ones who make their delivery legible and automated before they ever take a call.

The Bottom Line

The delivery model, not marketing, is what keeps 90% of MSPs under $1M in revenue. AI genuinely automates the routine half of the work, and in cyber-heavy comps the automated shops already trade two to four EBITDA turns above the labor-heavy ones. Nobody has publicly shown the buy-then-re-platform step working on an acquired book, so the hardest part of the thesis is still a bet.

If you invest here, back platform-first teams and demand delivery metrics, not deal counts. Ask what margin moved inside an acquired company, and treat "we raised X and bought Y" as a non-answer. If you own an MSP, do the automation on your own book before you sell it, because the spread between a custom shop and an instrumented one is the largest cheque you will ever write yourself.

The next move is the same either way: get honest about your own delivery economics before the market gets honest for you. If you want to compare notes on this, operator to operator, I am easiest to reach on LinkedIn.

FAQ