86 IoT Go-to-Market: Pricing and Unit Economics
A vibration sensor on a pump can keep sending useful readings while its subscription loses money. A maintenance team that needs frequent help creates a different cost from a customer who uses the same dashboard alone. Pricing has to cover that difference.
86.1 Start With the Decision
A low device price can still lose money after support and cloud costs. Pricing must cover the value and the full service burden.
86.2 Route Overview
This is part 2 of 2. Review IoT Go-to-Market: Deployment Strategy for the preceding evidence.
86.3 Learning Objectives
- Compare device, subscription, usage, and outcome pricing.
- Calculate LTV, CAC, and payback for an IoT offer.
86.4 Chapter Roadmap
- Key Concepts
- Introduction
- State the Unique Value Proposition Early
- B2B Industrial Sensor GTM
- Pricing Model Comparison
- Putting Numbers to It
- Checkpoint: Unit Economics
- LTV:CAC Ratio Tool
- Checkpoint: Launch Gates
- Continue to Part 2
Key Concepts
- IoT Business Model: Framework defining how an IoT product or service creates, delivers, and captures economic value.
- Recurring Revenue: Ongoing income from subscriptions, data services, or maintenance contracts that follows the initial device sale.
- Total Cost of Ownership (TCO): Complete cost of acquiring, deploying, and operating an IoT system over its full lifecycle.
- Value Proposition: Clear statement of the benefit an IoT product delivers to a specific customer segment, differentiating it from alternatives.
- Platform Business Model: IoT strategy enabling third parties to build applications on top of device data or connectivity infrastructure.
- Hardware-as-a-Service (HaaS): Model where customers pay a recurring fee for IoT hardware instead of purchasing it outright, reducing upfront cost barriers.
- Churn Rate: Percentage of IoT subscribers who cancel service in a given period; a key metric for recurring revenue business health.
86.5 Introduction
A go-to-market (GTM) strategy translates product capabilities into customer value through deliberate choices about segmentation, pricing, channels, and launch sequencing. For B2B IoT products, GTM strategy is especially critical because the sales process involves hardware installation, software integration, and ongoing service delivery — all of which must be coordinated across customer organizations with multiple stakeholders.
This chapter walks through a complete GTM strategy for a B2B industrial IoT sensor, demonstrating the analytical frameworks and decision-making processes that product leaders use to bring IoT products to market.
86.6 State the Unique Value Proposition Early
The unique value proposition (UVP), also called the unique selling proposition, states why this IoT product is worth choosing over alternatives. The source slide uses portability, light weight, and convenience as example benefits, then makes the planning rule explicit: differentiating the idea from competing products deserves time early in commercialization, not after the product is built.
Treat those words as claims that need a comparison. “Portable” needs a reference product or installation model; “lightweight” needs a competing form factor; “convenient” needs a user task that becomes easier. The six-step framework below can then test whether the claimed difference matters to the chosen segment, survives pricing and support costs, and can be demonstrated during launch.
The six-step GTM framework above shows the sequential decision process. Each step builds on the previous: customer segments inform pricing, pricing constrains channels, channels dictate support requirements, and competitive positioning shapes launch sequencing.
86.7 B2B Industrial Sensor GTM
Scenario walkthrough: Launching an Industrial Vibration Monitoring Sensor
Scenario: Your startup has developed an industrial vibration sensor for predictive maintenance of rotating machinery (motors, pumps, compressors). The sensor uses MEMS accelerometers, edge ML for anomaly detection, and LoRaWAN connectivity. You need to develop a comprehensive go-to-market strategy for B2B sales.
Goal: Design a pricing model, channel strategy, and support structure that maximizes recurring revenue while achieving sustainable customer acquisition costs in the industrial IoT market.
86.7.1 Step 1: Define Target Customer Segments
What we do: Identify and prioritize customer segments based on pain points, willingness to pay, and sales complexity.
Why: B2B markets are heterogeneous; different segments require different value propositions and sales approaches.
Customer segment analysis:
| Segment | Size (US) | Pain Point | Decision Maker | Sales Cycle | Priority |
|---|---|---|---|---|---|
| Large Manufacturing | ~5,000 plants | Unplanned downtime costs $260K/hour | VP Operations, Reliability Engineer | 6-12 months | Medium (long sales cycle) |
| Mid-size Manufacturing | ~25,000 plants | Can’t afford dedicated reliability team | Plant Manager, Maintenance Lead | 3-6 months | High (sweet spot) |
| Water/Wastewater Utilities | ~16,000 systems | Aging infrastructure, limited budgets | Operations Director, City Engineer | 4-8 months | High (regulatory pressure) |
| HVAC Service Providers | ~100,000 firms | Differentiate from competitors | Owner, Service Manager | 1-3 months | Medium (fragmented) |
| Oil & Gas | ~2,000 facilities | Safety-critical, existing solutions | Reliability Manager, HSE Director | 12-24 months | Low (entrenched vendors) |
Primary target selection: Mid-size manufacturing (500-2,500 employees)
Rationale:
- Large enough to have significant downtime costs ($50K-200K per incident)
- Small enough to lack dedicated predictive maintenance programs
- Decision authority often in single plant manager (faster sales)
- Less likely to have existing vendor relationships to displace
86.7.2 Step 2: Design the Pricing Model
What we do: Structure pricing to maximize lifetime value while minimizing adoption friction.
Why: B2B IoT pricing must balance upfront investment barriers against long-term revenue goals.
Cost structure analysis (our costs):
| Cost Component | Per Sensor | Ongoing Monthly |
|---|---|---|
| Hardware BOM | $85 | - |
| Manufacturing & test | $25 | - |
| LoRaWAN gateway (1 per 50 sensors) | $8 (amortized) | - |
| Cloud infrastructure | - | $0.50/sensor |
| Cellular backhaul (gateway) | - | $0.30/sensor |
| Customer support (allocated) | - | $1.20/sensor |
| ML model updates | - | $0.40/sensor |
| Total | $118 | $2.40/sensor |
Pricing model options evaluated:
| Model | Hardware | Monthly Fee | 3-Year Revenue | Pros | Cons |
|---|---|---|---|---|---|
| A: Hardware + Subscription | $299 | $29/sensor | $1,343 | Clear value separation | High upfront barrier |
| B: Subscription-only | $0 | $59/sensor | $2,124 | Low barrier, high LTV | Cash flow negative 6+ months |
| C: Hardware + Tiered SaaS | $199 | $19-49/sensor | $883-1,963 | Flexibility | Complexity, upsell friction |
| D: Outcome-based | $0 | 10% of savings | Variable | Aligned incentives | Requires baseline, disputes |
Selected model: Hybrid (Model A with financing)
| Component | Price | Notes |
|---|---|---|
| Sensor hardware | $299 (or $15/month lease) | Lease option reduces friction |
| Basic monitoring SaaS | $19/month/sensor | Dashboard, alerts, API |
| Advanced analytics tier | $39/month/sensor | ML predictions, work orders |
| Enterprise tier | $59/month/sensor | Multi-site, integrations, SLA |
| LoRaWAN gateway | Included with 10+ sensors | Removed as purchase barrier |
Unit economics at scale (100 sensors, Advanced tier):
86.8 Pricing Model Comparison
Compare different IoT pricing strategies and their impact on 3-year revenue, customer lifetime value, and cash flow dynamics.
| Metric | Value | Calculation |
|---|---|---|
| Hardware revenue | $29,900 | 100 x $299 |
| Monthly recurring revenue (MRR) | $3,900 | 100 x $39 |
| Annual recurring revenue (ARR) | $46,800 | $3,900 x 12 |
| 3-year total revenue | $170,300 | $29,900 + ($46,800 x 3) |
| 3-year gross margin | 72% | After COGS and infrastructure |
| Customer LTV | $122,616 | 3-year revenue x 72% margin |
86.8.1 Step 3: Build the Channel Strategy
What we do: Design the sales and distribution approach for each customer segment.
Why: B2B sales channels determine customer acquisition cost, sales velocity, and scalability.
Channel analysis for mid-size manufacturing:
| Channel | Reach | CAC | Pros | Cons |
|---|---|---|---|---|
| Direct sales team | High | $15K-25K | Control, relationships | Expensive, slow to scale |
| Industrial distributors | High | $8K-12K (margin share) | Existing relationships | Margin erosion, brand distance |
| System integrators | Medium | $5K-10K | Technical credibility | Requires training, certification |
| Online self-serve | Low | $1K-3K | Scalable, low cost | Complex B2B sales don’t fit |
| OEM partnerships | Very High | $2K-5K (per install) | Volume, sticky | Long development, margin pressure |
Selected channel mix:
| Channel | Year 1 Focus | Year 2-3 Evolution | Target % Revenue |
|---|---|---|---|
| Direct sales | 80% | 50% | Land enterprise deals, learn |
| System integrators | 15% | 30% | Scale through partners |
| Industrial distributors | 5% | 15% | Geographic expansion |
| OEM partnerships | 0% | 5% | Long-term embedded play |
Direct sales team structure (Year 1):
| Role | Count | Quota | OTE | Focus |
|---|---|---|---|---|
| VP Sales | 1 | Team | $250K | Strategy, enterprise deals |
| Account Executive | 3 | $500K ARR | $150K | New logo acquisition |
| Sales Engineer | 2 | Support AEs | $120K | Technical validation, POC |
| Customer Success | 2 | Retention, expansion | $100K | Onboarding, renewals, upsell |
CAC calculation for direct sales:
| Cost Component | Annual | Notes |
|---|---|---|
| Sales team fully loaded | $1,090,000 | Salaries, benefits, OTE |
| Marketing (lead gen) | $300,000 | Events, content, digital |
| Sales tools (CRM, etc.) | $50,000 | Salesforce, outreach tools |
| Travel & entertainment | $100,000 | Customer visits, demos |
| Total sales & marketing | $1,540,000 | |
| Target new customers (Year 1) | 50 | ~$100K average deal |
| CAC | $30,800 | High initially, improves with scale |
86.9 Putting Numbers to It
The $30,800 CAC must be justified by customer lifetime value. With hybrid pricing ($50K hardware plus $12K/year SaaS), the five-year industrial customer LTV model is: LTV = \$50,000 + (\$12,000 x 5) - COGS.
Assuming 40% hardware margin and 80% SaaS margin:
- Hardware gross profit:
\$50,000 x 0.40 = \$20,000. - SaaS gross profit:
\$12,000 x 5 x 0.80 = \$48,000. - Total LTV:
\$20,000 + \$48,000 = \$68,000.
LTV:CAC ratio: . This is below the 3:1 minimum threshold, indicating the business needs to either (a) reduce CAC through channel partners, (b) increase pricing, or (c) extend customer lifetime beyond 5 years to achieve sustainable unit economics.
Checkpoint: Unit Economics
You now know:
- The selected hybrid model combines $299 hardware with $19, $39, or $59 per sensor per month SaaS tiers.
- At 100 sensors on the Advanced tier, the chapter’s model shows $29,900 hardware revenue and $3,900 MRR.
- The five-year industrial example fails the gate at 2.2:1 because $68,000 LTV does not clear the 3:1 threshold against $30,800 CAC.
86.10 LTV:CAC Ratio Tool
Adjust the inputs below to calculate customer lifetime value, customer acquisition cost, and the critical LTV:CAC ratio for your IoT business model.
86.10.1 Step 4: Design the Support Structure
What we do: Create tiered support that scales with customer value and complexity.
Why: B2B customers expect support proportional to their investment; support costs can erode margins if unmanaged.
Support tier structure:
| Tier | Included With | Response SLA | Channels | Scope |
|---|---|---|---|---|
| Standard | Basic SaaS | 24 hours | Email, knowledge base | Product issues, how-to |
| Priority | Advanced SaaS | 4 hours | Email, phone, chat | Technical troubleshooting |
| Enterprise | Enterprise SaaS | 1 hour | Dedicated CSM, phone | Full support, integrations |
| Professional Services | Add-on | Scheduled | On-site, remote | Installation, training, custom |
Support cost model (per 100 sensors):
| Support Level | Monthly Cost | Staffing | Margin Impact |
|---|---|---|---|
| Standard | $120 ($1.20/sensor) | 0.1 FTE shared | Included in $19 SaaS |
| Priority | $350 ($3.50/sensor) | 0.25 FTE shared | Included in $39 SaaS |
| Enterprise | $800 ($8.00/sensor) | 0.5 FTE dedicated | Included in $59 SaaS |
Professional services offerings:
| Service | Price | Duration | Margin |
|---|---|---|---|
| Site survey & design | $2,500 | 1 day | 60% |
| Installation (per sensor) | $75 | 30 min | 40% |
| Integration (per system) | $5,000-15,000 | 1-3 weeks | 50% |
| Training (per session) | $1,500 | Half day | 70% |
| Annual maintenance review | $3,000 | Quarterly calls | 65% |
Customer success metrics:
| Metric | Target | Measurement |
|---|---|---|
| Net Revenue Retention (NRR) | >110% | (Starting ARR + Expansion - Churn) / Starting ARR |
| Gross churn | <10% annual | Lost ARR / Starting ARR |
| Time to value | <30 days | First actionable alert after install |
| NPS | >50 | Quarterly survey |
| Support tickets per sensor | <0.5/month | Indicates product quality |
86.10.2 Step 5: Develop Competitive Positioning
What we do: Articulate differentiation against incumbent and emerging competitors.
Why: Industrial IoT is increasingly competitive; clear positioning prevents commoditization.
Competitive landscape:
| Competitor | Positioning | Strengths | Weaknesses | Our Advantage |
|---|---|---|---|---|
| SKF Enlight | Premium, full-service | Brand, expertise, services | High price, complex, slow deploy | 3x faster deployment, 50% lower TCO |
| Fluke 3563 | Portable + connected | Known brand, flexible | Not continuous, manual | 24/7 monitoring, automated alerts |
| Augury | AI-first, SaaS | Strong ML, proven ROI | Higher price, requires Wi-Fi | LoRaWAN works in metal buildings |
| Banner Wireless | Low-cost sensors | Price, industrial heritage | Basic analytics, no ML | Edge ML, predictive not reactive |
| AWS IoT + DIY | Platform, flexibility | Customizable, scalable | Requires expertise, no domain | Turnkey solution, 2-week deploy |
Positioning statement:
“For mid-size manufacturers who can’t afford dedicated reliability engineers, [ProductName] is the only vibration monitoring system that deploys in 2 weeks and predicts failures 30 days in advance without requiring Wi-Fi infrastructure or data science expertise.”
Key differentiators to emphasize:
| Differentiator | Proof Point | Sales Enablement |
|---|---|---|
| 2-week deployment | Average install: 12 days vs. 90+ for competitors | Case study, guaranteed timeline |
| No Wi-Fi required | LoRaWAN penetrates metal, concrete | Live demo in metal shop |
| Edge ML | 95% of alerts processed on-device | Privacy/security selling point |
| 30-day predictions | 3 customer case studies with verified savings | ROI calculator with customer data |
| All-in pricing | No hidden gateway, integration, training fees | TCO comparison worksheet |
86.10.3 Step 6: Plan the Launch Sequence
What we do: Phase the market entry to manage risk and learn quickly.
Why: B2B launches require proof points before scaling; early customers validate value proposition and refine sales process.
Phased launch plan:
| Phase | Duration | Focus | Success Metrics |
|---|---|---|---|
| Alpha (Design Partners) | Months 1-3 | 5 friendly customers, free | Product feedback, case studies |
| Beta (Paid Pilots) | Months 4-6 | 15 customers, 50% discount | Conversion rate, NPS, time to value |
| Limited Availability | Months 7-9 | 30 customers, full price | Sales cycle, CAC, churn |
| General Availability | Month 10+ | Scalable sales motion | MRR growth, NRR, quota attainment |
Alpha customer selection criteria:
| Criterion | Requirement | Why |
|---|---|---|
| Industry | Manufacturing, water/wastewater | Primary target segments |
| Size | 200-1,000 employees | Mid-size sweet spot |
| Technical champion | Identified, engaged | Ensures adoption |
| Reference willingness | Agreed upfront | Case study material |
| Equipment variety | 3+ machine types | Tests ML model breadth |
Go-to-market budget (Year 1):
| Category | Q1 | Q2 | Q3 | Q4 | Total |
|---|---|---|---|---|---|
| Product development | $200K | $150K | $100K | $75K | $525K |
| Sales team ramp | $100K | $250K | $350K | $400K | $1,100K |
| Marketing | $50K | $75K | $100K | $125K | $350K |
| Customer success | $25K | $50K | $75K | $100K | $250K |
| Infrastructure (cloud, tools) | $30K | $30K | $35K | $40K | $135K |
| Total | $405K | $555K | $660K | $740K | $2,360K |
Revenue projections:
| Quarter | New Customers | Cumulative Sensors | MRR | ARR Run Rate |
|---|---|---|---|---|
| Q1 | 5 (alpha, free) | 100 | $0 | $0 |
| Q2 | 10 (beta, discounted) | 300 | $5,850 | $70K |
| Q3 | 15 | 600 | $19,500 | $234K |
| Q4 | 20 | 1,000 | $39,000 | $468K |
86.10.4 Final Result
Outcome: A comprehensive go-to-market strategy for a B2B industrial IoT sensor targeting mid-size manufacturers with a hybrid hardware + SaaS pricing model and a direct sales-led channel approach.
Key decisions made and why:
| Decision | Rationale | Risk Mitigation |
|---|---|---|
| Target mid-size manufacturing | Fastest sales cycles, highest need, manageable competition | Expand to utilities and HVAC in Year 2 |
| Hybrid pricing ($299 + $39/month) | Balances upfront barrier with recurring revenue | Offer lease option for budget-constrained |
| Direct sales first | Control narrative, learn sales process, build case studies | Partner channel in Year 2 for scale |
| 3-tier support | Matches support cost to customer value | Self-serve knowledge base reduces tickets |
| Phased launch | Reduces risk, builds proof points | Exit criteria for each phase |
Financial summary (Year 1 to Year 3):
| Metric | Year 1 | Year 2 | Year 3 |
|---|---|---|---|
| Customers | 50 | 150 | 350 |
| Sensors deployed | 1,500 | 6,000 | 18,000 |
| Hardware revenue | $449K | $1,347K | $3,592K |
| ARR (ending) | $702K | $2,808K | $8,424K |
| Total revenue | $702K | $2,808K | $8,424K |
| Gross margin | 65% | 70% | 75% |
| CAC | $30,800 | $18,000 | $12,000 |
| LTV:CAC ratio | 4.0:1 | 6.8:1 | 10.2:1 |
Critical success factors:
- Prove ROI with alpha customers: 3 documented case studies showing $50K+ annual savings
- Nail the 2-week deployment promise: Differentiation evaporates if installation is painful
- Build integration partnerships: CMMS (Fiix, UpKeep), ERP (SAP, Oracle) integrations required for enterprise
- Control churn: Year 1 churn above 15% signals product-market fit issues
- Manage CAC burn: Direct sales expensive; must improve efficiency quarter-over-quarter
Checkpoint: Launch Gates
You now know:
- Support costs, positioning claims, and launch phases are part of GTM economics, not after-sales detail.
- The phased launch uses 5 free alpha customers, 15 discounted beta customers, 30 limited-availability customers, and general availability only after the gates hold.
- The three-year summary improves from a 4.0:1 LTV:CAC ratio in Year 1 to 10.2:1 in Year 3 as CAC falls and the installed base grows.
86.11 Continue to Part 2
Continue with IoT Go-to-Market: Launch Gates and Channels.
86.12 When Support Changes the Advanced Tier Margin
Use the chapter’s Advanced tier at £39 per sensor per month as an illustrative currency-denominated version of the model. Keep the stated cost magnitudes: cloud £0.50, backhaul £0.30, model updates £0.40 and basic support £1.20. Together they cost £2.40 per month, leaving £36.60 before hardware and other business expenses. For 100 sensors, recurring revenue is £3,900 and this contribution is £3,660 per month.
The support table introduces a second assumption: Priority support costs £3.50 per sensor. Replace the basic allowance; do not add both allowances for the same service. The revised monthly cost is 0.50 + 0.30 + 0.40 + 3.50 = 4.70 pounds per sensor. Contribution becomes £34.30 per sensor, or £3,430 across the fleet. The difference is £230 each month. A sales proposal that promises Priority service while using basic support costs overstates the margin.
Follow the existing six-step framework from customer segment to pricing, channel, support, positioning and launch. Here the support step sends a constraint back to pricing: the promised response needs staff. The channel also matters. An installer who handles first-line questions may lower supplier workload but charge a fee. That fee belongs in the acquisition or running-cost model according to when it is paid.
Predict whether doubling the fleet guarantees twice the profit. It doubles the simple contribution only if cost per sensor stays fixed. A new customer with a complex factory connection may need extra integration work. Likewise, a free pilot can prove that alarms help a technician, but it cannot establish willingness to pay the full subscription.
Check the launch decision against a paid cohort with the promised support included. Compare observed tickets and staffing time with the allowance used above. This makes the go-to-market choice testable: the offer must deliver customer value and fund its own service burden. The figures here are model inputs, not supplier quotes or a forecast of demand.
86.13 Continue Your Route
This final part closes the route from Key Concepts through Continue to Part 2. Return to IoT Go-to-Market: Deployment Strategy or continue from the applications module index.