Skip to content

Plain-language guides to iot development

Date

Monday, November 16, 2026

Posted by

Date

How to Calculate ROI for an IoT Project

iot roi calculation

Planning an IoT project and need a number your finance team will trust? A sound iot roi calculation totals three years of full cost, counts only measurable savings, then tests the payback. Skip any step and you’re guessing.

This guide sits inside our wider look at iot business strategy, so read it alongside the other planning steps there.

Item Value
Median payback period across 36 validated IoT deployments 12 months
Deployments that paid back within 12 months 72%
Median reduction in unplanned downtime 28%
Reduction in energy and consumables roughly 20%
Suggested cost window for the business case three years

The figures come from SumatoSoft’s survey of IoT deployments and TagoIO’s guide to IoT ROI. They can change, so check the sources before you rely on them.

The basic IoT ROI formula

At its simplest, ROI compares the value of what a project saves with what it costs. The TeepTrak downtime guide writes its model as ROI = (baseline × reduction × cost per hour) / investment cost.

That guide lists four variables behind the formula:

  • Baseline unplanned downtime, measured in hours per year.
  • Reduction achieved, as a percentage of that baseline.
  • Cost per hour of downtime.
  • Investment cost, fully loaded with change management and training.

Downtime is only one use case, but the logic carries over. Swap in your own baseline, your own expected improvement and your own cost per event.

Start with the full cost of ownership

The sensor is usually the cheapest part of the bill. The total cost of ownership covers everything you pay across the life of the deployment, and TagoIO’s ROI guide says to total all of it across three years, not one.

Break the cost into lines so nothing hides:

  • Hardware: sensors, gateways, edge devices, spares and early failures.
  • Integration: engineering time to connect devices, build dashboards and wire up alerts, often the biggest line in year one.
  • Connectivity: cellular or LoRaWAN access that recurs monthly for every device.
  • Platform and storage: the cloud layer that ingests and serves the data.
  • Operations: monitoring, firmware updates, answering alerts and replacing dead units.
  • Failure risk: a pilot that never scales still costs you the pilot.

Battery life matters too. Radiant’s asset tracking guide notes that, depending on the battery life of the trackers you select, you’ll want to factor in the cost of replacements.

The way a platform is billed changes your recurring lines, so compare iot pricing models before you lock in the multi-year total.

Separate hard savings from soft savings

On the benefit side, keep two columns and never mix them. Hard savings are numbers that visibly changed. TagoIO gives these examples:

  • Energy spend, where optimization commonly targets reductions in the range of ten to twenty percent of the monitored load, depending on your baseline.
  • Labor hours, such as truck rolls avoided multiplied by the loaded cost of each trip.
  • Product loss avoided, such as spoiled cold-chain loads you can count from history.
  • Unplanned downtime avoided, priced at the known cost of past failures.

Soft savings are real but harder to price: audit evidence, fewer safety incidents, faster decisions and customer trust. The same guide says they belong in the case, but not in the hard column, and they should never carry the ROI on their own.

Soft gains do show up in practice. In SumatoSoft’s study, 58% of respondents cited trust and transparency for clients and auditors.

iot roi calculation Financial charts
A calculator and printed bar charts lie beside a laptop.

How do you estimate payback and test it?

Payback is the point where cumulative hard savings cover cumulative cost. TagoIO says predictive maintenance and monitoring deployments often land somewhere in the twelve to eighteen month range, but it treats that as a sanity check rather than a target (source).

Before anyone signs, pressure-test the case with four questions:

  1. Is the baseline documented, or only remembered? Remembered baselines flatter every project.
  2. Does the case still work if savings come in at half?
  3. Who is responsible for acting on each alert?
  4. Does recurring cost grow faster than the savings as you scale?

The baseline question is where cases fall apart. TeepTrak warns that finance will discount an estimated number by 20-40%, and suggests a 14-day IoT-based baseline measurement before you build the case.

Present results as a range, with a conservative, an expected and an upside case. The same guide says a range-based presentation gets through finance review faster than a single-point optimistic claim.

What do real payback benchmarks look like?

Use published results as a cross-check on your own math. SumatoSoft reports that across 36 validated IoT deployments, 72% paid back within 12 months and 36% within 9 months.

The same study found that unplanned downtime fell by a median of 28%, with energy and consumables down by roughly 20%. Its dataset included only responses with specific, measurable results, so treat these as encouraging rather than guaranteed.

The study also points to what separates good outcomes from poor ones. Integration mattered most: 61% of companies named connecting IoT signals to existing systems and processes as the top enabler, and the top barrier was resistance to new practices on the ground at 56%.

When the IoT ROI does not add up

Some projects should not happen, and the math will say so if you let it. TagoIO says IoT rarely pays back when the monitored asset is low value, and that it never pays back when no one owns acting on the data.

Integration cost is mostly fixed, so it dominates a case built on a handful of cheap assets. Spread across many units, or across a few critical ones, it shrinks.

If several candidates fail these tests, a ranking method such as iot use case prioritization helps you decide which one deserves funding first.

Frequently asked questions

What is a good payback period for an IoT project?

Show answer

Your own numbers decide, not a benchmark. Some quick-win cases in SumatoSoft’s study, in healthcare infection control and construction quality inspection, broke even in roughly 4 months, but those are specific and not typical (SumatoSoft).

Should soft savings go into the ROI figure?

Show answer

List them separately as supporting evidence. If the project only works once you attach a generous value to agility or morale, the hard savings are too thin to justify it.

Why use a multi-year cost window?

Show answer

Connectivity, platform and operations costs keep recurring after launch. A short view hides them and makes payback look faster than it will be.

What if I have no baseline data?

Show answer

Collect it with sensors before you build the case. TeepTrak reports that most plants it works with find their measured baseline is 25-40% higher than their reported one (TeepTrak).