Most IT support relationships do not collapse because the technicians are incompetent. They collapse because nobody wrote down what "support" actually means. Six months in, you are arguing about whether a server migration was included, your new starter waited two days for an account, and the only person who knows your firewall password is a contractor who stopped replying to emails.
All of that is avoidable, and almost all of it is decided before the contract is signed. Here are the mistakes worth steering around.
"Proactive monitoring." "Best-practice security." "Responsive support." These phrases feel reassuring and mean nothing. A managed services agreement should contain a service schedule that lists exactly what is covered and, just as importantly, what is not.
Push for specifics on the things that cost you money: how many devices and users are in scope, whether patching covers third-party applications or only the operating system, whether licence renewals and vendor chasing are included, and how project work is priced separately from routine support. A useful test is the reporting line. If the provider promises monitoring, ask what report you will receive each month and who reads it with you. No report, no monitoring.
"We'll get back to you quickly" is not a commitment. Response times belong in the contract, with two separate numbers: how long until a human acknowledges the ticket, and how long until the issue is resolved or worked around.
Ask them to define priorities in writing, with examples rather than labels:
Then ask the awkward follow-ups. Does the clock pause overnight? Is after-hours cover included, charged per call, or simply unavailable? What happens if they miss the target — a service credit, a review meeting, or nothing? A provider who is uncomfortable answering these questions in writing is telling you something.
This is the mistake that hurts most, because it is the hardest to undo. Without documentation, you cannot leave, you cannot audit, and you cannot recover quickly from a serious failure.
Documentation needs to be a deliverable in the contract, produced early rather than "when we get to it." At onboarding, expect a network diagram, an asset and licence inventory, a list of admin accounts, backup configuration details, and contact details for your ISP, phone system and software vendors. Most important: credentials should sit in a password manager that your business owns, with the provider given access as a user. If the master keys live only in their systems, you do not have a supplier — you have a hostage situation.
Read the termination section before you read the pricing page. Look for the notice period, whether the agreement auto-renews and how far in advance you must cancel, how price increases are handled, and whether the provider is obliged to assist with a transition.
Two clauses are worth insisting on. First, transition assistance for a defined period after notice is given, at a stated rate. Second, a clear statement that your data, documentation and credentials belong to you and will be returned in usable formats on request.
The headline price per seat is the easiest number to compare and the least useful. Two quotes can look similar while one excludes after-hours support, project labour, hardware procurement and the coordination of third-party vendors — the exact work that eats your time.
Ask each provider for a total first-year cost under three scenarios: business as usual, one major project such as a cloud migration, and an emergency like a ransomware incident. The quotes that look cheap often stop looking cheap once the scenarios are on the table.
You are handing a supplier privileged access to your systems, so their internal practices matter as much as yours. Ask whether they enforce multi-factor authentication on their own admin accounts, how they separate privileged access from everyday accounts, whether staff are background-checked, and how they would notify you if one of their tools or accounts were compromised.
Also ask who actually looks after your account. Will you have a named primary contact and a backup who knows your environment, or a rotating helpdesk queue where every call starts from zero?
Sales calls reward polished answers. Scenarios expose the real process. Describe a specific situation and ask them to walk you through it step by step: a director's laptop is stolen at an airport on a Friday evening with email logged in; a departing employee may have copied files to a personal drive; your main file server fails at 7am on a Monday.
Listen for calm, ordered answers that mention verification, containment, communication and recovery times. Vague reassurance is a warning sign.
None of this requires legal expertise, just a willingness to ask direct questions and wait for written answers. Take the extra week before signing. It is far cheaper than the year you might otherwise spend untangling a contract that never said what anyone thought it said. If the agreement involves significant liability, data protection obligations or regulatory requirements, have a qualified solicitor review it — the cost is small next to the risk.
Photo: 089photoshootings / Pixabay
Unassigned seats, duplicate subscriptions and forgotten renewal dates drain small IT budgets quietly. Here are ten...
Free antivirus covers basic malware blocking, but paid tiers add phishing defence, VPNs, parental controls, priority...
SSDs cut boot times and survive drops; hard drives still win on cost per terabyte. Here is how to match each drive...
Your trusted source for reliable IT solutions.
