When a growing business shops for an IT provider, the instinct is often to ask how big they are, on the assumption that a bigger team means more capability. It is an understandable assumption, and it is usually the wrong question. Capability is about process, tooling and accountability, not headcount. Here is what actually predicts whether a provider can support a growing business properly.
Why team size is the wrong question
A large provider with poor processes and an overloaded ticketing queue can deliver a worse experience than a smaller, tightly run one. Size tells you about capacity in the abstract. It tells you nothing about whether every ticket gets triaged consistently, whether the same standard applies to every client regardless of how loudly they complain, or whether backups are actually tested rather than just scheduled. Those are the things that determine whether a provider can actually support you as you grow.
Questions that actually reveal capability
A handful of specific questions cut through this far more reliably than “how many staff do you have.”
Ask what their average response time is, and how it is measured. A marketing figure (“we respond fast”) is different from a reported figure taken from actual ticket data. Ask when they last tested a restore, not just when the last backup ran. A backup that has never been tested to restore is a hope, not a safety net. Ask who owns a problem that sits between two systems or two vendors, because the answer should be a named person or role, not a shrug. Ask what is explicitly excluded from their agreement, since every provider has exclusions and a confident one will tell you before you ask. And ask whether you can speak to a client who left them. A provider secure in their own service will usually say yes.
Red flags regardless of size
Certain warning signs matter whatever size the provider is. Vague answers about response time measurement. Reluctance to put service commitments in writing. No clear ownership when an issue crosses between email, phone systems and security, three areas that are frequently split across different vendors. And any provider that cannot describe their patching and monitoring process in specific, concrete terms, rather than general reassurance, is one to be cautious of.
What a well-run provider looks like from the outside
A well-run provider, regardless of team size, tends to share a few visible traits. Every ticket follows the same documented process, so the outcome does not depend on which technician happens to answer. Monitoring and patching run continuously across every client, not just the ones who escalate loudly. Response times are tracked against real data, not asserted. And the provider is willing to be specific about what they do and do not cover, before a contract is signed rather than after something goes wrong.
None of this requires a large team. It requires discipline. A ten-person provider running a tight, documented process will usually outperform a fifty-person provider running an inconsistent one, and a growing business is generally better served by the former.
Frequently asked questions
Not necessarily. Response time depends on process and monitoring discipline, not headcount alone.
“When did you last test a restore, not just a backup?” It reveals more about actual discipline than almost any other question.
The better question is whether their process scales, not whether their current size matches yours. A documented, repeatable process scales far more reliably than headcount alone.