Direct Answer

What are healthy benchmarks for a managed service provider?

A healthy MSP at $600K-$2M should target 55-62% gross margins, 18-23% EBITDA, and $140K-$175K revenue per employee. Per-user pricing should sit at $185-$250/month for SMB clients, with MRR composing 65-78% of total revenue. Client churn at 8-12% annually. The defining tension is the break-fix to managed services transition - recurring revenue is the business model, but many MSPs still generate 25-40% of revenue from project and break-fix work that undermines predictability.

MSP

MSP Business Benchmarks

Managed service providers occupy one of the best structural positions in the service economy. Recurring revenue, multi-year contracts, high switching costs, and a client base that literally cannot function without the service. On paper, it’s a perfect business model. In practice, most MSPs between $600K and $2M are leaving significant margin on the table because of pricing decisions made when the business was smaller and service mix decisions that dilute the recurring revenue advantage.

These benchmarks cover the $600K-$2M revenue band, which maps to most 5-10 person MSPs. The data comes from structural analysis, with MSPs showing some of the most consistent operational patterns of any industry - which makes the performance gaps between average and best-in-class even more instructive.

Financial Benchmarks

MetricRangeNotes
Revenue (5-10 person MSP)$500K-$1.5MMost common band. Above $1.5M usually requires 10+ people.
Revenue (upper band)$1.5M-$2MRequires strong MRR base and efficient operations.
Gross Margin50-65%Service revenue: 50%+. Product/hardware: 20-30%. Blended: 55-65%.
Net Margin (EBITDA)12-25%Industry average 18.4%. Top quartile above 22%.
Per-User Pricing (SMB)$150-$300/user/moIndustry average $185. Security stack adds 42% premium.
MRR per Client$1,500-$5,000/moBelow $1,500 usually means underpriced or micro-clients.
Endpoints per Tech~250Benchmark for staffing decisions. Above 300 = strained. Below 200 = underutilized.
Revenue per Employee$120K-$200KIndustry average $142K. Below $120K indicates overstaffing.
MRR as % of Total Revenue60-80%The defining metric of MSP health. Below 60% means too much project/break-fix.
Annual Client Churn8-15%Below 10% is strong. Above 15% indicates service delivery or fit problems.

What “Healthy” Looks Like

MetricStrugglingAverageHealthyBest-in-Class
Gross MarginBelow 45%50-55%55-62%62-68%
Net Margin (EBITDA)Below 10%14-18%18-23%23-28%
Revenue/EmployeeBelow $110K$120K-$140K$140K-$175K$175K-$220K
Per-User PricingBelow $140$150-$185$185-$250$250-$325
MRR % of TotalBelow 50%55-65%65-78%78-90%
Client ChurnAbove 18%12-15%8-12%Below 8%
Endpoints/TechAbove 350280-320230-280200-230
Client Concentration (top 3)Above 45%30-40%20-30%Below 20%

Two numbers in this table deserve extra attention. Per-user pricing and MRR percentage together explain roughly 70% of the profitability variation between MSPs in this revenue band. An MSP charging $180/user with 60% MRR and an MSP charging $250/user with 80% MRR are in fundamentally different businesses - even if their top-line revenue looks similar.

MSP Revenue Benchmarks by Tier

TierTotal Revenue
StrugglingBelow $500K
Average$600K-$900K
Healthy$900K-$1.5M
Best-in-Class$1.5M-$2M+

Revenue per employee is the check on those totals. At the industry average, a 7-person MSP should generate roughly $1M. Below that, every new hire dilutes profitability. Above it, each hire adds to it. The number goes up through per-user rates that reflect 2026 delivery costs, automation of repetitive work (patch management, monitoring alerts, ticket routing), and dropping low-margin service lines that consume tech hours without proportional revenue. The Revenue per Person Calculator shows where your team falls.

The cheapest growth is selling more to existing clients. Most MSPs spend 80% of their growth effort on acquisition and 20% on expansion, when the math favors the reverse. When you do add clients, target $2,500+ a month in MRR so the onboarding cost and ongoing management overhead are justified.

MSP Profit Margins by Service Line

The blended gross margin in the tables above hides the mix underneath it. The MSPs that grow profit, and not just headcount, track margin by service line.

Service LineGross Margin RangeNotes
Managed services (core MRR)50-65%The engine. This is where the model works.
Security services (add-on MRR)55-70%Higher margin because tools scale across clients.
Project work (implementations)35-50%Labor-heavy. Scope creep erodes quoted margins.
Break-fix / hourly40-55%Unpredictable. High visible margin, low actual margin after unbilled time.
Hardware / product resale20-30%Necessary for some clients but margin-dilutive.
Cloud / SaaS resale10-20%Thin pass-through margins unless bundled with managed services.

If blended gross margin is below 50%, the cause is almost always too much revenue in hardware, cloud resale and break-fix, and not enough in managed and security MRR.

Security earns the top margin because the tools scale. A security stack (EDR, SIEM, MFA management, backup) costs $30-$60 per user per month in licensing, and roughly the same monitoring infrastructure and labor overhead covers 50 users or 500. At 50 users, tool cost is the dominant expense. At 200+ users it is amortized, and the margin on each incremental user is 70%+.

The gap between average and best-in-class EBITDA is roughly 8 percentage points, which is $80K a year on a $1M MSP. That gap comes from pricing and service mix decisions.

How to Calculate Your Margins

The margin your accounting software shows is blended across every service line. To benchmark it properly:

  1. Separate revenue by service line. Managed MRR, security MRR, project, break-fix, hardware, cloud resale.
  2. Allocate direct costs to each line. Tool costs to managed and security, tech labor in proportion to hours, hardware at actual cost.
  3. Calculate gross margin per line. Gross margin = (line revenue minus line direct costs) / line revenue. This shows which services carry the business and which drag it down.
  4. Roll up to blended gross margin, then EBITDA. EBITDA margin = (blended gross profit minus operating expenses) / total revenue. Operating expenses include rent, insurance, admin, sales and owner comp.

Run the blended result through the Profit Margin Calculator, then use the service-line view to find where the leakage is. The Client Profitability Calculator models the same economics one client at a time.

Where MSP Margins Leak

Break-fix tickets. A technician resolves an issue in 2 hours at $175/hour: $350 in revenue against maybe $40-$50 in loaded labor cost, which looks like 85% gross margin. That ticket also took 45 minutes of dispatch coordination and 20 minutes of follow-up documentation, and it pulled a tech off a managed client’s project. Counting the full chain, the loaded cost is closer to $150-$180. The larger cost is opportunity: every break-fix hour is an hour not spent on managed delivery or on security assessments that upsell existing clients. The fix is converting your best break-fix clients to managed agreements with a plain pitch: you spent $X on break-fix last year, and for $Y a month we will prevent most of those issues and respond faster to the rest.

Project dependency. Project revenue is unpredictable, it creates staffing volatility, and it trains the sales effort to chase one-time deals instead of building the recurring base. A $1M MSP that moves $100K from project work (delivered unevenly, often at cost) to managed contracts (delivered monthly, at 55%+ margin) typically adds $30K-$50K to the bottom line without adding a client.

Tool sprawl. The average MSP in this band runs 8-12 security and management tools when 4-6 with overlapping coverage would do the same job. Consolidating saves $5-$15 per user per month in licensing without losing capability. At 500 users, that is $30K-$90K a year that drops straight to the bottom line.

Owner Compensation

MSP owner compensation is more straightforward than most service industries because the recurring revenue model creates predictable cash flow, which makes it easier to set a consistent salary.

Revenue BandTypical Owner CompNotes
$500K-$800K$80K-$120KOwner usually still doing Tier 2/3 technical work.
$800K-$1.2M$110K-$160KTransition zone. Owner starts to hand off technical escalations.
$1.2M-$2M$140K-$200KOwner focused on sales, strategy, and client relationships.

The MSP-specific wrinkle: many owners comp themselves below market because they see the business’s equity value as the real payoff. MSP valuations at this revenue band typically run 0.8-1.2x annual revenue for well-run companies, meaning a $1.5M MSP is worth $1.2M-$1.8M in a sale. That equity upside is real, but only if the owner is building a business that can sell - which means removing themselves from daily technical operations.

An MSP where the owner is the primary escalation point for every critical issue is worth significantly less than one where operations run independently. Buyers price in key-person dependency heavily.

Seasonal Patterns

MSPs are less seasonal than most service businesses because managed services are, by definition, ongoing. But patterns still exist.

PeriodPatternOperational Impact
January-MarchBudget allocation for IT spend. New fiscal year decisions.Best window for upselling existing clients and closing new ones.
April-JuneImplementation season. New clients onboarding.Heaviest project load. Staffing strain if poorly planned.
July-AugustSummer lull. Decision-makers on vacation.Maintenance mode. Good time for internal improvements.
September-OctoberQ4 planning. “Spend remaining budget” season.Hardware refresh and project spikes. Good for project revenue.
November-DecemberHoliday slowdown. Fewer moves. More support tickets (year-end closings).Renewal season for calendar-year contracts. Critical for retention.

The most important “season” for an MSP isn’t on the calendar - it’s the contract renewal cycle. MSPs with staggered renewal dates (contracts renewing across all 12 months) have dramatically more stable revenue than MSPs where contracts cluster in Q1 or Q4. If more than 30% of MRR renews in any single quarter, the business has concentration risk that feels like seasonality.

The Structural Pattern

The MSP model is one of the clearest examples of a transition business in the service economy. The transition has a name - break-fix to managed - and most MSPs in the $600K-$2M band are somewhere in the middle of it, running a hybrid model that captures the worst characteristics of both.

Break-fix IT is simple: something breaks, the client calls, you fix it, you bill for the time. Revenue is unpredictable, margins are moderate, and there’s no recurring relationship. Managed services is the opposite: monthly fee, proactive monitoring, preventive maintenance, predictable revenue. The entire MSP industry has been moving toward managed for two decades, and the economic argument is settled - managed wins on every metric.

And yet. The average MSP in this revenue band still generates 25-40% of revenue from project work and break-fix. The reasons are structural, not strategic. Project work has higher visible margins per engagement (clients see a $20K project as a big sale). Break-fix requests from managed clients are hard to turn away (“but we pay you monthly”). And the hardest one: many MSPs don’t price their managed agreements to include the full cost of service delivery, so they depend on project revenue to make up the margin gap.

This is the pricing problem that defines the MSP industry at this scale. The average per-user price of $185/month was set when the security stack was simpler, compliance requirements were lighter, and the client’s environment was less complex. That $185 was probably appropriate five years ago. Today, the cost to deliver a comprehensive managed service - including security tools (EDR, SIEM, backup, MFA management), compliance documentation, and the labor to monitor and respond - runs $80-$120 per user per month. At $185 all-in, the margin is thin. At $150, it’s almost nonexistent.

The MSPs that are thriving in this band have repriced around a security-first stack. Adding a security layer to a managed agreement commands a 42% premium on average - taking per-user pricing from $185 to $260+. Clients accept this because cybersecurity is no longer optional and they know it. The MSP that positions security as a premium add-on makes it easy for the client to say yes. The one that bundles it invisibly into the base price misses the pricing opportunity.

Client concentration is the second structural risk. 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 what amounts to a key-account dependency that a single client decision could shatter. 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.

Per-User Pricing Tiers

Most MSPs sell in three tiers, and the security premium shows up in the gaps between them.

Pricing TierPer-UserWhat’s Included
Basic managed$140-$180Monitoring, patching, basic support
Managed + security$200-$260Above + EDR, SIEM, MFA, backup
Full compliance$260-$325Above + compliance documentation, vCISO

The gap between basic and full compliance is $120-$145 per user per month. For a 50-user client, that is $6K-$7.25K a month in added revenue against $2K-$3K in incremental delivery cost.

Against current delivery costs, this is what each price point leaves per user:

Per-User PriceMargin per UserWhat It Means
Below $140NegativeLosing money on delivery after tool costs
$150$30-$70Barely covers overhead allocation
$185$65-$105Tight but workable
$250+$130-$170Enough to fund growth

The Five KPIs to Track

RMM dashboards, PSA reports, ticket metrics and SLA compliance rates give an MSP dozens of numbers. Five of them predict profitability and growth. The tier table near the top of this page sets the target for each. This table covers how to calculate them and how often to look.

KPIHow to CalculateReview
MRR % of revenue(MRR x 12) / total revenueMonthly
Per-user pricingAverage monthly fee per managed user, across all clientsQuarterly, adjust annually
Endpoints per techTotal managed endpoints / technical staff FTEWeekly
Client concentrationRevenue share of your top 1 and top 3 clientsMonthly
Revenue per employeeTotal annual revenue / FTE headcount, including ownerMonthly

MRR percentage. Every 10 percentage points of MRR increase correlates with roughly 2-3 percentage points of EBITDA improvement. The gain comes from delivery: managed work is scheduled and batched, while project work is reactive and prone to scope creep. Closing the gap from average to healthy MRR also increases business valuation by 20-30%.

Endpoints per tech. The benchmark assumes a typical client mix. Complex environments (healthcare, finance, manufacturing with OT) may need 180-220 endpoints per tech. Simple ones (professional services, retail) can run 280-320 without quality issues. Review it weekly, because onboarding or losing a client shifts the ratio immediately, and seeing it early prevents a reactive cycle of hiring and layoffs.

Client concentration. The tier table tracks your top three clients. Watch the single largest one too:

LevelTop Client ShareRisk
DangerousAbove 30%One departure threatens the business
Risky20-30%Meaningful vulnerability
Healthy15-20%Manageable concentration
DiversifiedBelow 15%Resilient to any single loss

Model your largest client leaving with the Revenue Fragility Calculator. If the result is survivable but painful, make diversification the growth priority. If it is existential, it is urgent.

How the Five KPIs Relate

The five move together. High MRR percentage lifts 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 range, since you can afford enough staff. Low client concentration keeps pricing conversations from being held hostage by one account. Strength in one does not make up for weakness in another, so review all five together on one dashboard each month. It takes about 15 minutes.

How to Benchmark Your MSP

MSPs deliver a similar core service on similar cost structures, so the benchmarks compare cleanly and a gap from them points to a specific cause with a specific fix.

Step 1: Pull and Score Your Numbers

Take seven data points from the trailing 12 months. Most live in your PSA or accounting software.

MetricWhere to Find ItNotes
Total revenueAccounting softwareAll sources: MRR, project, hardware, everything
MRRPSA or billing systemContracted monthly recurring revenue only
Per-user pricingPSAAverage across all managed clients
EBITDAP&L statementRevenue minus all operating expenses, including owner comp
Headcount (FTE)PayrollFull-time equivalents, including owner
Total managed endpointsRMM dashboardAll devices under management
Top 3 client revenueBilling recordsCombined revenue from your three largest clients

Work out the ratios with the formulas in the KPI table, then place each one in the struggling, average, healthy or best-in-class column of the tier table.

Step 2: Calculate Your Cost to Serve

This is the number most MSPs have never calculated, and it matters most for pricing.

Per-user cost to serve = (tool costs + allocated labor + overhead) / total managed users

ComponentHow to Calculate
Security tools (EDR, SIEM, backup, MFA)Sum all per-user tool licensing
Monitoring and management tools (RMM, PSA)Platform costs divided by users
Allocated laborTech compensation x time allocation / users
Overhead allocationNon-labor operating expenses / users

Subtract cost to serve from your per-user price. A gap under $50 per user is too thin to sustain the business. A gap of $80-$120 is healthy.

Step 3: Read the Gaps

Different gap patterns point to different root causes:

Step 4: Fix the Highest-Leverage Gap First

For most MSPs in this band, the order is:

  1. Per-user pricing below the industry average: reprice. It is the single highest-ROI action. Every dollar of per-user increase across 500 users is $6K a year in revenue at near-100% margin.
  2. MRR below 60%: convert break-fix to managed. Fix the revenue mix before trying to grow total revenue.
  3. Any single client above 30% of revenue: diversify. Growth on top of concentration amplifies the risk.
  4. Endpoints per tech above 300: hire. Do it before quality slips, because the churn from degraded service costs more than the hire.
  5. EBITDA above 22% with everything else healthy: invest in growth. This is where marketing spend and sales hiring create real leverage.

Run the full diagnostic with the Business Assessment.

What to Look For in Your Business

These diagnostic questions surface the structural issues that separate MSPs on a growth trajectory from MSPs that are treading water.

Frequently Asked Questions

What is a good profit margin for an MSP?

Target 55-62% gross margin and 18-23% EBITDA. Industry average EBITDA is 18.4%, and top quartile MSPs exceed 22%. The biggest lever is service mix: managed services run 50%+ gross margin while hardware resale runs 20-30%. Every 10 points of MRR share correlates with roughly 2-3 points of EBITDA improvement.

What KPIs should an MSP track?

Five: MRR as a percentage of total revenue (target 65-78%), per-user pricing (target $185-$250 a month), endpoints per technician (target 230-280), top 3 client concentration (below 30% of revenue), and revenue per employee (target $140K-$175K). Together they explain most of the profitability variation between MSPs in the $600K-$2M range.

How do I benchmark my MSP business?

Pull seven numbers from the last 12 months: total revenue, MRR percentage, per-user pricing, EBITDA margin, revenue per employee, endpoints per tech, and top 3 client concentration. Compare each against the benchmarks for 5-10 person MSPs. The gaps point to the highest-leverage fix, which is usually pricing or MRR composition.

What is a good endpoints-per-tech ratio for an MSP?

About 250 endpoints per technician, with 230-280 as the healthy range. Below 200 means you are paying for tech capacity you are not using. Above 300, technicians are strained, and response times, quality and eventually client retention suffer. Complex environments such as healthcare, finance or manufacturing with OT may need 180-220.

Related Guides

Grounded in a 320,000+ claim knowledge base across 160+ domains. Pharallax AI provides adversarial structural analysis for operator-founders at $500K-$3M revenue.

Published 2026-03-31 | Updated 2026-10-07.

See what these patterns look like in your business

Get a free structural health score in 15 seconds.

Score My Business