Move from business model to sensor, not the other way around.
- 01
Clarify who benefits, which problem is solved and who pays.
- 02
Describe the complete chain from device and connectivity to platform, business application and user.
- 03
Include lifecycle, support, connectivity, cloud, security and product maintenance in the economics.
Which decision or task improves with device data?
A dashboard is not a product. Customers pay for less downtime, faster service, proven quality or simpler work.
Define who uses the information, which decision follows and what happens without action.
- User and problem
- Current cost
- Action from data
- Measurable improvement
Who pays for what, once or repeatedly?
Connected products can strengthen a sale, reduce service cost or become a digital offer.
Recurring fees require recurring value; a service package may sometimes fit better.
- Product value
- Service agreement
- Usage-based model
- Internal efficiency
The solution does not end in the IoT platform.
Devices, connectivity and platforms only become useful when a process or application turns data into action.
Design backwards from the end user and include CRM, ERP, service and portals.
- Hardware
- Connectivity
- Platform
- Business integration
- End-user experience
Every field device is a long-term promise.
Devices need identity, updates, monitoring and support over years.
For OEMs, reusable hardware, connectivity and platform services often reduce time and operating risk.
- Provisioning
- Firmware and security
- Connectivity cost
- Replacement and support
- Lifecycle
Seven questions for an IoT business case.
- 01
Which customer problem is solved?
- 02
Who acts on the information?
- 03
Who pays for which value?
- 04
Which systems are integrated?
- 05
What volume and rollout are realistic?
- 06
How are devices and support operated?
- 07
Which assumption should a field test prove?