Outsourcing Your IT Helpdesk vs the Whole IT Function

Ask three business owners what they pay their IT company for and you get the same answer. “They look after our IT.” Ask a harder one — who decided you needed forty-two licences, and when did anyone last check that a backup actually restores? — and the answers separate sharply.

Two different products are sold under one word. One is a helpdesk: a number your staff ring when something breaks. The other is the IT function — the work a department would do if you employed one. Both are legitimate purchases. The expensive mistake is buying the first while believing you bought the second, and finding out on the day something turns out to be nobody’s job.

What a helpdesk contract actually includes

A helpdesk contract is reactive by design, and there is no shame in that. It covers what staff notice: a laptop that will not start, a printer that has vanished, a password reset, a mailbox that stopped receiving. You get a way to raise a ticket, a target for how quickly it is picked up, and engineers who fix what has been reported.

Good ones are very good: quick, patient with non-technical staff, thorough about closing things properly. What they are not is responsible for anything nobody has reported. That distinction stays invisible right up until it matters.

What outsourcing the function adds

Outsourcing the function means somebody outside your business owns the work that has no ticket attached to it. In practice that is:

• Licensing. Someone counts what you pay for against who actually works here, and says so when the two drift. Left alone, licence spend only grows — nobody cancels a subscription by accident.
• Joiners and leavers. A process that runs the same way every time, so accounts are created properly and, more importantly, closed properly. Ex-staff with live access is one of the most common things we find when picking up an existing setup.
• Backup verification. Not “backups are configured” — someone restoring something on purpose, on a schedule, and reporting the result.
• Patching and updates. Applied on a rhythm across every machine, with the exceptions tracked rather than forgotten.
• Suppliers. Chasing the broadband provider, the phone system vendor, the line-of-business software company. Dull work, and genuinely valuable to hand over.
• Documentation. A written record of how your systems fit together, held somewhere other than one person’s memory.
• The budget conversation. A named person who tells you in October which machines will not survive the year, what the renewal will cost, and what should be replaced before it fails.

None of that generates a ticket. All of it costs you money when it does not happen.

The signs you bought a helpdesk and needed the function

You rarely notice this from the invoice. You notice it from the symptoms.

Nobody owns the restore test. Ask who last proved a backup could be recovered, and when. If the answer is “it says it’s running”, that is monitoring, not assurance.

Leavers keep their accounts. Somebody left in spring, IT was told in an email, and the mailbox is still licensed and still receiving. No ticket, so nothing happened.

The licence bill grows and nobody questions it. Every new starter adds a subscription. No leaver removes one. Nobody’s job includes noticing.

Every project needs a new quote. A new office, a Windows upgrade, a move to the cloud — each arrives as a separate proposal from a supplier who has not been thinking about your business in between. There is no roadmap, only a series of quotes.

Security is whatever came in the box. Nobody has reviewed the Microsoft 365 tenant settings, multi-factor coverage or admin rights since setup day. That review never produces a ticket, which is why securing a tenant properly so often turns out to be nobody’s job.

If several of those ring true, your provider is not bad at their job. Owning those things was never in the contract.

When the helpdesk contract is the right buy

Sometimes it is, and a provider who says otherwise is selling rather than advising.

The clearest case is where you already employ someone technical. They know the business and own the direction, and what they need is capacity — cover for holidays and sickness, somewhere to escalate, and a team to absorb the tickets that stop them doing anything else. That is co-managed IT support, and it works precisely because ownership stays in-house. Buying the full function on top of a capable internal person creates two parties who each assume the other did it.

It also fits businesses that are genuinely simple: a handful of staff, everything in Microsoft 365, no server, no compliance obligations worth the name. There is not enough function to outsource. Be honest about whether that still describes you, though — most businesses cross that line without noticing, usually around their fifteenth member of staff or their first regulated client.

What drives the price difference

The gap is not margin on the same work. It is a different quantity of work, most of it done when nothing is wrong.

A helpdesk provider’s cost tracks your ticket volume. A provider who owns the function carries scheduled time whether or not you raise a ticket: the patch cycle, the restore test, the quarterly review, and a named person who holds your account in their head. They carry the risk too, and providers price what they are accountable for.

So the cheaper contract is cheaper because you kept some of the work. That is fine, as long as you know which work you kept and who is doing it. It is the same trade-off underneath in-house versus outsourced IT — except here you can end up with neither by accident.

Four questions that reveal what you are buying

Ask a prospective provider these, and listen for a name and a frequency in the answer.

1. Who checks that our backups restore, how often, and what do we get to see? A good answer is a schedule and a report. A poor answer is a description of the backup software.
2. What happens the day someone resigns? You want a process that starts when HR says so, not when somebody remembers to raise a ticket.
3. Who tells us we are overspending on licences? If the honest answer is nobody, the licence bill is your job — decide that on purpose rather than by default.
4. What does the review meeting cover, and who attends? The function includes somebody senior turning up with a view about next year. A helpdesk contract has no reason to.

None of these is a trap. A provider who only sells a helpdesk should say so plainly, and good ones do.

The point

Buying only the helpdesk is a reasonable decision. Plenty of businesses should. The mistake is buying it while believing you bought ownership, then meeting the gap through a failed restore or a leaver who still had access.

Decide which you want, then check the contract in front of you describes it. If you would rather one company owned the lot, that is what outsourced IT support means. If you would rather keep ownership and buy capacity, say so — that is a different and often better answer.