Most small businesses pick IT support the same way they pick a plumber: something breaks, they Google fast, they call whoever answers. That works out fine until it doesn't - and by then you're locked into a contract with someone who bills by the hour to tell you your server is old.
Here's the evaluation checklist I'd use if I were hiring someone like me.
1. Ask how they price before you ask anything else
Hourly IT support has a built-in conflict of interest: slow work pays more, and prevention - which takes time up front and prevents billable emergencies later - pays nothing. Flat-rate providers are aligned with getting the job done right the first time. If a provider can't give you a fixed number for a defined piece of work, that tells you something.
2. Ask what happens at 2pm on a Tuesday
"We support small businesses" means nothing. Ask specifically: when something breaks mid-workday, who answers, how fast, and can they actually fix it remotely? Remote support done well resolves most issues in minutes instead of scheduling an on-site visit for next week. Local presence matters for hardware and cabling; everything else should be handled remotely, immediately.
3. Ask who does the work
Some shops send a salesperson, then hand your account to whoever's available. You want to know the actual person doing the work, their background, and whether you'll talk to the same person twice. Fourteen years in enterprise IT taught me that context is half the value of good support - a person who knows your setup fixes things faster than a stranger reading your ticket history.
4. Ask about lock-in
Monthly contracts make sense for genuine ongoing needs. But if you just need an overhaul, a migration, or help when something breaks, being pushed into a retainer is about their revenue model, not your infrastructure. Good providers earn continued business; they don't need paperwork to guarantee it.
5. Notice whether they explain things
If they can't explain what they're doing in plain English, either they don't understand it or they're hiding behind jargon. Both are bad.
You don't need to become technical. But you should finish every conversation understanding what was done, why, and what happens next. That's not a nice-to-have - it's how you stay in control of your own business.
How I answer these questions
Since this post would be strange without it: I'm based in Sacramento, serve clients remotely across all 50 states, quote flat rates per project, require no contracts or retainers, and you work directly with me - fourteen years of enterprise IT behind every fix. My IT services page covers overhauls, migrations, networking, security hardening, and remote support.
Whatever you decide - even if it's not me - run any provider through those five questions. The answers separate partners from vendors.