We need to bring device spending down 15% next year without hurting productivity.
Please put together a plan by the end of next week.
Dana
Dana, the FY27 device plan you asked for is ready, and Alex has approved it.
Only the redeployment was done automatically, under existing policy. Moving refresh from age to condition needed Alex’s approval, and the accessory catalog goes through Procurement at the laptop agreement renewal. I left out a lower-spec standard for power users because their devices are already close to their performance limits, and field engineering refreshes stay on schedule.
| LEVER | FY27 | WHO ACTS |
|---|---|---|
| Redeploy recovered laptops before buying$410K done, $290K still to go | $0.7M | Agent |
| Refresh on condition, not age1,900 of 4,200 laptops due are healthy for another year | $1.1M | Agent, once approved |
| Repair instead of replaceBatteries and screens on out-of-warranty devices | $0.35M | Agent |
| Claim warranty before buying260 failing devices still under warranty | $0.25M | Agent |
| Consolidate the accessory catalog46 SKUs to 12, at the laptop agreement renewal | $0.4M | Procurement |
| Lower-spec standard for power usersTheir devices are already near performance limits | $0.45M | Excluded |
| Total identified, including completed work | $2.8M |
Savings are counted only once a purchase is cancelled or a redeployed device is confirmed in use. Operational detail goes to the program owner.
Hey, Dana just asked for a plan to bring FY27 device spend down 15%, about $2.7M on our $18M plan, without hurting productivity.
I’ve already started working on it. I’m reading device health, warranty, stock and the FY27 refresh schedule to find where we can spend less without slowing anyone down.
I’ve also flagged 4,200 laptops due for age-based refresh in FY27, which is where most of the room is.
I’ll put together a prioritized plan with projected savings, risks, and the actions I can take under our existing policies.
Is there anything you’d like me to prioritize or avoid?
Understood. Field engineering refreshes stay on schedule, and I’ll check their 380 devices for any that need replacing sooner.
I’ll continue with the rest of the fleet and bring you a recommendation.
I’ve completed the analysis: $2.8M in FY27 savings identified, including work that’s already done.
$410K is already secured. I redeployed 512 recovered laptops to new hires under our existing policy instead of buying new ones, and took those purchases out of the FY27 plan.
One change from my first pass: a lower-spec standard for power users would have saved $450K, but their devices are already close to their performance limits. I left it out and replaced most of it with repair-first for out-of-warranty batteries and screens ($350K). That puts us $100K over target, with less cushion than I’d like.
Field engineering refreshes stay on schedule, as you asked. And the regular work kept going: 96 devices fulfilled and 23 recovered since Monday.
The plan, with evidence and risks, is ready for your review.
11,600 laptops · device health and warranty · stock and depots · FY27 refresh schedule · Workday hiring plan
Weighs every option against policy, Alex’s guidance, device performance and the 15% target
Executes what policy allows, verifies it in each system, and routes the rest to people