The Total Cost of an IoT Deployment: What to Budget Beyond the Devices
November 11, 2026 · 5 min read · Etzal Group Team
A proposal for two hundred sensors arrives, and attention goes straight to the unit price. Three years later the organisation finds that it has spent more on technicians' travel, SIM cards and software subscriptions than it ever did on the devices. Understanding the total cost of an IoT deployment before signing changes which design you choose.
A five-year view is a practical horizon. It covers most battery lives, at least one round of calibration and the period over which a business case is usually judged.
One-time costs
Devices. Sensors, gateways, enclosures, mounting hardware, antennas, power supplies or solar kits. Include spares, typically five to ten percent.
Installation. Labour, travel, access equipment, cabling and conduit, electrical work and permits. At sites that are high, remote or hazardous, installing a sensor can cost several times the sensor itself.
Commissioning. Configuring each device, checking readings against a reference, labelling and documenting. This is the step that is most often underestimated.
Integration. Connecting to existing controllers or business systems, mapping data points and setting up dashboards, alerts and user accounts.
Project work. Site surveys, design, coverage testing, project management and training.
Recurring costs
Connectivity. SIM subscriptions and data charges, or the upkeep of your own gateways and network. Multiply by the number of connections and by sixty months.
Platform. Subscription or hosting, storage that grows with history, and fees per device or per message.
Maintenance. Site visits to clean, repair and replace. The cost per visit, more than the cost per part, drives this line.
Batteries. Replacement cells and the labour to fit them. Battery life depends on reporting frequency, signal quality and temperature.
Calibration. Periodic checks, reference instruments and records, particularly in regulated settings.
Replacement. Devices fail and are damaged. Plan a yearly percentage.
Support and software. Security updates, platform changes, user support and the staff time to manage the fleet.
Monitoring the monitors. Someone has to notice when a device stops reporting.
A worked illustration
Suppose a deployment of 100 monitoring points. The figures below are placeholders to show the method. Use your own quotations.
- Devices and spares: 100 units of cost.
- Installation and commissioning: often comparable to the device cost, and more at difficult sites.
- Integration and project work: a fixed amount that does not scale down for small deployments.
- Connectivity over five years: a small monthly fee per point, times sixty.
- Platform over five years: a monthly fee, times sixty.
- Maintenance over five years: expected visits per year, times cost per visit, times five.
- Batteries, calibration and replacements over five years.
When organisations fill in this table with real numbers, the recurring lines frequently add up to more than the one-time lines. That is the insight worth having before the purchase order.
Design choices that move the total
Reporting interval. Sending every minute where every fifteen minutes would do multiplies data charges and shortens battery life.
Power. Mains power removes battery visits. Where it is unavailable, a larger battery or a solar kit may cost less over five years than repeated replacement trips.
Connectivity type. One gateway serving fifty low-power sensors can be cheaper than fifty cellular subscriptions, if the sensors are within range. For scattered single points, cellular is simpler.
Remote management. Devices that can be configured, updated and diagnosed remotely avoid visits. This feature is worth paying for.
Standardisation. A few device models mean fewer spares, simpler training and faster repairs.
Robustness. A sensor with the right protection rating costs more and avoids the replacement visit a cheaper one will need.
Scope. Every measuring point that informs no decision is pure cost. Remove it.
The costs of not doing it
Set the total against what it prevents: product lost in a cold room, a pump destroyed by dry running, energy wasted overnight, unnecessary routine visits, penalties for missed compliance records. Estimate these from past incidents. A deployment is justified when the avoided losses and savings exceed the five-year total with margin.
Questions for suppliers
- What is included in the price, and what is not?
- What are the monthly charges per device, and how do they change with volume?
- What battery life do you expect at our reporting interval and signal conditions?
- Can devices be updated and diagnosed remotely?
- What is the warranty, and what does a replacement cost afterwards?
- Who owns the data, and can we export it?
- What happens to the devices and data if we end the contract?
Start with a pilot that measures cost
A pilot is usually run to prove that the technology works. Use it also to measure the cost: actual installation time per point, visits needed in the first months, real data consumption and failure rate. These numbers replace assumptions in the five-year model.
We prepare five-year cost models as part of the design stage of our IoT and Control projects, so that the choice of devices and connectivity is made on the full figure. If you have a quotation that lists only hardware, send it to us and we will point out what else to budget.
Summary
Budget for installation, commissioning, integration, connectivity, platform, maintenance, batteries, calibration and replacement, not only for devices. Model five years. Reduce the total by measuring less, reporting only as often as needed, managing devices remotely and standardising hardware. Compare the result with the losses the system prevents.
Frequently asked questions
What is usually the largest cost in an IoT project?
Over several years it is rarely the sensors. Installation labour at the start and maintenance, connectivity and platform fees afterwards commonly exceed the hardware. Sites that are remote or hard to access raise the share of labour further.
How can we lower the cost of an IoT deployment?
Measure only what leads to a decision, choose devices that can be updated and diagnosed remotely, standardise on a few hardware models, and match the reporting interval to the need. Each of these reduces site visits or data charges, which are the costs that keep recurring.
Should we buy the hardware or pay for monitoring as a service?
Buying suits organisations with their own technical staff and long-lived sites. A service model spreads the cost and moves maintenance to the provider. Compare the five-year totals of both, and check who owns the data and what happens to the devices if the contract ends.
Related service
WhatsApp AI Chatbot
We build, train, and run a WhatsApp AI agent that answers customers 24/7, qualifies leads, and follows up.
