MSP Benchmarks 2026: The Numbers Every MSP Owner Should Know

TL;DR

The gap between a top-quartile MSP and an average one isn't luck - it's three levers pulled at the same time: endpoint-to-tech ratio (350 vs. 156), tool spend (22% of revenue vs. 29%), and automation rate (40%+ of repetitive work handed to a supervised agent vs. almost none). Top shops are running 18-20% EBITDA margins; median shops are at 9-11%; bottom quartile is at 5% or less. The structural difference is that best-in-class operators treat automation as an operational necessity, not a future initiative. If you're an MSP owner reading benchmarks and wondering where you land, this post walks through every number that matters - and what to do if you're off-pace on any of them.

The bifurcation nobody talks about

Most benchmark reports present averages. Averages are almost useless for MSP owners, because the distribution is so wide that the middle tells you nothing about what's actually achievable.

Here's what the data actually shows: only 13% of MSPs were unprofitable in Q2 2025, down from roughly 25% a few years earlier, according to the ConnectWise Service Leadership Index. That sounds like progress. But the flip side of that number is that plenty of shops are still scraping by at 5% EBITDA or below, while the top quartile is operating at 18-20% margins - in the same market, serving the same kinds of customers.

That gap is structural, not cyclical. It doesn't close when times get better. The shops at 18-20% built a fundamentally different operation. The shops at 5% are running the same model they've always run, just with slightly more pressure on it every year.

Understanding which side of that gap you're on - and why - starts with knowing the benchmarks.

Technician productivity: the ratio that drives everything else

The single most predictive number in MSP operations is the endpoint-to-technician ratio. Everything downstream - margins, hiring needs, automation ROI - is a function of how many endpoints each tech can carry.

The gold standard, consistently cited across industry research including Flamingo's P&L analysis, is 350 managed endpoints per technician. The industry average is closer to 156.

The math on why this ratio matters so much: a fully-loaded technician costs roughly $85,000 per year. Spread that across 156 endpoints, you're spending roughly $545 per endpoint per year in labor. Spread the same salary across 350 endpoints, and you're at $243 per endpoint. That's a 55% reduction in labor cost per managed endpoint - from the same headcount, without adding revenue.

Billable utilization is the companion metric. Top-performing technical teams consistently hit 78-82% billable utilization. Below 70% is a signal of over-hiring, poor process, or untracked overhead work bleeding into the numbers. Above 85% is usually unsustainable and tends to show up as burnout and attrition before it shows up in the P&L.

Revenue per technician of $150K-$200K annually is the benchmark for a healthy shop. If you're below $120K per tech, either you're over-staffed, your pricing is too low, or your utilization is leaking somewhere.

What's pulling the industry average down? Two things, mostly. First, 65% of MSPs still analyze SLA performance by hand, which means 20-40 hours per month of technician time disappears into spreadsheets and manual reporting. Second, most shops haven't meaningfully automated the L1 ticket volume that consumes the most tech-hours. When a tech spends 40% of their day on password resets and account unlocks, the endpoint-to-tech ratio never improves no matter how many endpoints you add.

Profitability benchmarks: what the numbers actually look like

The profitability story in MSPs has always been about the gap between what revenue looks like and what sticks.

Global managed services revenue is expected to hit $595 billion in 2025, up 13% year-over-year. MSPs grew revenue 9.6% in 2025, while adjusted EBITDA grew 17.1% - meaning the best operators are successfully translating growth into margin, not just top-line. But the distribution matters more than the average.

The bifurcation at the EBITDA level is stark: a 15-point gap between median and top-quartile. That gap doesn't come from pricing - it comes from cost structure.

"Running an MSP is 70% business skills, not technical skills. You're solving business problems, not just computer problems." - r/SmallMSP community discussion

The observation is right, and the benchmark data backs it up: the shops at 18-20% EBITDA are running tighter operations, not just charging more. They've solved the cost side before worrying about the revenue side.

The cost structure: where margin actually disappears

If you want to understand why most MSPs can't break 12% net margin, this is the section that explains it.

A Flamingo analysis of a representative $2.5M MSP breaks down exactly where revenue goes before the first dollar of profit:

Tool licensing: 29% of revenue ($725K)

The old benchmark was 20% of revenue to external technology. Reality is significantly worse once you count everything:

That's 29% of $2.5M revenue. And it's almost certainly understated - AI copilots are now adding another 2-3% of revenue in per-ticket or per-query fees on top of the base stack.

Repetitive labor: 24% of revenue ($600K)

24% of revenue typically goes to repetitive, manual tasks - ticket re-keying, alert triage, onboarding checklists, password resets, manual QBR prep. On a 10-tech team, that's roughly 7 full-time equivalents of labor doing work a well-configured automation could handle. The fully-loaded cost of that labor is $600K annually.

Combined: 53% of revenue eaten before a dollar of profit.

The top-quartile benchmark: 22% of revenue on tools (down from 29%) and significantly less repetitive labor overhead. That's not achieved by negotiating better vendor rates - it's achieved by consolidating from 15-20 tools to 4-5 core platforms, eliminating redundant licensing, and building enough automation that routine tickets don't require a tech's hands.

95% of MSPs say direct integration of tools is essential to scalable operations, but nearly a third admit they're losing time to tool-hopping and poor integration. The benchmark shops have solved this - the average shops are still living it.

Automation benchmarks: what "good" actually looks like

This is where the benchmark conversation gets specific. 71% of MSPs are using automation for routine tasks like patch management and backups. Only 58% have automated any ticketing tasks. Over 70% of high-performing MSPs have automated at least 30% of their workflows.

The useful way to think about automation maturity isn't a percentage - it's a ladder.

Rung 1 - Alerting (10-15% labor freed): Notify a tech when a backup fails, CPU spikes, or a login anomaly triggers. Most MSPs are here. Risk is minimal; the human still decides on action.

Rung 2 - Enrichment (15-20% freed): Auto-attach device history, recent tickets, and relevant documentation to the incoming ticket before a tech touches it. Still low-risk, but you've just cut the triage time on every ticket.

Rung 3 - Guided action (25-35% freed): Suggest remediation steps, pre-fill commands, require human approval before execution. The agent is doing the cognitive work; the tech is the approver.

Rung 4 - Supervised autonomy (40-50% freed): Execute approved runbooks - password resets, account unlocks, endpoint script runs - log every step, escalate on exception. This is where the margin unlock happens. Most MSPs are stuck between rungs 1 and 2; the ones at 18-20% EBITDA are operating at rung 4 for their high-volume L1 work.

Rung 5 - Full autonomy (60-80% freed): Resolve tickets end-to-end within defined guardrails. Higher risk profile; requires audit trails, rollback capability, and clear exception escalation rules. Research suggests up to 80% of routine tickets are auto-resolvable at this level.

The realistic 12-month target for most MSPs isn't rung 5. It's moving 40% of repetitive work from human to supervised-autonomous. That single shift frees $240K in capacity on a $2.5M shop - enough to either redeploy those tech-hours to higher-margin work or stop the next hiring cycle.

The ticket cost differential is real. An L1/helpdesk ticket costs approximately $22 to resolve. The same ticket escalated to desktop support costs approximately $62 - a 2.8x premium for the exact same resolution. Keeping tickets at L1 through automation is one of the most straightforward margin moves in the business.

A note on AI copilot risk

Not all automation moves are clean wins. AI copilot fees from individual vendors can add 2-3% of revenue - $50-75K on a $2.5M shop - on top of the base tool license. If you have 19 tools, each with their own AI meter, the automation savings get partially clawed back in per-query fees. The benchmark shops are consolidating the automation layer, not layering another vendor on top of the existing stack.

Pax8's CEO has warned that MSPs that fail to pivot to AI could lose 30-50% of their margins. The context matters: the risk isn't from automation itself - it's from letting vendors own the telemetry and therefore the value. The shops that retain margin through automation are the ones who control the automation layer, not the ones who buy AI add-ons from every existing vendor.

Hiring and workforce benchmarks

The staffing side of the benchmark picture tells a story most MSP owners already know from their own hiring queue.

52% of channel companies report experiencing a workforce shortage, per CompTIA's IT Industry Outlook. 16% of MSPs report difficulty hiring skilled technicians - up from 9% in 2025. Onboarding a new tech to full productivity takes 3-6 months.

The structural tension: as MSPs try to scale past $2-5M in revenue, the traditional answer is to hire. But many MSPs hit a growth ceiling at that range because every new customer requires a new hire, and every new hire compresses margins. The only sustainable way out is increasing the endpoint-to-tech ratio - which means automation.

On performance management: 67% of MSPs conduct performance reviews annually or not at all. Only 14% run quarterly structured check-ins. Retention problems often have roots in management process, not just compensation.

SLA and service delivery benchmarks

The standard SLA metrics - uptime percentage, ticket response time, customer satisfaction scores - are necessary but not the leading indicators. By the time a client escalates a ticket or churns, the SLA failure already happened.

The benchmark shift among top-performing MSPs is from lagging operational metrics (tickets closed, endpoints managed) to leading indicators of service risk: queue growth, aging unresolved incidents, repeat escalations, asset non-compliance rates.

64% of MSP clients want best-practice guidance beyond the tools, according to Kaseya's 2025 benchmark. 63% prefer fewer vendors to meet their technology needs. Both numbers are pointing the same direction: clients want a simpler, more strategic relationship, not more tickets resolved slightly faster.

The practical implication: MSPs investing in QBRs and proactive communication are seeing higher retention and lower churn. Customer success, in this model, is a profit center.

The benchmark checklist

If you want to know quickly where you stand, here are the five numbers worth pulling from your PSA today:

If your endpoints-per-tech is below 150: You're either over-staffed or under-automated. Probably both. The fix is automation before hiring.

If your tool spend is above 25%: An audit will almost certainly surface $100K+ in redundant or underused licensing. Consolidation to 4-5 core platforms typically pays for itself in 6-12 months through reduced license cost alone, before touching labor.

If your EBITDA is below 9%: This is a cost structure problem. Pricing increases help at the margin, but the fix is in the 53% that's going to tools and repetitive labor.

If your repetitive work percentage is above 50%: You're running a headcount-scaling model, not an automation-scaling model. Every new customer will cost you a new tech. The benchmark shops have inverted this ratio.

"Profitability is structural, not cyclical. Best-in-class shops operate at 18-20% EBITDA year over year. Bottom quartile struggles at 5% or less." - r/MSP community consensus

Valuation benchmarks: what these numbers mean at exit

For MSP owners thinking about eventual sale, the operational benchmarks above aren't just internal management tools - they're what determines your exit multiple.

The median MSP acquisition multiple is 8.9x EBITDA. The range is wide: 3-5x revenue for sub-$5M shops, up to 14x for scaled, AI-enabled, or high-growth operators. MSPs grew revenue 9.6% and adjusted EBITDA 17.1% in 2025, and that EBITDA growth differential is exactly what multiple expansion looks like.

The math is straightforward: a $2.5M MSP at 10% EBITDA has an EBITDA of $250K. At 8.9x, that's a $2.2M exit. The same shop at 18% EBITDA has an EBITDA of $450K. At the same multiple, that's a $4M exit. The operational benchmarks above aren't just about managing a better business today - they're about what that business is worth tomorrow.

One in three MSPs named winning new business their single biggest challenge, per Kaseya's 2025 benchmark. That's the wrong thing to be worried about if your cost structure is at 53% before profit. Sort the operations first; the revenue side follows.

Try Rallied

If your MSP is running above 50% of technician time on repetitive L1 work - password resets, account unlocks, access provisioning, onboarding and offboarding - Rallied is worth looking at seriously.

Rallied is an AI technician that connects to your PSA, RMM, M365, identity systems, and documentation, and resolves L1 and L2 tickets autonomously. Not workflow suggestions, not summarization - it takes first touch on every ticket, diagnoses the issue against live client context, and closes it. Password reset? Done in M365 and logged to the ticket. New hire? Full M365 provisioning, group membership, Teams, shared mailbox. Offboarding? Delegated mailbox, group removal, credential rotation, PSA notes.

Most MSPs go live in under a week, with no workflow library to build first. Rallied starts in Plan Mode - it posts what it would do on every ticket without touching anything, so you can check its judgment against your real queue before it acts. Rallied is $150 a month, billed monthly, with 2,000 credits included. Each ticket costs 1, 3 or 8 credits depending on how much work the agent did on it, so a typical month covers about 700 tickets. Tickets it couldn't finish or wasn't allowed to act on are never charged.

The benchmark target is rung 4: supervised autonomy on your highest-volume L1 work. That's where the $240K in freed capacity lives on a $2.5M shop. Rallied is built for exactly that rung - and it gets there in a week, not a quarter.

Frequently Asked Questions

What is the benchmark for endpoints per technician at an MSP?

Top-quartile MSPs consistently hit 350 managed endpoints per technician. The industry average is closer to 156 - meaning most shops are leaving substantial efficiency gains on the table. If you're below 150 endpoints per tech, it's a signal that you're either over-staffed relative to your endpoint count or underusing automation.

What EBITDA margin should an MSP target?

Top-performing MSPs operate at 18-20% EBITDA margins. The median MSP lands at 9-11%, and anything below 5% is a structural problem, not a growth problem. If you're stuck at median margins, the fix is almost always in your cost structure - tool spend and repetitive labor - before pricing.

How much should an MSP spend on tools?

The optimized benchmark is 22% of revenue on tools. Most MSPs are spending closer to 29%, once you count RMM, PSA, EDR, SIEM, backup, identity, documentation, and AI copilots correctly. On a $2.5M shop, that's a $175K annual gap. Consolidating to 4-5 core platforms typically closes most of it within 12 months.

What percentage of MSP tickets can be automated?

Research suggests up to 80% of routine tickets are auto-resolvable at full autonomy, but a realistic 12-month target for most MSPs is moving 40% of repetitive work to supervised-autonomous. That frees roughly $240K in technician capacity on a $2.5M shop - enough to shift two techs from L1 grunt work to higher-margin service delivery.

What is a healthy billable utilization rate for MSP technicians?

Top-performing technical teams consistently achieve 78-82% billable utilization. Below 70% is a warning sign of over-hiring or inefficient processes. Above 85% tends to be unsustainable and leads to burnout. Revenue per technician of $150K-$200K annually is the benchmark for healthy shops.