How to choose an IT provider: 7 questions to ask before you sign

Choosing an IT provider is like choosing an accountant or a lawyer: the mistake doesn't show up right away — it shows up at the worst possible moment, and it costs more than everything you saved by choosing carelessly. The trouble is that in the pitch everyone looks the same: "reliable," "24/7," "tailored approach." The difference surfaces later.

To make it surface before you sign rather than after, here are seven questions. They work with any provider, not just us. A good partner answers them calmly and specifically; on the weak spots you'll hear generalities — and that tells you everything.

1. How fast do you respond, and is it in the contract?

"Fast" is not a timeframe. Ask for specifics: how many minutes or hours until you get a first response to a critical failure, during and outside working hours. And crucially, are those targets in the contract or just spoken?

A healthy answer sounds like a formula, not a promise — ours is spelled out in full in Always on watch: monitoring in minutes, an engineer inside 30, round-the-clock escalation outside working hours. Response and resolution targets are written into every contract. If the targets aren't in the contract, they don't exist.

2. How do backups work, and who tests them?

"We have backups" isn't enough. Ask what principle they're built on, whether there's an off-site copy, and — most important — when someone last verified that data actually restores from them.

A good sign is a provider who talks about restore testing, not just the fact of copying. A copy no one has ever restored is an assumption, not protection. If the answer is "well, it backs up automatically" with no mention of testing, that's a red flag.

3. Is pricing transparent, or do I learn the number on the invoice?

Ask what your monthly payment is made of and what happens if the workload grows. Ideally the price is fixed and predictable, not "as billed" with end-of-month surprises.

Ask separately about price reviews. A healthy model is one where your rate is fixed in the contract rather than quietly changed, and reviewed once a year against real statistics: how many requests, which incidents, how fast the response. And reviewed both ways: fewer problems is grounds to pay less, not only more.

4. What happens to our data and access if we part ways?

This question separates partners from hostages. Ask directly: if we decide to leave, what stays with us? The good answer is that all documentation and all keys remain yours, and any next engineer picks up where the last one left off.

The bad answer is when access, passwords and "knowledge of your system" live in one person's head or on the provider's side. That means you're not a client but a hostage: you can't leave, because leaving costs you control of your own IT.

5. Are we month-to-month, or locked in for years?

Long contracts with stiff exit penalties are a way to hold onto a client who's hard to hold onto with quality. Ask about exit terms. Month-to-month with no multi-year locks is a sign of confidence: the provider expects you to stay because you're happy, not because you can't leave.

This doesn't mean long commitments are never justified — sometimes they are. But they should be your deliberate choice, not a trap in the fine print.

6. Will I see what's happening, or take it on trust?

Ask about transparency. Is there a way to see the state of your systems, the history of work done, and an access log — who did what, and when? Or does it all reduce to "everything's fine on our end"?

We call it a technical passport: live status of every system, a history of failures and completed work, backup status with the date of the last test, an inventory of hardware and licenses, and an access log. Your provider doesn't have to call it the same thing. It does have to let you verify their words instead of just hearing them.

7. Are you a team, or one person?

One person physically can't know servers, networks and security equally well, and that person takes holidays, gets sick, and quits. Ask what happens to your IT when the key person is unavailable. If the answer is "well, you wait until they're back," you've just found the single point of failure in your own business.

A team closes that gap: different specialists for different tasks, and someone always on the line. It isn't always more expensive than an in-house hire — often the opposite, because you pay for outcomes and availability, not for 100% of the salary of someone busy 50–60% of the time.

The last, most honest point

There's one phrase to fear more than any price: "we guarantee everything will work." Nobody can guarantee that without seeing your equipment, and anyone who promises it regardless of that equipment's condition is, in fact, accountable for nothing.

An honest provider puts it differently: here's what we take full responsibility for, here's where the decision is yours, and if you choose to wait on a recommendation of ours, we'll record that in writing, with a date, so it's clear where our responsibility ends and your choice begins. That answer — not the prettiest pitch — is the sign you can sign a contract with this provider.

Want to start from zero? An independent look at your own IT costs nothing: a free audit that shows the risks and gives you a transparent estimate is where real cooperation begins — with us or not.