MSP KPIs: The 5 Metrics That Matter
MSPs have more operational data than almost any other service business. RMM dashboards, PSA reports, financial statements, ticket metrics, SLA compliance rates - the average MSP has access to dozens of metrics. The problem isn’t measurement. It’s knowing which five numbers actually predict profitability and growth, and which are noise that creates the illusion of management.
Across 160+ structural analyses, these five KPIs together explain roughly 80% of the performance variation between MSPs in the $600K-$2M revenue band. An MSP that gets these five right and ignores everything else will outperform one that tracks 30 metrics but misses these five.
1. MRR as Percentage of Total Revenue
What it is: Contracted monthly recurring revenue divided by total revenue.
Why it matters: This is the defining metric of MSP health. It measures how much of the business is predictable. Below 60% means the MSP is running a hybrid model that captures the worst characteristics of break-fix and managed services.
| Level | MRR % | What It Means |
|---|---|---|
| Struggling | Below 50% | More project/break-fix than managed. Not really an MSP model. |
| Average | 55-65% | Typical. Still too dependent on project revenue. |
| Healthy | 65-78% | Strong managed base with project upside. |
| Best-in-Class | 78-90% | Predictable, valuable, sellable. |
The 15-point gap between average and healthy might not look dramatic, but on a $1M MSP it’s $150K in revenue shifting from unpredictable project work to contracted recurring. That shift improves cash flow forecasting, reduces sales pressure, and increases business valuation by 20-30%.
Every 10 percentage points of MRR increase correlates with roughly 2-3 percentage points of EBITDA improvement. The margin gain comes from operational efficiency - managed service delivery is scheduled, batched, and systematic. Project work is reactive, custom, and scope-creep-prone.
2. Per-User Pricing
What it is: Average monthly fee per managed user across all clients.
Why it matters: Per-user pricing is the single largest profit lever in the MSP model. It determines gross margin per client, which determines whether growth adds profit or just adds work.
| Level | Per-User | Margin Impact |
|---|---|---|
| Below market | Below $140/mo | Losing money on delivery after tool costs |
| Average | $150-$185/mo | Thin margins. Dependent on project revenue to be profitable. |
| Healthy | $185-$250/mo | Sustainable margins. Security stack included. |
| Premium | $250-$325/mo | Full compliance + security. Highest margins. |
The industry average of $185/month was set when the security landscape was simpler. Today’s delivery costs run $80-$120 per user per month. At $185, margins are $65-$105 per user - tight but workable. At $150, margins are $30-$70 - barely covering overhead allocation. At $250+, margins are $130-$170 per user - enough to fund growth.
MSPs that have repriced around a security-first stack see a 42% premium on average. That’s not a marginal improvement. It’s the difference between a break-even business and a profitable one.
3. Endpoints per Technician
What it is: Total managed endpoints divided by full-time-equivalent technicians.
Why it matters: This is the staffing efficiency metric that prevents the two most common MSP failures - overstaffing (which kills margins) and understaffing (which kills service quality and then kills clients).
| Level | Endpoints/Tech | What’s Happening |
|---|---|---|
| Underutilized | Below 200 | Paying for capacity you’re not using |
| Healthy range | 230-280 | Balanced efficiency and service quality |
| Average | 280-320 | Workable but tight on complex environments |
| Strained | Above 350 | Response times slipping, quality declining |
The benchmark of approximately 250 endpoints per tech is a starting point, not a universal rule. Complex environments (healthcare, finance, manufacturing with OT) might require 180-220. Simple environments (professional services, retail) can run 280-320 without quality issues.
Track this weekly. When you onboard a new client or lose one, the ratio shifts immediately. Having visibility on the ratio in real time prevents the reactive hiring-and-firing cycle that kills team morale and operational consistency.
4. Client Concentration
What it is: Revenue percentage from your top 1 and top 3 clients.
Why it matters: MSPs at this revenue band often have 2-3 clients representing 30-40% of total revenue. Those clients have enormous leverage, and the MSP knows it. Pricing conversations get deferred. Scope creep gets tolerated. And the business runs on a dependency that a single client decision could shatter.
| Level | Top Client | Top 3 Clients | Risk |
|---|---|---|---|
| Dangerous | Above 30% | Above 45% | One departure threatens the business |
| Risky | 20-30% | 35-45% | Meaningful vulnerability |
| Healthy | 15-20% | 25-35% | Manageable concentration |
| Diversified | Below 15% | Below 25% | Resilient to any single loss |
Use the Revenue Fragility Calculator to model the impact of your largest client leaving. If the scenario is survivable but painful, diversification should be the growth priority. If it’s existential, it’s urgent.
The healthiest MSPs cap any single client at 15% of revenue - not by turning away large clients, but by growing the base so that no single relationship has existential weight. See the full MSP benchmarks for the client concentration analysis.
5. Revenue per Employee
What it is: Total annual revenue divided by full-time-equivalent headcount.
Why it matters: This single number captures pricing power, operational efficiency, and utilization. It predicts whether the next hire will add to profitability or dilute it.
| Level | Revenue/Employee | Signal |
|---|---|---|
| Over-staffed | Below $110K | Hiring ahead of revenue or underpricing |
| Average | $120K-$140K | Typical MSP. Room to optimize. |
| Healthy | $140K-$175K | Efficient operations, good pricing |
| Best-in-Class | $175K-$220K | Premium pricing, lean operations |
The path to higher revenue per employee runs through pricing (higher per-user rates), automation (fewer hours per endpoint on routine tasks), and service mix (more managed MRR, less break-fix labor). The Revenue per Person Calculator shows where your team stands against these benchmarks.
Tracking These Five Together
The five metrics interact. High MRR percentage enables better revenue per employee because managed work is more efficient than project work. Healthy per-user pricing creates the margin that keeps endpoints per tech in the right range (you can afford enough staff). Low client concentration means pricing conversations aren’t held hostage by dependency.
Monthly review. One dashboard. Five numbers. 15 minutes. That’s what separates the MSPs that are building equity from the ones that are building a treadmill.