The outsourced IT helpdesk decision usually shows up about six months after it should have. By then the in-house IT person is buried, holiday cover is broken, and the founder is fielding password reset tickets at 9pm. I’ve seen this exact pattern at four London SMEs in the past two years.
The wider question isn’t whether outsourcing your IT works, it does, for most SMEs north of about 30 staff. The harder question is when to switch, what to expect, and how not to pick a bad provider. Most of the bad outcomes I’ve watched come from the same three mistakes, and they’re all avoidable.
When an outsourced IT helpdesk actually makes sense
The honest threshold for SMEs is around 25 to 35 employees, give or take depending on how technical your team is. Below that, a part-time consultant on a couple of days a month usually beats a full helpdesk arrangement. Above 50, you almost certainly need either a strong in-house lead or a fully managed helpdesk, because half-measures break.
Three signals point to “switch now”. First, your one in-house IT person hasn’t taken a proper holiday in 12+ months. Second, ticket response times have crept past 24 hours and nobody can tell you why. Third, you’re hiring engineers and they keep getting pulled into password resets instead of proper project work.
Stop trying to fix this with another internal hire. The economics rarely work below 80 staff. A decent outsourced helpdesk costs roughly £25 to £40 per user per month in London, and that covers most of what a junior IT hire would handle, but with proper holiday cover, escalation paths, and tooling already in place.
Most companies cross that line about a year later than they should.
What outsourced IT helpdesk arrangements actually cost
The headline rate isn’t the whole picture. A fair London SME outsourced IT helpdesk contract sits in the £25 to £40 per user range monthly, but you also need to factor in onboarding (one-off £500 to £2,500 depending on environment complexity) and the cost of any tooling licences they don’t include in the headline price.
Where it gets interesting: most providers bury the cost of after-hours coverage, hardware procurement support, and project work outside the contract. The genuinely good ones price these as line items so you can choose. The bad ones bundle them in vague “additional services” terms and stack invoices later. Read the SLA section like you’d read a tenancy agreement.
Well, actually it’s a bit more complicated than that.
Onboarding done badly costs more than the first six months of the contract combined. Document your asset inventory, your domain admin accounts, and your line-of-business apps before the kickoff call. Providers that ask for this upfront are giving you a signal: they know what they’re doing. Providers who say “don’t worry, we’ll figure it out as we go” are about to charge you for the figuring out.
What to look for in a provider
Three things matter more than the brochure. First, response SLAs that distinguish urgent (P1) from cosmetic (P4) issues, because a flat “we respond in 4 hours” SLA is a red flag, not a guarantee. Second, Cyber Essentials certification at minimum, because without it an outsourced helpdesk with admin access to your network IS your supply chain risk. Third, the right named contact when something breaks at 8am on a Monday.
Ignore the testimonial wall. Every MSP has 12 happy quotes on its homepage. Ask for the names and emails of three current clients you can speak to without sales-team mediation. The willingness to share that, not the answer, tells you what you need to know.
There’s also a useful reverse test. Ask the sales contact what their average ticket-to-resolution time was last quarter. If they say “we hit our SLAs” instead of giving you a number, the answer is probably bad. Real numbers are easy to share when they’re good, and hand-waving is the language of providers who don’t measure their own work.
The decision is simpler than the marketing makes it look.
What to do this week
If you’re seriously considering an outsourced IT helpdesk for the first time, do three things in the next seven days. Count your tickets, because even a rough log of what your IT person handled in the last month gives you the volume baseline you need. Map your current pain points by frequency, not severity. And book three discovery calls with potential providers, because three is the minimum number to compare honestly. The decision usually makes itself once you’ve seen what good actually looks like.