Efficiency is the engine of profitability in the managed services world. While top-line growth often gets the spotlight during sales meetings, the health of an MSP is truly revealed in its operational metrics. Among these, MSP revenue per technician stands as perhaps the most critical indicator of whether a business is built to scale or simply surviving on a treadmill of reactive support.
At its core, this metric tells you how effectively your technical team generates income relative to the cost of their labour. It isn't just about how hard your engineers are working; it’s a reflection of your pricing strategy, your service standardisation, and your ability to automate the mundane. If this number is too low, you aren't running a scalable business—you’re running a high-stress charity for your clients.
Luis Navarro, the founder of MSP Agenda, understands this balance intimately. Over 15 years, he co-founded and grew Totality Services from a small team into a highly profitable MSP serving over 150 clients across London and Johannesburg. That journey, which culminated in a successful eight-figure acquisition, was driven by a focus on commercial clarity. Luis wasn't the "technical guy"; he was the one ensuring that technical excellence translated into business value and healthy margins. This article draws on that real-world experience to help you master your revenue efficiency.
Understanding MSP Revenue Per Technician
In the simplest terms, MSP revenue per technician is a productivity ratio. It measures the gross revenue generated by the business for every technical employee on the payroll. This includes helpdesk analysts, field engineers, project technicians, and cloud architects. It typically excludes administrative staff, pure sales roles, and leadership who do not perform billable or contract-based technical work.
Why does this specific number matter more than total revenue? Because labour is an MSP’s largest expense. If you add $20,000 in Monthly Recurring Revenue (MRR) but have to hire two new technicians at $70,000 each to support it, your business hasn't actually become more valuable—it’s just become larger and more complex. High-performing MSPs focus on "operating leverage," which is the ability to grow revenue faster than expenses.
To calculate it, use the following formula:
(Total Annual Revenue) / (Total Number of Technical FTEs) = Revenue Per Technician
What the Numbers Tell You
The industry generally breaks down performance into three tiers based on this metric. Note that these figures are based on US market standards for mature managed service providers.
| Performance Tier | Revenue Per Technician | Business Characteristics |
|---|---|---|
| Laggard | Under $150,000 | Reactive "break-fix" mentality, lack of standardisation, low pricing, and high technician burnout. |
| Average | $175,000 - $225,000 | Solid managed services foundation, some automation in place, moderate pricing, but still heavily dependent on manual labour. |
| World-Class | $250,000 - $350,000+ | High degree of stack standardisation, significant project revenue from security, and mature automated remediation. |
The Commercial Impact of Technician Efficiency
When Luis Navarro was scaling Totality Services, the focus was always on how to make the business more profitable without burning out the team. High revenue per technician isn't about cracking a whip; it’s about removing the obstacles that prevent technicians from being productive. When you improve this metric, you change the entire financial profile of the MSP.
Higher efficiency leads directly to higher gross margins. In a service business, your "cost of goods sold" is primarily the salary and benefits of your technical team. If each tech supports $300,000 in revenue, your margin is significantly wider than if they only support $150,000. This extra margin provides the "dry powder" needed to invest in better tools, marketing, and higher-tier talent.
Furthermore, this metric is a key driver of enterprise value. During the acquisition process that led to the sale of Totality Services, buyers looked closely at operational maturity. An MSP that requires 20 techs to manage $3M in revenue is far less attractive—and less valuable—than one that manages the same $3M with only 10 techs. Efficiency proves that your processes are documented and your technology stack is standardised.
The Trap of the "Busy" Technician
A common misconception is that a technician who is "busy" all day is a productive one. In reality, a technician spent four hours fixing a recurring printer issue is a drain on the business. A technician who spends those four hours implementing a security project or a cloud migration is generating high-value revenue. MSP revenue per technician forces you to look at the value of the work, not just the volume of tickets.
