Where Your Technicians' Billable Hours Actually Go
Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
Your techs are busy. Tickets are moving, phones are ringing, and nobody's sitting idle. So it comes as a shock when you finally do the math and realize you're paying for roughly 2,080 hours a year per tech and billing — or recovering through your managed fee — a lot less than you assumed. The hours didn't disappear. They leaked, an hour here and twenty minutes there, into work that never made it onto anything you can price. The problem in most MSPs isn't lazy technicians; it's that a large share of paid tech time quietly turns into unbilled overhead nobody is tracking.
That gap is the difference between a shop that feels busy and one that's actually profitable. Two MSPs can run the same headcount and revenue and land in completely different places, purely on how much of each tech's paid day converts into work a client is paying for.
ONE TECHNICIAN'S PAID DAY (8 hrs)
▇▇▇▇▇▇▇▇▇▇▇▇ billable / recovered client work
░░░░ internal tickets, meetings, ramp-up
░░ travel, admin, "quick favors"
░ idle / rework
Paid for all 8. Only the ▇ hours earn.Owner symptoms
Everyone looks slammed, but the revenue-per-tech numbers don't match the effort.
You can't say, without guessing, what percentage of a tech's week is billable or recovered.
Small unbilled favors and "just five minutes" tickets seem to eat whole afternoons.
Why this happens
Most MSPs never separate paid hours from earning hours. Time gets logged against tickets — if it gets logged at all — but nobody rolls it up into a simple utilization picture. Managed-services billing hides the leak further: because clients pay a flat monthly fee, there's no invoice line that screams when a tech spends three hours on an out-of-scope request. The hours are real and the payroll is real, but the connection between them and revenue goes unmeasured. On top of that, techs default to "help first, log later," and later rarely comes.
Common mistakes
Treating "busy" as "billable." Activity feels like productivity, but motion isn't the same as recovered revenue.
Not tracking time at all, or tracking it so loosely that half the day lands in a vague "internal" bucket.
Ignoring travel, ramp-up, and admin as if they were free, when they're paid hours that must be recovered somewhere in your pricing.
Letting scope creep ride — absorbing small out-of-scope tasks that never touch a ticket or a fee.
Measuring utilization once, panicking, then never looking again.
Business consequences
Unmeasured leakage shows up as thin margins you can't explain. You raise rates, add clients, hire another tech — and profit barely moves, because each new tech leaks at the same rate as the last. An owner who knows their real utilization prices the managed fee to recover the actual cost of delivery, staffs against real capacity instead of a guess, and spots the out-of-scope drain before it becomes a habit. The one who doesn't keeps mistaking a full schedule for a healthy business, and wonders why growth never reaches the bottom line.
How experienced operators think about it
They think in terms of conversion, not effort. The question isn't "are my techs working hard?" — it's "of every hour I pay for, how many convert into work a client is paying for, and where do the rest go?" They accept that 100% is neither possible nor desirable; techs need time for internal work, training, and reset. But they want that non-billable time to be chosen and visible, not a black hole. A known 70% is a business you can price and staff. An unknown number is a business you're running blind. The goal isn't to squeeze every minute; it's to see the day clearly enough to make deliberate decisions.
Practical actions
Require time logged against every task — billable, internal, travel, and admin alike. You can't fix a leak you can't see.
Calculate real utilization per tech: earning hours divided by paid hours, over a normal week. Start rough; precision comes later.
Name the non-billable buckets — meetings, ramp-up, rework, favors — so overhead stops hiding inside "other."
Flag out-of-scope work the moment it's logged, so recurring drains become a pricing or scope conversation, not a silent cost.
Set a target utilization band you consider healthy, and review the actual against it monthly — not once a year in a panic.
Questions every owner should ask
If I divide the hours I pay a tech by the hours that actually earn revenue, what number do I get — and do I even know?
Where does the non-earning time go, and how much of it did I choose versus inherit?
Is my managed fee priced to recover the real cost of delivery, or an optimistic version of it?
Frequently asked questions
What utilization rate should an MSP technician hit?
There's no single right number, and chasing a benchmark can mislead you. What matters more is knowing your own figure and understanding what fills the non-billable portion. A tech at a lower utilization who spends the gap on documentation, training, and internal improvements may be more valuable than one pushed to the limit and burning out. Measure first, understand the buckets, then decide what band is healthy for your shop — rather than importing someone else's target.
We bill flat monthly fees, so why does billable time even matter?
Because the flat fee has to recover the labor behind it, and you can't price what you don't measure. If a client's contract consumes far more tech time than you assumed, you're subsidizing them out of your margin without knowing it. Tracking the hours behind each agreement tells you which clients are profitable, which are underpriced, and where scope has quietly expanded past the fee — even though no per-hour invoice ever changes hands.
Related articles
Running a Profitable Managed IT Services Business — the pillar.
Balancing Project Work Against Recurring Managed Revenue — how the revenue mix shapes tech time.
Stopping the Small Favors That Quietly Blow Up Your Contracts — where much of the leaked time actually goes.
What Does a Job Actually Cost You? Real Job Costing — costing the labor behind the work.
Am I Charging Enough? How to Know for Sure — pricing to recover real delivery cost.
Every business has more decisions than time
Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.
Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.