Monday, May 17, 2021
How to Choose an IT Support Vendor
Updated September 2026: in 2021 I posted a short list of what to look for in an IT support vendor: flexibility, cost reduction, mature processes and continuous improvement. I have rewritten it into a fuller guide based on those points.
The original post argued that an IT support model should be scalable and flexible, so a client can choose services to match business needs. It listed cost reduction through the right staffing and the ability to absorb peaks in demand, mature processes built on the vendor's knowledge management and experience with similar clients, and continuous improvement through problem management and long-term fixes that stabilise systems.
What should you look for in an IT support vendor?
- Flexibility: the ability to scale support up or down, and to add services as needs change.
- Relevant experience: support for similar applications and industries.
- Mature processes: incident, problem and change management that follow a recognised framework such as ITIL.
- Knowledge management: documented fixes that reduce dependence on individuals.
- Continuous improvement: fewer repeat incidents over time, not just faster fixes.
How do you compare vendors fairly?
Give each the same data: ticket volumes, applications, hours of cover and current pain points. Ask for a transition plan, a staffing model and service levels with penalties. Speak to their existing clients, ideally ones they did not choose for you.
Where do cost savings really come from?
From fewer incidents and less rework, not only from lower rates. A vendor that fixes root causes can reduce ticket volumes year on year. Ask how they will measure that.
What service levels matter most?
Response and resolution times by priority, user satisfaction, and the backlog of open problems. Too many measures dilute attention; five or six well-chosen ones work better.
What are the warning signs?
Vague answers on staffing, reluctance to share references, and service levels without consequences. A good vendor is specific about how it will earn your trust.
How long should the first contract run?
Long enough to cover transition and a period of stable service, often two to three years, with a review point and the right to exit if service levels are missed repeatedly. A clear exit plan protects you if the relationship does not work.