Overtime, burnout, client risk, the real price of “we’ll get to it.”
There’s a specific kind of quiet that settles over a business when a technical role goes unfilled. Nobody panics on day one. The team absorbs the work, a project manager reshuffles a sprint, someone senior picks up the on-call rota for a few extra weeks. It feels manageable. That’s exactly what makes it dangerous, the cost of a vacant seat doesn’t arrive as a single bill. It accrues quietly, week after week, until it’s too large to ignore.
The overtime tax
The first cost shows up on a timesheet. When an infrastructure or engineering role sits empty, the work doesn’t pause, it redistributes. Existing team members pick up the slack, often without anyone formally deciding they should. Three or four extra hours a week feels tolerable at first. Multiply that across a team of five or six people, sustained over two or three months, and you’re looking at the equivalent of another full-time salary spent on overtime, project delays, and rushed handovers, without ever actually hiring anyone.
Burnout doesn’t announce itself
The second cost is harder to see on a spreadsheet but far more expensive to fix. Sustained overload changes how people show up to work. Engineers who were engaged and proactive six months ago start doing only what’s asked. Response times slip. Small mistakes creep in because nobody has the bandwidth to double-check their own work, let alone anyone else’s. Then, often just as the business finally opens a requisition, one of the team members carrying the extra load hands in their notice because the seat that should have been filled months ago was never filled, and they were the ones covering for it. Replacing a burned-out senior engineer costs far more, in time and money, than filling the original vacancy ever would have.
The client sees it before you say a word
The third cost is the one that should worry a leadership team most: client risk. In IT and technology delivery, a vacant seat rarely stays invisible for long. Response SLAs slip. A project milestone that used to land on time starts landing a week late, then two. A client who’s used to a dedicated point of contact suddenly finds themselves passed between three different people, none of whom have full context. None of this needs to be dramatic to do damage, a client doesn’t need a catastrophic failure to start quietly benchmarking other suppliers. Trust erodes in small increments, and by the time it shows up as a lost contract or a renewal that doesn’t happen, the actual cause, an unfilled seat from four months earlier, is long forgotten.
“We’ll get to it” is the most expensive plan there is
The instinct to delay a hire, to see if the team can absorb it a little longer, to wait for the “right” candidate rather than moving on a strong one, is understandable. Recruitment takes time and money, and it’s tempting to treat it as a cost you can defer. But every week a critical technical seat stays empty is a week of overtime accruing, morale eroding, and client confidence quietly draining away. None of that shows up as a line item until it’s already a problem: a resignation, a missed deadline, a client conversation that starts with “we need to talk.”
The MSPs that handle this well don’t treat hiring as a reactive fire drill. They treat time-to-fill as a metric worth protecting, because they’ve done the maths on what a vacant seat actually costs, not just in salary not paid, but in overtime, attrition risk, and client goodwill. Filling a role a month faster isn’t just a recruitment win. It’s the difference between a team that’s stretched and a team that’s breaking, and between a client who stays and one who’s already looking elsewhere.
