A laptop dies in month five. The supplier says it is a support problem. The support company says it is a warranty problem. Your staff member works off a phone for three weeks.
Nobody in that story is lying. Each company did exactly what it was paid to do. The supplier delivered a sealed box. The support company fixes faults in machines it did not buy. The work that sits between those two jobs belongs to neither contract, so it belongs to nobody.
This is the case for using one partner for IT procurement and support. It is not always the right case, and further down we say when it is wrong.
Where the gap shows up
Three problems recur. They look different but share a cause: the people who bought the equipment are not the people who live with it.
Warranty claims
A warranty claim needs the invoice, the serial number, proof of purchase date, and often a registration done at the time of sale. The supplier holds the invoice. The support company holds the faulty machine. Your accounts team holds a scanned PDF somewhere.
Then the claim itself. Somebody has to run the manufacturer's diagnostics, log the case, ship or carry the unit to the service centre, and chase it. With a return-to-base warranty, that can mean a laptop out of service for weeks. The support company will do this, as a billable job, if they can find the paperwork. The supplier will do it if you bring the laptop back to their shop. Neither one treats it as theirs.
"It was like that when it arrived"
A machine shows up with 8GB of RAM when the quote said 16GB. Or with Windows Home instead of Pro, which matters the day you try to join it to your company's device management. Or with a dead pixel line nobody noticed until the support engineer imaged it a week later.
At that point the supplier says the unit left their store in working order. The support engineer says they found it like that. There was no acceptance test, so nobody can prove which is true. You pay for the fix.
Spec drift
Your support provider wants a standard machine: one model, one image, one set of drivers, one spare charger that fits everything. Your supplier ships whatever is in stock at the quoted price. Each order is reasonable on its own. Three years later you have 40 laptops across 11 models, and every new hire's machine is a small support project.
Spec drift is invisible on any single invoice. It shows up as support cost, and it shows up slowly.
What one partner for procurement and support changes
When the same company supplies and supports the equipment, the record runs unbroken from quote to retirement. In practice that means:
- The spec that was quoted is the spec that gets supported. If it arrives wrong, it is the partner's problem, and they find it, because their engineer is the one who unboxes it.
- Acceptance happens at delivery, by the people who will support it. Serials are recorded against locations, and faults are rejected before the delivery note is signed.
- Warranties registered in your company's name, with the documents handed to you and a copy held by the people who will make the claim.
- Repeat orders match. When a department grows, the next machine is the same model, or a deliberate successor, not whatever was in stock.
This is how we run IT procurement alongside managed services. It is also why a private hospital in Abuja that we supply and support comes back to us for repeat orders: the second order is easier than the first, because we already hold the record of what is installed. The full write-up is in our hospital procurement case study.
When splitting them is still the right call
Sometimes we would tell you to keep them apart.
You have a capable in-house IT team. If your own staff run acceptance tests and log warranty claims against your own asset register, the gap is already closed. The supplier is then a source of boxes, and you should buy boxes on price and availability.
A specialist category with its own channel. A telephony system or a large storage array may be better bought direct or through a specialist. So may equipment sold with a manufacturer's own on-site warranty. If the manufacturer sends an engineer next business day under the warranty, the manufacturer is your hardware support for that item, and that is fine.
Your support partner's prices do not hold up. Some support firms treat procurement as margin. If a line-itemised quote from your partner is consistently well above the market for the same part number, buy elsewhere and tell them why.
A single large order where price dominates. A one-off order of 200 identical machines, bought with your own acceptance process in place, can justify a separate tender. Make sure the spec you send out is the one your support team signed off.
In each case the condition is the same. Somebody still owns the gap. If that somebody is you, by design and with the records to prove it, split freely.
How to structure it without locking yourself in
The fear is fair. One partner holding your purchase records and your admin passwords has a lot of power at renewal. The wider method for avoiding single-supplier dependence is in how to run a vendor consolidation review without locking yourself in. For supply and support specifically, five terms do most of the work.
- You own the records. The asset register, warranty registrations, licence accounts and administrator credentials belong to your company and sit in your systems. Your partner works from copies.
- Separate agreements. The support contract and the supply arrangement should be separate documents with separate termination. Buying hardware from a partner should never oblige you to keep their support, and the reverse.
- Line-itemised quotes with part numbers. This is what lets you benchmark. Once a year, or on any order above a threshold you set, send the same spec to a second supplier. If the numbers are close, you have confirmed the relationship. If they are not, you have a conversation to have.
- A written handover obligation. On exit, the partner hands over documentation and credentials within a stated period. Put the period in the contract.
- Acceptance criteria on every order. What gets checked at delivery, and who signs. This protects you whether or not you stay with the partner.
None of these terms cost the partner anything if they are doing the job well. A partner who resists them is telling you something.
Frequently asked questions
Is it cheaper to buy IT equipment and support from the same company?
Not always on the invoice. A specialist supplier may beat a support partner on the unit price of a laptop. The saving from one partner shows up elsewhere: fewer defects found too late to reject, and a standard estate that costs less to support. Benchmark the quotes so you know what the difference is.
Who should handle warranty claims on our IT equipment?
Whoever holds the purchase records and the faulty machine at the same time. With one partner that is them. With a split arrangement, decide in writing which company makes claims, and give them the invoices and registrations they need to do it.
How do we avoid being locked in to one IT partner?
Keep the records and credentials in your own name, keep supply and support in separate agreements, insist on part numbers in every quote, and benchmark against a second supplier at least once a year. A written handover obligation covers the rest.
What should we check when IT equipment is delivered?
Whatever the quote promised, checked before you sign the delivery note. The step that catches most problems is powering each unit on and reading the specification and Windows edition from the system itself, not the sticker. The full same-day list is in our IT procurement process for private firms.
If you buy from one company and get support from another, send us a list of your last three warranty claims or delivery problems and who handled them. We will show you where the gap sits in your current arrangement, and whether closing it is worth what it costs.
