What’s the Right Amount of IT Staff for Your Company?

The correct number of IT staff is always obvious. It is either slightly fewer than you currently have, or slightly more, depending on whether the last system outage happened yesterday or six months ago.

That observation isn’t a joke. It reflects how most executive teams actually think about technology staffing.

Certainty around headcount tends to arrive only after something breaks, and even then leadership quickly reframes the event as an anomaly rather than a signal. Before the incident, the team felt “bloated”. Afterwards, it looked “dangerously lean”. The number never moved. Only the story did.

A widely held belief says a correct ratio must exist: users to IT staff, revenue per technologist, tickets per engineer. Something neat enough to benchmark, graph, and approve. Ideally with decimals. Executives keep this belief alive because it feels disciplined. Unfortunately, it’s also wrong.

The comforting fiction of ratios

Boards like ratios. Ratios suggest control, and control suggests governance. Somewhere, surely, a correct answer exists for how many IT staff a £500m company needs. Without one, civilisation would start to feel unstructured.

Most IT ratios, however, quietly assume technology behaves like a utility: stable, predictable, and largely inert. Electricity, but with worse branding.

In reality, technology behaves more like an organisational mirror. It moves constantly and reflects behaviour with uncomfortable accuracy. Every workaround, exception, acquisition, regulatory tweak, or “just this once” request leaves residue. People then have to manage that residue.

When executives ask for headcount benchmarks, they usually want reassurance that their organisation is normal. IT staffing refuses to provide it.

Complexity is the real headcount driver

IT staffing doesn’t scale with company size. It scales with how many different things systems must do, how often priorities shift, and how much fragility leadership will tolerate.

Picture a mid-sized organisation running:

• three ERP systems (for reasons no one can now reconstruct),
• five customer databases (none fully trusted),
• bespoke integrations sustained by folklore,
• and a regulatory environment that changes annually.

That company will need more IT staff than a larger business running a single coherent platform with the discipline to say “no”.

Boards often find this surprising because complexity usually arrives dressed as progress. Each decision looked sensible at the time. Together, they produce an organisation that needs people simply to stop it tripping over its own feet.

The invisible labour problem

IT teams often appear overstaffed because much of their work prevents problems rather than fixes them. When systems behave, nothing seems to happen. When they don’t, observers assume nobody prepared.

This gap creates a familiar executive hallucination: that IT staff only work during incidents. The rest of the time, one assumes, they adjust monitor heights and reset passwords for extended family.

Effective IT teams, in practice, spend most of their time compensating for decisions made elsewhere. Product launches with immovable dates. Acquisitions that introduce “temporary” parallel systems. Security requirements added after contracts close. None of this shows up cleanly in a headcount spreadsheet.

When “lean” becomes brittle

Every organisation enters a phase where it feels proud of how lean its IT team looks. This phase usually arrives alongside phrases like “automation”, “self-service”, and “doing more with less”.

Occasionally, that confidence holds. More often, it masks deferred cost.

Lean IT teams function because individuals absorb risk personally. They stay late. They remember undocumented systems. They respond because they care. That arrangement works until it doesn’t. At that point, the organisation realises that resilience came from private sacrifice.

The early warning sign isn’t outages. It’s bus-factor anxiety. When senior leaders start asking, “What happens if Alex leaves?”, the answer rarely inspires calm.

Outsourcing is not a headcount strategy

Replacing internal staff with suppliers doesn’t reduce the amount of IT work. It simply moves uncertainty around.

Organisations still need people who understand their systems, translate business intent, and challenge suppliers without hesitation. Without that capability, headcount falls while invoices rise, which looks clever briefly and fails steadily.

Outsourcing works when complexity stays low and expectations remain stable. Many organisations attempt it precisely when neither condition applies.

The only useful question

The real question isn’t “How many IT staff should we have?”

A more honest version asks: What level of operational risk are we genuinely willing to tolerate, and do we admit it?

If leadership wants very little risk, headcount will follow. If it wants some risk, but only as long as it stays invisible, the numbers will never add up.

IT staffing isn’t about efficiency. It’s about how much uncertainty leaders expect people to absorb on their behalf.

Some organisations pay for slack, resilience, and institutional memory. Others run close to the edge and hope nothing important breaks during a board meeting.

Both approaches can work. Trouble starts when leadership funds one and claims the other.

A quiet test for executives

To gauge whether your IT team is sized correctly, try this:

Ask what the team has deliberately not done because time ran out.

If the answer includes documentation, security hardening, refactoring, succession planning, or technical debt reduction, you’re running lean.

If they say “nothing significant”, you are either exceptionally well run or about to be surprised.

The right amount of IT staff allows an organisation to change without holding its breath.

Most companies only discover that number after exhaling too late.