Industry of Things Players
Who is in the room, who pays, who earns, and who sets the rules.
The Ecosystem
| Player | Role | Example |
|---|---|---|
| OEMs | Design and manufacture devices | Impinj, Bosch, Zebra |
| Network operators | Deploy and run devices, earn per event | Helium, GEODNET, Devin Labs |
| Protocol teams | Define schemas, identity, settlement | Peaq, IoTeX, Sui, Solana |
| Integrators | Wire devices into enterprise workflows | Regional IoT system integrators |
| Enterprise buyers | Consume verified events | Wineries, shippers, insurers, pharma |
| Regulators | Enforce jurisdictional rules | Telecom, customs, financial |
| Standards bodies | Publish cross-vendor schemas | GS1, W3C, IEEE |
Three Tribes
From consulting psychology. Pilot purgatory is tribal imbalance.
| Tribe | Who in This Industry | Current State | Imbalance |
|---|---|---|---|
| Explorers | DePIN teams, protocol designers, venture studios | Over-represented | Novelty outpaces operational discipline |
| Automators | OEMs, integrators, enterprise ops | Under-represented | Few make the messy middle reliable |
| Validators | Auditors, insurers, regulators, standards bodies | Almost absent | Nothing forces Explorers to close the loop |
Diagnosis: Explorers dominate because the tokens reward them. Automators avoid the space because the standards are not stable. Validators stay away because the legal framework is unclear. The unlock is an Automator-led play that gives Validators something to audit.
Buyer Problem
Two buyer archetypes. Different jobs, different hidden objections.
| JTBD | Buyer A — Wine Importer (SME) | Buyer B — Global Pharma (Enterprise) |
|---|---|---|
| The job | Prove storage conditions across a 12-week sea journey | Prove cold chain integrity across a 200-site distribution network |
| Current solution | Manual data loggers, paper custody, trust the shipper | Enterprise track-and-trace platform, annual audits |
| Trigger | A container arrived warm and the claim was denied | A product recall traced to a distribution gap |
| Hidden objection (Sutherland) | "If I prove the damage, am I also proving I'm a bad buyer?" | "If we change systems, our auditors will question every prior year" |
| Progress they're hiring for | Confident claims, faster payouts, lower insurance | Lower recall risk, regulator-ready evidence, fewer audits |
The real sale: Not the hardware. Not the chain. The sale is confidence — the ability to speak in front of a regulator or insurer and point at a chain nobody can rewrite. Buyers pay for the confidence, not the devices.
Tightness Score: 3/5
The players exist and are identifiable. Incumbents (OEMs, telcos, enterprise software vendors) are clear. Challengers (DePIN networks, protocol teams) are clear. The gap is tribal — Explorers dominate, Automators are scarce, Validators are almost absent. Until an Automator-Validator pairing emerges, pilots will not graduate to production.
Context
- Consulting Playbook — Three tribes, presenting vs real problem
- Phygital Beings — Devices as economic actors
- JTBD Framework — Buyer problem lens
- DePIN Tokens — Token layer of the ecosystem
- Economy of Things — Protocol layer binding players together
Questions
Which player holds the binding constraint — the OEM with cheap hardware, the protocol team with standards, the integrator with enterprise relationships, or the validator with regulatory trust?
- What would an Automator-led play look like in the Industry of Things?
- Who becomes the first insurance company to underwrite on a DePIN chain?
- Which enterprise buyer will pay a premium for "regulator-ready" over "cheap"?