You can successfully complete a hardware refresh, hit your deadlines, stay within budget and still leave your team dealing with the same connectivity problems they had before.
It's easy to see how it happens. Your routers are nearing end of life, and the budget to replace them has already been approved. Meanwhile, your IT team is stretched just keeping the existing network running.
The existing connectivity? That's a separate contract, potentially with a different renewal date. It's been working well enough, and reviewing carriers or data plans would only add another layer to an already complex project.
So, you replace the hardware, keep the existing connectivity and move on.
It's a perfectly understandable decision. But it's worth asking whether you're keeping that connectivity because it still meets the business's needs, or simply because changing it wasn't part of the project.
New Equipment Doesn't Fix Old Connectivity Problems
Think about the sites that keep coming back into the support queue. At one location, the connection appears to be up, but applications are painfully slow. At another, users report brief dropouts that have disappeared by the time your team investigates.
Your team opens a ticket, sends over diagnostics and chases updates. By the time the provider tests the connection, everything looks normal again.
The ticket gets closed. A few weeks later, the same site is back.
If the underlying connectivity is the problem, replacing the router won't make it disappear.
Your wireless backup deserves the same scrutiny. Perhaps you've standardized on one carrier across your locations because it's easier to procure and manage. But does that carrier perform equally well at the head office, inside a warehouse or at a remote location?
Even where failover works as designed, the backup connection may struggle to support the site's critical traffic. It doesn't need to match the capacity of the primary connection or support every application, but it does need to keep the services the business depends on running during an outage.
That doesn't mean every connection needs to be changed. But a hardware refresh is a good reason to look at the connectivity sitting behind it and decide whether it's still doing the job you need it to do.
The Cost of Doing It Later
Now imagine discovering these limitations six months after completing your hardware refresh.
Several locations need connectivity changes. At some sites, that means replacing physical SIMs or installing different network equipment. For wired connections such as dedicated internet access (DIA), it could mean arranging new fiber circuits, installing carrier termination equipment or making changes to existing connections.
Then there's the logistics of coordinating engineers, securing site access and scheduling installation windows without disrupting business operations. If you don't have local IT resources, that could mean flights, hotels, rental cars and time spent traveling between locations.
And you're now spending time and money revisiting sites where you've only recently completed a hardware refresh.
That's the part I'd want to avoid.
Make the Next Refresh Count
I'm not suggesting that every hardware replacement should become a complete network redesign. But before approving the refresh, ask one question: Once this equipment is installed, what changes could still require us to send someone back to the site?
Some sites may need more attention than others. Start by looking at where you already have problems, where requirements have shifted and where today's equipment choices could make future changes unnecessarily difficult.
From there, you can make three decisions:
- Keep as is: If the existing connectivity is performing well and meets the site's requirements, there's no need to touch it simply because you're replacing the router.
- Address during the refresh: Prioritize locations with recurring connectivity issues, poor carrier coverage, unsuitable data plans or backup connections that haven't been adequately validated. Investigate the cause and see what makes sense to address while engineers are already scheduled to be there.
- Plan for future changes: Some locations may be working perfectly well today, but what if you need to switch carriers later? Consider whether the new hardware and provisioning capabilities will allow you to handle that remotely, rather than sending someone back to replace a physical SIM or install more equipment.
Make those decisions before the deployment, while there's still time to coordinate the work.
Don't Let the Project Scope Make the Decision for You
That might mean looking beyond the immediate scope of the refresh.
We saw this with a large U.S. retailer that was refreshing network equipment across more than 80 locations. They had already selected their hardware provider when we came in, but nothing had been deployed yet. We designed an eSIM-based connectivity solution with access to three major U.S. carriers and a shared data pool across them. We also took on the deployment of both the hardware and connectivity, so the customer didn't have to manage either rollout themselves or bring in a separate deployment partner. What could have been two separate projects became one coordinated deployment.
But the benefits went beyond the initial deployment. If coverage or carrier requirements change at a location in the future, eSIM gives them the flexibility to switch carrier profiles remotely, where supported, rather than automatically needing another site visit just to replace a physical SIM.
And that's the bigger point: A hardware refresh isn't just about replacing equipment that's reached the end of life. It's an opportunity to address existing problems and make sure today's decisions don't create unnecessary work further down the line.
So, before your next hardware refresh, ask: Are you solving the problems you already know about, or installing new equipment around them?