Eleven Questions to Ask an Equipment Vendor Before You Sign

Most equipment vendor demos answer the same five questions. These are the eleven that decide what the contract actually costs you.

Emily Thompson Emily Thompson • • 25 min read

TL;DR

  • Most equipment vendor demos answer the same five questions, and none of them is the one that decides what the contract costs you.
  • Nobody in this category publishes a price. Six vendors' own pricing pages checked on 14 October 2026 show no figure, so the quality of your questions is the only lever on the quality of your quote.
  • The highest-return question is about a bad day in a specific country, not about capability in general. Capability is universal in the demo and uneven in practice.
  • Four exclusions recur: retrieval, storage between holders, shipping to a second address, and devices the vendor did not supply.
  • Ask who the importer of record is per country and whether duty is in the number. A quote that is notably cheaper usually answers this differently from the others.
  • Get the replacement commitment per country rather than globally. A vendor who will commit for Germany but not Brazil has told you exactly where their stock sits.

The Quote That Was Forty Per Cent Cheaper

A 180-person company ran a proper process. Four vendors, same brief, a scoring matrix, a decision in six weeks. One quote came in substantially below the others and the team took it, reasonably, because the brief had been identical and the capabilities looked the same.

Eleven months later the actual spend had passed the second-cheapest quote. Retrieval had been excluded and was billed per collection. Storage between holders was billed monthly and nobody had modelled how many machines sit idle at any time. Two countries turned out to be served by a partner rather than directly, at a markup. And the ninety devices bought before the contract were never imported, so a second spreadsheet ran alongside the platform for the whole year.

None of that was hidden. Every one of those items was in the document, phrased as a scope boundary rather than an exclusion, and nobody had asked the question that would have surfaced it.

So the lesson is not that the vendor behaved badly. It is that an identical brief does not produce comparable quotes when the vendors are free to decide what the brief includes.

Why Nobody Publishing a Price Changes How You Buy

This category behaves differently from most software purchases and it is worth being explicit about why, because the buying behaviour that works elsewhere fails here.

In a category with published pricing, you can shortlist from a web page. Three tiers, a feature matrix, a rough fit, and you arrive at a demo already knowing the approximate number. The conversation is about fit.

Free Weekly Briefing Stay ahead of what's changing in HR and people ops.

Join 4,200+ leaders getting practical insights every week — no fluff, just signal.

Join Free →

Here there is no such page. We checked six vendors on 14 October 2026 and every one routes to a demo request or a conversation. That is not evasiveness peculiar to these companies; the cost genuinely depends on your country mix, your volumes and which jobs you want covered, and those vary enough that a tier would be meaningless.

The consequence is that shortlisting happens after the first call rather than before it, which means you will spend four or five hours on vendors you were never going to pick. Budget for that, and shorten it by sending the specification before the call so the first conversation is already about your numbers.

The second consequence is that the cheapest quote carries more information than usual. With published pricing, cheap usually means fewer features. Here, cheap most often means fewer inclusions, and the inclusions are invisible unless you ask. That is the single reason this article exists.

The third is that you cannot benchmark. There is no public reference point for what this should cost, so the only comparison available is between your own quotes. Which makes the identical-specification discipline not a nicety but the entire basis of the decision.

Why the Demo Does Not Tell You This

Equipment vendor demos are genuinely good, and they are all good at the same things. You will see a device ordered, shipped, tracked on a map and appearing in a register. That path works at every vendor in this category.

What the demo cannot show you is the distribution. It shows a successful shipment to a well-served country on a normal week. Your costs are decided by the unsuccessful shipment to a poorly served country during your busiest month, and that scenario is never the one somebody builds a demo around.

So the questions below are deliberately specific. Each one is designed to produce an answer that differs between vendors, because a question every vendor answers identically has told you nothing and used up goodwill you will want later.

The Eleven Questions

One: What happens when a laptop fails in month four, in Brazil?

Replace Brazil with whichever of your countries is hardest, and ask it about a real country where you actually employ somebody rather than a hypothetical one. This is the single most useful question in the set, because it tests stock location, partner arrangements, warranty ownership and response time in one go.

Listen for whether a replacement ships from local stock or from a hub, and how many working days that is. Listen for who makes the warranty claim. Listen for whether the broken machine gets collected and by whom. A vendor with real depth answers this in specifics within a minute; a vendor without one answers in process language.

Two: Who is the importer of record, and is duty in your number?

Per country, for your top five. The three possible answers are that the vendor handles and includes it, that the vendor ships and the courier bills your employee at the door, or that the obligation sits with you.

The middle one produces a genuinely bad first day for a new starter and is more common than anybody advertises. If one quote is noticeably cheaper than the rest, this is the first place to look.

Three: Which of these are included, which are extra, and which are not offered?

Read the list aloud: procurement, configuration, shipping, in-country stock, tracking of your existing devices, retrieval, storage between holders, redeployment, repair, disposal. Make them answer each one with one of those three words.

This is the question that would have saved the company in the opening of this article. Scope boundaries phrased as capabilities sound like inclusions.

Four: Will you hold records for devices you did not supply?

And if yes, which fields survive the import. Several vendors say yes and mean partly, which is worth discovering before rather than after.

This matters more than it sounds because your existing machines are usually your oldest, and excluding them means refresh planning is built on the newer half of the fleet.

Five: Where does stock physically sit?

Not the country list. The warehouse list. A vendor can ship to ninety countries and hold stock in four, and those are completely different products priced as though they were the same.

The follow-up is which of your countries are served from local stock and which from a hub, because that single distinction explains most differences in replacement time.

Six: What is the replacement commitment, per country, in writing?

A global service level is a marketing number. A per-country working-day target with a stated remedy is a commitment.

Expect a vendor to commit confidently for some countries and hedge on others. That is honest and useful. A vendor who commits identically everywhere is either very large or not reading the question.

Seven: What happens at offboarding, step by step?

Who triggers the collection, who sends packaging, who chases, who checks condition, and what the return rate actually is for home addresses.

Packaging is the detail that decides the number. A prepaid, pre-labelled box arriving at the door recovers materially better than instructions asking somebody to find their own.

Eight: Is condition recorded at both ends?

Because a damage dispute without a dispatch condition record is an argument you lose. Ask whether a condition note and photographs exist at dispatch and at return, and whether you can see them.

Vendors who do this say so immediately. Vendors who do not tend to describe their process for handling disputes, which is a different answer.

Nine: What does a bad month look like on the invoice?

Describe your worst recent month: the nine onboardings, the three failures, the country you opened without warning. Ask what that month costs.

Quotes are built on averages and averages are not what breaks. The gap between the normal month and the bad month tells you how much variable risk the vendor has left with you.

Ten: What do I get if I leave?

An export of the register, in what format, including which fields, and what is deleted afterwards. The register is yours and the answer should be immediate.

A vendor who has to go and check has not been asked before, which is itself informative about how often customers leave and how much thought has gone into it.

Eleven: Who is my named contact, and what happens out of hours?

If you have no internal IT function, the vendor is your IT function. A ticket queue with next-business-day response and a named person who answers the phone are different products, and both get described as support.

The Four Exclusions That Recur

Excluded item How it is usually phrased What it costs you
Retrieval "Available as a module" Per collection, at your leaver rate
Storage between holders "Warehousing is priced separately" Monthly, on every idle machine
Second-address shipping "One delivery per deployment" Every relocation and every re-issue
Devices not supplied by them "Assets we have fulfilled" A second register, run in parallel

None of these is dishonest. Each is a reasonable scope boundary. All four are invisible unless the question in the first column gets asked directly, and together they are routinely the difference between the cheapest quote and the most expensive one.

How to Score the Answers Without Fooling Yourself

Collecting eleven answers from four vendors produces forty-four pieces of information and no decision. The scoring is where most processes quietly go wrong, usually by weighting everything equally.

Weight by what you cannot fix later. Stock location cannot be fixed by you. Response time in a country where the vendor has no presence cannot be fixed by you. An exclusion you discovered in advance can be priced and budgeted, which makes it a cost rather than a risk. So questions five and six should carry more weight than question three, even though question three is the one that changes the invoice.

Score the specificity, not just the content. A vendor who says four working days to Brazil from stock in São Paulo has given you something you can hold them to. A vendor who says they aim for a rapid turnaround has given you a sentence. Both might be true. Only one is a commitment, and the difference is more predictive of how the relationship goes than the stated number.

Watch for the answer that changes between calls. Ask question five of sales, then again of the solutions engineer. Consistent answers are a good sign about internal clarity. Inconsistent ones are not necessarily dishonesty, and they do tell you the organisation does not have a single view of its own footprint, which surfaces later as surprises.

Record who said what. Not to catch anybody out. Because in six months the account manager will have changed and the only record of what was promised will be your notes, and a named person attached to a claim is much easier to re-raise than an anonymous assurance.

One thing worth not doing: building a weighted scoring matrix with twenty criteria and two decimal places. It produces a number that feels objective and mostly encodes whatever weights somebody chose on a Tuesday. Three tiers, something like strong, acceptable and concerning, across the eleven questions, gives you the same decision with less false precision and a much easier conversation when somebody senior asks why.

What Good Answers Actually Sound Like

It helps to know the shape of a good answer rather than only the shape of a bad one, because several of these questions can be answered honestly in a way that sounds unimpressive.

On question one, a good answer includes a number and a caveat. Something like: in Germany we ship a replacement from local stock next working day; in Brazil we hold no stock, so it is five to seven working days from our hub and we would suggest you keep a spare on site. That is a vendor telling you about their weakness before you find it, which is the single best signal available in this process.

On question three, a good answer is fast. A vendor who knows their own scope can go through the ten items in two minutes. Hesitation on this list usually means the answer depends on the contract, which is fine, but then the honest response is to say so rather than to describe a capability.

On question seven, a good answer talks about packaging unprompted. Vendors who recover devices at a decent rate know that packaging decides the number and they bring it up themselves. Vendors who describe their chase process instead are telling you where their effort goes.

On question nine, a good answer asks you questions back. Working out what a bad month costs requires knowing your volumes, your countries and your failure rate. A vendor who quotes a bad month without asking for those has not calculated anything.

And on question eleven, a good answer names a person. Not a role, not a queue, not a service level. If the answer is a tier of support rather than a human, that is a legitimate product and you should know you are buying it, particularly if you have no internal IT function and the vendor is effectively filling that gap.

Three Answers That Should Worry You

"We cover 150 countries." Coverage lists count countries a courier reaches. Ask how many have stock, and the number drops sharply. The country list is the least informative figure any vendor publishes.

"That is handled during onboarding." Sometimes true and frequently a way of moving an unanswered question past the decision point. If it genuinely is an implementation detail, it can be written into the contract now.

"Everyone else does it this way." Possibly accurate and not an answer to the question you asked. In a category where nobody publishes pricing, the claim that something is standard cannot be checked by you, which is exactly why it gets made.

"We can be flexible on that." The most agreeable answer in the set and the least useful, because flexibility expressed in a call is not a term. Ask what the flexible version would say in the contract, and the answer either becomes concrete or quietly disappears, and both outcomes are worth having before you sign.

Five Questions to Ask Yourself First

Which countries actually matter? By headcount, written down. Vendors optimise their answers around the countries you name, so naming the wrong five produces a quote optimised for the wrong five.

What is your real leaver rate? Retrieval cost scales with it, and most teams underestimate their own number. Pull the actual figure for last year rather than an impression.

How many devices do you already own? This decides whether question four is a nuisance or a deal-breaker.

What replacement time would you genuinely accept? Next day everywhere is not purchasable at most scales. Stating what you would accept gets you a real conversation; stating what you would like gets you a sales answer.

Who will own this internally? A name. Every failure in this category traces back to the arrangement being somebody's fourth priority, and vendors can tell within one call whether there is an owner on your side.

The Options

RemoAsset, named below, is owned by the same people who publish HROpsLab. Its limitations are stated as plainly as everybody else's.

RemoAsset

Device lifecycle coverage for distributed teams: procurement, deployment, tracking and retrieval, with enrolment into your management system before dispatch.

Against the eleven questions, its honest answers include three that count against it. It publishes no price and requires a demo, so question nine has to be asked in a call. It is noticeably weaker for hardware it did not supply, which is question four and a real limitation. And it is not a device management system, so it enrols into yours rather than replacing the need for one.

Workwize

Hardware lifecycle with its own warehouse network. Its domain is now goworkwize.com; the older workwize.com no longer resolves, verified 14 October 2026.

Against the questions: the warehouse footprint gives it strong answers on questions five and seven, which are the two that most often separate vendors. No published price.

Firstbase

Equipment provided on a subscription basis with retrieval and replacement folded into the arrangement rather than priced separately.

Against the questions: the subscription shape means question three has fewer surprises, because more is included by design. The tradeoff is question ten, since a subscription leaves you with no residual asset. No published price.

GroWrk

Procurement, deployment and retrieval across a wide country list, scoped per customer rather than sold in tiers.

Against the questions: a tailored model answers question three well and question nine slowly, because each arrangement is scoped individually. Its own pricing page is an invitation to a conversation.

allwhere

Equipment procurement and management with a consultative, managed-service character.

Against the questions: strong on eleven, because a managed service is built around a named relationship. Slower on nine, for the same reason every consultative model is. No published figures.

Deel IT

Devices attached to an employment platform, so hardware and employment come from one provider.

Against the questions: simplifies three and two where the employment arrangement already exists in that country. Question five is the one to press, since the device half is a younger product than the employment half. No published price.

The Comparison

Vendor Own warehouses Retrieval included Imports existing assets Pricing
RemoAsset Partner network Yes, in scope Weaker, verify Quote-based, demo required
Workwize Yes Verify per contract Verify Quote-based
Firstbase Partner network Yes, by design Verify Quote-based
GroWrk Partner network Scoped per customer Verify Quote-based, tailored
allwhere Partner network Scoped per customer Verify Quote-based
Deel IT Partner network Verify per country Verify Quote-based

Several cells read "verify" deliberately. The point of this article is that those are the cells where published material and reality diverge most, and where the answer changes by contract rather than by vendor.

The Decision Table

Situation Scale Setup Primary Pain Recommended Starting Point
One quote far below the others Any Re-ask questions two and three Exclusions priced as scope Re-quote all four on an identical inclusion list
High leaver rate Any Retrieval in the base, not a module Per-collection billing compounding Price retrieval as included before comparing
Large pre-existing fleet 100 plus Vendor that imports existing assets Two registers in parallel Get the import commitment in writing
Hiring in hard countries Any Vendor with local stock there Replacement measured in weeks Ask question one about that exact country
No internal IT owner Under 150 Managed service, named contact Vendor is your IT function Weight question eleven above price
Spiky hiring Any Variable-cost model Quote built on an average month Ask question nine with real numbers
Devices move between holders Any Storage and redeployment included Idle machines billed monthly Confirm storage treatment explicitly
Considering an EOR bundle Under 150 Specialist if populations differ Bundle covers only employed staff Map device population against employed population

How to Run the Conversation

The questions work better in a particular order and with a particular person in the room.

Ask for somebody technical on the call. Sales can answer capability questions accurately and cannot usually answer question five with precision. A solutions engineer either knows where stock sits or can find out in a day.

Open with question three. The inclusion list sets the frame for everything after it, and asking it first stops the conversation drifting into capability.

Put questions one and nine in the middle. They are the uncomfortable ones and they land better after some rapport than as an opener.

Close on questions ten and eleven. Exit terms and named contacts are reasonable late-stage questions and they signal that you intend to hold the arrangement to something.

Write the answers down during the call, in their words. Not a summary afterwards. The exact phrasing matters, because the difference between included and available is one word and six months later nobody remembers which was said.

Then send your notes back to the vendor and ask them to confirm. The ones who correct a detail are doing you a favour. The ones who do not reply have told you something about the support relationship.

One practical note on tone. None of this needs to be adversarial, and treating it that way produces worse answers rather than better ones. Vendors in this category deal with a lot of vague briefs and most of them would rather talk to somebody who knows what they are asking. Framing the eleven questions as help me scope this properly gets fuller answers than framing them as a cross-examination, and the information you want is the same either way.

And give them your bad news early. If you have no management system, no internal owner and a fleet of unknown provenance, say so in the first call. The vendors who cannot serve that will withdraw, which saves you weeks, and the ones who stay will quote against reality rather than against the tidy version.

The Questions That Change After You Have Signed

Four of the eleven are worth re-asking annually, because the answer genuinely moves and nobody will tell you when it does.

Where stock sits. Vendors open and close warehouses, change partners and shift their footprint as their own customer base moves. A vendor who held stock in your second-largest country at signature may not two years later, and the first you hear of it is a replacement that takes a week instead of a day.

Who the named contact is. Account managers change constantly in this category. The practical move is to ask at each renewal who the current named contact is and to get it in the record, rather than discovering during an incident that the person you have been emailing left in March.

What is included. Scope creeps in both directions. Things get added during a renewal negotiation and quietly dropped in a restructure. An annual walk through the same ten-item list takes fifteen minutes and catches both.

What the exit looks like. Export formats change as products change. A commitment made against a product that has since been rebuilt may not survive, and the time to discover that is not the month you are leaving.

The broader point is that this is a relationship with a long switching cost, which means the questions are not a gate you pass once. Companies that re-ask these four every year are the ones that notice a deteriorating arrangement in month fourteen rather than month thirty.

When None of the Answers Is Good Enough

Sometimes the honest conclusion from eleven questions times four vendors is that none of them fits, and it is worth naming what to do then rather than defaulting to the least bad.

If the problem is scale, wait. Below roughly fifty people in two countries, a platform is frequently premature. A spreadsheet register, a local reseller and a named owner cover the same ground at a fraction of the cost and considerably less commitment, and you will make a far better platform decision at a hundred and fifty people with real data about your own volumes.

If the problem is one country, solve that country separately. A specialist arrangement for the hard market plus a mainstream platform for everywhere else is a legitimate structure. It costs you a second relationship and it beats paying a premium for coverage that turns out to be a courier arrangement anyway.

If the problem is the management system gap, fix that first. Several teams go into this process looking for a logistics vendor when the actual missing piece is device management. Buying logistics first means shipping sealed machines nobody can configure, and no amount of vendor selection solves it.

If the problem is that every quote exceeds the budget, go back with a reduced inclusion list rather than asking for a discount. Dropping storage and redeployment, or taking retrieval only in your top three countries, changes the number far more than negotiation does, and it is an explicit decision about what you are prepared to do yourself rather than a discount that quietly removes something anyway.

And if the problem is that nobody internally owns this, no vendor will fix that either. The managed-service options come closest and they still need somebody on your side to receive the service. A purchase made to avoid naming an owner tends to fail in month six regardless of which vendor was chosen.

What Getting This Wrong Costs

The direct cost is the gap between the quote and the spend, which in the opening example was most of a year's budget and arrived as a series of individually small invoices.

The harder cost is the internal credibility of the decision. A team that ran a proper process, scored four vendors and picked the cheapest has done everything it was supposed to do. When the spend overruns anyway, the lesson learnt internally is often the wrong one: that vendor quotes cannot be trusted, or that procurement processes do not work. The actual lesson is narrower and more fixable, which is that an identical brief does not produce comparable quotes unless the brief specifies inclusions rather than outcomes.

And there is the switching cost, which is why this matters more here than in most categories. Changing equipment vendors means migrating a register, re-papering in-flight shipments and possibly moving physical stock. It is expensive enough that most companies live with a bad fit for a full contract term rather than fix it, which is exactly why the eleven questions belong before signature rather than after.

Ask it this way before you decide. If every vendor answered question three in writing and you re-scored on that basis alone, would you still pick the same one?

Writing the Specification the Questions Depend On

The eleven questions work on a call. They work far better when the vendor has already seen a one-page specification, because then the answers are costed rather than hypothetical.

Headcount by country, including the ones with a single person. Those single-person countries are where quotes diverge most and where vendors most often assume you meant something easier.

The device standard as a specification rather than a model. Processor class, memory, storage, screen size and operating system. Models go out of stock constantly and a quote anchored on one specific machine is a quote that expires.

Annual joiners and leavers, from last year's actual numbers. This is what drives cost in practice, far more than headcount does. A stable two-hundred-person company and a two-hundred-person company with thirty per cent turnover are completely different customers.

Your replacement expectation as a working-day target you would accept, per country tier rather than globally. Stating what you would accept gets a real conversation. Stating what you would like gets a sales answer.

The ten-item inclusion list from question three, formatted as a table with a column for the vendor to complete. This single table does more work than everything else on the page, because it forces the quiet exclusions into a format where they can be compared.

And your three worst weeks rather than your average one. The month with nine onboardings, the week three machines failed, the quarter you opened an unplanned country. Vendors price around averages and averages are not what breaks.

Send the identical page to everybody. Tailoring per vendor feels helpful and destroys the only thing that makes four quotes comparable.

When You're Ready to Go Further

Two things are worth doing once you have answers from everybody, and both take under a day.

Normalise the quotes yourself. Build one table with your own inclusion list down the side and each vendor across the top, filling in included, extra or not offered from their own words. Then add the extras at their stated rates using your real volumes. The ranking frequently changes, and when it does not, you have a decision you can defend.

Run a single-hire pilot before signing the full term. One real person, in a country that is not your easiest, through the entire chain including a deliberately raised support issue. A vendor who will not support that is telling you how they will behave when you have a problem at scale, which is the most valuable thing you will learn in the whole process.


Frequently Asked Questions

What is the most useful question to ask an equipment vendor?

What happens when a laptop fails in month four in your hardest country, named specifically. It tests stock location, partner arrangements, warranty ownership and response time in a single question, and the answers differ sharply between vendors in a way that general capability questions never do, because every vendor in this category can show you a successful shipment to a well-served country.

Why do equipment vendor quotes vary so much on an identical brief?

Because an identical brief does not constrain what each vendor decides to include. Retrieval, storage between holders, shipping to a second address and tracking of devices they did not supply are all reasonable scope boundaries, and all four are commonly phrased as capabilities rather than exclusions, so the cheapest quote is frequently the one that left the most out.

Does any equipment platform publish its pricing?

Not one of the six checked on 14 October 2026. Every vendor named in this article was read from its own pricing page and none shows a currency figure, because arrangements are scoped per customer on country mix, volume and inclusions, which means comparison depends entirely on sending a specification that defines inclusions rather than outcomes.

What does importer of record mean and why does it matter?

It is the party legally responsible for a device crossing a border and for the duty and import tax attached to it. The three possibilities are that the vendor handles and includes it, that the courier bills your employee at the door on their first morning, or that the obligation sits with you, and the difference explains a large share of the variation between quotes.

Should I trust a vendor's country coverage number?

Treat it as the least informative figure any vendor publishes, because coverage counts countries a courier can reach rather than countries where stock is held. Ask instead for the warehouse list and which of your specific countries are served from local stock, since that single distinction explains most of the difference in replacement times.

How do I compare vendors when nobody publishes a price?

Normalise the quotes yourself: build one table with your own inclusion list down the side and each vendor across the top, fill it in from their own words, then add the extras at their stated rates using your real volumes rather than an average month. The ranking often changes, and when it does not you have a decision you can defend internally.

What should go in the contract rather than the quote?

The replacement commitment stated per country with a remedy, whether duty is included per country, what export of your register you get on exit and what is deleted, and who the named contact is with an out-of-hours position. None of it needs a lawyer; it needs the answers moved out of email and into the document before the account manager changes.

Is it worth running a pilot before signing?

Yes, and it should deliberately include a bad path rather than only a successful shipment. One real hire in a country that is not your easiest, taken through order, ship, configure and day-one login, followed by a support issue you raise on purpose, tells you more than any demo, and a vendor who will not support a single-hire pilot has answered a different question honestly.

HROpsLab takes no vendor money and publishes no paid placements.

Share on X Share on LinkedIn

What to do next?

Explore More Articles

Dig deeper into HR Ops strategy, tools, and workflows built for real teams.

Browse the blog →
Join the HROpsLab Community

Connect with People Ops practitioners sharing real workflows, tools, and challenges.

Join now →