Device as a Service Providers: How the Monthly Figure Is Built

TL;DR

• Device as a service bundles the hardware, its financing and a set of services into one per-device monthly charge, and the whole decision turns on knowing which of those three you are paying for.
• If you buy laptops outright every three years and that works, you do not need DaaS. It is a cash-flow and operations decision, not a cost saving.
• No provider in this category publishes a price, so every comparison you make will be between quotes rather than list prices.
• Ask for the monthly figure split into hardware, finance and service. A provider who will not split it is telling you something.
• Month 37 decides whether the deal was good. What happens at the end of term is the clause nobody reads and the one that costs money.
• The honest comparison is against buying plus everything you currently do yourself, not against the purchase price alone.

The Quote That Could Not Be Compared

A company with 240 laptops ran a procurement exercise to replace an ageing fleet. Three device-as-a-service providers quoted, and the quotes arrived as a single per-device monthly figure each, over a 36-month term. The numbers were within about 15 per cent of each other.

Finance asked a reasonable question: which is cheapest. Nobody could answer it, because the three figures described different things. One included on-site replacement within two business days and one did not. One included collection and certified disposal at end of term, one included collection only, and one was silent. Two assumed the company would return every device; one allowed a buyout at a price to be determined later. The spread between the three was smaller than the value of the differences between them.

They were not three prices for the same thing. They were three bundles, each mixing hardware, financing and services in different proportions, presented in a format that made them look comparable. The procurement exercise compared the only number that was easy to compare and in doing so compared nothing.

Recommended Tools

Best tools for Device Management

B BambooHR HR management system L Lattice Performance management D Deel Global payroll & EOR

View all recommended tools

So the first job with any DaaS quote is to take it apart, and the rest of this article is about how.

When You Don't Actually Need DaaS

When the manual way is genuinely fine

You buy laptops when people join, you have the cash, and nobody is complaining. Outright purchase is simple, cheap in total terms, and leaves you owning an asset you control. The pressure to move usually comes from cash flow or from operational load rather than from anything wrong with buying.

When friction starts appearing

The signal is rarely financial. It is the refresh that keeps slipping because nobody can face the project, or the growing proportion of staff on machines older than your own standard. DaaS is attractive at that point because it converts a periodic project into a running cost, and that is a real benefit worth naming honestly.

When it becomes a liability

When the fleet's age distribution starts producing support load you can measure: repeat hardware tickets, failed updates, people unable to run the tools their role needs. At that point the question is not whether to refresh but how to fund it, and that is the question DaaS answers.

The edge case that forces it

Rapid headcount growth with constrained capital, or a business where the finance team has a strong preference for operating expenditure. Both are legitimate reasons and neither has anything to do with the hardware, which is worth saying plainly because the vendor conversation will be about the hardware.

Five Questions People Ask First

"Is DaaS cheaper than buying?" Almost never in total cash terms, and that is not its argument. You are paying somebody to finance the asset and carry risk, and neither is free. It can be cheaper in total cost of ownership once you count the things you currently do yourself and do badly, such as refresh projects, disposal and the devices you never recovered, which is a genuine case and a different one.

"What is actually in the monthly figure?" Three things in varying proportions: amortisation of the hardware itself, a finance charge for spreading it over the term, and services such as configuration, delivery, support, replacement and end-of-life handling. Providers present it as one number because that is simpler to sell, and because it makes the finance charge invisible.

"Who owns the devices?" Usually the provider or a funder behind them, and this matters more than it sounds. It affects what you may do with the machine, what happens if you want to keep one, and what your obligations are at the end of the term. The specifics vary by arrangement and by jurisdiction, so the contract and local advice are the right route rather than a general rule.

"What happens if somebody breaks one?" This is where quotes differ most and where the cheapest-looking one often is not. Accidental damage, loss and theft are usually treated separately from hardware failure, and the terms around them are the single largest source of unexpected cost during a term.

"Can we get out early?" Usually at a cost, and the shape of that cost should be established before signing rather than discovered during a downturn. A three-year commitment on a headcount that might fall is a real risk, and the question to ask is what happens to devices you no longer need.

Taking the Monthly Figure Apart

Ask every provider for the same decomposition, in writing. Most will supply it when asked directly and very few volunteer it.

The hardware component. What the machine would cost to buy, spread across the term. You can sanity-check this against retail for the same specification, which is the single most useful thing you can do with a quote. A hardware component materially above market tells you the bundle is carrying cost somewhere it is not admitting to.

The finance component. The cost of somebody else owning the asset while you use it. This is legitimate and it is also the part that is never labelled. If the hardware component checks out against retail and the total is well above it, the difference is finance and services, and you are entitled to know the split.

The service component. Configuration, delivery, support, replacement, collection, disposal. This is where the real differences between providers live and where the value genuinely is for a distributed company, because these are expensive and annoying to do yourself across borders.

The assumptions. Term length, refresh point, expected return rate, and what happens to devices that do not come back. Quotes are built on assumptions about your behaviour, and a quote that assumes a 95 per cent return rate when yours is 60 per cent is not a quote for your company.

What to Hold Each Component Against

The last row is the one that decides whether the arrangement was good, and it is the row most often left blank in a proposal.

Why the Services Half Is Worth More Than It Looks

The financing half of DaaS is easy to be cynical about, since you are paying a margin to avoid spending capital. The services half is where the genuine case sits, and it is systematically undervalued because the costs it replaces are spread across people's weeks rather than sitting in a budget line.

Cross-border procurement is the clearest one. Buying a laptop in a country where you have no entity involves a payment method that works, a supplier who will deal with you, a delivery address, and an import that may or may not attract duty. Doing that once is an afternoon of somebody's attention. Doing it eleven times a year is a part-time job nobody has been given.

Replacement speed is the second. A failed machine for a remote employee is days of lost work unless somebody can get a replacement to them quickly, and that capability is expensive to build and cheap to buy. The value is not the hardware, it is the elapsed time.

Collection is the third and the most undervalued. Most companies have no reliable way to get a device back from somebody in another country, which is why recovery rates are what they are. A provider with a collection network turns that from a chase into a booking.

Configuration matters least for most companies, because modern enrolment means a machine configures itself on first boot wherever it is. Providers price it as a service and it is often the least valuable thing in the bundle, so discount it accordingly when comparing. The exception is asset tagging and a pre-recorded serial handed to you as data, which is genuinely useful and costs the provider almost nothing, so it is worth asking for as an inclusion rather than paying for as a line.

So the useful way to read a DaaS proposal is to score the services against what you currently cannot do, rather than against a feature list. The ones you already do well are worth nothing to you no matter how prominently they appear.

The Three Shapes of Contract

Pure lease, devices return

You pay monthly, you hand everything back at the end, the provider takes the residual value.

Right when you genuinely want to be out of hardware ownership and your refresh cycle is predictable. It fails when return rates are poor, because a device you cannot return is usually charged at a figure that assumes you kept something valuable.

Lease with buyout option

Same, with the right to purchase devices at the end.

Right when some machines will be worth keeping and you want the choice. The thing to establish is how the buyout price is determined, because "fair market value at the time" is an open position and "a stated percentage" is a known one.

Subscription with refresh built in

Devices are replaced on a cycle as part of the service, with no distinct end of term.

Right for companies whose actual problem is that refreshes never happen. It fails on flexibility, since you are committing to a replacement rhythm that may not match how your business changes.

The thing to check in this shape specifically is what triggers a refresh. A cycle defined by device age replaces machines that are working fine alongside machines that needed replacing a year ago, which is the same blunt outcome as a scheduled purchase, just funded differently. A cycle that allows condition-based replacement within an overall budget is considerably more useful and is worth asking for, because it is the one version of DaaS that actually improves on what a well-run in-house programme does rather than merely financing it differently.

Month 37, and Why It Decides Everything

A 36-month term has a 37th month, and most of the disappointment in this category happens there.

Devices have to come back, and yours are in flats across several countries. The provider's recovery assumption is in the contract and your actual recovery rate is in your register, and if those two numbers differ you will pay the difference. This is the single most common unpleasant surprise, and it is entirely predictable from data you already have.

Condition standards apply. Normal wear is accepted and the definition of normal is the provider's. Ask what proportion of returned devices typically attract a charge and what the common reasons are. A provider who can answer precisely has thought about it; one who waves it away has not.

Missing accessories count. Chargers, in particular, go missing at a rate nobody anticipates, and they are charged individually. Across a fleet of a few hundred machines this is not a trivial line, and the fix is almost comically simple: say in the original delivery note that the charger must come back with the device, and say it again in the return instructions. Most of these losses are people assuming the cable is theirs to keep rather than anybody acting badly.

The transition overlaps. New devices arrive while old ones are still being collected, so for a period you hold both and may be paying for both. Establish how the overlap is handled before signing, because an unplanned overlap of two months across a fleet is a meaningful cost.

The practical protection is to run your own recovery rate into the model before agreeing a term. If you recover 70 per cent of devices from leavers today, a contract priced on 95 per cent returns is a contract you will lose money on, and you should either fix recovery first or negotiate the assumption.

Building Your Own Comparator First

Every quote in this category is unanswerable without a number of your own, and almost nobody has it. Producing it takes a morning and changes every subsequent conversation.

Start with the purchase price over the real life you get, not the planned one. If you intend a three-year refresh and the fleet actually averages four and a half years, use four and a half. This single correction usually reduces your calculated annual hardware cost by a third and makes outright purchase look considerably better than the vendor's comparison assumed.

Add configuration and delivery, measured per device. Time spent by whoever prepares and ships a machine, at a realistic internal rate, plus actual shipping and any customs charges. For a distributed company this is a much larger number than people expect and it is the component DaaS most reliably improves.

Add hardware support. Tickets touching hardware, average handling time, plus the elapsed days somebody could not work while waiting. The second part is the one that gets left out and it is frequently the largest.

Add disposal. What you currently spend, or, more honestly, what you will spend once somebody deals with the cupboard.

Add the write-offs. Devices issued to people who left and never returned, at their residual value. This is the line that makes the most difference and the one companies are most reluctant to include, because it requires admitting the recovery rate. It is also the line a provider will happily help you calculate, for the obvious reason, so produce it yourself first and decide what you believe before anybody else offers you a figure for it.

Divide by device count and by years and you have a figure per device per year that you can hold any quote against. And the exercise is worth doing even if you never buy DaaS, because three of those five lines are costs you could reduce without changing anything about how you finance hardware.

One caution. Resist the temptation to load every indirect cost into the comparator to justify a decision already made. A comparator built to win an argument will win it, and then the arrangement underperforms against a number that was never real.

How to Choose: Five Questions Before You Talk to Any Vendor

What is your current all-in cost per device per year? Purchase price spread over the real life you get, plus configuration, plus support time, plus disposal, plus the written-off value of devices never returned. Without this number you cannot evaluate any quote, and most companies do not have it.

What is your device recovery rate? It is an input to the contract whether you supply it or not. Supplying it lets you negotiate the assumption rather than inherit it.

Which of the bundled services do you actually need? A distributed company usually values delivery, replacement and collection highly and on-site support not at all. Paying for a service model built around offices is a common and avoidable cost.

How stable is your headcount? Term length should follow this. A company that might shrink should pay more for flexibility rather than less for a long commitment.

Who owns the relationship afterwards? DaaS moves work from your team to a provider and creates a vendor-management job that did not exist before. Name the person.

The Providers

Not one provider in this category publishes a price, checked against each vendor's own pricing pages most recently on 7 and 9 October 2026. What follows compares them on everything except price, because price is not available.

Workwize, Deel IT, Firstbase, GroWrk and allwhere

All five offer variations on procurement, delivery, management and retrieval across international markets, with differing degrees of financing attached. They differ most on country coverage depth, which the headline country count hides, so shortlist against your own markets. None publishes figures, and each describes a model without attaching numbers to it.

Manufacturer programmes

The large hardware manufacturers run their own device-as-a-service arrangements, which are generally strongest on hardware and support and weakest on the distributed logistics problem. Worth noting that Lenovo TruScale's product URL now returns a 404 although the brand is still referenced on their services pages, so treat any older reference to it with caution and confirm the programme still exists before building a shortlist around it.

RemoAsset

Disclosure: RemoAsset is owned by the same people who publish HROpsLab. It appears here because it competes in this category and is assessed against the same criteria as everything else on this page, with its limitations stated in the same detail.

Best for: companies whose real problem at month 37 is recovery, since the same platform that delivered the device triggers and tracks its return.

Why companies choose it: the asset record is created at delivery rather than typed afterwards, so the serial, recipient and address exist from day one, which is precisely the data a return depends on. Devices can be held and reissued in region rather than shipped centrally.

Where it struggles: it publishes no price and requires a demo. Its advantage weakens considerably for hardware it did not supply. And it is not a certified disposal vendor, so the end-of-life certification in a DaaS arrangement comes from somewhere else.

Buying outright, as the honest comparator

Always include this as a line in the comparison. It is cheaper in total cash, it ties up capital, and it leaves you doing the services yourself. Quantifying what those services cost you today is the only way to tell whether a bundle is good value.

There is a middle option that rarely appears in these exercises and often wins: buy the hardware outright and buy only the services you cannot perform, from a logistics platform, without the financing. You keep the asset and the cheaper total cost, and you still get delivery, replacement and collection in the markets where you cannot manage them yourself. Several of the providers listed above will sell the service layer without the finance layer if asked, and almost none of them will offer it unprompted, because the bundled arrangement is both easier to sell and more valuable to them. Ask for it explicitly.

The Comparison

The Decision Table

The Clauses Worth Reading Twice

Six places where these contracts differ in ways that do not show up in the monthly figure. None of them is obscure and all of them are routinely skimmed.

Damage, loss and theft, treated separately. Hardware failure is usually covered; a dropped laptop frequently is not, and a stolen one is a third category again. Ask for the charge in each case and for whether there is an annual cap, because a company with field staff will hit these repeatedly.

The condition standard at return. Who defines normal wear, and what proportion of returns typically attracts a charge. A provider with real data here is a provider who has thought about it.

Device substitution during the term. What happens when somebody needs a different specification, and whether swapping mid-term resets anything. Growing companies change role mixes and the contract should allow it without a renegotiation.

Volume flexibility in both directions. Most contracts handle adding devices gracefully and removing them badly. Establish what happens if headcount falls by a fifth, because that is the scenario the arrangement is least prepared for and the one you most need an answer to.

Where the data obligation sits. The device goes back to somebody else's warehouse with your data having been on it. Establish who wipes it, to what standard, when, and what evidence you receive, because the obligation does not transfer just because the hardware does.

What happens on provider failure or acquisition. Your fleet sits with a third party under a financing arrangement. This is the lowest-probability clause here and the one with the widest range of outcomes, and it is worth a question rather than an assumption.

The pattern across all six is the same: the monthly figure covers the expected case, and these clauses govern everything else. Most of the regret in this category comes from the everything else.

Measuring Whether It Worked

Four numbers, and none of them is the monthly figure.

All-in cost per device per year, before and after. Include everything the bundle replaced, or you will compare a complete arrangement against a partial one and conclude wrongly.

Days from request to device in hand. One of the main operational reasons to buy DaaS is speed, and it is easy to measure and rarely checked afterwards.

Return rate at end of term. The contract assumed a figure. Track the actual, because it determines your end-of-term charges and your next negotiation.

Support load on your own team. Tickets and hours spent on hardware issues. If the bundle was supposed to move this to a provider and the number has not fallen, the service component is not delivering what you are paying for.

Take all four as a baseline in the quarter before the arrangement starts, because none of them can be reconstructed afterwards and all of them will be disputed at renewal. A team that cannot say what its hardware support load was before the contract has no way to demonstrate the contract helped, which means the renewal conversation is conducted entirely on the provider's figures. Half a day of measurement before go-live is worth more than any amount of reporting during the term, and it is the step that gets skipped because the project is busy launching.

Running the Arrangement Once It Starts

A DaaS contract is not a purchase that completes. It is a relationship that needs managing, and the companies that get value from it do three things the companies that do not get value skip.

Reconcile the invoice against your register monthly. You are billed per device, so the bill is a claim about how many devices you have. Checking it against your own count takes ten minutes and routinely finds devices billed after return, devices billed twice following a replacement, and devices you believed were cancelled. Nobody does this and it is the single highest-return habit available.

Keep your own asset record regardless. The provider has a register and it is theirs, built for their billing rather than your operations. Relying on it entirely means you cannot answer a question without asking them, and you are in a weak position at renewal because they hold the only account of what happened.

Track replacements as a quality signal. A rising replacement rate on a particular model is useful information for the next term, and it is invisible unless somebody is counting. It is also your evidence if you want to change specification mid-term.

Diary the end of term at least six months out. The month-37 problems are all avoidable with two quarters of notice and all expensive with two weeks. Recovery of devices from distributed staff cannot be compressed, so the collection effort has to begin while the term is still running.

And name the person who owns the relationship. DaaS moves work from your team to a provider and creates vendor management that did not previously exist. Unowned, the arrangement drifts: invoices go unchecked, service failures go unrecorded, and the renewal arrives with no evidence to negotiate on.

What Getting This Wrong Costs

The direct cost is overpaying for financing, and at a few hundred devices across three years it is a number worth caring about without being dramatic.

The second cost arrives at month 37 and is usually larger than the first. Devices that cannot be returned, condition charges, missing accessories and an unplanned overlap period between fleets. All four are foreseeable and all four are routinely absent from the business case.

The third is the one that does not appear in any model. A bundle chosen on the headline figure rather than on the service mix leaves you paying for on-site support you cannot use while still doing your own international shipping, which is both expensive and demoralising for the team who expected the arrangement to help them. That is the opening example, continued eighteen months on.

There is a fourth cost that is strategic rather than financial, and it is worth naming because it is the one that outlasts the contract. A three-year DaaS arrangement moves your procurement, delivery, replacement and collection capability to a provider, and if you had any of those in-house they will not survive the term. People move on, processes stop being documented, supplier relationships lapse. At renewal you are not comparing the provider against doing it yourself, because doing it yourself is no longer an option you hold; you are comparing them against a competitor and against the cost of rebuilding. That is a normal consequence of outsourcing anything and it belongs in the decision rather than arriving as a discovery in month 34.

So the question to take into the next procurement exercise is not which monthly figure is lowest. It is what each figure contains, and whether any provider will write the split down.

When You're Ready to Move Beyond Buying Outright

Buying outright is the default and it is a good default. It is the cheapest way to own hardware, it keeps the decisions with you, and for a company in one place with a functioning refresh process there is no argument for changing.

What ends it is almost never the economics. It is that the work around the hardware, meaning procurement across borders, configuration, replacement, collection and disposal, grows faster than the team doing it, and the refresh becomes a project that keeps being deferred because nobody has three weeks. DaaS is a way of buying that work, and framed that way the decision is clear rather than confusing.

The sequence that works: calculate your own all-in cost per device per year first, including the things you do badly, so you have a comparator. Measure your recovery rate, because it is going into the contract either way. Ask every provider for the monthly figure split three ways and treat a refusal as information. Get the month-37 terms in writing before anything else. Then compare on the service mix against your actual markets, which is where the real difference between providers sits, rather than on a bundled number that was never comparable in the first place.

Frequently Asked Questions

HROpsLab takes no vendor money and publishes no paid placements, which is why this page says no provider publishes a price rather than estimating one.