Effective management of an IT services firm relies on one primary lever: msp technician utilisation. This metric represents the percentage of a technician's total capacity spent on revenue-generating or client-facing work. While it sounds like a simple accounting exercise, it is actually the pulse of your operational efficiency and the ceiling of your profitability.
In the world of Managed Service Providers, time is the inventory. If your technicians are spending their days on untracked internal tasks, poorly defined projects, or administrative friction, that inventory is expiring without producing a return. Mastering utilisation is not about "squeezing" your team; it is about ensuring that the expertise you pay for is actually reaching the clients who pay you.
MSP Agenda was founded by Luis Navarro, following more than 15 years spent building and growing a successful Managed Service Provider. As co-founder of Totality Services, Luis helped take the business from an idea and a small team to a highly profitable MSP serving more than 150 clients. He learned firsthand that technical excellence means nothing if the commercial engine—driven by utilisation—is broken. This guide breaks down how to measure, manage, and maximise this critical KPI.
What Is MSP Technician Utilisation?
Technician utilisation is a KPI that measures how much of a technician's workday is dedicated to productive, client-related activity compared to their total available hours. It is the bridge between your payroll (the cost) and your service delivery (the value).
To calculate it, use the following formula:
(Billable Hours + Client-Contract Hours) / Total Available Work Hours x 100 = Utilisation %
For example, if a technician works an 8-hour shift (480 minutes) and logs 6 hours of time against client tickets or projects, their utilisation for that day is 75%. The remaining 2 hours were likely spent on internal meetings, training, breaks, or administrative overhead.
Recommended Utilisation Benchmarks by Role
Not every role in an MSP should have the same target. A Tier 1 help desk tech has a different workflow than a Senior Project Engineer or a Technical Account Manager. Overloading a senior resource with a 90% utilisation target leaves no room for the strategic thinking required for complex security reviews or infrastructure planning.
| Role | Target Utilisation | Primary Focus |
|---|---|---|
| Help Desk / Tier 1 | 75% - 85% | Reactive tickets, quick fixes, and remote support. |
| NOC / Escalations | 70% - 80% | In-depth troubleshooting and proactive maintenance. |
| Project Engineer | 80% - 90% | Scheduled deployments and infrastructure upgrades. |
| Senior Architect / Lead | 50% - 60% | Strategy, mentoring, and high-level escalations. |
Why Utilisation is the Ultimate Profitability Lever
For an MSP, the cost of labour is usually the largest expense on the P&L. When msp technician utilisation is low, your cost per ticket rises, and your effective hourly rate on flat-fee managed contracts drops. If you are paying a technician $40 an hour but they are only "productive" for 4 hours a day, your actual labour cost for that productive time is effectively $80 an hour.
By increasing utilisation through better scheduling and reduced administrative friction, you are essentially increasing your capacity to take on more clients without hiring additional staff. This is where "operating leverage" comes from in a services business. Luis Navarro saw this clearly at Totality Services: the journey to an eight-figure acquisition wasn't just about selling more; it was about ensuring the technical team was optimised to deliver that growth profitably.
High utilisation also improves client satisfaction, provided it isn't driven by rushing. When technicians are properly utilised, tickets move through the system faster, and projects stay on schedule. The key is finding the "Goldilocks Zone"—high enough to be profitable, but low enough to allow for quality work and professional development.
Common Obstacles to High Utilisation
Most MSPs struggle with utilisation not because their technicians are lazy, but because the business processes are broken. If a tech has to spend 20 minutes hunting for a password or another 15 minutes documenting a simple fix in a clunky PSA, that is time stolen from client delivery.
1. Documentation Gaps
If your documentation is scattered across spreadsheets, Word docs, and the brains of senior engineers, your utilisation will suffer. Technicians spend hours "researching" instead of "fixing." Standardising how information is stored is a prerequisite for efficiency.
2. Administrative Friction
Expectation setting is key. If a technician is required to join every internal huddle, fill out complex expense reports, and manually update three different tracking systems, their billable potential is capped. An MSP owner must relentlessly remove non-technical hurdles from the technician’s path.
3. The "Ticket Purgatory"
Tickets that sit in "Waiting for Customer" or "Pending" often lead to context switching. A technician starts a task, gets blocked, switches to another, and then has to spend time getting back into the flow of the first task. This "switching cost" is a silent killer of msp technician utilisation.
Practical Strategies to Improve Utilisation
Improving utilisation requires a mix of cultural changes and technical optimisations. It is not a one-time project but a continuous cycle of measurement and refinement.
- Implement "Real-Time" Time Entry: The most accurate way to track utilisation is to require time entries as tasks are completed. Relying on technicians to "reconstruct" their day at 5 PM leads to lost hours and inaccurate data.
- Standardise Service Offerings: The more "bespoke" your clients are, the harder it is for technicians to be efficient. When every client has a different firewall, backup solution, and AV, your team is constantly learning on the fly. Standardisation allows for muscle memory and speed.
- Optimise the Dispatch Role: A dedicated dispatcher or service coordinator ensures that the right tech is working on the right ticket at the right time. This prevents "cherry-picking" and ensures that high-priority issues aren't languishing while techs work on easier, low-value tasks.
- Invest in Training: A technician who is well-trained in your specific stack will resolve issues faster than one who is winging it. Training is an investment in future utilisation.
Connecting Utilisation to Client Value
From a commercial perspective, utilisation shouldn't just be about closing tickets. It should be about freeing up time for high-value activities that strengthen the client relationship. For instance, if your team is highly efficient at handling reactive support, you can reallocate that time to performing deep-dive security reviews or proactive site visits.
This is a core philosophy at MSP Agenda. Luis Navarro’s experience showed that clients don't value the "hours" worked; they value the results. However, the MSP needs to track those hours to ensure the contract remains profitable. When you can demonstrate that your team is spending time on strategic improvements rather than just "fighting fires," the perceived value of your MSP increases significantly.
High utilisation allows you to be more selective with your client base. When you know your capacity, you can identify which clients are "noisy" and dragging down your team's efficiency. This data gives you the confidence to either raise rates for those clients or transition them out to make room for more profitable partnerships.
The Risks of Over-Utilisation
While low utilisation is a financial problem, chronic over-utilisation is a structural risk. If your team is consistently running at 95% or higher, you are one flu season or one major client outage away from a total service collapse. Over-utilised technicians make more mistakes, skip documentation, and eventually burn out.
Signs of Over-Utilisation:
Increased ticket reopen rates (rushed work). Declining documentation quality. Higher than average employee turnover. Missed SLAs on low-priority tasks. Lower scores on client satisfaction surveys (CSAT).
When you hit these ceilings, it is a clear signal that it is time to hire or, more importantly, to look at your automation capabilities. Can you automate the "noise" so your current team can handle more volume without increasing their individual stress levels?
Using Data to Drive Behaviour
Visibility is the greatest motivator. Sharing msp technician utilisation data with the team shouldn't be about "Big Brother" oversight. Instead, it should be framed as a way to identify where the business is failing to support the technical team.
If a specific technician has low utilisation, ask: "What is getting in your way?" Frequently, the answer is a lack of tools, poor training on a specific product, or a specific client that is difficult to work with. Use the data to start a conversation, not to issue a reprimand.
Utilisation and the "Service Profit Chain"
The concept is simple: internal quality leads to employee satisfaction, which leads to service value, which leads to client satisfaction and profit. Utilisation is the metric that monitors the "Internal Quality" and "Service Value" links. If you ignore it, the rest of the chain eventually breaks.
| Metric Group | Primary KPI | Impact on Business |
|---|---|---|
| Efficiency | Utilisation Rate | Directly correlates to Gross Margin and scalability. |
| Effectiveness | First Response Time / Resolution Time | Drives client trust and contract renewals. |
| Quality | CSAT / Ticket Reopen Rate | Ensures that high utilisation isn't masking poor work. |
The Luis Navarro Perspective: From Growth to Exit
At Totality Services, Luis was never the "technical guy." His focus was on the business side: sales, marketing, and profitability. This outsider perspective allowed him to see the technical team as a critical engine that needed fuel and maintenance. He realised that if the "engine" (the technicians) was spending half its energy idling (unproductive time), the "car" (the MSP) would never reach its destination.
Luis spent years bridging the gap between what the techs were doing and what the clients were seeing. He learned that a recommendation a client doesn't understand is unlikely to become a project. Similarly, a technician's time that isn't tracked is unlikely to be valued by the client. MSP Agenda was built to solve this exact problem—taking the complex reality of MSP operations and turning it into clear, actionable, and commercially viable outcomes.
The journey from a small team to a multi-national, eight-figure acquisition was paved with data-driven decisions. Utilisation was one of the core metrics that allowed Totality Services to scale without losing control of their margins. It provided the clarity needed to know when to hire, when to invest in automation, and when a client relationship was no longer sustainable.
Advanced Insights: The "Effective Hourly Rate" (EHR)
To truly master msp technician utilisation, you must eventually link it to your Effective Hourly Rate. This is calculated by taking the total monthly recurring revenue (MRR) from a client and dividing it by the total hours your team spent servicing that client.
If a client pays $2,000 a month and your team spends 10 hours on them, your EHR is $200. If utilisation is high but your EHR is low, it means your team is working hard but your contracts are priced incorrectly or the client is too complex for the current agreement. This is where the commercial side of the MSP must step in to renegotiate or refine the service scope.
Automation: The Great Utilisation Multiplier
In the modern MSP landscape, you cannot achieve elite utilisation levels through manual effort alone. You must leverage RMM (Remote Monitoring and Management) and PSA (Professional Services Automation) tools to their fullest extent. Automated script deployments, self-healing alerts, and streamlined ticket routing are essential for keeping your technicians focused on high-level work rather than "janitorial" IT tasks.
Every time you automate a password reset or a disk cleanup, you are effectively "buying back" utilisation points for your team. This recovered time can then be invested in higher-margin projects or strategic security initiatives that drive long-term client loyalty.
Building a Culture of Accountability
Accountability is not about blame; it is about ownership. When technicians understand how their utilisation contributes to the health of the company, they are more likely to take pride in their efficiency. High-performing MSPs often tie utilisation targets to performance bonuses or career advancement paths.
However, this must be balanced with a culture that values accuracy over "padding" time. If techs feel pressured to hit impossible targets, they will start exaggerating their hours, which renders your data useless. The goal is a transparent environment where everyone knows what a "good day" looks like and feels supported in achieving it.
Summary of Best Practices
- Establish Clear Categories: Define exactly what counts as "utilisation" (e.g., client tickets, project work, onsite travel) versus "overhead" (e.g., internal meetings, training).
- Daily Reviews: Service managers should review utilisation dashboards daily to catch anomalies before they become trends.
- Reward Efficiency: Acknowledge technicians who maintain high utilisation and high CSAT scores simultaneously.
- Address the "Lulls": Have a "backlog" of non-urgent internal projects or training modules for technicians to work on during quiet periods so their time remains productive.
- Standardise the Stack: Reduce the cognitive load on your team by limiting the number of different technologies they have to support.
