Search for “IoT device cost” and you will find pages about app development budgets. Useful if you are building an app. Useless if you are building a device, because the costs that sink hardware programmes are not in the software column. They are in the seven layers below, and most first-time hardware budgets capture only the first one.

The figures below are representative planning ranges for a typical connected product, a cellular or LPWAN sensor or controller class device, drawn from the engagements we see. Your numbers will differ; the structure will not. (For a per-unit estimate against your own inputs, the IoT Device Cost Calculator runs this model interactively.)

Layer 1, The BOM (The Only Cost Everyone Budgets)

The bill of materials is the visible cost, and even it misleads, because the prototype BOM and the production BOM are different numbers in both directions. Dev-kit modules and connectorised assemblies inflate the prototype; at production volume, chip-down integration and negotiated pricing typically cut the electronics cost substantially, while everything the prototype ignored (enclosure, gaskets, fasteners, cables, packaging, labels) climbs back in. A realistic production BOM for a mid-complexity connected device commonly lands in the €15–60 range at volume; the prototype that preceded it cost €100–400 per unit. Neither number predicts the other without doing the work, which is the entire subject of Why Your $50 Prototype Will Cost $500k to Manufacture.

Layer 2, Engineering NRE

Taking a validated concept through EVT, DVT, and PVT is the largest single line for most programmes: hardware design and board spins, firmware including an OTA path designed for the product’s lifetime, mechanical design, and test development. For a mid-complexity device, total engineering NRE typically runs €150K–500K whether spent on internal salaries, a consultancy, or both. Two or three board spins are normal; budgeting for one is the classic first-programme error.

Layer 3, Tooling

Injection-mould tooling for a two-to-four-part enclosure commonly runs €20K–120K depending on part complexity, steel class, and cavitation, and a mould is a one-way door: enclosure changes after tooling are either five-figure rework or a new tool. Add test fixtures and programming/provisioning stations for the line (€10K–50K). Tooling is the step function that makes the stage-gate cadence non-negotiable.

Layer 4, Certification and Compliance

The regulatory layer most budgets undercount. CE with the RED cybersecurity delegated act, EMC, and safety testing for a wireless product typically runs €15K–50K through a test house, per major variant, per significant revision. Add FCC for North America. Cellular devices add module-dependent carrier and PTCRB/GCF costs that can multiply the line.  And from 2026 onward the engineering side of compliance, CRA vulnerability handling, SBOM, ESPR/DPP data, is a real workstream with real hours, not a folder of certificates.

Layer 5, Manufacturing Ramp

Between PVT and stable mass production sits a cost nobody itemises: pilot runs, first-article inspections, early yield loss, line-rework, and the engineering hours spent at the CM resolving issues that only appear at quantity. A planning allowance of 5–15% of first-year production cost is realistic; zero is not.

Layer 6, The Per-Device Operating Cost

Hardware margin models break when the device costs money every month it is alive. Cellular data plans, LPWAN network fees, cloud ingestion and storage, and push/messaging infrastructure typically total €0.20–2.00 per device per month depending on radio and data profile. Multiply by fleet size and a 7–10 year service life and this line frequently exceeds the entire BOM, which is why connectivity architecture is a finance decision wearing an engineering costume.

Layer 7, The Tail: Field Failures and the 10-Year Commitment

The layer that separates experienced hardware companies from first-timers. An RMA reserve (1–3% of shipped units, fully loaded with logistics and replacement cost). Truck rolls for devices that cannot be recovered remotely, €100–300 per incident, which is the financial argument for ogetting OTA right. And the long tail the EU has now made mandatory rather than optional: spare-parts inventory, a staffed firmware-security function for the declared support period, and recertification when components go end-of-life. Across 7–10 years, the tail commonly totals 30–60% of the original programme cost, committed on the day you ship.

What the Stack Adds Up To

For a representative mid-complexity connected device at, say, 10,000 units:

Layer	Representative range
Engineering NRE	€150K–500K
Tooling & fixtures	€30K–170K
Certification	€20K–80K+
Ramp allowance	5–15% of year-one production
Production BOM	€15–60/unit
Connectivity & cloud	€0.20–2.00/unit/month
Field & support tail	30–60% of programme cost over life

The summary number that matters is not “what does the device cost to build” but what does one fielded device cost over its life, and on that metric, the BOM is routinely a third or less of the truth. Programmes priced on the BOM alone do not fail at launch. They fail in year two, when the layers they did not budget arrive on schedule.

---

🔍 Budgeting a hardware programme?

Better Devices team  pressure-test programme budgets against this structure, NRE, tooling, certification, OPEX, and the support tail, before the spend is committed, as a short fixed-scope review. Talk to an Embedded Architect →

---

Frequently Asked Questions

How much does it cost to build an IoT device in 2026? For a mid-complexity connected device, representative ranges are €150K–500K in engineering NRE, €30K–170K in tooling and fixtures, €20K–80K+ in certification, a production BOM of €15–60 per unit at volume, plus €0.20–2.00 per device per month in connectivity and cloud, and a field-support tail of 30–60% of programme cost over a 7–10 year life. Exact figures depend heavily on radio, volume, and regulatory scope.

Why is the production cost so different from the prototype cost? The prototype carries dev-kit and low-volume pricing the production design eliminates, while the production budget adds everything the prototype ignored: tooling, certification per variant, manufacturing ramp losses, and the long-term support commitment. The two numbers are connected only through the engineering work between them.

What is the most commonly underestimated cost layer? Two compete for the title: certification (which recurs per variant and per significant revision, and now includes CRA/ESPR engineering work) and the operating tail, connectivity OPEX plus RMA, spare parts, and the firmware-security function for the declared support period, which together frequently exceed the original BOM over the fleet’s life.

Does connectivity choice really change the economics? Substantially. At €0.20–2.00 per device per month across a fleet and a 7–10 year service life, the connectivity and cloud line routinely exceeds the entire hardware BOM, which makes radio and backend architecture one of the highest-leverage financial decisions in the programme.