Buying IT Services: A Beginner’s Primer and Mini-Glossary

Buying IT Services: A Beginner’s Primer and Mini-Glossary

Sooner or later every team lead, office manager, or first-time founder has to buy IT services — a migration, an integration, a support contract — without ever having been taught how. This primer on buying IT services covers the whole beginner’s path: the vocabulary, the sequence, and the one habit that separates clean engagements from messy ones. No procurement experience required; by the end you will know exactly what to write, send, and compare.

Start here: the one habit that matters

Everything in this primer reduces to a single rule: get the need on paper before you ask anyone what it costs. A supplier can only price the project you describe. Describe it differently to each supplier — or not at all — and the prices you collect belong to different projects. Describe it once, in writing, to everyone, and the prices become comparable. That single habit does more for your outcome than any negotiation tactic you will ever learn.

Mini-glossary: the eight words you actually need

  • Requirement (or brief): your written description of the work — current situation, desired outcome, constraints, deadline. One page is often enough.
  • RFQ (request for quotation): the act of sending that requirement to several suppliers and asking each for a priced response.
  • Bid (or quote): a supplier’s written answer: price, approach, timeline, team.
  • Scope: the work the price actually covers. The most important word in the list.
  • Exclusion: work the supplier is explicitly not pricing. Good bids name their exclusions; dangerous ones stay silent.
  • Itemised pricing: the total broken into labelled parts, so you can see what each piece costs and compare it across bids.
  • Shortlist: the three to five suppliers you invite. More than five adds noise, not insight.
  • Award: the moment you pick a winner and confirm scope and price in writing — always the last step, never the first.

The sequence, beginner-proof

Run the steps in this order: write the requirement, pick the shortlist, send the identical document to all of them, collect bids by one deadline, compare them in a table, award, and only then sign. If that sounds abstract, look at how healthcare now packages the same sequence for ordinary patients. On MyHospitalNow, where a patient’s written medical requirement draws estimate bids from hospitals, the journey runs from submitting the request, through the platform’s check of it, to receiving hospital bids, weighing them against each other, approving one, and getting connected to that hospital. Commitment sits at position six of six. Keep it there in your IT purchases too.

Two reassurances for first-timers. Requesting bids is free and normal — MyHospitalNow even answers the “does the quote cost anything?” worry with a plain no on its own pages, and IT suppliers treat responding to RFQs as routine business development. And suppliers who decline to answer a written brief have told you something useful at zero cost.

How to read the bids you get back

Build a four-part table and fill it only from what is written. Money: the itemised total, plus every exclusion priced back in so totals match like-for-like. People: who, by name, does the work, and what they have delivered before. Logistics: location, timezone, start date, how support works after go-live. Evidence: references, certifications, and claims you can check. Healthcare marketplaces present hospital bids in nearly this exact shape — charge, facility profile, and city in one view, with the platform’s trust labels alongside (there, “verified” is the marketplace’s own description of its hospitals, which is worth remembering as you read). The shape is the lesson: four kinds of information, one view, no lone number making the choice.

Beginner trap worth naming: the cheapest bid usually differs from the others by scope, not efficiency. Before celebrating a low total, find the work it left out.

Know enough to write the brief

You do not need to be an engineer to buy engineering, but a weekend of orientation sharpens the requirement enormously. If you are buying delivery-pipeline or automation work, skim an end-to-end tour of DevOps workflows and tooling so the vocabulary in supplier bids does not wash over you, and how CI/CD pipelines carry code from commit to production so you can ask where testing lives in each bid. You are not studying to do the work — only to recognise when two bids are secretly describing different amounts of it.

Budgeting around the decision

Set the budget ceiling before bids arrive, not after, or the highest bid will quietly become your anchor. Hold back a contingency — ten to fifteen percent of the award — for genuine discoveries, and treat dipping into it as an event that needs a written reason. If money habits are the part of this you dread, the approach in pairing specific money problems with small workable habits transfers well: one ritual (the table, the ceiling, the written reason) per failure mode.

Your first RFQ, this week

Pick the smallest real need on your list. Write one page: where you are, what you want, by when, under what constraints. Send it to three suppliers with a response date. Table the answers across money, people, logistics, and evidence. Decide, confirm in writing, done. The whole exercise costs a few hours, and it installs the habit that platforms like MyHospitalNow have proven at consumer scale: structured, comparable estimates first, commitment last. Every purchase after this one gets easier — because from now on, you will always know exactly what question your prices are answering.