A connected device earns nothing on the day you ship it. It earns over years, in small increments, every time it reports back and something useful happens because of that report. The connectivity that carries those reports is a monthly cost that runs for the life of the device. So the honest question is not “what does a SIM cost.” It is whether the value the fleet produces over its life clears the total connectivity cost over that same life, with margin to spare. That is IoT connectivity ROI, and most buyers never actually calculate it.
The scale of the decision is growing. Analysts who track the connected-device market expect the global installed base to keep climbing, from 21 billion devices at the end of 2025 toward 48 billion by 2035, per a widely cited forecast that puts the ten-year growth at a compound annual rate of about 9%. Every one of those devices needs connectivity, and every connectivity contract locks in a recurring cost that compounds across the fleet and across the years. Get the ROI of IoT connectivity wrong at ten devices and you lose pocket change. Get it wrong at ten thousand and it shows up in the annual accounts.
This guide gives you the formula first, then the full cost side, then the value side, then the pricing models that move the number, then a worked example with illustrative figures, and finally how to judge a provider on value instead of sticker price. The numbers in the example are made up to show the method. They are not Trafalgar Wireless prices, and no provider’s real quote is in here.
IoT connectivity ROI, defined (start with the formula)
IoT connectivity ROI is the net value a connected-device deployment produces divided by what the connectivity costs, measured over a defined time horizon. In plain arithmetic:
IoT connectivity ROI = (value gained minus total connectivity cost) divided by total connectivity cost, over a set period.
Express it as a percentage. A result of 0% means you broke even. A result of 200% means the deployment returned three dollars of value for every dollar of connectivity cost over the horizon you chose. The horizon matters as much as the ratio, so always state it: ROI over one year and ROI over a five-year device life are different questions, and connectivity is a five-year kind of cost.
A few companion terms make the formula usable.
Total cost of ownership (TCO) for IoT connectivity is every cost tied to keeping devices connected across their life, not just the headline data rate. It includes the data plan, the SIM hardware, activation, platform and management fees, any overage or roaming charges, the staff time to run it, and the cost of retiring devices at the end. TCO for IoT connectivity is the denominator in the ROI math, and it is almost always larger than the line item people budget for.
Cost per connected device per month is TCO divided by the number of active devices divided by the number of months. It is the single most useful normalizing unit in this whole exercise, because it lets you compare a two-device pilot against a two-thousand-device rollout, and one provider’s quote against another’s, on the same footing.
Payback period is how long the deployment takes to return its cumulative connectivity cost in value. If a fleet produces $400 of value per device per year and connectivity costs $120 per device per year, the device pays back its connectivity in roughly four months and then runs in the black. Short payback periods de-risk the whole program.
Hold those four ideas together and the value of connected devices stops being a slogan and becomes a spreadsheet you can defend.
The full cost side: what TCO of IoT connectivity actually includes
Most connectivity budgets are wrong in the same direction. They count the data and forget the rest. Here is the fuller list of what belongs in total cost of ownership for IoT connectivity, so the denominator in your ROI is real.
- Data plans: the recurring charge for the megabytes or gigabytes your devices move, billed per device, pooled across the fleet, or per megabyte. This is the line everyone sees and the only line many people count.
- SIM or eSIM hardware: the physical cards or embedded modules, plus any premium for industrial-grade or long-life parts. A rugged SIM built to run for well over a decade costs more up front and saves a fortune in devices you never have to open again.
- Activation and provisioning: the cost to bring a SIM live and load it with the right profile. With some vendors this is a separate charge. With others it is included, which changes the per-device math.
- Platform and management fees: the cost of the software you use to see usage, set alerts, and activate or suspend SIMs. Some providers bill separately for portal access and API calls. Those fees belong in the IoT connectivity cost even though they do not feel like connectivity.
- Overage and roaming: the charges that fire when a device exceeds its plan or crosses a border onto a partner network. Overage is the single most volatile line in many bills, and it is where the difference between a pooled plan and a per-device plan gets expensive.
- Staff time and support overhead: the hours your team spends chasing a silent device, reconciling a confusing invoice, or waiting in a carrier support queue. This cost is invisible on the bill and often the largest real number in the whole TCO.
- Field visits: the cost of physically touching a device to swap a SIM, reset a modem, or diagnose a connection. A truck sent to a device is one of the most expensive things a connected-device operator does, and connectivity choices drive how often it happens.
- Decommissioning: suspending and closing out SIMs when devices retire, and making sure you stop paying for connectivity on hardware that is in a landfill.
Notice how few of these are the data rate. When Trafalgar Wireless talks with IoT solution providers and growth businesses about IoT connectivity cost, the recurring pattern is that the cheapest per-megabyte quote often carries the highest total cost of ownership, because the savings on data get eaten by portal fees, overage, and support hours. The sticker price and the TCO are different numbers, and only one of them belongs in your ROI.
The value side: how to quantify the benefit of connected devices
The numerator is harder than the denominator, because value shows up in a dozen places and rarely as a single invoice. Four drivers cover most of it. Assign a dollar figure to each that you can defend, even if it is an estimate, and the value of connected devices becomes a number you can put next to the cost.
Downtime avoided. A device that loses connectivity stops earning and often starts costing. A dashcam that cannot upload is not protecting the fleet. A payment terminal offline is a sale not made. Estimate the revenue or protection lost per hour of downtime, multiply by the hours of downtime a more reliable connection prevents, and you have a value line. Multi-network coverage that fails over to a stronger signal instead of dropping is worth exactly this number, which is why reliability is an ROI argument and not just a technical spec.
Field visits reduced. Every truck roll you avoid is labor, travel, and time you keep. Remote provisioning, over-the-air profile changes, and connectivity that simply stays up mean fewer devices need a human in front of them. Multiply your fully loaded cost of a field visit by the number of visits avoided per year, and this is often the biggest single value line in the whole model. It is also the clearest place where better connectivity pays for itself.
Predictive maintenance. Connected devices that report their own health let you fix things before they fail. Catching a failing sensor or a degrading battery early avoids the cost of an emergency repair, an unplanned outage, and the knock-on damage. Estimate the failures caught early per year and the cost of each failure prevented. This is where the ROI of IoT connectivity crosses over from cost control into genuine operational advantage.
New revenue. The connection can open up things you can now charge for: a usage-based service tier, a safety feature that wins a contract, a data feed a customer will pay for. This is the hardest line to estimate and often the largest. Our biggest customer, SureCam, builds network-connected dashcams that cut insurance-claim costs for fleets, and reliable multi-network connectivity is what lets that product exist and scale. When connectivity is what makes the product sellable, its value is a share of the revenue the product earns, not the cost of the data it moves.
Add the four together for the horizon you chose, subtract the TCO, divide by the TCO, and you have the ROI. The exercise is only as honest as the estimates, so write down your assumptions and keep them conservative.
Pricing models and how they change your IoT connectivity ROI
The pricing model you pick is not a billing detail. It is one of the biggest levers on the ROI of IoT connectivity, because it decides how your cost behaves as the fleet grows and as usage swings. Three models cover most of the market.
Pooled or shared data. The fleet draws from one shared data allowance instead of a fixed allotment per device. A device that uses very little subsidizes one that spikes, and the plan as a whole absorbs the variance. The Dynamic IoT Data Plans that Trafalgar Wireless offers to IoT solution providers work this way, with data shared across devices and no overage charges when one device runs hot. Pooled plans win when your fleet has uneven or unpredictable usage, which is most fleets, because they turn a lot of scary overage risk into one predictable monthly number.
Per-device. Each device gets its own fixed plan. This is simple to reason about and can be cheapest when every device uses a known, steady amount of data. It gets expensive fast when usage varies, because you either over-provision every device to be safe or you eat overage on the ones that spike. Per-device pricing suits predictable, uniform fleets and punishes variable ones.
Pay as you use. You pay per megabyte actually consumed, plus a fixed monthly fee per SIM. Trafalgar Wireless offers Pay As You Use plans for growth businesses and asset-tracking operators whose devices send very little, very occasionally, so they are not paying for data they never touch. This model is cheapest for low, sporadic usage and dangerous for anything that might suddenly move a lot of data, since the meter runs with no ceiling.
One more factor sits underneath all three: the fees that are not the data. A model that looks cheap per megabyte can carry separate charges for portal access, APIs, activation, and suspension, and those turn a low quote into a high total cost of ownership. Trafalgar Wireless folds portal access, APIs, activation, and suspension into the plan rather than billing them separately, and keeps a one-month minimum instead of a long lock-in, which is the kind of detail that decides the real IoT connectivity cost long after the headline rate is forgotten. A connectivity management platform that shows usage and fires alerts before a device blows through its plan is part of the pricing model too, because visibility is what stops overage before it becomes a bill.
A worked ROI example (illustrative numbers only)
Here is the method end to end. Every figure below is invented to show how the math works. None of it is a Trafalgar Wireless quote, and your real numbers will differ.
Suppose you run a fleet of 1,000 connected asset trackers over a five-year device life. You are choosing between two connectivity approaches and want to compare them on IoT connectivity ROI, not on the per-megabyte rate.
Start with the cost side, per device per month, as illustrative assumptions:
- Data plan: $2.00 per device per month on a pooled plan sized for the fleet’s real average usage.
- SIM hardware, amortized: a $5 industrial SIM spread over the 60-month life is about $0.08 per device per month.
- Platform and management: $0.00, because in this example portal access, APIs, activation, and suspension are included in the plan rather than billed separately.
- Overage: budgeted at $0.00, because the pooled plan absorbs the spikes instead of charging per device.
- Support and field visits: assume reliable connectivity holds avoidable truck rolls to one visit per 20 devices per year, at a fully loaded $150 per visit. That is $7.50 per device per year, or about $0.63 per device per month.
Total illustrative TCO: roughly $2.71 per device per month, or about $32.52 per device per year. Across 1,000 devices for five years, that is roughly $162,600 in total connectivity cost.
Now the value side, again as illustrative assumptions, per device per year:
- Downtime avoided: more reliable coverage prevents an estimated $30 per device per year in lost billable uptime.
- Field visits reduced: better connectivity avoids roughly one extra truck roll per 10 devices per year versus the alternative, worth about $15 per device per year.
- Predictive maintenance: early fault detection saves an estimated $20 per device per year in emergency repairs and outages.
- New revenue: a connectivity-enabled service tier adds an estimated $25 per device per year in margin.
Total illustrative value: $90 per device per year, or $90,000 across the fleet per year, or $450,000 over five years.
Plug it into the formula: ROI equals ($450,000 minus $162,600) divided by $162,600, which is about 177% over the five-year horizon. The payback period is roughly the point where cumulative value ($90,000 per year) clears cumulative cost ($32,520 per year), so the deployment pays back its connectivity in well under the first year and runs in the black after that.
Change one input and watch it move. If the “cheaper” alternative shaves the data rate to $1.50 but adds a $0.50 portal fee, a $0.75 per-device overage average, and one more truck roll per 20 devices, its TCO climbs above the pooled plan even though its sticker price is lower. That is the entire point of measuring IoT connectivity ROI instead of comparing per-megabyte rates: the lowest quote and the lowest total cost of ownership are frequently not the same option.
How to evaluate a provider on ROI, not just price
In the conversations we have with buyers, the pattern is almost always the same. They reach out to three or four providers, and the first thing they ask for is the price. There is very little time for discovery, and the whole thing collapses into a like-for-like comparison on the data rate, a price beauty contest. It is an understandable instinct and a costly one, because it optimizes the smallest line in the TCO and ignores the largest.
If you want the real ROI of IoT connectivity, evaluate a provider on the things that move total cost of ownership and value, not just the rate:
- Ask what is not in the quote. Get portal fees, API fees, activation, suspension, and overage in writing. The included-versus-extra split changes the cost per connected device more than the headline rate does.
- Model the overage risk. Ask how the plan behaves when a device or the fleet exceeds its allowance. A pooled plan with no overage charge and a per-device plan with steep overage can start at the same price and end thousands of dollars apart.
- Price the support. Ask who answers when a device goes dark, how fast, and whether your account manager is also your service manager. Support overhead is a real TCO line, and slow or generalist support is where cheap connectivity gets expensive. It is worth remembering that most connectivity providers do roughly the same technical thing, and many work hard to look unique when they are not, so the wrapper around the data, the billing model, the visibility, and the support, is usually where the ROI difference actually lives.
- Check coverage against your real routes. Reliability is a value line, so a provider with access to more networks where your devices actually operate, such as 500+ networks in 180+ countries, protects the downtime-avoided number in your ROI.
- Test before you pay. A free-data pre-activation window that lets you prove connectivity on your own devices before billing starts de-risks the whole model, because it turns assumptions into measured usage before you commit.
Run the same TCO and value model against each provider, express it as cost per connected device per month and as ROI over your device life, and the winner is usually not the cheapest quote. It is the option with the lowest total cost of ownership for IoT connectivity and the highest defensible value.
Frequently asked questions
How do you calculate IoT connectivity ROI?
Take the value the deployment produces over a set period, subtract the total connectivity cost over that same period, and divide the result by that total cost. Express it as a percentage, and always state the time horizon, because ROI over one year and over a five-year device life are very different numbers.
What is a typical cost per connected device per month?
It varies too widely to quote a single figure honestly, because it depends on data volume, region, pricing model, and the fees a provider does or does not include. The useful move is to compute your own: take the full total cost of ownership, including platform fees, overage, and support, then divide by active devices and by months. Compare providers on that number, not on the data rate alone.
What counts as a good payback period for an IoT deployment?
Shorter is better, and many well-scoped deployments recover their connectivity cost within the first year. The levers that shorten it are avoided field visits, reduced downtime, and any new revenue the connection creates. If the payback period runs past the device’s useful life, the ROI of IoT connectivity is negative and the model needs rework.
Which pricing model gives the best IoT connectivity ROI?
It depends on your usage profile. Pooled or shared data plans usually win for fleets with variable or unpredictable usage because they absorb spikes with no overage. Per-device plans can be cheapest for uniform, predictable fleets. Pay as you use fits devices that send very little, very occasionally. Match the model to the fleet, and watch the non-data fees, which often decide the total cost of ownership.
Why does the cheapest quote often have the worst ROI?
Because the data rate is a small part of the total cost of ownership. A low per-megabyte quote can carry separate portal, API, activation, and overage charges, plus weaker support that drives up staff time and field visits. Those hidden lines frequently push the cheapest sticker price to the highest IoT connectivity cost over the life of the fleet.
Key takeaways
- Measure ROI, not rate. IoT connectivity ROI is (value gained minus total connectivity cost) divided by total connectivity cost over a set horizon. The per-megabyte price is one small input, not the answer.
- Count the whole TCO. Total cost of ownership for IoT connectivity includes data, SIM hardware, activation, platform fees, overage, support overhead, field visits, and decommissioning. The lines that are not the data rate usually dominate.
- Normalize on cost per connected device per month. It is the one unit that lets you compare a pilot against a rollout and one provider against another on equal footing.
- Quantify the value side. Downtime avoided, field visits reduced, predictive maintenance, and new revenue are the four drivers that make the value of connected devices a defensible number.
- The pricing model is a lever. Pooled data suits variable fleets, per-device suits uniform ones, and pay as you use suits low sporadic usage. Included fees and no-overage terms move the ROI more than the headline rate.
- Evaluate providers on value. Ask what is excluded from the quote, model the overage risk, price the support, and test before you pay. The lowest quote and the lowest total cost of ownership are often not the same option.
Conclusion
The reason IoT connectivity ROI gets skipped is that the sticker price is easy and the total cost of ownership is work. But the work is where the money is. A connected fleet is a five-year commitment, and the connection carrying it is a recurring cost that either compounds against you through overage, hidden fees, and truck rolls, or quietly pays for itself through uptime, fewer field visits, and new revenue. The formula does not care about marketing claims. It cares about the value your devices produce and the total cost of keeping them connected, and it will tell you plainly which provider actually wins.
If you want to run these numbers against real plans, Trafalgar Wireless helps IoT solution providers and fleet and asset-tracking operators turn IoT connectivity ROI into a decision, with pooled and pay-as-you-use IoT data plans, usage visibility, and concierge support built to lower the total cost of a connected fleet. Map its multi-network data plans and the SureCam connectivity story to the cost and value lines in your own model, then compare on total cost of ownership rather than the rate alone.
