MSP KPIs: 12 Metrics, Benchmarks and a Free Checker

Most MSP owners track revenue. Some track profit. Very few track the handful of metrics that actually predict whether their business is getting healthier or slowly dying. The difference between an MSP that gets a strong offer from a buyer and one that closes its doors is almost always visible in the numbers — months or years before the outcome is obvious.

This guide covers the 12 KPIs that matter most for MSP operations, with how to calculate each one, which ones have a real public benchmark (and which do not), and specific actions you can take when a metric is off track.

If you're still building your MSP foundation, start with our guides on what an MSP is and how to start an MSP business. This article assumes you have clients and revenue to measure.

Why Most MSPs Track the Wrong Things

Here's a common pattern, with illustrative numbers: an MSP owner opens their accounting software, sees that revenue is up 20% year over year, and feels great. But buried underneath that number, three things are going wrong simultaneously. Gross margins are declining because they hired a technician they didn't need yet. Their largest client now represents 30% of revenue. And ticket volume per endpoint is climbing, which means they're not being proactive enough.

Revenue is a lagging indicator. By the time revenue declines, the problems that caused it have been festering for months. Leading indicators — the KPIs in this guide — let you catch problems early and course-correct before they hit your bank account.

The other mistake is tracking too many things. If you have a dashboard with 47 metrics, you effectively have zero metrics because no one is paying attention to any of them. Focus on these 12. Review them monthly. Act on the ones that are off target.

What Most MSPs Actually Track

Before the list, a reality check on current practice. ScalePad's 2026 survey of MSPs found MRR is the most-tracked financial metric, and only about a third of MSPs track client churn.

58%

ScalePad, 2026 MSP Trends Report, 2026Vendor surveyVerified 2026-10-11

If you track MRR and churn consistently, you are already ahead of most. The twelve metrics below add the delivery and profitability measures that explain why those two move.

The 12 KPIs That Matter

1. Monthly Recurring Revenue (MRR)

What it measures: Total predictable revenue from managed services contracts, billed monthly.

How to calculate: Sum of all recurring monthly contract values. Do not include project revenue, break-fix hours, hardware sales, or one-time fees.

Target: There is no meaningful absolute target; it depends entirely on your size and goals. The trend and the ratio matter more.

MRR ratio target (MSPCoach rule of thumb, no neutral public benchmark): 70-90% of total revenue should be recurring. If your MRR ratio is below 60%, your business is too dependent on project work and you don't have a managed services business — you have a break-fix shop with some contracts.

How to improve:

• Convert break-fix clients to managed agreements. Even a basic monitoring + help desk package converts unpredictable revenue to recurring.
• Add security and compliance packages on top of base managed services. These are high-margin recurring add-ons.
• Eliminate or minimize one-time project work that doesn't lead to recurring relationships.

Review frequency: Monthly. Track MRR growth rate (month over month) and net MRR change (new MRR minus churned MRR).

For more on building predictable income, see our guide on MSP pricing models.

2. Client Churn Rate

What it measures: The percentage of clients (or MRR) lost in a given period.

How to calculate:

• Logo churn: (Clients lost in period / Total clients at start of period) x 100
• Revenue churn: (MRR lost from churned clients / Total MRR at start of period) x 100

Always track revenue churn — it's more meaningful. Losing a $500/month client is different from losing a $15,000/month client.

Target (MSPCoach rule of thumb, no neutral public benchmark): Under 10% annual revenue churn, and a rising trend is a warning sign whatever the level. We found no neutral public churn benchmark, so we do not quote a market range.

Why it matters more than you think:

How to improve:

• Implement Quarterly Business Reviews (QBRs). Most clients who churn feel ignored or undervalued. Proactive communication fixes this.
• Track satisfaction systematically — post-ticket surveys, quarterly NPS, regular check-ins.
• Identify at-risk clients early. Warning signs: decreasing ticket volume (they've stopped calling because they've given up), late payments, unresponsiveness to QBR invitations.
• Use 12-36 month contracts where clients will accept them, but do not rely on contract length to hide poor service.

Review frequency: Monthly. Calculate trailing 12-month churn for trend analysis.

3. Customer Satisfaction Score (CSAT)

What it measures: How satisfied clients are with your service, typically measured after ticket resolution.

How to calculate: (Number of positive responses / Total responses) x 100. Most MSPs use a simple thumbs up/thumbs down or 1-5 scale after each ticket closure.

Target (MSPCoach rule of thumb, no neutral public benchmark): 95%+ positive satisfaction. Below 90% is a red flag. Below 85% suggests systemic service delivery problems. Response rates and survey design change the number, so compare against your own trend first.

How to improve:

• Respond fast. In our experience first response time is often what clients notice first, ahead of resolution time. Clients want to know you've seen their problem and are working on it.
• Set realistic expectations. If a fix will take 4 hours, say so. Clients get frustrated by silence, not by timelines.
• Follow up on negative ratings personally. Every negative CSAT response should trigger a call from a manager within 24 hours.
• Track CSAT by technician. Often, poor CSAT scores cluster around one or two team members who need coaching on communication, not technical skills.

Review frequency: Weekly (aggregate), with real-time alerts on negative responses.

4. First Response Time

What it measures: How quickly your team acknowledges a new ticket or request.

How to calculate: Average time from ticket creation to first meaningful response (auto-replies don't count).

Target (example SLA tiers, MSPCoach rule of thumb; set yours from your contracts and staffing):

• Critical/emergency: Under 15 minutes
• High priority: Under 1 hour
• Normal priority: Under 4 hours
• Low priority: Under 8 hours (same business day)

Why this matters so much: A client who gets a response in 10 minutes saying "we see this, investigating, will update within 2 hours" is usually happier than a client who hears nothing for 3 hours and then gets a fix.

How to improve:

• Implement auto-triage that categorizes and routes tickets based on content and client.
• Staff dedicated triage roles during business hours. At least one person should be watching the queue at all times.
• Set up SLA timers in your PSA with escalation alerts when response windows are approaching.

Review frequency: Weekly. Track by priority level and by client.

5. Mean Time to Resolution (MTTR)

What it measures: Average time from ticket creation to confirmed resolution.

How to calculate: Sum of all resolution times / Number of tickets resolved in the period.

Target (example thresholds, MSPCoach rule of thumb, no neutral public benchmark):

• Password resets, simple how-to: Under 30 minutes
• Standard workstation issues: Under 4 hours
• Server/network issues: Under 8 hours
• Complex projects: Define per-project SLAs

Aggregate target (rule of thumb): Under 8 hours for all tickets combined. Resolution-time benchmarks vary widely with ticket mix, so track the trend by category rather than chasing a single number.

How to improve:

• Build and maintain a knowledge base. If the same issue gets resolved 20 times by 5 different techs, the fix should be documented once and reused.
• Automate common remediations. Password resets, printer driver reinstalls, disk cleanup, service restarts — all of these can be automated or self-service.
• Reduce escalations. Every escalation adds hours to resolution time. Train Tier 1 techs to handle more issues independently.
• Track reopens. If tickets are getting "resolved" but reopened within 48 hours, your MTTR looks good but your actual performance is worse than it appears.

Review frequency: Monthly. Segment by ticket category to identify which issue types take longest.

6. Technician Utilization Rate

What it measures: The percentage of a technician's available time spent on billable or productive work.

How to calculate: (Productive hours / Total available hours) x 100. Productive hours include ticket work, project work, and proactive maintenance. Non-productive hours include idle time, internal meetings, training, and admin work.

Target (MSPCoach rule of thumb, no neutral public benchmark): 65-80%. Below 60%, you're overstaffed or your techs are spending too much time on non-billable activities. Above 85%, your team is overloaded and heading for burnout and quality problems.

The sweet spot is 70-75%. This leaves enough capacity to absorb spikes without burning people out.

How to improve (if too low):

• Reduce unnecessary internal meetings.
• Audit admin time — are techs spending hours on documentation that could be automated?
• Fill gaps with proactive work: security audits, optimization projects, documentation updates.
• If consistently below 60% with no proactive work to fill the gap, you may need to hold off on your next hire. To size a hire from workload, see hiring for an MSP.

How to improve (if too high):

• Hire before you're desperate. By the time utilization hits 85%+, service quality is already degrading.
• Implement automation to offload repetitive tasks.
• Outsource after-hours monitoring or Tier 1 overflow to a NOC partner.

Review frequency: Monthly per technician and as a team average.

7. Endpoints per Technician

What it measures: The number of managed endpoints (workstations, servers, network devices) per service delivery team member.

How to calculate: Total managed endpoints / Number of service delivery staff (include all techs, not just Tier 1).

Target: No neutral public benchmark exists for endpoints per technician, and it varies with environment complexity, so we do not quote a range. Measure your own ratio and watch the trend.

Why this matters: This ratio directly determines your cost to serve and therefore your gross margins.

How to improve:

• Invest in RMM automation. Every scripted remediation increases the number of endpoints each tech can handle.
• Standardize client environments. The more similar your clients' setups are, the less unique troubleshooting your team needs to do.
• Build runbooks for common scenarios so junior techs resolve issues that currently require senior escalation.
• Use AI-powered ticket triage and automated first-touch diagnostics, after measuring a baseline (see where AI pays back in service delivery).

Review frequency: Monthly. Track the trend — it should be gradually increasing over time.

8. Gross Margin

What it measures: Revenue minus direct costs (technician salaries, tool costs, license costs) as a percentage of revenue.

How to calculate: ((Revenue - Direct Costs) / Revenue) x 100. Direct costs include: tech salaries and benefits, RMM/PSA/security tool subscriptions, third-party NOC or help desk costs, Microsoft/vendor license costs (if you resell at a margin). Do NOT include owner salary, sales, marketing, rent, or G&A — those are overhead, not COGS.

Target (MSPCoach rule of thumb, no neutral public benchmark): 50-70%. Published gross-margin targets conflict because they use different definitions of direct cost, so define yours first. Below 50%, you're either underpricing your services or overspending on delivery. Above 70%, you're either very efficient or may be underinvesting in your team and tools.

How to improve:

• Raise prices. Seriously. Most MSPs are underpriced. If your gross margin is below 50%, pricing is almost certainly the primary issue.
• Audit tool spend quarterly. MSPs accumulate SaaS subscriptions like barnacles on a hull. Cut anything you're paying for but not actively using.
• Improve technician efficiency (see endpoints per technician above). Every efficiency gain goes straight to gross margin.
• Negotiate vendor contracts annually. Don't auto-renew at list price.

Review frequency: Monthly. Track per-client gross margin quarterly to identify unprofitable accounts.

9. EBITDA Margin

What it measures: Earnings Before Interest, Taxes, Depreciation, and Amortization as a percentage of revenue. This is the metric acquirers and investors care about most.

How to calculate: ((Revenue - All Operating Expenses) / Revenue) x 100, adding back interest, taxes, depreciation, and amortization.

Benchmarks (sourced): The best-in-class line comes from Service Leadership, which is owned by ConnectWise: 19% or more adjusted EBITDA, held for a sixth consecutive year. Adjusted EBITDA adds back owner compensation above market and other one-offs, so it is not the same as net profit. For net profit, the best public distribution is Kaseya's 2026 survey.

19%+

Service Leadership, 2026 Annual IT Solution Provider Industry Profitability Report (press release, 2026-06-23), 2026Vendor-owned indexVerified 2026-10-11

10%

Kaseya, 2026 State of the MSP Report, 2026Vendor surveyn=1,061Verified 2026-10-11

Neither figure is a target for your business; they show where surveyed MSPs sit. Kaseya's net profit bands are in its 2026 report, and our KPI benchmark checker shows where your own margin falls against them. For the full distribution and the differences between gross, net and EBITDA margin, read MSP profit margins.

Why EBITDA matters for valuation: Buyers price an MSP on adjusted EBITDA multiplied by a multiple that depends heavily on deal size. Published multiples for small deals are much lower than headline figures, so be cautious with any rule you read. The median multiples by deal size from Aventis Advisors are below, and the valuation estimator shows the maths. Our guide to MSP valuation by deal size goes deeper.

5.2x

Aventis Advisors, MSP Valuation Multiples (2025-01-22), 2025M&A advisorn=120Verified 2026-10-11

How to improve:

• Focus on gross margin first (see above). You can't have good EBITDA with bad gross margins.
• Control overhead. Rent, admin staff, and owner perks are the usual suspects.
• Scale revenue without proportional overhead growth. Your office rent and back-office cost shouldn't increase linearly with revenue.
• Pay yourself a market-rate salary and measure EBITDA after that salary. Owners who pay themselves nothing overstate EBITDA, and acquirers adjust for it.

Review frequency: Monthly. Compare to trailing 12-month average to identify trends.

10. Revenue per Employee

What it measures: Total revenue divided by total headcount (full-time equivalents).

How to calculate: Annual revenue / Total FTE count. Include all employees — techs, sales, admin, management.

Target: No neutral public benchmark exists for revenue per employee. Ranges quoted online are consultant rules of thumb with no source, so we do not repeat them. We plan to publish one from assessment data once the sample is large enough.

How to improve:

• Improve pricing per endpoint.
• Increase automation so each employee generates more output.
• Be disciplined about hiring. Every new hire should be justified by a clear revenue capacity calculation, not "we feel busy."
• Consider outsourcing non-core functions (bookkeeping, after-hours help desk) rather than hiring.

Review frequency: Quarterly. Track the trend — it should be stable or increasing.

11. Client Concentration Risk

What it measures: How dependent your revenue is on your largest clients.

How to calculate: (Largest client MRR / Total MRR) x 100. Also calculate: (Top 5 clients MRR / Total MRR) x 100.

Target (MSPCoach rule of thumb, no neutral public benchmark): No single client above 15% of MRR. Top 5 clients below 40% of MRR. If your largest client is more than 20% of revenue, losing them would be an existential event.

Why acquirers care: Buyers generally treat client concentration as a risk. An MSP with $40K MRR spread evenly across 30 clients looks less risky than one with the same MRR where a single client represents $12K (illustrative numbers).

How to improve:

• Actively grow your client base to dilute concentration. The fastest fix is adding new clients, not reducing service to existing ones.
• Avoid the trap of over-servicing your largest client at the expense of growing smaller ones.
• If you lose a major client, treat it as validation that concentration is a risk — not as an argument for finding another whale.

Review frequency: Monthly. Display as a visual (bar chart of client MRR distribution).

12. Net MRR Growth Rate

What it measures: The net change in MRR after accounting for new business, expansions, contractions, and churn.

How to calculate: ((New MRR + Expansion MRR - Contraction MRR - Churned MRR) / Starting MRR) x 100

• New MRR: Revenue from brand new clients
• Expansion MRR: Revenue increases from existing clients (upsells, added users, new services)
• Contraction MRR: Revenue decreases from existing clients (downsized, dropped services)
• Churned MRR: Revenue from clients who cancelled entirely

Target: There is no neutral public benchmark for net MRR growth. Aim for a positive, steady trend. Near zero means you are adding clients at roughly the rate you are losing them. For context on annual revenue growth (not MRR), Service Leadership reports the following for MSPs in 2025:

9.6%

Service Leadership, 2026 Annual IT Solution Provider Industry Profitability Report (press release, 2026-06-23), 2026Vendor-owned indexVerified 2026-10-11

Why this is the ultimate KPI: Net MRR growth captures your entire business performance in a single number. It reflects your sales effectiveness (new MRR), your account management (expansion MRR), your service quality (churn and contraction), and your pricing power — all in one metric.

How to improve:

• Focus on expansion revenue from existing clients. Upselling an existing client usually needs less selling effort than winning a new one. Security packages, advisory and compliance add-ons are natural expansion paths.
• Reduce churn through the tactics described under Client Churn Rate above.
• Maintain pricing discipline. Discounting to win new clients drags down your net MRR growth even when logo count grows.

Review frequency: Monthly. This is the first number you should look at every month.

KPI Definitions at a Glance

Benchmark Yourself

Net margin and MRR per client are the two measures with a published distribution. Enter yours and see where you fall, with every benchmark source shown. No signup.

Building Your KPI Dashboard

Knowing which KPIs to track is step one. Actually tracking them consistently is where most MSPs fail. Here's a practical approach:

Week 1: Set up a simple spreadsheet with all 12 KPIs. Populate the current values as best you can. Many of these you can pull from your PSA and RMM.

Week 2-4: Identify which metrics you can automate. Your PSA should be able to report on CSAT, MTTR, first response time, and utilization. Your accounting software handles MRR, gross margin, and EBITDA. Client concentration can be calculated from your billing data.

Monthly ritual: Block 2 hours on the first Monday of every month to review all 12 KPIs. Look at the trend lines, not just the current values. A gross margin of 55% is fine — a gross margin that's been declining from 62% to 55% over six months is a problem.

Share selectively: Your technicians should see CSAT, response time, MTTR, and utilization. Your service manager should see all delivery metrics. Financial metrics (gross margin, EBITDA, client concentration) may be appropriate for senior leadership but don't need to be shared company-wide.

The KPIs You Should NOT Obsess Over

A few metrics that MSP owners often over-index on, and why they can be misleading:

Total ticket volume. More tickets isn't necessarily bad (growing client base) and fewer tickets isn't necessarily good (clients stopped reporting because they gave up). Volume without context is noise.

Total headcount. Hiring more people feels like growth but is meaningless without revenue-per-employee context. Some of the most profitable MSPs are surprisingly lean.

Website traffic. Vanity metric unless you're tracking conversion to qualified leads. 10,000 visitors that generate zero leads is worth less than 500 visitors that generate 5 demos.

Win rate in isolation. A 90% win rate might mean you're only pursuing easy deals and leaving harder (but valuable) opportunities on the table. Win rate matters, but in context with deal size and pipeline volume.

Summary: The KPI Hierarchy

If you can only track five metrics, track these:

1. Net MRR growth rate — your single best indicator of overall business health
2. Gross margin — are you making money on the work you deliver?
3. Client churn rate — are clients staying and growing?
4. Technician utilization — is your team productive?
5. CSAT — are clients happy with the experience?

Everything else matters, but these five will tell you most of what you need to know.

The best MSP owners don't just track numbers — they build systems around them. When a metric dips below target, there's a defined response. When a trend line moves in the wrong direction for two consecutive months, it triggers a review. When targets are consistently hit, they get raised.

For more on the operations side, see the MSP operations hub and our guide to documentation best practices. If you want a structured assessment of how your MSP is performing across the dimensions that matter — not just financial metrics but operational maturity, service delivery, and growth readiness — we've built a tool for that.

---

Ready to measure what matters? Take the free MSP Readiness Assessment to get a personalized scorecard across the operational, financial, and strategic dimensions that determine MSP success. It takes about 10 minutes and gives you a clear picture of where to focus.