Telecom Product Strategy: Monetizing IoT Services

Telecom companies generated $116B in IoT revenue globally in 2025, per IoT Analytics. Most carriers I've worked with capture less than 8% of their addressable B2B IoT market. The gap isn't connectivity. It's product strategy. I spent 18 months inside a Fortune 10 telecom and IoT provider building the platform approach that grew their connected services revenue from $400M to $680M. The difference between carriers that monetize IoT and those stuck selling SIM cards comes down to three decisions: platform vs. point solution, pricing model, and product-sales alignment for enterprise accounts.

What Is IoT Monetization for Telecom?

IoT monetization is the practice of building recurring revenue from connected devices, data services, and platform capabilities beyond raw connectivity. It's the shift from selling data plans to selling outcomes, analytics, and managed services layered on top of the device fleet.

Most telecom companies still treat IoT as a connectivity play. They sell per-device data plans at thin margins and watch revenue grow linearly with device count. That model caps per-device revenue at $2-5/month. Platform-based approaches, where the carrier owns device management, data orchestration, and vertical applications, generate $15-40/month per device. I've measured that range across three carrier engagements. The unit economics aren't close.

Why Do Most Telecom IoT Strategies Fail to Scale?

The primary failure mode is building point solutions instead of platforms. Carriers build one connected fleet management tool for logistics, one asset tracker for manufacturing, one smart meter dashboard for utilities. Each vertical gets custom engineering. The code doesn't share components. The sales team can't cross-sell. Revenue grows linearly with headcount rather than compounding through the platform.

I've seen this pattern at two carriers with $1B+ IoT ambitions. Both had 12-15 IoT "products" that were really custom projects wearing product labels. Engineering costs scaled with customer count, not device count. Gross margins sat at 25-30% when they should have been 60%+.

The P&L outcome looked more like a services business than a platform business.

The fix is architectural, not incremental. You need a shared platform layer that handles identity and access management, device provisioning, data ingestion, and billing. Vertical applications sit on top. Each new vertical reuses 70-80% of the stack. That's where margin and scale live.

How Do You Build an IoT Revenue Engine?

Building a revenue engine for connected services requires a platform foundation, a clear packaging strategy, and an operating cadence that ties product investment to revenue outcomes. I've built this three times in telecom. Here's the sequence that works.

Step 1: Audit the Connected Services Portfolio

Map every IoT product and service to its revenue contribution, gross margin, and engineering cost. Most carriers discover that 2-3 offerings generate 80%+ of IoT revenue while the rest consume engineering capacity without material contribution. At the Fortune 10 carrier, 4 of 14 IoT products generated 87% of connected services revenue. We deprioritized 6 products in the first quarter and redirected engineering to the platform layer.

This diagnostic takes 3-4 weeks. The output is a one-page portfolio map showing revenue, margin, and cost per offering. I run this as the first deliverable in every telecom engagement.

Step 2: Build the Shared Platform Layer

The platform must handle five things: device provisioning, connectivity management, data ingestion and normalization, identity and access control, and metered billing. Everything else is a vertical application.

At the Fortune 10 carrier, we consolidated three separate provisioning systems and two billing engines into one platform. That consolidation alone saved $3.2M in annual infrastructure costs and cut new-product launch time from 9 months to 11 weeks.

Step 3: Package for B2B Buyers

Enterprise IoT buyers don't purchase connectivity. They purchase business outcomes: fleet uptime, asset visibility, energy cost reduction. Package connected services around the outcome, not the technology.

I restructured the product catalog at the carrier from 14 technology-defined SKUs to 5 outcome-defined bundles. Average deal size increased 35% in the first two quarters because the bundles aligned with how procurement evaluated ROI.

Step 4: Install the Revenue Cadence

Weekly pipeline reviews with product and sales in the same room. Monthly connected services P&L review. Quarterly roadmap recalibration against the revenue plan.

The Shipped Revenue Framework works here: every product initiative maps to a P&L line. KPI ownership is explicit. The product leader owns net revenue retention, platform adoption rate, and per-device ARPU. The sales leader owns pipeline creation and new logo acquisition. Those KPIs feed the same weekly review.

What Pricing Models Work for Connected Services?

Three models dominate telecom IoT, and the right choice depends on the customer's device count and usage variability.

Per-device flat rate works for large, homogeneous fleets. A logistics company with 50,000 trackers wants predictable pricing. Charge $8-15/device/month for connectivity plus basic device management. Margin is thin on small fleets but compounds at volume. This model accounts for roughly 45% of enterprise IoT contracts I've seen.

Usage-based pricing fits variable workloads. Industrial IoT sensors that transmit data in bursts, connected vehicles with seasonal mileage patterns, smart building systems with peak and off-peak cycles. Charge a base platform fee plus a per-message or per-GB rate. This model captures more revenue from high-usage customers without overcharging low-usage ones. Net revenue retention runs 15-25% higher than flat-rate models because revenue expands naturally with usage.

Tiered bundles combine the two. A base tier includes connectivity and device management. A mid tier adds data analytics and alerting. A premium tier includes predictive maintenance, API access, and dedicated support. This was the model I installed at the Fortune 10 carrier. It drove a 28% increase in average contract value within three quarters because customers self-selected into higher tiers once they saw the data layer's value.

The pricing model you choose also shapes the sales motion. Per-device pricing sells on spreadsheets. Usage-based requires a proof-of-concept. Tiered bundles need a land-and-expand strategy with clear upgrade triggers built into the product.

How Do You Align Product and Sales for Enterprise IoT?

Enterprise IoT sales cycles run 6-12 months. The deals are technical. Procurement needs ROI models, security reviews, and integration plans. Sales teams without product support close at half the rate.

Product-sales alignment for enterprise IoT means three things. First, product teams own the proof-of-concept phase. They scope the pilot, define success metrics, and run the technical validation. At the Fortune 10 carrier, assigning product managers to the top 20 deals cut the average sales cycle from 11 months to 6.5 months. Second, product builds the ROI calculator that sales uses in procurement meetings. The calculator maps device count, usage, and tier to expected cost savings. Third, product and sales share a weekly pipeline review. Funnel leakage in enterprise IoT typically happens between pilot completion and contract signing. That handoff is where deals die quietly.

I got this wrong at the carrier initially. I assumed the sales team could run pilots independently with documentation and demo environments. They couldn't. The technology was too complex, the integration questions too specific. Pilot close rates sat at 22% until we embedded product managers in the top 20 accounts. Close rates jumped to 48% within two quarters. That failure cost us roughly $15M in delayed revenue over 6 months. The lesson: own the pilot, own the close.

What Should You Do This Week?

Pull your IoT product portfolio into a single spreadsheet. List every connected service with its revenue, gross margin, engineering cost, and customer count. Rank by margin contribution. Identify the bottom 30% by margin. Those products are either platform consolidation candidates or cut candidates.

Then ask one question: "What would our revenue look like if we redirected engineering from the bottom 30% to improving the top 3 offerings?" That's your 90-day plan starting point.

If you want help running this diagnostic and building the platform strategy, book a diagnostic.

Frequently Asked Questions

How long does it take to build a telecom IoT platform?

A minimum viable platform takes 6-9 months if you're consolidating existing systems. Building from scratch takes 12-18 months. At the Fortune 10 carrier, we reached a functional shared platform in 8 months by consolidating rather than rebuilding. Start with the billing and provisioning layers. They create the most engineering duplication.

What gross margins should telecom IoT products target?

Platform-based connected services should target 55-70% gross margins. Connectivity-only products run 20-35%. If your IoT portfolio sits below 40% blended gross margin, you're selling too much connectivity and not enough platform value. I've seen carriers improve blended margins from 30% to 55% within four quarters by shifting to outcome-based packaging.

Can smaller carriers compete in IoT against Tier 1 providers?

Yes, by going vertical. Tier 1 carriers build horizontal platforms that serve every industry. Regional carriers and MVNOs win by building deep, industry-specific IoT solutions for 2-3 verticals. A $200M regional carrier I advised focused exclusively on agricultural IoT and smart utilities. They captured 15% market share in those verticals within their coverage area, competing against carriers 50x their size. Vertical depth beats horizontal breadth when your sales team can speak the customer's language.

If you want help applying this on Telecom Product Strategy: Monetizing IoT Services, Book a diagnostic.

Use The Shipped Revenue Framework to keep roadmap and revenue tied together, then course-correct weekly.

Related

• IAM Orchestration for IoT - identity and access management patterns for connected device platforms
• AI and Data Strategy for IoT - building the data layer that makes IoT services valuable
• Case Studies - results from engagements including a Fortune 10 telecom and IoT provider