Selecting a provider of managed IT services for small business is closer to hiring a small department than to buying a product. The contract will shape how quickly problems get resolved, who holds the keys to your systems, and how easily you could change direction later. None of that is visible in a price list.
Most evaluation processes lean on the sales presentation, which is designed to be reassuring. A more productive approach is a structured set of questions asked early, with the answers recorded in writing, so that proposals can be compared on substance rather than on confidence of delivery.
The questions below cover scope, service levels, escalation, credentials, documentation and exit. They are ordered so that a weak answer early on makes the later ones unnecessary.
Define Your Own Requirements Before You Listen to Anyone
No provider can scope what you have not described, and vague requirements tend to be filled in with the cheapest available interpretation. Before taking meetings, write down the number of users and devices, the locations involved, the systems whose failure would stop revenue, your operating hours, and any regulatory obligation that touches your data.
That short inventory becomes the basis for comparing proposals. It also keeps the conversation on your terms, because you are asking for coverage of something specific rather than reacting to a package that was designed for someone else.
Service Levels: Commitments Versus Targets
Ask how the agreement distinguishes what the provider promises from what it merely aims for. The difference matters when a system is down and your team is standing still.
How priorities are classified
A useful schedule names concrete examples of each priority level instead of vague adjectives. Does a single user unable to work count as urgent? Does a degraded system that still functions count as lower priority than a total outage? The classification determines everything that follows.
Response, restoration and resolution
These three are often blended in marketing material but mean different things. Response is acknowledgement. Restoration is a workaround that gets people working again. Resolution is the permanent fix. Ask for a target for each, and ask which of them is binding.
Coverage hours and how they are measured
Confirm whether the clock runs continuously or only during business hours, when the business day starts in the provider’s time zone, and how holidays are treated. A four-hour target that pauses overnight is a very different commitment from one that does not.
Escalation: The Route When the First Attempt Fails
Every ticket is easy until it is not. Ask who receives a request first, what qualification that person holds, when a ticket is escalated, and who owns it after that. Then ask whether you can reach a manager or technical lead directly when something critical is stuck.
Look for a named route rather than a general queue. A provider that can describe its escalation steps clearly has usually thought about them; one that answers with reassurance has usually not.
Access, Credentials and Ownership
Support requires privileged access, which is why this area deserves careful handling. Ask which accounts the provider will hold, whether administrative access is protected with multi-factor authentication, how credentials are stored, and what happens when a technician leaves the firm.
Ownership should be explicit in the contract: accounts, data, software licenses, configurations and documentation belong to your organisation, and you can obtain them in usable form. It is worth asking for at least one administrative account that remains under your control and is used only for emergency access.
Documentation and Continuity
A capable provider maintains records of your environment: an asset register, network layout, configuration decisions and the reasoning behind them. Ask to see a sample of the documentation format, not just a promise that documentation exists.
Continuity matters as much as the content. Ask what happens during holiday periods, illness or staff turnover. If one engineer knows your environment and nobody else does, the arrangement is fragile regardless of how well the paperwork is written.
The Exit Path: What Happens If You Leave
The moment to negotiate an exit is while you are still a desirable customer. Ask what notice period applies, whether any transition fee exists, and what assistance the provider will give during handover.
A reasonable answer includes cooperation with a successor, return or transfer of credentials and data, and a timeline for withdrawing access. An evasive answer is a warning sign, because a provider confident in its service has little reason to trap clients.
A Due Diligence Question List
- Which users, devices and locations are covered, and how are changes billed?
- What response, restoration and resolution targets apply to each priority level?
- Which service levels are contractual commitments rather than internal goals?
- How does escalation work, and who do we contact when a ticket stalls?
- Who holds administrative credentials, and how are they protected and stored?
- What documentation will we receive, in what format, and how often is it reviewed?
- Which security responsibilities remain with our organisation?
- What is the notice period, and what does handover include?
Frequently Asked Questions
How many providers should we evaluate?
Three is usually enough to reveal the range of approaches without consuming weeks of effort. Fewer than three makes comparison difficult; many more tends to produce proposals that are hard to distinguish from one another.
Should we weight price heavily in the decision?
Price matters, but a proposal that is much cheaper than the others deserves closer scrutiny of what it excludes. Over time, the cost of an excluded service tends to exceed the saving that justified the choice.
What is the strongest warning sign during evaluation?
Reluctance to put specifics in writing. Estimates of time, coverage and cost that only appear in conversation cannot be held to later, and any provider unwilling to commit them to paper is offering flexibility that works only one way.
Is a short trial period possible?
Some providers offer an initial assessment or a limited scope arrangement before a longer commitment. Even a defined first quarter can be valuable, provided the exit terms for that period are clear from the outset.
Choosing Is Mostly About Fit and Clarity
The provider with the most impressive presentation is not necessarily the one that will serve you well. The stronger signal is precision: clear scope, defined priorities, documented escalation, and a straightforward answer about how the relationship ends.
This article provides general information about evaluating technology service providers and is not professional, legal or financial advice. Requirements vary by organisation, so seek qualified guidance before entering into a contract.