Many SMBs don't look for an IT service provider on a regular basis and have no dedicated purchasing or procurement department for it. The search then often runs unstructured: a request goes out to one familiar provider, maybe a second one, and in the end gut feeling decides rather than a real, traceable comparison. That costs time, leads to surprise add-on costs, and makes it hard to explain afterwards why that particular provider got the job. The following seven-step approach helps you proceed systematically — without setting up an elaborate procurement process for it.
1. Clarify the need and the goal internally
Before the first request goes out, get clarity inside the company: what problem needs solving, and what's the actual goal behind it? A new inventory management system isn't an end in itself — the real goal might be eliminating a manual handoff between warehouse and accounting. Anyone who only describes the symptom ("we need new software") will later get offers that look impressive on paper but miss the actual problem. A common mistake at this point: the goal only exists in one person's head and is never aligned with the colleagues who will later work with the result. Take deliberate time for this first step — a short internal conversation with the people involved from the relevant department and IT saves several rounds of back-and-forth with outside providers later on.
2. Set the frame
Decide on a rough budget corridor for the project, a target date by which a solution should be in place, and who makes the final decision. These three points don't need to be communicated publicly, but should be settled internally before the first request goes out. Without a budget corridor, you'll get offers ranging anywhere from "can be done in a few days" to "six-figure project" — which makes a real comparison impossible. Without a clear decision-maker, the selection later drags on unnecessarily, because every follow-up question first has to be aligned internally. Especially in smaller companies, it's worth putting this decision-making authority in writing, even if it feels informal — it noticeably speeds up providers' follow-up questions later on.
3. Describe the need in a structured way instead of staying vague
A request like "we're looking for someone for IT support" is hard to answer seriously. Instead, describe the current state (which systems, how many workstations, any particularities), the desired outcome, and the key constraints. The more concrete the description, the better the offers will fit — and the fewer follow-up questions you'll have to answer afterwards. A typical mistake is to keep the description deliberately vague in order to "not rule out any provider": the opposite is true, because vague requests either produce very generic offers, or providers who, out of uncertainty, would rather not respond at all. The guide to writing a scope description covers in detail how a good scope description is put together.
4. Choose the right provider category and specialization
IT services cover a wide field: IT support and managed services, custom software development, consulting and project management, cloud migration, cybersecurity, business software rollouts, infrastructure, or even video surveillance technology each call for different specializations. A generalist can be the right choice for smaller, ongoing matters; for a specific undertaking — such as a cloud migration or a security assessment — a provider with a clearly demonstrated focus in exactly that area usually serves you better. Choosing the right category saves time on both sides: you get better-fitting offers, and providers whose focus doesn't match filter themselves out instead of submitting offers that don't fit. A common mistake is choosing too broad a category to get "as many offers as possible" — the result is usually a larger number of poorly comparable offers rather than fewer, better-fitting ones.
5. Get several offers in parallel, not just one
A single offer can't really be evaluated — you have no benchmark for whether the price, scope, or timeline are realistic. So request several offers in parallel from the start, not one after another. That not only shortens the overall length of the search, it also quickly shows how differently providers interpret one and the same request — a valuable signal for how clear your scope description actually was. A common mistake is asking only a single, already-known provider out of misplaced politeness. That may seem simpler in the short term, but it rules out any reliable assessment of whether price and service are actually in line with the market.
6. Compare offers by scope, references, availability and pricing model — not just price
Price is only one of several comparison factors and says little on its own. Also check: what's included in the scope, and what explicitly isn't? What relevant experience does the provider bring for exactly this kind of undertaking? Is the offered availability realistic for your timeframe? And what pricing model underlies the offer — a fixed price, an hourly or daily rate, or a non-binding price range? These models can't simply be weighed against each other; the guide to comparing offers covers in more detail how a comparison can still succeed. A common mistake: price gets used as the first and only criterion, while scope and exclusions only come to light after the job has been awarded — often in the form of a costly follow-up offer.
7. Make your choice and put expectations in writing before work starts
Once the decision is made, one last step pays off that's often skipped: put the agreed key points — scope, price, timeline, points of contact on both sides — in writing before the actual work begins. This doesn't need to be an elaborate contract, but a short summary confirmed by both sides prevents misunderstandings later. Especially with commitments made verbally or informally, expectations tend to drift over the course of a project — a written basis creates clarity for both sides here. On legally relevant questions, such as contract terms or liability, you should, when in doubt, bring in your legal department or an appropriately specialized advisor instead of relying on informal agreements.
Common mistakes at a glance
- The goal and need are only kept informally in one person's head instead of being aligned internally.
- The budget corridor and the decision-maker stay unclear until the first offers are already in.
- The request stays deliberately vague to "not rule out anyone" — the result is offers that don't fit.
- Only a single, already-known provider gets asked.
- Price is used as the only comparison criterion; scope and exclusions get overlooked.
- Agreed key points aren't put in writing before work begins.
None of these seven steps is demanding on its own — but together they create exactly the structure that an irregular, unpracticed procurement process otherwise lacks. Anyone who takes the time to clarify the need, gather offers in parallel, and compare beyond price ends up making a decision built on traceable facts rather than chance.