October 5, 2026
A $1 million managed services business can pay its owner $180,000 a year and still net 3%. Bering McKinley, an MSP consulting firm, used exactly that profile in September 2026 to describe a business that looks healthy and isn’t.
Revenue hides problems. MSP profit margins are where the truth shows up, and most owners look at them too late: once a quarter, after every pricing, staffing, and tooling decision has already been made.
So what is a good number? A healthy MSP nets 10% to 20% of revenue and keeps a service gross margin of 65% or higher. Below 10% net, one lost client or one bad hire can push the business into a loss. Below 50% gross, the delivery model itself is underpriced.
This guide pulls together the benchmarks scattered across accountants, consultants, and industry analysts. It shows where those sources disagree, walks through the math, and covers one cost line almost nobody measures.
Net margin alone tells you whether you made money. It doesn’t tell you why. Owners who track only the bottom line end up guessing at the cause when it drops.
The table below brings together the operating benchmarks that practitioners use. Where sources differ, both figures are shown.
| Metric | Healthy range | Source |
|---|---|---|
| Net profit margin | 10% to 20% of revenue | Profitwise Accounting, 2026 |
| Net margin after owner-pay restructuring | 10% to 15% | Bering McKinley, 2026 |
| Service gross margin | 65% or higher; 70%+ for top performers | Profitwise Accounting, 2026 |
| Technician payroll as % of service revenue | Under 33% | Profitwise Accounting, 2026 |
| Service revenue per technician | $150,000 to $200,000 per year | Profitwise Accounting, 2026 |
| Revenue per technical headcount | $17,000/month minimum, $20,000/month target | Paul Cissel via Technology Marketing Toolkit, 2024 |
| Technician utilization | 60% to 75% | Profitwise Accounting, 2026 |
| Recurring share of revenue | 60% or more | Profitwise Accounting, 2026 |
| Endpoints per technician | 200 to 300 typical; 350 as the gold standard | Sherweb and Acronis, cited by AvePoint, 2025 |
| Office and admin overhead | Under 15% to 20% of revenue | Profitwise Accounting, 2026 |
Plenty of articles say MSPs should net 20% to 30%. Most of them cite nobody.
The firms that actually read MSP books put the bar lower. Profitwise Accounting, a CPA-led firm that publishes MSP finance benchmarks, treats 10% to 20% as healthy and flags anything under 10% as fragile. Bering McKinley reports that owners who restructure their pay typically climb from low single digits into the 10% to 15% range.
A 25% net margin is excellent. Treating it as normal leads to the wrong fixes.
Gross margin measures what you keep after paying to deliver the service. That means fully burdened technician labor plus the tools you deliver with: RMM, PSA, security stack, backup.
Profitwise sets 65% as the floor, with top performers aiming for 70% or more. Many MSPs run at 50% to 60% without realizing it. At that level, the business needs constant volume and perfect execution just to stay profitable.
Labor is the biggest line on an MSP’s P&L. Three ratios show whether it’s working.
Technician payroll should stay under 33% of service revenue. Each technician should support roughly $150,000 to $200,000 in annual service revenue, according to Profitwise. Paul Cissel, an MSP valuation advisor, sets the bar higher at $17,000 to $20,000 per technical head per month, or $204,000 to $240,000 a year. Use the lower range as a floor and the higher one as a goal.
Utilization matters too. 60% to 75% is the target band. Below 60%, you’re paying full salaries for part-time output. Above 80%, burnout and turnover cost more than the extra hours earn.
The math is simple. The discipline is in sorting costs correctly. Most errors in MSP profit margins come from mixing direct costs with overhead, which makes gross margin look healthier than it is.
Gross margin formula: Service gross margin = (Service revenue – Direct service costs) ÷ Service revenue × 100
Net margin formula: Net profit margin = (Total revenue – All costs) ÷ Total revenue × 100
Direct service costs include technician salaries plus taxes and benefits (Profitwise estimates fully burdened labor at 20% to 25% above base salary), and the tools used to deliver services. Overhead covers everything else: owner and admin salaries, sales and marketing, rent, insurance.
Take an MSP with $1,200,000 in annual service revenue, or $100,000 in monthly recurring revenue (MRR).
| Line item | Annual amount |
|---|---|
| Service revenue | $1,200,000 |
| Fully burdened technician labor | $330,000 |
| Delivery tools (RMM, PSA, security, backup) | $90,000 |
| Gross profit | $780,000 (65% gross margin) |
| Overhead (owner, admin, sales, marketing, rent, insurance) | $612,000 |
| Net profit | $168,000 (14% net margin) |
This business passes. Gross margin sits right at the 65% floor, technician payroll is 27.5% of revenue, and net margin lands inside the healthy band.
It has almost no slack, though. Lose one $8,000-a-month client without cutting any costs, and net profit falls from $168,000 to $72,000. That’s a 6.5% net margin, well below the healthy band.
Want to see how infrastructure costs change this math for your clients? Talk it through with our MSP partner team.
Explore our MSP partner program
Company-wide margins average out the problem. One client at 70% gross margin can hide two clients at 20%.
Profit doesn’t spread evenly across a client base. Clive Longbottom, writing for SmarterMSP, notes that loss-making accounts tend to be the smaller ones. They lean on the help desk for every question because support is already in the subscription, and some of them also have to be chased for payment every month.
Divide each client’s monthly fee by the hours your team actually spent on them.
Profitwise gives a clear example: a $2,000 monthly contract that consumes 40 hours earns $50 an hour. If your fully burdened labor costs $75 an hour, that client loses you money every month. Target an effective rate of 2x to 3x your burdened labor cost.
Every client below that line gets one of three responses. Reprice the contract. Rescope it, with clear boundaries on what the flat fee covers. Or, if neither works, let the client go.
Ending a relationship feels expensive. Keeping an unprofitable client is more expensive, because it consumes the capacity your profitable clients pay for.
The pressure is structural this year. Omdia’s 2026 MSP market analysis, as summarized by NinjaOne in The Price Gap Problem, puts managed services revenue at $635 billion and growing up to 10% annually. It also warns that organic growth, excluding acquisitions and price increases, will be hard for most providers.
Clients now expect security monitoring, compliance documentation, and cyber insurance readiness inside the same contract. About three-quarters of MSP deals tracked in 2025 were private equity funded, according to the same analysis, and those roll-ups compete hard on price.
When senior technicians or the owner handle work a junior tech could do, labor costs inflate quietly. Start Grow Manage recommends a 70/20/10 split across Tier 1, 2, and 3, with documentation as the mechanism that pushes work down.
AvePoint cites research showing 74% of MSPs would like to use fewer tools. Every overlapping license is a direct cost that lowers gross margin, and every extra console adds technician time.
Bering McKinley’s argument is blunt. An owner on a fixed, comfortable salary stops feeling the cost of every operating decision. Their fix: set owner salary low, around $50,000, and take the rest as distributions from real profit. Owners who did this, they report, ended the year earning more than the salary they gave up.
Flat-rate contracts expand silently. A new compliance request here, an after-hours fix there. None of it gets repriced, and the effective hourly rate falls a little every quarter.
Quiz: Find the Perfect Pricing Model for Your MSP
Not sure which pricing model fits your MSP business? Take our free 5-minute quiz to discover the best approach based on your business size, client needs, and service structure.
Get clear, actionable insights to help you price your services effectively—start now!
Here’s the cost no benchmark report isolates: the on-premise servers and aging infrastructure you support for clients inside a flat monthly fee.
Consider a 10-person client with an in-office file and application server. As an illustration, say it absorbs five technician hours a month: patching, backup checks, the occasional reboot after hours. At a $75 burdened rate, that’s $375 a month of labor buried in the contract. Then the hardware ages, and the refresh becomes a project the client resists paying for.
Unpriced infrastructure work is one of the quietest drains on MSP profit margins. It never shows up as its own line, so it never gets repriced.
Moving those workloads to managed cloud desktops changes the cost structure. Instead of open-ended labor, the infrastructure becomes a fixed monthly cost you can mark up.
On our side, pricing is per VM and sized by workload type, from Basic through Power. A Mid Level VM, suited to accountants, analysts, and operations staff, starts at $60 a month, and less frequent users can share a VM. We handle daily automated backups and 24/7 support, so the patching and backup checks leave your technicians’ queue.
What this changes: your margin on infrastructure becomes something you set, not something labor erodes.
Not every workload belongs in the cloud. Clients with specialized local hardware or strict latency needs may stay on-premise. And the migration itself is project work, which needs scoping and pricing like any other project.
Improving MSP profit margins doesn’t require a new strategy. It requires measuring before deciding.
Separate direct costs from overhead in your books. Calculate service gross margin overall and per service line. Then calculate the effective hourly rate for every client.
Take the three lowest-margin clients and reprice, rescope, or exit each one. Audit your tool stack and cancel overlapping licenses. Decide whether owner pay should move to a low salary plus profit distributions.
Document every task that happens twice so it can move down a tier. Convert recurring project work into managed agreements. List every client still running infrastructure you support for free, and price it or move it.
Margin follows measurement. The MSPs that check monthly fix problems in weeks, not years.
There’s also a payoff at exit. Cissel values MRR at roughly $1.60 per dollar, compared with about $0.14 for hardware revenue. A profitable recurring business isn’t only more comfortable to run. It’s worth more when you sell.
If client infrastructure is eating your margin, we can help you model the change for a specific account.
Most MSP-focused accountants and consultants consider 10% to 20% net profit healthy. Below 10% is fragile, and 25% or more is exceptional rather than typical. Track service gross margin as well, with 65% as the floor.
Service gross margin should be 65% or higher, and top performers aim for 70%. Below 50%, the delivery model is underpriced or overstaffed.
Subtract direct service costs (fully burdened technician labor and delivery tools) from service revenue, then divide by service revenue for gross margin. For net margin, subtract all costs, including overhead, from total revenue and divide by total revenue.
Clients expect security, compliance, and cyber insurance readiness inside the same contract price. Private equity-backed roll-ups compete on price, and tool sprawl plus manual processes raise the cost of delivering each service.
Industry data cited by AvePoint puts the average at 200 to 300 endpoints per technician, with 350 fully managed endpoints as the gold standard. Automation and documentation push the ratio higher.
Divide the client’s monthly fee by the hours your team spends on them. If that effective hourly rate falls below 2x your fully burdened labor cost, the contract needs repricing or rescoping.
Bering McKinley recommends a low salary, often around $50,000, with the rest taken as distributions from actual profit. Tying owner income to profit keeps every spending decision honest.
Your V2 CloudCare team — real people, on the line.