Device-as-a-Service explained: what it is, costs, who it’s for
- What is Device-as-a-Service in plain language
- What DaaS actually bundles (and what stays with you)
- Real Indian DaaS pricing for a 100 to 1,000 device fleet
- Who DaaS is for: the 5 fleet-shape tests
- Who DaaS is NOT for
- What a sane DaaS contract looks like
- What DaaS replaces line by line
- FAQ
If you have heard the term Device-as-a-Service in approx six vendor calls over the last year and still cannot explain it to your CFO without sounding uncertain, this piece is for you. Rohan is the IT operations head at a 280-person Pune specialty chemicals company. His laptop fleet has crept from 120 to 280 devices in three years on a buy-as-we-grow basis. AMC renewals last quarter came in 22 percent higher than the year before. He had Googled “device as a service India” four times and bookmarked seven pages, mostly OEM marketing. None of them said the rupee figure he needed to take to his CFO.
So we ran a structured scoping call. Two pages of notes later, he had a real per-device monthly figure in writing and a clear answer to “is my company the right shape for this.” That is approx 9 out of 10 IT heads I meet in his fleet band. Nobody has explained the model end-to-end with rupee figures attached. Most write-ups stop at “what is Device-as-a-Service” and dodge the cost question. This piece is the version of Rohan’s conversation, written down.
The promise: how to understand the model end to end in 12 minutes, including what it costs per device per month in 2026, who it is for, and who it is not for, even if every previous explanation you read sounded like a sales deck dressed up as content.
What is Device-as-a-Service in plain language
Device-as-a-Service is a single contract under which a vendor supplies your business laptops (or tablets, or phones), configures them, ships them to your employees, monitors them through their working life, repairs them when they break, replaces them on a refresh cycle, and disposes of them when the term ends. You pay one monthly fee per device. The vendor carries the financing, the warranty, the helpdesk, the MDM, the imaging, the asset register, and the end-of-life process. Your in-house IT team stops handling those motions and starts owning the things that actually need your team: applications, identity, security policy, escalations.
The shorthand is DaaS. The longer version is everything in the previous paragraph. The model exists because, for fleets above approx 100 devices, the operational lift of managing laptops yourself is bigger than the price difference between buying them and renting them on a structured contract. Once you put real numbers on the AMC line, the helpdesk-time line, the ITAD line, the refresh-discipline line, and the downtime line, the rent-versus-buy comparison stops looking like a finance question and starts looking like an operations question.
DaaS is not a lease. A lease is a financing wrapper around a laptop you still operate yourself. DaaS is an operational service that happens to be paid for monthly. If your vendor is selling you something that looks like a lease with extra paperwork, you are not buying DaaS, you are buying a financing product mislabelled. The honest way to test which one you are looking at is to read the SLA section. A lease will be thin. A real DaaS contract will have measurable SLAs on deployment time, repair turnaround, replacement time, refresh window, and end-of-term data wipe.
What DaaS actually bundles (and what stays with you)
The number one source of confusion in any DaaS explanation is the in-scope vs out-of-scope question. A clean contract draws the line in one table on page two. Anything outside that table is your team.
| Line | In DaaS scope | Stays with your team |
|---|---|---|
| Hardware supply | Laptop, dock, charger, carry case, peripherals if specified | Choice of model from a 2 to 3-tier menu agreed at contract signature |
| Imaging / gold image | Build, maintain, push the gold image; quarterly patching | Define what is in the gold image (apps, security baseline, policy) |
| Deployment | Configure, asset-tag, ship to employee address pan-India | Owner allocation, on-boarding sequence, escalation tree |
| Helpdesk L1 | L1 ticketing, common issues, password resets, driver fixes | L2 application support, identity, business logic |
| Onsite warranty by city tier | Tier-1 cities next business day, tier-2 cities 2 to 3 business days, tier-3 cities 3 to 5 business days | Approving the SLA tier mix during contract design |
| MDM enrolment | Enrol every device into MDM at deployment | Define MDM policy, security baseline, data-handling rules |
| DOA replacement | Dead-on-arrival replacement within 5 to 7 working days | Notification path from employee to helpdesk |
| Refresh | Hardware replacement on the agreed cycle (36 or 48 months) | Approve refresh windows, communicate to users |
| ITAD / end of life | Pickup, certified data wipe, e-waste certificate per state rules | Sign off on the destruction certificate, retain for audit |
| Asset register | Maintain live asset register with serial, owner, location, status | Audit access; integration with your CMDB |
| Reporting | Monthly fleet health, ticket SLA, refresh forecast | Review with the IT and finance leadership |
Two lines deserve a callout. AMC and warranty are merged into one operational SLA, paid for inside the monthly fee. There is no separate AMC invoice every June. ITAD is included end-to-end with the e-waste certificate, which closes the audit gap most mid-size companies have where old laptops sit in a storeroom for 8 to 14 months because nobody owns the disposal motion.
What stays with your team is not nothing. Identity, security policy, application stack, business logic, escalations, vendor management. The two-roles split keeps DaaS from feeling like an outsource. Your team owns the strategic device decisions; the vendor runs the operational motion. Read why DLM does not replace your in-house IT team for the longer version of that split. The piece walks through the contract-grade responsibility table line by line.
Real Indian DaaS pricing for a 100 to 1,000 device fleet
Here is where most “what is DaaS” articles go vague. The honest pricing band for an Indian mid-market fleet in 2026, on a 36-month plan, with the scope table above, is approx Rs.1,250 to Rs.1,800 per device per month. Where you land in that band depends on five variables: laptop tier, fleet size, contract length, city-tier SLA mix, and MDM stack. The math is not hidden, but it is also not on most vendor home pages because the per-month figure sounds large until you put the line-by-line replacement next to it.
| Fleet size | Tier-2 business laptop (i5/16/512) | Tier-1 business laptop (i7/16/512) | Notes |
|---|---|---|---|
| 50 to 100 devices | Rs.1,650 to 1,850 per device per month | Rs.2,100 to 2,400 per device per month | Operational lift per device is high; pricing reflects it |
| 100 to 300 devices | Rs.1,400 to 1,650 per device per month | Rs.1,800 to 2,100 per device per month | The sweet spot; Rohan’s 280-device fleet lands here |
| 300 to 700 devices | Rs.1,300 to 1,500 per device per month | Rs.1,650 to 1,900 per device per month | Channel rebates start kicking in; ITAD scale economics apply |
| 700 to 1,500 devices | Rs.1,200 to 1,400 per device per month | Rs.1,550 to 1,750 per device per month | Custom imaging cost amortises across the base |
For Rohan’s 280-device fleet at the tier-2 laptop spec, the centred figure was Rs.1,520 per device per month. The 36-month all-in came to approx Rs.1.43 crore. His current self-owned shape over the same 36 months, when we counted CapEx (approx Rs.1.62 crore at Rs.58,000 average laptop), AMC (approx Rs.12,500 per device cumulative over 3 years), informal ITAD (Rs.2,500 to 4,000 per device, often unrecovered), MDM licences (approx Rs.5,400 per device cumulative), in-house deployment time (Rs.3,200 per device cumulative), and downtime cost (Rs.4,800 per device cumulative on a conservative 1.2-day-per-year estimate at Rs.4,000 per blocked-day) came to approx Rs.2.36 crore. The savings was approx Rs.93 lakh over the term, with the cash-flow shape flattened from a Rs.1.62 crore lumpy CapEx wave to a steady Rs.4 lakh per month OpEx. The number that mattered for his CFO was not the per-device monthly. It was the Rs.93 lakh delta, with the cash-flow shape attached.
For the per-device working backwards, see the DaaS cost per device guide. It breaks the per-month figure into its component cost lines (hardware amortisation, financing cost, warranty, MDM, helpdesk, refresh, ITAD) so you can sanity-check any vendor quote.
Who DaaS is for: the 5 fleet-shape tests
Not every fleet is the right shape for DaaS. There are five tests. If three or more come back yes, the case is worth taking to your CFO. If four come back yes, the case will likely close. If all five come back yes, the only question left is which vendor.
- Fleet size between 100 and 1,500 devices. It is the band where vendor operational efficiency pays off and your in-house team is too small to run all five motions at scale. Below 100, the per-unit lift is small and the case is weak. Above 1,500, you may have the scale to insource cheaper, depending on internal cost structure.
- Refresh discipline is currently slipping. If you have any laptops past 4 years old running production work, your discipline has already broken down. DaaS forces refresh on a fixed cycle, which means you stop losing productivity to old hardware.
- Three or more OEMs are in your fleet. Mixed-OEM fleets are AMC nightmares because every renewal cycle is a different vendor, a different portal, a different SLA. DaaS standardises onto a 2 or 3-tier menu, which means one operational throat to choke.
- Quarterly capex committees are killing your refresh budget. If your refresh request gets cut in Q4 every year because manufacturing capex won, the budget conversation is the problem. DaaS moves it out of capex committee entirely, so you can save mental pain by stopping the annual fight.
- Your IT team is under 6 people for a 200-plus fleet. Below that ratio, the operational motions are eating productive time. DaaS frees the team to work on identity, security, application, and integration, which means strategic projects start moving instead of stalling.
Rohan’s 280-device chemicals fleet hit four of the five. The only test he missed was the OEM count. His fleet was 80 percent Lenovo, 15 percent Dell, 5 percent HP, which is concentrated enough that the AMC pain was real but not extreme. The case closed in one CFO meeting because the other four tests were unambiguous.
Who DaaS is NOT for
Honestly, not every IT operation should be on DaaS, and pretending otherwise wastes your CFO’s time and your own credibility. If your fleet is under 50 laptops, just buy them and refresh in 3 years. If your refresh discipline is already strong, your AMC costs are under control, and your IT team has the bandwidth, you are paying for a process you already run. If you are a tech company with 12-plus IT engineers who already image, deploy, and ITAD at scale, the L1 productivity gain is marginal and the gross margin you pay the vendor is the cost of convenience you may not need. If you operate in defence or critical infrastructure with data-residency rules that block the typical pan-India device pickup channel, talk to your compliance lead before any DaaS pitch.
One specific industry edge to call out: manufacturing-floor rugged tablets and handhelds used by shop-floor operators behave differently from white-collar laptops. Bash factor is higher, replacement turnaround needs to be faster, the device gets dropped, splashed, and exposed to chemicals. Most DaaS contracts are written for white-collar fleets and treat the shop-floor devices as a footnote. If you have a meaningful shop-floor fleet, ask for a separate scope clause with a different SLA. Kavya pushed back on this in our Monday review last quarter for the same Pune chemicals scoping. Her counter was that the contract had to split the white-collar fleet from the shop-floor handhelds because the device economics and the failure modes are not the same. We landed on a two-clause scope split.
What a sane DaaS contract looks like
A clean DaaS contract is approx 14 to 18 pages. Most of it is operational SLAs. Five clauses do the heavy lifting and you should read them before signing.
- Scope split. The in-scope vs out-of-scope table from the section above, attached as Annexure A. It defines what each side owns, so you can avoid effort fighting over scope mid-contract, which means month-7 conversations are about how the fleet is performing, not who is supposed to do what.
- SLA by city tier. Onsite repair turnaround for tier-1, tier-2, tier-3 cities, with explicit per-incident penalties for SLA misses. The penalty is not large; it is a signal of how the vendor takes the SLA seriously. If the contract has no penalty clause, the SLA is theatre.
- Reversibility clause. Your right to exit at month 18 or month 24 with a buy-out schedule for the in-flight devices. Every CFO asks this. The clause needs to be specific: exit triggers, notice period, device buy-out price by month, in-source migration support hours.
- Data wipe certification. At end of term and at every device replacement, a written certificate that the device was wiped to a known standard (NIST 800-88 minimum, ISO 27001 control 8.3.2 equivalent). For SDG and DPDP exposure this is non-negotiable; the data on the laptop is your liability.
- Refresh discipline clause. The vendor must refresh devices on the agreed cycle. If they slip, your fleet age starts creeping again, and the value proposition collapses. Include a clause that allows you to mark slipped refreshes as SLA breaches.
The other 10 pages are commercial. Price escalation cap (usually CPI plus 2 percent), payment terms (45 to 60 days net), GST input credit treatment, jurisdiction clause, and the boilerplate. The five clauses above are where deals get won or lost.
What DaaS replaces line by line
If you want to walk into your CFO meeting and show what the monthly fee actually buys, the line-by-line replacement is the slide that closes the room. For a 280-device fleet over 36 months, here is the comparison.
| Cost line (3-year total) | Self-owned today | DaaS | Delta |
|---|---|---|---|
| Hardware CapEx (laptops + accessories) | Rs.1.62 crore | Rs.0 (included in monthly) | Rs.1.62 crore freed up |
| AMC and out-of-warranty repairs | Rs.35 lakh | Included | Rs.35 lakh out of P&L |
| MDM licences (Knox / Intune / Kandji) | Rs.15.1 lakh | Included or pass-through | Operational efficiency |
| In-house deployment + imaging time | Rs.8.96 lakh | Included | ~165 IT FTE-days returned |
| Downtime (1.2 days per device per year) | Rs.13.4 lakh | Reduced to approx 0.3 days | Rs.10 lakh productivity recovered |
| ITAD pickup, data wipe, e-waste cert | Rs.7 to 11 lakh (often unrecovered) | Included | Audit-clean disposal |
| Total 3-year cost | Approx Rs.2.36 crore | Approx Rs.1.43 crore | Approx Rs.93 lakh saved |
The line your CFO will spend most time on is row 1. Rs.1.62 crore of CapEx not spent over 3 years means Rs.1.62 crore of working capital that stays in the business. For a chemicals company funding raw-material inventory at 60-day cycles, that figure is not abstract. It is the inventory of one product line. That is the conversation. The savings story matters; the cash-flow story matters more.
Most companies treat DaaS like a finance product wearing operational clothing. That is why they read the per-month figure first, multiply by 36 and 280, and walk away. The order of comparison is wrong. You compare DaaS to your current operational shape, not to a hypothetical buy-and-manage shape where everything works perfectly. The L1 vendors in our channel know this. The OEM channel partners know this. The buyer is the only one who does not, and that asymmetry is what makes the model feel expensive when it usually is not.
By the way, did you know we run a free 30-day device fleet audit that produces a written savings number for your specific fleet, not a generic benchmark? It compares your current self-owned cost lines against a like-for-like DaaS shape on the same SLA mix. Approx 6 out of 10 audits surface savings of Rs.30 lakh or more on a 200-plus fleet. Reply “AUDIT” on WhatsApp and we will scope it for your fleet size in the first 4 working hours.
If you want to read the natural sibling pieces before scoping: the DaaS TCO math for 500 devices piece walks the same comparison at a different fleet size, with the same line structure. It will tell you whether the savings shape in Rohan’s case generalises to your fleet.
FAQ
Q: What is Device-as-a-Service in one sentence?
A: Device-as-a-Service is a single contract under which a vendor supplies, configures, deploys, monitors, repairs, refreshes, and disposes of your business devices, paid for as a per-device monthly fee, with measurable SLAs on every operational motion.
Q: How much does Device-as-a-Service cost per device per month in India in 2026?
A: Approx Rs.1,250 to Rs.1,800 per device per month for an Indian mid-market business-laptop fleet on a 36-month plan with onsite warranty by city tier. The exact figure depends on fleet size, laptop tier, contract length, SLA mix, and MDM stack. For a 200 to 300-device tier-2-laptop fleet, expect Rs.1,400 to 1,650.
Q: Is Device-as-a-Service the same as leasing a laptop?
A: No. A lease is a financing wrapper around a laptop you still operate yourself. Device-as-a-Service is an operational service that happens to be paid for monthly. The SLA section is the test. If there are no operational SLAs in the contract, you are looking at a lease, not DaaS.
Q: Does Device-as-a-Service replace my in-house IT team?
A: No. It moves the operational device motions to the vendor and leaves identity, security policy, application support, and business escalations with your team. For a 280-device fleet, expect your team to recover approx 165 FTE-days a year, which usually gets reinvested in projects that were stalled because device operations were eating bandwidth.
Q: What happens to the laptops at the end of the Device-as-a-Service term?
A: The vendor picks them up, runs a certified data wipe to NIST 800-88 standard, issues an e-waste certificate, and disposes of them through an authorised recycler. You keep the certificate for your audit file. Nothing sits in your storeroom for 14 months.
Q: Can I exit a Device-as-a-Service contract early?
A: Yes, if the reversibility clause is written into the contract. Most clean contracts allow exit at month 18 or month 24 with a buy-out schedule for the in-flight devices. If your vendor will not write that clause, walk.
I have walked through this exact DaaS explanation approx 40 times in the last two years with IT heads sitting on fleets between 100 and 1,000 devices. About 7 out of 10 calls close into a free fleet audit because by the time the per-device monthly figure is on the table next to the line-by-line replacement, the conversation stops being theoretical. When I presented the Pune chemicals case to Sudeep last month for a similar 350-device Hyderabad pharma scoping, his first question was “who pays for the laptops the operators bash up on the production floor.” That question reframed the whole scope conversation, seedha boss, and forced us to put the shop-floor handheld clause into Annexure B for that deal.
You compare DaaS to your current operational shape, not to a hypothetical buy-and-manage shape where everything works perfectly.
Here is the part nobody says out loud. Most IT heads who finally bring DaaS to their CFO are doing it partly because they are tired of the Q4 capex committee fight. The CFO knows this. The pitch goes better when you stop pretending it is only about TCO and acknowledge it is also about planning discipline. The seperate truth is that the vendor knows this too, which is why a real DaaS contract puts the reversibility clause first. If your vendor is allergic to that clause, that is your signal that they are selling you a lease theek hai, not DaaS.
The polarising bit: most DaaS write-ups on the public internet are too cautious. They explain the concept and dodge the cost question because the writer either does not know the Indian-market figures or is not allowed to publish them. The IT head sitting in front of his CFO does not need cautious. He needs the actual rupee band, the actual fleet-shape test, and the actual contract clauses. If a piece does not give you those three things, it is not an explanation, it is a brochure.
Book a free 30-day device fleet audit and walk out with a written DaaS savings number for your specific fleet.
200+ businesses trust Sirius Star to scope DaaS deals across pharma, BFSI, logistics, manufacturing, and chemicals. Response within 4 working hours.
If our audit does not surface at least Rs.30 lakh of recoverable savings over 36 months on a 200-plus fleet, the audit is free and you keep the written savings analysis to take to your next vendor conversation.
Book the audit on WhatsApp with a pre-filled message, or fill the form at contact us and we will respond within 4 working hours. For the parent service page, see Device Lifecycle Management.
Free DaaS Scope Sheet PDF (1 page, the in-scope vs out-of-scope table above with a city-tier SLA matrix and the five-clause contract checklist). Reply “SCOPE” on WhatsApp to claim it. Free parallel quote from our DLM team versus your current laptop vendor on a matched configuration; reply “QUOTE” on WhatsApp.
P.S. The 1-page DaaS Scope Sheet we use on every 100-plus fleet scoping call is a one-page PDF. Reply “SCOPE” on WhatsApp and we will send it. It includes the exact in-scope vs out-of-scope table, the city-tier SLA matrix with onsite turnaround windows, and the five non-negotiable contract clauses (scope split, SLA penalty, reversibility, data wipe certification, refresh discipline) printed in a single-page format you can hold during your vendor conversation. The IT heads who walk into their CFO meeting with this sheet close the audit step in one meeting approx 8 out of 10 times.
