Knowing When You Need Another Tech Before Service Slips
Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
Most MSP owners hire a tech the same way: they wait until the team is visibly drowning, response times have already slipped, a client has already complained, and only then do they post the job. By the time that new hire is trained and productive — often two or three months later — the team has spent an entire quarter running hot and shedding goodwill. The hire was right; the timing was late. Capacity is a leading problem you can see coming, but most owners treat it as a lagging one they discover after the damage is done.
The signals that your team is full show up well before service actually breaks. Tickets sit a little longer. Techs stop doing the proactive work that keeps clients from having problems in the first place. Small things get skipped. If you learn to read those signals, you hire ahead of the slip — while service is still good and you have time to recruit and train properly.
CAPACITY AND THE HIRING WINDOW
load ░░░░░░▓▓▓▓▓▓▓▓▇▇▇▇█████
│ │ │
│ proactive │ service
│ work drops │ slips
│ │ │
└ HIRE HERE ┘ └ not here
(signals up, (clients
quality holds) notice)Owner symptoms
Techs have stopped doing proactive maintenance and are only reacting to tickets.
Response and resolution times are creeping up, but nothing's broken yet.
You keep telling yourself the team can absorb one more client.
Why this happens
Capacity is invisible until it isn't. An MSP team doesn't fail all at once — it degrades quietly. When techs get busy, the first thing to disappear is the non-urgent, preventive work: patching schedules, documentation, checking on the client who hasn't called. That work has no deadline, so it's the natural release valve. The team looks like it's coping because urgent tickets still get handled, but the buffer that prevents future problems is being spent. Owners miss it because they watch for fires, and there are no fires yet — just the slow removal of the work that stops fires from starting.
Common mistakes
Waiting for a complaint before hiring, which means the slip already happened.
Measuring only urgent tickets, so the loss of proactive work stays invisible.
Adding clients one at a time without asking what the last one is displacing.
Assuming utilization can run near 100%, leaving no room for training, sickness, or a bad week.
Starting the hunt too late, so you fill the seat under pressure with whoever's available.
Business consequences
Hiring late costs more than the salary you delayed. During the stretch where the team is over capacity, proactive work stops, so clients start having preventable problems — which generate more reactive tickets, which push the team further behind. Service quality slips right as you're least able to fix it, and churn risk climbs. Then the rushed hire, made under pressure, is more likely to be a poor fit. The owner who watches capacity signals hires while service is still strong, recruits without panic, and trains the new tech before the team is underwater — so clients never feel the transition at all.
How experienced operators think about it
They treat capacity as a buffer, not a ceiling. The goal isn't to run the team as full as possible; it's to keep enough slack that proactive work still happens and a bad week doesn't break service. So they watch the first things to slip — maintenance skipped, response times drifting, techs working through lunch — as early warnings, not acceptable trade-offs. They also count backward: if a productive tech takes two to three months to hire and train, the decision to hire has to be made while the team still has headroom, not after it's gone. The question isn't "are we drowning yet" but "are we still doing the work that keeps us from drowning."
Practical actions
Track proactive work, not just tickets. Watch whether scheduled maintenance and documentation are actually getting done — their quiet disappearance is your earliest signal.
Set a capacity trigger in advance. Decide now what combination of signals — rising response times, skipped maintenance, sustained overtime — means "start recruiting," so the decision isn't made in a panic.
Count the lead time backward. Know how long hiring and ramp-up really take in your shop, and hire that far ahead of the wall.
Ask what each new client displaces. Before signing, name the work the team will stop doing to absorb it — if the answer is "proactive maintenance," you're at capacity.
Protect a slack buffer. Plan around techs being productively busy, not pinned at full, so training, sick days, and rough weeks have somewhere to go.
Questions every owner should ask
Is my team still doing proactive work, or only reacting to what breaks?
How long does it actually take me to hire and ramp a productive tech?
What am I watching to tell me we're full — and did I decide that in advance or in the moment?
Frequently asked questions
How do I know it's a capacity problem and not just a workload-balancing problem?
They can look identical from the owner's chair, so check distribution first. If one tech is buried while another has room, that's balance — solvable by moving work, not by hiring. If every tech is running hot, proactive work has stopped across the board, and there's no slack to redistribute, that's capacity. Hiring into an imbalance just gives you an expensive new tech and the same uneven load, so rule out balance before you conclude you're full.
Isn't hiring before I'm sure I need someone just paying for idle time?
A new tech is rarely idle for long in a growing MSP — but even a short stretch of slack is cheaper than the alternative. Hiring late means running the team over capacity for a full quarter, losing proactive work, absorbing preventable tickets, and risking client churn while the new person ramps. A brief period of extra headroom is a small, predictable cost; a service slip in front of clients is a large, unpredictable one.
Related articles
Running a Profitable Managed IT Services Business — the pillar.
Balancing Ticket Load So One Tech Isn't Drowning While Another Coasts — rule out imbalance before you hire.
Scheduling Big Rollouts Without Stalling Day-to-Day Support — protecting capacity during projects.
Why Jobs Take Longer Than You Quoted — the general estimation problem.
Where Time Leaks on a Typical Job — where hidden load hides.
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.