Entitlement value and cost map
Entitlement value and cost map
A quick test is to write the model as a value loop. The device observes something, the platform turns that observation into a decision or service, and the customer pays because that decision remains useful. If the loop stops at “we collect data,” the model is unfinished. If the loop names the payer, the recurring outcome, the cost driver, and the renewal trigger, it is ready for pricing work.
Start with a one-page entitlement map. For each tier, list the number of devices, retention period, alert rules, integrations, API limits, firmware support, service-level commitments, and human support included. Then list the signals that measure whether the entitlement is being consumed: active devices, message volume, storage growth, dashboard sessions, API calls, alerts generated, tickets opened, and field visits avoided. This keeps pricing tied to usage instead of vague feature labels.
Pricing also has to match operating cost. A device that publishes high-frequency telemetry over LTE-M or NB-IoT has a different cost profile from a Wi-Fi device that sends summary events. A product that promises OTA fixes needs release operations, staged rollout, rollback policy, and support scripts. Those requirements belong in the business model, not only the engineering plan, because they decide gross margin, payback period, and the minimum healthy contract length.
- Name the payer. Identify whether the buyer, user, installer, operator, insurer, utility, or partner receives the value.
- Name the entitlement. Define what the paid tier unlocks: device count, retention period, alerting, APIs, integrations, analytics, or support level.
- Name the cost driver. Track messages, storage, compute, cellular data, warranty visits, support cases, and update operations before setting price.