The Mobility and IoT Buying Guide: How to Buy Corporate Wireless, Device Management, and IoT Connectivity

Corporate wireless is the technology purchase that nobody remembers making. It arrived one line at a time, through hires and device swaps and a field team that needed tablets, and it is now a monthly invoice that runs to dozens of pages and that nobody reads past the total. IoT then adds a second population of connections, sensors and trackers and kiosks and vehicles, on their own carriers and their own contracts, growing the same way.

The result is a category most companies buy every few years under time pressure, usually when a carrier agreement is expiring or a bill has finally become impossible to ignore. This guide is the evaluation we run when we advise on mobility and IoT, written out so you can run it with an advisor or entirely on your own.

The inventory is the leverage

Every other step in this guide depends on one document most companies do not have: a current inventory of every line and device, who holds it, and what it actually uses. Carriers reprice generously for buyers who arrive with clean data and a credible alternative, and politely for everyone else, so the audit is not preparation for the purchase. It is the purchase's first and most valuable step.

Build it from the last three invoices, not from the HR roster. The invoices show the lines that exist. The roster shows the people who should have them, and the gap between the two lists is the money. Expect to find lines assigned to departed employees, devices retired but never disconnected, tablets bought for a project that ended, and plan features nobody enabled. The zero-use and near-zero-use population alone is often large enough to fund the management layer this guide recommends later, before any rate changes at all.

Classify what remains by how it is used: heavy data users, voice-and-email users, field devices, international travelers, and machines. Each class wants a different plan structure, and the comparison you run later only works if the usage profile you hand each supplier is real. If the inventory has to stay current after the purchase, that is the job of expense and asset management tooling, and it belongs in the same program.

Three purchases hiding in one invoice

The mobility line item is actually three different products, and the buying process goes wrong when they are treated as one.

• Airtime. The carrier agreement: voice, messaging, data, roaming, and the pooled structure that holds them. This is the commodity, and it is where most of the invoice sits.
• Lifecycle. Procurement, staging, enrollment in a device management platform, repairs, replacements, and recovery when someone leaves. By default nobody owns this layer, which is how inventories rot.
• Machines. IoT connectivity for devices that are not phones: different data profiles, different tooling, and different contract lengths.

Decide deliberately which of the three you are buying, from whom, and whether they should come together. A carrier will happily sell all three, and sometimes that is the right answer, but the lifecycle layer and the IoT layer both have specialists who beat a repurposed phone plan on every axis that matters for their piece. Sourcing the three as one program with clear ownership at each seam is the goal. Buying them as one undifferentiated contract is the mistake.

Test coverage where you operate, not on the map

Coverage maps describe the network on a good day. The signal that matters is the one inside your warehouse, along the rural delivery route, in the basement of the clinic, and at the job site that moves every month. Before any proposal is scored, test the real sites with real devices on each finalist's network, and have the field team do it, because they know where the calls drop.

For IoT, coverage has a second dimension: the network technology itself. Sensors and trackers frequently use low-power network types that not every carrier supports in every place, and the devices will live for years. Ask each supplier, in writing, which technologies are supported where your devices will be, and what the plan is when a network generation is retired. Companies that deployed on the wrong technology learned that lesson during the 3G shutdowns, when working hardware went dark on a schedule set by someone else.

Pooled structures and the boundary

Business plans price per line against a shared pool of data, and the pool is what separates a good agreement from a bad one. Pooling absorbs individual variance, so the heavy user and the light user average out and the overage charges that dominate unmanaged accounts mostly disappear.

The questions live at the pool boundary. What happens when the pool is exhausted: overage at what rate, throttling to what speed, or an automatic step-up to a larger tier that never steps back down. How lines enter and leave the pool mid-term, and what each movement costs. Whether unlimited means unlimited, or whether it carries a threshold after which traffic is deprioritized, a distinction that matters a great deal to field devices at month end.

International use deserves its own line in the evaluation. Roaming for traveling staff should be a defined plan feature with a known cost, not a surprise on the invoice, and the right structure depends on whether you have three occasional travelers or a team that lives on planes.

Management is the product, airtime is the commodity

The carrier sells minutes and megabytes. The program needs lifecycle, and the lifecycle is where the operational risk sits. An unmanaged corporate phone that walks out the door takes its mailbox, its files, and its authenticator with it, and offboarding that depends on someone remembering to call the carrier is not a control.

Two layers are available. A mobile device management platform (MDM) gives you enrollment, policy, remote wipe, and an inventory that updates itself. Managed mobility services go further and take the whole lifecycle, procurement through recovery, for a per-device monthly fee. The first is close to mandatory for any company with corporate devices. The second earns its keep when the IT time spent on phones is real money, typically from a few hundred devices upward, or sooner when devices are mission-critical in the field.

Whichever you choose, ask for evidence rather than assurances. Every departure should trigger line suspension and device recovery within days, and the platform or provider should be able to show you that it happened, in a report, without anyone asking.

IoT is a different purchase

IoT connectivity looks like a phone plan on the invoice and behaves like infrastructure in practice. The economics are inverted: tiny data per device, enormous device counts, and hardware that will be in the field for five to ten years. Buying it on repurposed phone plans overpays per megabyte and underdelivers on everything else.

Evaluate IoT suppliers on the things that distinguish the category. Bulk provisioning and per-device visibility, because a thousand SIMs cannot be managed one at a time. Multi-carrier or roaming-capable coverage where devices move, including embedded SIM options that let a device switch networks without a truck roll. Data tiers matched to device behavior rather than to a phone user. And contract terms that respect device lifetimes: rate protection, sunset commitments, and the ability to add devices at the same terms as the deployment scales.

The pilot is where IoT purchases are most often mispriced. Pilot pricing for fifty devices is a marketing decision. Production pricing for five thousand is the real contract. Get the production price schedule, the volume steps, and the platform fees in writing before the pilot starts, so that scaling is a decision you make on known numbers rather than a conversation from a weak position.

Contract terms that decide the next three years

Mobility contracts are easy to sign and expensive to leave, because the term is usually anchored to device financing and the lines are the business's phone numbers. Three sets of terms deserve attention while alternatives still exist.

Rate protection and plan retirement. Carriers retire plans and introduce new ones on their own schedule. The contract should say what happens to your rate when your plan is retired mid-term, and whether the replacement can cost more.

Line flexibility. What it costs to add, suspend, and remove lines mid-term, and whether dropping below a line-count threshold changes the pricing of the lines that remain. Companies that grow and shrink with the season need the answer before they sign, not after the first reduction in force.

Devices and the exit. Device subsidies and financing are frequently what tie you to the term, and early termination is priced per line. Know the total exposure on day one, get the buyout schedule in writing, and confirm what happens to device balances at renewal. The renewal playbook applies here with full force: the carrier's renewal offer arrives with a clock attached, and the company that starts the evaluation six months early is the one that gets the market rate.

Compare quotes on total program cost

Mobility quotes resist comparison because each supplier bundles differently: one wraps device costs into the monthly rate, another shows them separately, a third includes management tooling the others price as an add-on. Comparing per-line headline rates tells you how each document was formatted, not which program costs less.

Normalize every proposal to one number: total program cost over the term, per line per month, including airtime, device costs and financing, management fees, activation and change fees, and modeled overage exposure using your actual usage classes. Then run the same usage profile through each supplier's pooled structure, because the winner at a hundred lines can be the loser at four hundred. The quote comparison method works for this category as written. The only mobility-specific addition is that device economics belong inside the total, never beside it.

Red flags worth slowing down for

• A proposal arrives before anyone has asked for your invoices or your usage by class.
• The quote is a per-line rate with no pool size, no boundary terms, and no definition of unlimited.
• Nobody can say what happens to your rate when the plan you are buying is retired.
• The offboarding process is described as a phone call to the account team.
• IoT devices are quoted on phone plans, or pilot pricing is offered with no production schedule.
• Device financing terms sit in a separate document from the service agreement, and the two do not end on the same date.

Where an advisor fits

All of the above is runnable on your own, and this guide exists to make that practical. What an advisor adds is the market work that a company shopping this category every few years cannot do from the inside: we help you build the inventory and the usage classes, then run carriers, managed mobility providers, and IoT connectivity specialists across the whole market against them. You get 3 to 5 recommended suppliers with our reasoning on each, quotes normalized into comparable total program costs, and contract terms benchmarked against what companies like yours actually sign. It costs you nothing, we have no stake in which supplier wins, and you sign directly with the one you choose.

If an expiring carrier agreement, a field team that has outgrown its plans, or an IoT deployment moving from pilot to production has put this purchase on your list, a thirty-minute conversation before the renewal offer lands will save you from buying three years of the wrong structure by default.