A denied capital request doesn’t mean the refresh is off. It usually means the refresh, as proposed, was too big to approve in one decision.
If your devices are aging, inconsistent across sites, and slowing your frontline workers down, and leadership just said no to replacing them, you have more options than waiting for next year. Most of them involve changing the size, timing, or funding of the request rather than the need behind it.
This post covers how to phase a refresh, the funding models that avoid a single large capital spend, how to recover value from the old fleet, and how to rebuild the case so it gets approved.
Why refresh requests get denied
Refresh requests usually fail for reasons that have little to do with whether the devices need replacing. The request is large, it lands in a tight budget year, and it’s presented as an IT purchase rather than an operational fix.
The cycle makes it worse. When devices are bought all at once, they age together, and every few years the organization faces the same large request. Leadership sees a big number with a familiar shape and defers it.
If you’re still working out how to keep the current fleet going in the meantime, the post on what to do when the refresh budget is frozen covers triage and safe life extension. This post is about getting the refresh itself moving.
Phase the refresh by role and site
A phased refresh turns one large request into several smaller ones. It also puts new devices where they’ll make the biggest difference first.
Start with the devices that hurt operations most. That’s usually the roles that use devices hardest, such as drivers, pickers, and receivers, and the sites with the highest failure rates. Devices that no longer get security updates belong in the first phase regardless.
Then plan the next phases by quarter or by fiscal year. Each phase is a smaller, easier approval, and it breaks the pattern of the whole fleet aging at once. The post on what a healthy refresh cycle looks like covers how to stagger replacements for the long term.
Phasing also gives you something capital requests rarely have, which is evidence. The first phase shows leadership what new devices change on the floor, such as fewer repair tickets or fewer swaps, and that makes the next approval easier to win.
Just know that a phased refresh means running two device models for a while. Plan for two sets of accessories, chargers, and configurations, and make sure your help desk knows which sites are on which device.
Funding models that avoid one large capital spend
If the obstacle is capital specifically, changing how devices are paid for can move the refresh forward. Each model has trade-offs worth understanding before you propose it.
Leasing. Leasing spreads the hardware cost over a term. It suits organizations that want new devices now and are comfortable returning or buying them out at the end.
Check what happens at end of term and what’s included beyond the hardware itself.
Device as a Service (DaaS). DaaS bundles the hardware with services such as staging, support, repairs, and refresh into a monthly cost per device. It turns refresh into a predictable, recurring line instead of a periodic capital spike.
The piece on how DaaS delivers cost savings covers where the model helps and where it doesn’t.
Vendor financing. Some suppliers offer payment terms that spread a purchase over time. It keeps ownership with you but still puts the full cost on your books.
Whichever model you consider, talk to your finance team about how it would be treated in your budget. That treatment varies by organization, and it often decides which option leadership will approve. The post on leasing mobile devices covers the leasing route in more depth.
Recover value from the old fleet
The devices you’re replacing may still be worth something. Depending on their age, model, and condition, some can be resold or traded in, and that value can offset part of the refresh.
Recovering it takes planning. Old devices need to be collected from every site, counted against your records, and securely wiped before they leave your control. In Canada, you remain accountable under PIPEDA for personal information on devices you control, so the wipe and the paper trail matter as much as the price.
Here’s what actually happens when this step is skipped. Old devices pile up in back rooms as unofficial spares, their resale value drops every month, and eventually someone has to deal with a closet full of devices that hold data nobody has accounted for.
Rebuild the case in operational terms
A refresh case gets approved when it’s framed around what the business loses by waiting. Leadership responds to missed deliveries, idle workers, and customer complaints more than to device age.
- Show the cost of the current fleet, including last year’s repair spend and how it’s trending.
- Put a number on lost time in your own terms, such as shifts with workers short of devices or deliveries delayed by failures.
- Name the security exposure, listing any devices that no longer receive security updates.
- Make the first ask small, with a phased plan and the funding model that fits your budget rules.
One freight carrier we work with had nearly six-year-old devices failing regularly in the field and first considered buying more of the same legacy model. A full-fleet replacement with an extended warranty turned out to be the stronger case, and around 800 devices were deployed across its depots in six weeks. The transportation case study covers how that decision was made.
Where outside help fits
If the refresh is stuck on capital, a subscription model may let it go ahead in a different form. We offer Device as a Service, with sourcing, staging, support, and secure retirement of old devices handled by our in-house Canadian team in one monthly cost per device. The Device as a Service guide explains how the model is structured.
Just know that DaaS fits best when predictable costs and a built-in refresh schedule matter more to you than owning the devices. If capital becomes available and you have the team to run the cycle, buying outright may still be the better choice.
Questions we hear about funding a device refresh
How can I refresh devices without a capital budget?
Change the size, timing, or funding of the request. Phase the refresh so each approval is smaller, start with the roles and sites that need new devices most, and consider leasing or Device as a Service to turn the cost into a monthly expense. Recover value from the old fleet where you can.
How do I phase a device refresh?
Start with devices that no longer get security updates and the roles and sites with the highest failure rates. Plan later phases by quarter or fiscal year. Expect to run two device models during the transition, and plan accessories, configurations, and help desk support for both.
When does Device as a Service make sense?
When predictable monthly costs and a scheduled refresh matter more than owning the devices, and when you’d rather not run staging, repairs, and retirement in-house. It may be less attractive if capital is readily available and your team already manages the full device lifecycle well.
Where to start
List the devices that must be replaced first, by role and site, and cost that group on its own. Then ask finance which funding models your organization can approve and how each would be treated. A smaller first phase with the right funding model is far more likely to get a yes than a second attempt at the original request.