The Real MSP Profitability Problem: Revenue Shrank. Overhead Didn't

The number that should be keeping MSP owners up at night isn't their churn rate or their NPS score. It's a single data point from Kaseya's 2026 State of the MSP Report: the share of MSP clients spending $25,000 or more annually fell from 75% to 41% in a single year.

That's not a blip. That's not a slow trend. That's a structural shift in what MSP revenue looks like, and it happened fast enough that most operators haven't adjusted for it yet.

The MSPs that notice late will spend 2026 trying to close the gap with volume. More clients, more deals, more pipeline. It's the instinctive response. It's also the wrong one.

The math stopped working

Here's the problem with chasing volume when deal sizes compress: it only works if your cost to deliver service compresses too.

It doesn't. Not automatically. Not without deliberate work.

When a client who used to spend $3,500 per month starts at $800, every ticket you handle for them costs the same as it did before. Your tech still has to triage it. Someone still has to route it. A dispatcher still has to follow up if it stalls. The labor overhead per ticket doesn't know what the client is paying.

So your revenue went down. Your cost per ticket stayed the same. And your service gross margin — the number that actually tells you whether your operation is healthy — quietly got worse.

Most MSPs don't see it this way because the P&L doesn't surface it cleanly. Revenue looks like a sales problem. Margin looks like a pricing problem. Neither framing points at the real issue: the cost structure of service delivery hasn't kept pace with what the market is willing to pay.

The cost you can't see on the P&L

There's a category of labor in every MSP service desk that doesn't show up as a line item. It's not billable. It's not tracked. It's distributed across every ticket in the queue as overhead, and it's quietly destroying margin on every single one.

Dispatch work.

A minute to re-route a ticket that landed in the wrong queue. Three minutes to chase a response that should have been captured at intake. Five minutes to figure out who owns an escalation that's been sitting for two hours. None of it is billable. None of it is visible. And almost none of it actually requires a human.

Multiply that across your full ticket volume and you're looking at a material chunk of your labor cost that exists purely as coordination overhead, the gap between a ticket arriving and the right person acting on it.

When deal sizes were larger, that overhead was easier to absorb. When average MRR per client trends toward $800 or $1,000, it becomes the difference between a profitable account and one that costs you money to service.

This is the lever most MSPs aren't pulling. Not because they don't know it exists, but because the problem is invisible until the margin is already gone.

The only number you fully control

Revenue is partly a market problem. Pricing is partly a competitive problem. Deal size, as Kaseya's data makes clear, is increasingly a structural problem that MSPs can't unilaterally fix.

Cost per ticket is different. That one is yours.

If you know what it costs you in labor to fully resolve a ticket from open to close — not time-to-close, labor hours — you know your service economics. You know which clients are profitable at their current contract size and which ones are quietly destroying margin while looking fine on paper.

Most MSPs don't have that number. They have feature adoption metrics and utilization reports and CSAT scores. What they don't have is a clear answer to the question that actually determines whether the business is healthy: what does it cost us to deliver service, and is that number moving in the right direction?

That's the standard service desk investment should be held to. Not whether the team is using it. Not what percentage of tickets flow through it. What is it doing to the cost of delivering service?

The window is narrower than it looks

The Kaseya data is a snapshot of what already happened. The MSPs who responded to that survey are operating in the margin environment it describes, right now, today.

The ones who pull ahead won't be the ones who closed the most deals in 2026. They'll be the ones who recognized that the market repriced managed services, adjusted their cost structure accordingly, and built a service operation that's profitable at smaller contract sizes.

That requires connecting service delivery to financial outcomes, not just running efficient tickets, but knowing exactly what each one costs and holding your tools accountable to reducing that number.

That's what Intelligent Service Delivery (ISD) looks like in practice. And it's the standard Thread is built to meet.

See what Thread does to your cost per ticket — book a demo.