Most industrial IoT projects stall at connectivity. They get devices streaming data to a dashboard and declare victory. The dashboard is not the product. The intelligence layer is the product. And the progression from connected devices to autonomous operations follows a predictable three-phase arc.

I have built data platforms across three companies, each at a different phase of this progression. The pattern is consistent regardless of the industry: construction technology, fleet telematics, supply chain logistics. Connectivity is table stakes. Contextualization is where the value inflects. Autonomous action at the edge is where the business model transforms.

What does Phase 1 look like?

Phase 1 is Connect. Get devices streaming data reliably. Sensors, telemetry, GPS, RFID, temperature, vibration, pressure. The technology for this phase is mature. MQTT for lightweight device-to-cloud messaging. Store-and-forward for intermittent connectivity. Cellular backhaul for mobile assets. The hard problems in Phase 1 are not technical. They are operational: provisioning devices at scale, managing firmware across heterogeneous fleets, and keeping cost-to-serve low enough that the unit economics work.

At one company, I reduced cost-to-serve 82% by replacing professional-install hardware with a plug-and-play self-install device. Zero-touch provisioning. No technician dispatch. No vehicle downtime. No manual configuration. The connectivity itself was not the innovation. The operational model around it was.

What changes in Phase 2?

Phase 2 is Contextualize. Raw sensor data has no business meaning. A temperature reading of 47.3 degrees means nothing without context: what asset, what location, what historical baseline, what threshold triggers action, what downstream system needs to know. Phase 2 transforms raw telemetry into structured, AI-ready intelligence.

This is where most organizations underinvest. They build the pipeline from device to dashboard and skip the intelligence layer. The result is a monitoring product. The field operator still has to look at the screen, interpret the data, and decide what to do. That is a visualization product, not an intelligence product.

The contextualization layer requires three capabilities: a data model that maps physical assets to digital twins, a state machine that tracks asset conditions over time, and a rules engine (or ML model) that identifies patterns worth acting on. The data model is the foundation. Without it, you are storing telemetry. With it, you are building intelligence.

At one company, I designed a three-tier telemetry ingestion architecture: real-time data for safety-critical alerts, near-real-time data for operational monitoring, and batch data for analytics and reporting. Each tier had different latency requirements, different storage costs, and different downstream consumers. The architecture decision was not “how do we ingest data” but “which data matters when, and to whom.”

What does Phase 3 require?

Phase 3 is Act. Autonomous actions at the edge driven by contextualized data. The system processes sensor data, applies the intelligence model, and makes decisions without waiting for a human to interpret a dashboard. The field operator’s device does not show them a graph. It tells them what to do. Or it does it for them.

I shipped an AI platform with an on-board neural network that processes 8,000+ data points per workflow into autonomous decisions at the edge. No cloud dependency for core operations. The device updates its intelligence model periodically from the cloud, but it acts independently in the field. This matters because the environments where industrial AI creates the most value are the environments with the least reliable connectivity: underground, remote, GPS-denied, connectivity-constrained.

Phase 3 is where the business model changes. A connectivity product is sold per-device. An intelligence product is sold per-outcome. The pricing architecture follows the value architecture: when the platform makes decisions that save the customer money, the product captures a share of that value.

How does this apply to manufacturing?

Manufacturing is the clearest case study for this progression. Phase 1: connect machines and track production data. Phase 2: contextualize that data with drawing revisions, work orders, and quality records so the intelligence layer knows what the machine is supposed to be making and whether it matches spec. Phase 3: the system catches a revision mismatch before the operator runs the wrong part.

The gap in manufacturing is not connectivity. Machines have had data ports for decades. The gap is contextualization. The drawing, the work order, the material cert, and the machine program all exist. They exist in different systems, different formats, different revision states. The intelligence layer that connects them does not exist for most small and mid-size manufacturers. That gap is the opportunity.

What should product leaders take from this?

Three principles:

Build the intelligence layer before you need it. If you wait until customers ask for AI, you are two years behind. The contextualization layer requires data model decisions that are expensive to change later. Design for Phase 2 even if you are still shipping Phase 1.

Edge-first architecture is non-negotiable for industrial environments. Cloud dependency is a luxury that field operators, factory floors, and remote worksites cannot afford. The intelligence must live where the action happens. Cloud is for model updates, analytics, and fleet-wide pattern recognition. The edge is for decisions.

Pricing follows the value curve. Connectivity is commodity. Intelligence is differentiated. Autonomous action is transformational. Price accordingly. The per-device subscription model works for Phase 1. Phase 2 and Phase 3 justify consumption-based and outcome-based pricing that scales with the value delivered.

Connect. Contextualize. Act. That is the progression. The companies that stall at connectivity will be displaced by the ones that reach autonomy.