Device refresh policy India: a Bengaluru SaaS CFO meeting
Device refresh policy India: a Bengaluru SaaS CFO meeting
Last updated: 23 June 2026
9:50 AM, Tuesday in June 2026, rains had started early in Whitefield. Aakash, IT manager at a 180-seat B2B SaaS firm, was printing v3 of a device refresh policy India the founder, the CFO and the COO had been arguing about since March. The CFO had said no twice. Aakash had v4 outlined on his screen already.
“Aakash, ye refresh policy ka 3rd version hai? Bas. Aaj final karte hain,” Vikram the CFO had messaged on Slack the previous evening. Aakash had read it the way you read a doctor’s report you have been postponing.
He had the printout, a one-page TCO sheet, the AMC bill from the last 11 months, and an email from a hiring manager with the subject line “Laptop replacement, urgent, third time”. No vendor in the room. Deliberate. We have seen 30-plus of these meetings; the deliberate ones tend to close.
9:50 AM. The third version
The first two versions had asked for money. v1 in March asked for ₹74 lakh to refresh 140 laptops over the next two quarters. The CFO had looked at the number, looked at the cash position, and said no. v2 in June asked for ₹52 lakh and a phased rollout. The CFO had parked it because the funding round was 6 weeks away and capex was on freeze.
v3 was a different document. It was not an ask. It was a policy.
The cover page had three lines. Refresh trigger 1: laptop age > 42 months. Refresh trigger 2: warranty expired or extension cost > 35% of replacement. Refresh trigger 3: break-fix incidents > 2 in the last 9 months. Any device hitting any one trigger goes into the refresh queue. The queue runs on a quarterly cadence. The capex is forecast 6 months in advance.
Aakash had stopped asking the CFO to approve a number. He was asking him to approve a rule.
This is the part that buyers miss. A device refresh policy is not a procurement document. It is a forecasting document. The CFO’s actual fear is not the spend. It is the uncosted, unscheduled, mid-quarter spend that breaks his variance commentary at the board meeting.
What a device refresh policy India CFOs actually read looks like
The earlier two drafts had buried the math. v3 put one paragraph on page 1. It said: at our current run rate, 38 laptops will fail or fall out of warranty by Q4 FY27. Replacement at that point will be reactive, full-margin, and on emergency PO. Forecast cost of doing nothing for 18 months: ₹61 lakh in break-fix, overtime, lost engineering hours, and the 3 hiring offers we lost in the last 6 months because new joiners had to wait 11 days for a laptop.
That paragraph was the only thing in the document the CFO underlined.
The second page was the policy itself. The third page was the 36-month TCO comparison. The fourth page was the warranty cliff math. The fifth page was a single recommendation, two options, and a date by which the call had to be made.
Anjali rule for any policy you take to a CFO: front-load the cost of inaction, then offer two paths. A CFO who has to choose is a CFO who engages. A CFO who is presented with a single ask defaults to “let me think about it” and you lose another quarter.
10:30 AM. The page-4 question
Vikram walked in 4 minutes late, opened the printout to page 4 first, and said “explain this.” That was a good sign. Page 4 was the warranty cliff.
Aakash had built a table of every laptop by month of purchase, original warranty end date, and the cost of extending warranty vs replacing. 64 of the 180 laptops were on their second or third extension already. The extension cost averaged ₹14,200 per device per year by month 38. The replacement cost for a comparable Dell Latitude 5450 or HP ProBook 450 G10 was around ₹68,000 to ₹78,000 depending on SKU. The math became uncomfortable at month 42 and openly bad at month 48.
“Math hai?” Vikram asked. He was engaging.
Of course the warranty cliff was at month 38, two months after he had insisted laptops should last 5 years. Aakash had not framed it that way. He had let the table do it.
The conversation shifted. Vikram stopped asking whether to refresh. He started asking when, in what tranches, and on which path.
The 36-month TCO that closed it
Page 3 was the part Aakash had rewritten four times. He had built it as a side-by-side that a CFO could read in 90 seconds and a board could read in 30.
Three paths, 180 devices, 36 months, all numbers including GST and excluding peripherals.
| Path | Year-1 capex | 3-year total | What it covers | What it does not |
|---|---|---|---|---|
| Buy outright, refresh in tranches | ~₹52 lakh (90 units) | ~₹98 lakh (180 units, phased) | Hardware, 3-yr OEM warranty, basic imaging | AMC after Yr 3, ITAD at end-of-life, MDM, deployment hands |
| DaaS, ₹510/device/month, 36 months | ~₹11 lakh (Yr-1 cash outflow) | ~₹1.04 Cr (full subscription) | Hardware, full-term warranty, imaging, helpdesk, refresh in Yr 4 | The few specialist SKUs (Precision workstations) sit outside |
| Do nothing, reactive replacement | ~₹4 lakh (emergency only) | ~₹70 lakh hardware + ₹61 lakh hidden | Nothing planned. Each failure handled at full margin. | Hiring offers, engineering hours, variance commentary, sleep |
The capex path was cheaper by ₹6 lakh on paper. The DaaS path was easier to defend at the board because it converted a step-function capex spike into an even OpEx line. The third path was the one they had been on by default for 18 months.
Vikram looked at row 3 for a long second. “Agar hum aaj nahi karte, hum already ₹14 lakh ki hidden cost le rahe hain har quarter. Yeh I did not see in the AMC sheet.”
He had said “we” at the end. That was the moment v3 became a signed document.
The TCO comparison is also the bridge into the larger Device-as-a-Service explanation we keep for CFOs and FP&A leads, and into the longer-form DaaS vs buying total-cost bake-off a Mumbai CFO ran over 36 months. Different sectors, same shape of decision.
The clause that turned v3 into a signed SOW
Aakash had left one paragraph on the last page. It said: this policy will be reviewed every 12 months. Refresh triggers may be tightened if break-fix incidents exceed plan. The CFO co-owns the trigger thresholds with IT. Either party can call a review without 6 months of warning.
That was the clause that turned the room.
Vikram had not been against the refresh. He had been against an open-ended capex with no review mechanism. The minute the policy gave him a co-owned trigger and a 12-month review, the spend stopped being a recurring fight and became a calendar item. He signed the cover page, asked for the vendor pricing by Friday, and stood up.
If I were rewriting this policy today, I would add one line in section 12: any device with two break-fix incidents in a single quarter goes into the refresh queue automatically, no review. That removes the one place IT and Finance still have to negotiate per case.
Aakash sent me a one-line WhatsApp at 11:14. “Done. Vendor brief by Friday. v4 deleted.”
I was at the coffee machine. The office boy had brought a fresh round of thanda chai for the team because the rains had picked up again. The procurement lead asked me what had changed. I said, the policy got the math the earlier two drafts had hidden. He nodded. He had been on the wrong side of three of these.
That is usually all that changes.
What we usually see when a CFO has parked a refresh twice
We have run this exact meeting in some form for 180-, 250-, and 420-seat firms across Bengaluru, Pune, Mumbai, Hyderabad and Chennai over the last two years. The fleet sizes change. The CFO question does not.
The pattern that gets refresh policies signed is consistent. The IT lead stops asking for money and starts writing a rule. The rule has 3 triggers, not 12. The TCO sits on one page with three paths. The cost of inaction is the first paragraph. The DaaS option is presented as a sibling, not a fallback, so the CFO has a choice to make.
The conversation we then have is almost never about which laptop. It is about which path, which tranches, and how the policy handles the next refresh. Hardware is downstream of policy. Our role is to bring the SKU benchmark (the Dell Latitude and Precision shortlists we keep for SaaS fleets, the HP ProBook and EliteBook side), the warranty math, the AMC vs ProSupport call, and the ITAD path. If the firm picks the DaaS path, we run the 36-month leasing programme; if it picks capex with phased refresh, we run that too, through the device lifecycle management practice.
The two documents we ask the IT lead to read before walking into the CFO meeting are the existing how-to-build-a-device-refresh-policy guide and the pitch-DaaS-to-your-CFO deck. They are 12 and 9 minutes of reading. They have closed more meetings for us than any vendor brochure.
If you want a sense of the field reports on the hardware side of these refreshes, the 175-seat Chennai analytics firm story and the 220-seat Pune engineering refresh are the two most recent. Both are the post-policy chapter of the same kind of Tuesday morning.
Public sources we keep on hand for the math: the IDC India PC tracker for commercial volumes, the Gartner end-user-device TCO framework, the MeitY e-waste rules guidance for the ITAD path when the retired fleet leaves the building, and the CERT-In advisories we keep in the policy appendix for the security side of an end-of-life device. The numbers in this story are anonymised; the shape of them is not.
Get a quote on a 30-minute refresh policy review for your fleet
P.S. Anjali here. I sat through three of these meetings in May and June 2026. The IT lead does not lose on the laptop spec. They lose on the first page. v3 wins because v3 finally has the cost of doing nothing on page 1 and a co-owned trigger on the last page. If you are sitting on a CFO no, you are likely 90 minutes of rewriting away from a yes. Reach us on WhatsApp at +91 91375 93228 between 10 and 7 IST and we will read your draft before you take it back in.