If you run a business with anywhere from five to fifty people, you've probably had a call with a large IT solutions provider at some point — the kind with decades of history, hundreds of certifications, and client logos from companies you've heard of. They were competent. Maybe even impressive. And the conversation still felt slightly off, in a way you couldn't quite name.
Here's the name for it: you were talking to a company built to solve a different problem than yours.
Large IT solutions providers exist because large organizations need them. A company with thousands of employees, dozens of departments, and a formal procurement process needs a vendor who can navigate multi-stakeholder sign-off, produce compliance paperwork for a security team, and manage a contract that might run into seven figures. Everything about how these providers operate — their sales process, their account structures, their minimum engagement sizes — is shaped by that reality.
None of that is a criticism. It's just a mismatch when the customer on the other end is a 12-person company that needs a cloud migration finished in six weeks, not a six-month evaluation process.
The provider isn't wrong for the job. You're just not the job they're built for.
1. You've never spoken to the person actually doing the work. If every conversation goes through an account manager who then "checks with the technical team," you're paying for a relay system. That's normal — even necessary — at enterprise scale, where one account manager might coordinate a dozen specialists across a client's infrastructure. At small-business scale, it's just a delay you don't need.
2. Onboarding takes longer than the actual project would. Enterprise-grade providers often have onboarding processes — security reviews, master service agreements, SOWs that go through legal — that make sense when the contract is worth millions. If your project is a two-month app build or a network refresh, and onboarding alone eats three weeks, the process is fighting the size of the work.
3. There's a minimum contract size you're stretching to meet. Some providers won't take an engagement under a certain dollar threshold, because it's not worth their overhead to staff it. If you find yourself trying to bundle unrelated work together just to hit a provider's minimum, that's the provider telling you, indirectly, that you're not really their customer.
For a business in the 5–50 person range, the things that actually matter are usually simpler than what a large provider is optimized to deliver:
This is also, generally, where a smaller, specialist consultancy is a better fit — not because it's "friendlier," but because its entire operating model is sized correctly for the problem you actually have.
To be fair to the other side of this: a large provider brings things a small firm can't always match — a long roster of vendor certifications, a global support footprint, deep bench strength if your project suddenly needs twelve specialists instead of two. If you're a 2,000-person company standardizing Microsoft licensing across twelve offices, that scale is exactly what you should be buying.
But if you're not that company, you're paying — in time, in process, in reduced access to the people doing the work — for scale you don't need. The trade-off runs the other way too: a smaller provider won't have the same bench depth or the same list of enterprise partnerships. What you get instead is speed and direct access. Which one matters more depends entirely on the size and shape of your actual problem, not on which provider has the more impressive website.
The honest answer to that last question tells you almost everything you need to know before signing anything.