A few months ago, Jackie—a program manager at a regional mobile-health organization—asked me for advice. Her team was outfitting 40 nurse vehicles with Bluetooth blood pressure cuffs and tablets. The plan was to send vitals back to the clinic while the nurses were still on the road. And the question she led with was: can we use 5G phones as hotspots instead of a proper device like the LX40 Sierra Wireless 5G router?
I did not give her a one-line answer, because if someone tells you “always buy the rugged router” or “hotspots are fine,” they are not listening to your situation. This is a decision where the answer changes with the use case. Sometimes a hotspot is fine for a while. Sometimes the cheapest long-term option is a 5G Sierra Wireless router. And sometimes you shouldn’t buy a router at all—you should buy an embedded module. Figuring out which one is about the cost of a failure, not the sticker price.
Start with Failure Cost, Not Sticker Price
For the past six years I’ve tracked every connectivity invoice that crossed my desk. When I audited our 2023 spending, the pattern was clear: cheap hardware can get expensive fast. Between reconfigurations, lost field time, and failed data sessions, the $200 hotspot we bought on a Thursday was costing us more than the $800 router we avoided on Monday. I don’t remember the exact totals—don’t hold me to that comparison—but the lesson stayed: hidden costs multiply when a device does its job badly.
So when I help operations teams choose, I break the problem into scenarios. Broadly, I see four: mobile field work, fixed sites with wired backup, low-power sensor installations, and short-term pilots. Your answer will depend on which one you are in.
Scenario 1: Moving Vehicles, Mission-Critical Data
Use a vehicle-grade router. This is the situation where a phone hotspot can fool you. Jackie asked the question I hear constantly: “why are phones so strong?” She was in a clinic parking lot, watching her phone hold 5G, and wondering why she should spend money on anything else. My answer back was: strong in a parking lot, sure. But your nurses aren’t doing patient visits in a parking lot.
When a vehicle moves, the modem needs to hold a session across tower handoffs, survive brief coverage gaps, and manage heat and power dips. A consumer phone is designed to be excellent at many things. A router like the LX40 Sierra Wireless is designed to be excellent at one thing: staying connected. In a mobile clinic, that distinction decides whether a nurse can transmit a blood pressure cuff reading from the van or has to call the office and re-explain the visit.
The same logic applies to an ambulance, a service van, or a utility truck. If losing the connection means a delayed appointment, a missed update, or a public-facing service failure, the premium router is not the cost problem. The failed visit is the cost problem. To be fair, I have seen operations teams run successfully with a phone and external antenna for a while. But the moment the service is public-facing, quality becomes part of your brand, and that is a bad area to save money.
Scenario 2: Fixed Sites with Wired Internet
If the “vehicle” is parked for months, or you already have a stable wired connection, a 5G router is usually backup, not mission-critical. In that world, buying the most rugged model in the catalog is overkill. A lower-cost Sierra Wireless LTE router—or, if business needs are modest, a quality hotspot with a real data plan—can provide the same failover for a fraction of the cost.
To be clear, you still want the connection to be reliable. But the risk is measured in minutes, not in failed field visits. If the wired circuit drops at 3 a.m. and reboots by 3:20 a.m., nobody feels it. Paying extra to turn that twenty-minute blip into a two-minute blip only makes financial sense when those extra minutes have real consequences. Granted, there is a benefit to standardizing on one router model across your fleet. In that case, buy the LX40 for vehicles and pick a simpler—and cheaper—unit for fixed sites. Don’t let standardizing become an excuse to over-spec everything.
Scenario 3: Tiny Sensor Payloads
Not everything needs a router. If your product is a connected blood pressure monitor in a health kiosk, or a tank sensor that sends one reading per hour, an embedded cellular module is often the smarter buy. A Sierra Wireless module becomes part of the device itself: no external box, no separate power supply, no extra configuration. That’s not just cheaper hardware—it’s lower operational overhead over the device’s life.
This is usually an engineering decision, not a procurement decision. If you have developers, have a conversation about integration. If you don’t, a small router or gateway is acceptable—but recognize you are paying a convenience premium. You’re also adding one more device to secure, power, and troubleshoot. For a 500-endpoint deployment, the right answer matters more than for a five-device pilot.
Scenario 4: A Short-Term Pilot
If you are testing a service idea for less than ninety days, the frugal answer is: use what you have. A phone hotspot is okay when the stakes are “we are learning whether this works.” But pilots need an expiration date. I’ve seen hotspots become “production” by accident because nobody made the call to replace them. The most frustrating part is that nobody intends it. You’d think a pilot end date would be obvious—but the date passes, and the hotspot is already in the van.
So my advice for pilots: set a hard date. On that date, either kill the idea or move to equipment that meets your production requirements. That transition is where quality stops being theoretical. Clients don’t see your cost tracking. They see whether the data uploads, whether the video call is stable, whether their appointment starts on time. That visible reliability is your brand, and it’s a legitimate line item in any budget.
How to Identify Your Situation
- What does one failed connection cost? If it is an inconvenience, you are in scenario 2 or 4. If it delays a clinician, breaks a service, or costs a customer, treat it as scenario 1.
- Does the device move? Movement changes antenna design, power requirements, and handover behavior. Moving devices deserve vehicle-grade hardware.
- How many things are behind the connection? One sensor can use a module. A vehicle full of laptops, tablets, and medical devices needs a router.
Still uncertain? Do the test I recommend to Jackie before she bought the LX40: take a 5G phone and a Sierra Wireless 5G router—or the router you’re weighing—drive the same route for an hour, and see how many sessions drop. Per FTC guidelines (ftc.gov), a marketing claim about performance needs evidence. Your drive test is better evidence than a sales sheet.
I should add that my experience is mostly North American fleets. If you are deploying internationally or using spectrum I haven’t worked with, ask an engineer to verify bands and certifications. The decision looks different when you carry a device across borders.
Jackie went with the LX40. It wasn’t because I persuaded her—it was because the pilot did. After watching hotspot sessions fail during a real route, she stopped asking whether she could afford a router and started asking where to put them. She still jokes that the question “why are phones so strong” is a parking-lot question. The road is where you find out.
Bottom line: you are not buying a router. You are buying confidence that the job completes. Price that confidence first, and the hardware decision gets easier.