Outsourced IT Support

When nobody owns IT any more

Very few businesses sit down and decide to outsource their IT. They arrive at it. The person who was quietly good with computers leaves, or moves into a role that has nothing to do with laptops, and a month later nobody can say who holds the Microsoft 365 global admin account. Or the company passes fifteen or twenty staff and the informal arrangement stops scaling: every new starter eats half a day of someone’s week, and that someone was hired to do something else.

The choice is usually binary. Hire a person, or hand the function to a provider. “Outsourced IT support” is a vaguer phrase than it sounds, and the distance between a helpdesk contract and a real department replacement is where most of the disappointment lives.

What a whole IT function actually contains

Ask a business owner what IT is and most will describe fixing things. Fixing things is the visible tenth of it. Underneath sits a set of jobs that only become obvious once nobody is doing them:

• Identity and access — who has an account, what it can reach, and what happens to it the day they leave. Offboarding is the job small businesses skip most often, and the one most likely to turn into an incident.
• Licensing and subscriptions — knowing what you pay for, who actually uses it, and whether you are funding eleven licences for eight people.
• Patching and hardware lifecycle — keeping machines current, and knowing when a laptop is far enough past its useful life that replacing it beats nursing it.
• Backup verification — not “the backup job reported success”, but somebody restoring a file and confirming the restore is usable.
• Supplier management — broadband, phone lines, the line-of-business software vendor. Chasing them is work, and it is nobody’s favourite work.
• Security posture — multi-factor authentication, what staff may install, and what happens in the hour after someone types their password into a fake login page.
• Documentation — a written record of how the systems fit together, so the knowledge stops living in one person’s head.
• Budget and decisions — a view of what is coming, roughly what it will cost, and a recommendation you can act on rather than a menu handed back to you.

A contract that covers the first line of that list and nothing else is a helpdesk. That may be all you need, and there is no shame in it. But it is not a department, and it will not stop the licence bill drifting or an ex-employee’s mailbox quietly collecting supplier invoices for another eighteen months. When you compare providers, compare which of those jobs each one will genuinely own.

The honest case for hiring instead

An internal hire has one advantage nothing else replicates: they are in the room. They overhear the sales team complaining about the CRM before it becomes a ticket. They learn which system the whole month-end depends on. They can be pulled onto something at ten seconds’ notice, and their attention is not split across other clients. If your business runs on one unusual piece of software — a bespoke database, or the practice-management system behind a dental surgery — someone who lives in it daily is often worth more than a broader team who meet it occasionally.

The limits are structural rather than a criticism of the person. One individual cannot be on holiday and on call. One individual cannot credibly be a network engineer, a Microsoft 365 specialist, a security analyst and a hardware buyer; the ones who claim all four usually turn out to be strong in one. And a lone hire has nobody to check their work. If their backup design is wrong, there is no one in the building qualified to notice, and that gap stays invisible right up until the day it is the only thing that matters.

Outsourcing trades intimacy for breadth and continuity. You lose the person in the room. You gain cover that does not disappear in August, a second opinion on design decisions, and specialisms you could never justify employing. Our guide to in-house versus outsourced IT works through the same trade-off in more detail.

Where the line usually falls

Between roughly five and fifty staff is where handing over the whole function makes the most sense. You have enough systems to need real management, enough people to make downtime expensive, and not enough of either to fill an experienced person’s week with work worth their salary. Below five, most businesses want something lighter — a way to reach an engineer when something breaks, rather than a department.

Above fifty or sixty, the maths changes again. At that size an internal IT manager has a genuine full-time job and, more usefully, ownership of the relationships and the roadmap. What businesses of that size normally want is reinforcement rather than replacement, which is what co-managed IT support is for: your person keeps ownership, and an outside team takes the overflow, the specialisms and the projects.

What outsourced IT actually costs

There is no single number, and any provider who offers one before looking at your setup is guessing. The things that genuinely move the price are your headcount and device count, what sits in your estate (a business on Microsoft 365 with laptops and no server is simpler to run than one with an on-premise server, a legacy application and a site-to-site VPN), whether you need cover outside office hours, your compliance load, and the state of things on day one. An estate that has gone years without an owner usually needs remediation before it can be run efficiently, and a straight provider separates that work from the ongoing fee rather than burying it.

The pricing model matters as much as the price. A fixed monthly fee puts the provider on the same side as you: every fault they prevent is time they get back, so they have a reason to fix root causes rather than symptoms. Hourly billing does the reverse — it pays for the visit, not the outcome — which is reasonable for occasional work and poor for running a function. Read the boundary of the fixed fee carefully, because that is where surprise invoices are born. Our breakdown of what IT support costs in the UK goes through each model properly.

What the handover actually involves

The first few weeks are mostly archaeology, and it is rarely tidy. Nearly every takeover turns up something nobody knew about: a domain name registered to the personal email address of someone who left years ago, a mailbox still receiving supplier invoices, a backup that has been failing silently, an admin account shared by four people. None of it is unusual or anyone’s fault — it is what happens when a function has no owner.

After that, the order matters. Administrative control comes first, because you cannot manage what you cannot administer: domain, tenant, firewall, backup console. Documentation follows, so the setup exists somewhere other than in conversation. Then the risks that would hurt most if they landed — unprotected accounts, unverified backups, machines that can no longer receive security updates. Improvements come last, once the things that could genuinely damage the business are handled. Day-to-day managed IT support runs alongside the whole process, because the printer still jams during a migration.

What outsourcing does not fix

This is worth saying plainly, because the sales version of this page would not.

Outsourcing does not create a budget. If a machine is years past its useful life and the answer to every replacement quote is “next year”, any provider will keep it limping and you will keep losing hours to it. The advice changes; the decision does not.

It does not remove the need for someone internally to own decisions. Somebody at your end still approves spend, decides who gets access to what, and answers yes or no when a recommendation lands. That role is usually small, but it cannot be handed over with the rest.

And it does not turn a bad process into a good one. If three people share one login because that is how the software is licensed, that is a commercial problem wearing a technical costume, and the fix is a conversation with the vendor, not a change to your network.

What to ask before you sign

Three questions separate providers who run functions from providers who answer phones. Ask who holds the administrative credentials to your domain, your Microsoft 365 tenant and your backups, and whether you can have them on request — the only good answer is that you own them and can have them whenever you ask. Ask what happens on the day you leave, because a provider with a clean exit process has nothing to protect. And ask them to describe the last thing that went badly wrong for a client and what they changed afterwards. Vague reassurance is a bad answer; so is a provider who cannot recall anything ever going wrong. Our guide to choosing an IT support company covers what else to check.

If you are unsure which side of the decision you are on, that is a normal starting point. A review of what you run, what it costs and where the gaps sit usually makes the answer obvious — and if it turns out you need less than a full handover, ongoing business IT support may be the better fit.