Workforce and Labor

MSP Technician Utilization: The Number That Turns on You

Managed service utilization is unusual: the contract is fixed-fee, so every hour spent is a cost rather than revenue. That inverts the incentive and breaks the benchmarks borrowed from billable service.

Utilization means something different in a managed service business than in a time-and-materials one, and importing benchmarks across that line produces bad decisions. Under a fixed-fee agreement, an hour of technician time is pure cost: the revenue arrived regardless. High utilization in that model is not a sign of a healthy business, it is a sign that the contracts are consuming more labor than they were priced for.

What to measure instead of billable percentage

Four measures that fit the model

• Hours per contract per month, trended. This is the real unit economics of the agreement, and it should be falling as an environment stabilizes rather than holding flat.
• Reactive versus proactive hour split. A high reactive share means the environment is unstable and the contract is being run as break-fix, which is where fixed-fee margin dies.
• Endpoints or devices per technician, which is the capacity metric the commercial model actually scales on.
• Escalation rate to senior staff, since a ticket resolved by a senior engineer costs multiples of one resolved at first line.

Where the practitioner bands sit, and why they vary

Industry surveys and practitioner communities commonly discuss billable utilization targets in the sixty to seventy-five percent range for service delivery staff, with the wide spread reflecting how differently firms define the denominator. I would treat any specific figure quoted without its definition as unusable. The more reliable comparison is internal and directional: your own hours per contract this quarter against last, which controls for definition entirely because both numbers came from your system.

Under a fixed fee, a busy technician is not revenue arriving. It is margin leaving, and the utilization dashboard will show it as a good month.

The stabilization curve is the whole business model

A managed contract typically consumes heavy hours in onboarding and early months while backlogged problems get resolved, then should decline toward a steady state as the environment stabilizes. That curve is the model: the profitable years are the later ones. A contract whose hours are not declining after the first year is not stabilizing, and the reason is usually either an environment that needs capital investment the client will not fund or a scope that was underestimated at sale. Both need addressing commercially rather than by working the team harder.

The pricing consequence

If hours per contract are tracked from the beginning, renewal pricing becomes a data exercise rather than a negotiation instinct. A client whose environment consumed twice the modelled hours can be shown the curve, and the conversation shifts to either a price adjustment or a remediation project, both of which are better outcomes than absorbing the overrun silently for another term. Firms that do not track this discover it only when margin has already gone.

Use the technician utilization calculator to establish your own baseline before benchmarking against anyone else. Model the capacity

Published 2026-08-08.