"Choosing an IT support provider comes down to verifiable answers on a short list of questions: guaranteed response times in writing, security included as standard, references from businesses like yours, a documented onboarding process, and a contract you can actually read. This checklist covers each one and the answers that should concern you.
What should you look for first?
Start with the service level agreement. Any provider can promise fast responses; the question is what is guaranteed in writing, measured how, and what happens when it is missed. Ask to see the standard SLA before any sales meeting: a provider reluctant to share it has answered your question.
Which questions reveal the most?
Five questions do most of the work. How many clients do you support with a team of what size, which tells you whether you will matter. Who exactly answers the phone, which distinguishes a real helpdesk from a call-back promise. What is included versus billable, which surfaces the surprise invoice culture. How do you handle security as standard, which separates modern providers from box-shifters. And can we speak to two clients our size in our sector, which tests everything else they have said.
How important is local presence?
It depends on your hardware reality. A fully cloud business can live with remote-only support; anyone with offices, servers or sites needs engineers who can attend, and the honest test is where the provider's engineers are actually based rather than where its website says it covers. For West Midlands businesses, ask specifically how often you can expect proactive on-site time, not just emergency attendance.
What should be in the contract?
Clear inclusions and exclusions, the SLA with measurement and remedy, data protection terms including where your data and credentials are held, exit provisions that guarantee handover of documentation and admin access, and a term length you are comfortable with. Treat any resistance to exit provisions as the answer it is: good providers keep clients through service, not lock-in.
What does good onboarding look like?
A structured audit of your environment, documentation of every system and credential, deployment of monitoring and security tooling, introductions and ways of working for your team, and a named point of contact. Ask each candidate to describe their onboarding process step by step; the ones with a real process describe it instantly, and it tells you how the relationship will run. Our guide to what managed IT support includes covers what the ongoing service should then look like.
When should you switch providers?
When response times drift, when every fix generates an invoice, when security is repeatedly an extra, or when you realise nobody has proactively reviewed anything with you in a year. Switching feels disruptive but a capable incoming provider manages the entire handover, including dealing with the outgoing supplier. LeapIT onboards businesses across Birmingham and the West Midlands from exactly this position: our outsourced IT support page covers how the transition works.
Frequently asked questions
How long should an IT support contract be?
Twelve months is standard and reasonable. Be cautious of long initial terms sold with discounts, and pay attention to notice periods and what happens to your documentation at exit.
Should we choose the cheapest quote?
Compare what is included before comparing figures. Quotes that look cheaper often exclude security, out of hours cover or on-site time, which returns as invoices later.
Do certifications matter?
Recognised signals such as Cyber Essentials certification and vendor partnerships indicate a provider takes its own standards seriously. Treat them as a filter, then test service quality through references.
How do we compare providers fairly?
Give each candidate the same written brief covering your users, sites, systems and priorities, and ask for their standard SLA and a sample contract with the proposal. Identical inputs make the differences visible.
If you are reviewing providers, LeapIT will happily be measured against this checklist, including the two references. That is what it was written for.
