The most expensive guess in the business
Deciding when to add a technician is one of the highest-stakes calls a field operation makes, and most owners make it on feel. Hire too early and you're paying a full salary, a truck, insurance, and a phone for someone who's idle half the week — a fixed cost that bleeds margin every day until the work catches up. Hire too late and the damage is quieter but just as real: your existing crew runs flat out, overtime costs climb, the quality slips under the pace, good techs start eyeing the door, and customers who can't get on your schedule for three weeks call the competitor who can come Tuesday. You lose the job and, worse, you lose the customer to a relationship with someone else.
The reason it feels like a gut call is that owners try to make it from the symptom — "we feel slammed" — which is unreliable. A crew always feels busy; busyness is not the same as being at capacity, and the gap between them is exactly where the money is. The signals that actually tell you whether you need more hands are already sitting in your operational data. You don't need a forecasting model or a consultant; you need to look at three numbers you can already pull, understand what each one is telling you, and act before the late-hire damage starts instead of after.
The three numbers that actually tell you
Capacity isn't one metric, it's a triangulation. Any single number can mislead; together, three of them draw a clear picture of whether you're under, at, or over capacity.
- Technician utilization — are the techs you have actually full? This is the share of paid hours that turn into billable work. If your techs are at 55% utilization, you're not short on people — you're short on scheduling the people you've got, and hiring would just add a second under-used truck. If they're consistently pinned near the practical ceiling (realistically 75–85%, never 100% — drive time and slack are real), you've genuinely run out of hours to sell, and that's the precondition for a hire. Utilization is the gate: you don't even look at the other numbers until it's high.
- Backlog — how much committed work is waiting? The pile of scheduled-but-not-yet-done jobs. A backlog that's stable means supply and demand are matched. A backlog that's growing week over week while utilization is already high means demand is outrunning your capacity to deliver — the clearest single signal that a hire is overdue rather than premature.
- Booking lead time — how far out is your first available slot? How many days until a new customer can actually get an appointment. This is the number your customers feel directly. When it creeps from "this week" to "two or three weeks out," you've crossed from healthy demand into the danger zone where customers start defecting to whoever can come sooner. Rising lead time with high utilization and a growing backlog is the trifecta that says hire now.
Read together, they disambiguate. High utilization with flat backlog and short lead time: you're at a healthy, well-scheduled capacity — hold. Low utilization with a growing backlog: you have a scheduling and dispatch problem, not a headcount problem, and a hire would mask it expensively. All three climbing at once: the case for adding capacity has already made itself, and every week you wait is overtime and lost customers.
Where these numbers come from
You can only read these signals if your operation is producing them as a byproduct of normal work, rather than requiring someone to assemble them by hand from timesheets and memory. That's the practical barrier for most shops — the data theoretically exists, but reconstructing it is so tedious that nobody does until the crisis is already here.
In Hosting Field the inputs fall out of the day-to-day. Because techs clock in and out against jobs, you get real billable hours against paid hours — the raw material for the utilization ratio — instead of a guess. Because every job carries a status and a scheduled date on a shared board, your backlog of committed-but-undone work is a visible list, not a feeling, and your first genuinely open slot is something you can see rather than estimate. The operational data you'd need to make the hire/no-hire call deliberately is the same data the system keeps to run dispatch and invoicing day to day; you're reading numbers that already exist for another reason.
The honest boundary matters here, because capacity planning is exactly the kind of thing software overpromises. Hosting Field surfaces the inputs — measured utilization, a visible backlog, real lead time — as clean, current numbers. It does not forecast your demand, predict next quarter's volume, or tell you "hire a tech on March 1st." There's no predictive model under the hood, and you should be suspicious of anyone selling you one for a business this lumpy. What you get is an honest, up-to-date read on where you stand today and which way the trend is pointing; turning that into a hiring decision — weighing your cash position, your pipeline, how long it takes you to recruit and train — is judgment the numbers inform but don't make. The system tells you the truth about your current capacity. Deciding what to do about it is still the owner's job.
Acting on the signal without overcorrecting
Even with clear numbers, the response needs a steady hand, because the costs are asymmetric and the lead times are long.
- Account for the ramp. A new tech isn't productive on day one — there's onboarding, there's learning your standards, there's the period where a senior tech slows down to train them. If recruiting and ramping takes you two months, you have to read the signal and act two months before you're truly underwater, which is precisely why watching the trend beats reacting to the crisis.
- Check whether scheduling buys you the capacity first. Before you commit to a fixed salary, ask whether better routing, tighter scheduling, or trimming windshield time would recover the hours you need. Squeezing utilization from 65% to 80% can be the equivalent of a partial hire at zero added fixed cost — and if your utilization isn't already high, this is almost always the right move before adding a head.
- Consider the reversible options before the irreversible one. Overtime, a subcontractor, or a seasonal hire are ways to absorb a demand spike without taking on a permanent cost. If the high-utilization, growing-backlog signal is sustained across months rather than a seasonal blip, that's when it's time for the permanent hire; if it's a spike, flex capacity is the cheaper, safer answer.
The goal is to add capacity just ahead of sustained demand — early enough that customers never feel the squeeze, late enough that you're not paying for idle trucks. That timing is only possible if you're watching the trend, not the crisis.
What to measure
- Utilization trend, not the snapshot. A single week's utilization is noisy; the direction over a quarter is the signal. Sustained high utilization is the precondition for any hire — if this number isn't climbing toward the ceiling, the answer to "should I hire" is almost always no.
- Backlog growth rate. Whether your committed-but-undone work is stable, growing, or shrinking week over week. Growing backlog on top of high utilization is the single clearest "demand is outrunning capacity" signal you have.
- Booking lead time to first open slot. The days until a new customer can be seen, tracked over time. This is the number customers feel and defect over; when it crosses from days into weeks while the other two signals are flashing, the hire is no longer early — it's late.
The hire/no-hire decision will always carry judgment that no number can make for you — your cash, your nerve, your read on whether the busy season holds. But it doesn't have to be a blind guess. Utilization tells you whether you're actually full or just busy; backlog tells you whether demand is outrunning you; lead time tells you whether customers are about to feel it. Watch those three as trends rather than snapshots, act on the ramp-adjusted lead time rather than the crisis, and check whether scheduling buys you the capacity before you buy a truck. Do that and the most expensive guess in the business becomes a decision you can actually defend — made from the numbers your operation was already producing.