Buying equipment looks like the simplest kind of technology purchase and produces more disappointment than any other. The reason is that the difficult parts are not in the price, and a requirement written around the price will not surface them.
This is what to settle before asking for a quote, and what belongs in the requirement itself.
Settle these four things first
What the equipment has to do, in the words of whoever depends on it. Not "forty laptops" but what those forty people are doing that the current ones will not support. Suppliers can suggest better answers to a stated problem and can only price a stated list.
Who is going to own it afterwards. Equipment arrives, and then somebody has to enrol it, patch it, track it and eventually dispose of it. If that team is already at capacity, the purchase should include the work, and pretending otherwise is how organizations accumulate unmanaged devices.
What the funding source requires. This is the one most often discovered late. Where federal award funds are involved, property standards at 2 CFR 200.313 require property records, a physical inventory reconciled at least once every two years, and a control system that guards against loss, damage and theft. Those duties begin the day the equipment arrives, so the tagging and record keeping belong in the purchase rather than in a later project.
When it has to be working. Not when it should be delivered. Lead times on some equipment are long and unpredictable, and a date that assumes availability is a date built on nothing.
What belongs in a hardware requirement
A requirement that produces comparable quotes is specific about six things, and vague requirements produce quotes that differ for reasons nobody can see.
The configuration, completely. Processor, memory, storage, and any component that varies. A quote for "a business laptop" is not a quote.
The quantity and the phasing. Whether all of it arrives at once or in tranches, because that changes both the price and the logistics.
The warranty term and level. Three years next business day is a different product from one year return to base, and the difference is frequently larger than the difference between two suppliers.
What happens to the equipment before it reaches a desk. Imaging, asset tagging, enrolment in your management platform, and disposal of packaging. Each is real work, each can be bought or not bought, and the quotes will diverge sharply depending on the assumption made.
Delivery and receiving. Where it goes, who signs for it, and where it is stored between arrival and installation. An agency taking delivery of two hundred devices needs somewhere for two hundred boxes, and this is routinely forgotten until the pallet arrives.
What happens to what it replaces. Old equipment has to be removed, wiped and disposed of. Saying so in the requirement is the difference between a clean project and a store cupboard full of machines nobody may throw away.
Getting quotes you can actually compare
Send the same document to everyone and ask for the response in the same shape. Three specifics make the difference.
Ask for the catalog reference on the hardware lines. Which manufacturer catalog, and on what date. That is what lets you verify the discount has actually been applied rather than assumed.
Ask for services to be priced by role and hour, separately from the equipment. A bundled number cannot be compared and cannot be reduced by scope. Separated, you can see whether a supplier has priced two days of imaging or ten.
Ask what is excluded. The most useful question on any quote, and the one suppliers answer honestly because the exclusions protect them too.
Then compare totals, not percentages. Two suppliers with identical discounts can differ substantially on the same requirement, because the divergence lives in the warranty, the services and the accessories rather than in the headline device.
What usually goes wrong
The equipment arrived and nobody could take delivery. A loading dock, a store room and a person are all required, and none is the supplier's problem unless you made it one.
The asset register was updated months later, from a delivery note. By then some devices had moved and two could not be found. Tagging at the point of receipt costs an hour and is the only version of this that works.
The old equipment stayed. Nobody was accountable for removing it, so it sits in a cupboard with data on it, which is both a storage problem and a disclosure risk.
The support arrangement was assumed. The warranty was with the manufacturer, the configuration was done by the supplier, and when something failed the user called the help desk, which had not been told the equipment existed.
What good looks like
Three months after a purchase that went well: every device is in the asset register with a tag that matches a physical label; the people using them were told in advance what was changing and when; the equipment that was replaced has been disposed of with a record of how; and the service desk knows what it is supporting and under what arrangement.
None of that is about the equipment. All of it is decided in the requirement, which is why the requirement deserves more attention than the quote.
Standardization is the decision under the purchase
Every hardware purchase quietly decides what your estate looks like for the next several years, and most organizations make that decision by accident.
Buying one configuration in volume makes everything downstream cheaper: one image to maintain, one set of drivers, one spare parts holding, one support conversation. Buying whatever was keenest at each purchase produces an estate of variants, and the cost of that shows up in support hours rather than on any invoice.
The counterweight is that a standard held too long stops fitting. A three year old specification bought again because it is the standard is a worse purchase than a fresh one. The workable discipline is to review the standard annually, buy against it in between, and record why when a deviation is genuinely justified.
Software and licensing, which follow different rules
Licences are bought on the same contracts as hardware and behave nothing like it, which catches out buyers who treat a purchase order as the end of the matter.
A licence has a term, and the term begins somewhere: on purchase, on activation, or on a coterminous date aligned to your other agreements. Which of the three applies changes what you are actually buying, and aligning renewal dates across an estate is worth more over a few years than any discount.
Entitlement also has to be recorded somewhere your organization will find it later. The proof of purchase for a perpetual licence bought today will be needed in five years by somebody who has never heard of this project, and an audit is a poor time to discover that the record lives in a mailbox nobody has access to.
Ask, before ordering, what is being bought: a subscription, a perpetual licence with support, or a perpetual licence without it. The three look similar on a quote and diverge sharply in year two.
One practical note on both of those. The person who signs the purchase order is rarely the person who will live with these decisions, so write the standard and the licensing position down somewhere that outlasts the project. A one page note naming the current configuration, the licence terms and the renewal dates is the cheapest institutional memory an IT team can build, and it is what stops the next purchase starting from nothing.
Placing the order
Public agencies can buy the equipment and the work around it on one awarded contract rather than assembling separate purchases. The procedural sequence is in how to purchase IT services through a TIPS contract, the pricing model for products is explained in what discount off catalog pricing means, and the questions to put to any supplier are in the supplier evaluation checklist.
LABUSA supplies hardware procurement, professional and managed services, cybersecurity, physical security and low-voltage systems and field support under this contract, with dedicated personnel, help desk both remote and on site, and procurement and lifecycle asset management available as services in their own right. The published scope and ceilings are on the awarded contract this equipment would be bought under, listed with TIPS.
If you have a refresh coming and want the requirement read before it goes out, send us the draft you are working from.