Imagine a team pitching IoT growth with no way to explain unit economics. This chapter turns enthusiasm into financial evidence by following acquisition cost, churn, margin, device support, subscription revenue, payback, and lifetime value through the connected-product lifecycle.
This chapter follows the money trail in four passes:
Checkpoints recap the decision question at each stage. Deep calculations and calculators are support tools; the main path is deciding whether the connected product can scale without hiding cost.
By the end of this chapter, you will be able to:
This chapter assumes:
Financial metrics are useful only when they describe a specific customer cohort, device fleet, and recurring service promise. LTV, CAC, ARPU, churn, payback, and TCO are not independent scoreboard numbers. They are a connected story about how much value a customer receives, how expensive it was to win that customer, how much the connected service costs to operate, and how long the relationship lasts. In IoT, the story is harder than ordinary software because hardware, installation, connectivity, warranty, support, storage, field service, and safety requirements all affect the same margin.
The first reader habit is to ask what is being counted. A device sale can create cash today while hiding future support cost. A high ARPU account can still be weak if it needs expensive truck rolls or cellular traffic. A low CAC channel can be misleading if it brings customers who churn after one billing cycle. A strong LTV:CAC ratio can still strain cash if payback takes too long. This chapter treats each metric as one lens on the same unit-economics system.
| Metric | Question It Answers | IoT Evidence Needed |
|---|---|---|
| LTV | How much margin does a cohort create before it leaves? | Plan revenue, gross margin, churn, attach rate, support load, device replacement cost |
| CAC | How expensive is it to acquire and activate a useful customer? | Channel spend, demo cost, installation labor, onboarding time, sales cycle length |
| Payback | How long is cash tied up before the customer repays acquisition cost? | CAC, contribution margin, billing cadence, hardware subsidy, deployment lag |
| TCO | What does the platform really cost to run at scale? | IoT hub traffic, cloud storage, analytics, support, compliance, integration maintenance |
The goal is not to memorize thresholds. The goal is to notice which number would change a launch decision. If LTV:CAC is below 3:1, acquisition or retention needs work. If payback is longer than the expected customer lifetime, growth burns cash. If TCO grows faster than ARPU, the service may scale revenue while losing margin. The metrics are decision tools, not decorations for a dashboard.
Practitioners should build a unit-economics ledger before building executive charts. The ledger links every device, account, plan, billing event, support event, cost driver, and renewal outcome to a durable identifier. A dashboard that shows revenue by month is not enough. The team must be able to explain which cohort produced the revenue, which channel acquired it, which devices generated cost, and whether the customer renewed because the connected service kept producing measurable value.
A practical stack usually combines product telemetry, billing records, support data, and cloud cost allocation. Stripe Billing, Chargebee, Paddle, NetSuite, or an ERP system may hold subscription state and invoices. AWS IoT Core, Azure IoT Hub, EMQX, or a fleet backend may hold device events. A warehouse such as BigQuery, Snowflake, Redshift, or Postgres may join account identifiers, device identifiers, plan tiers, usage events, support tickets, and cloud-cost tags. Tools such as dbt can make the metric definitions explicit so finance, product, and engineering use the same LTV, churn, and margin logic.
The practitioner mistake is to average too early. A blended ARPU can hide one profitable industrial fleet and one unprofitable consumer segment. A single churn percentage can hide a problem with a firmware release, a cellular coverage region, or a support policy. Keep cohort cuts visible until the launch decision is clear. Then summarize with the smallest set of metrics that explain the decision.
Under the hood, IoT financial metrics are data-modeling problems. A correct LTV calculation requires revenue and cost events to meet at the same grain. If billing is by account, telemetry is by device, support is by ticket, cloud cost is by service tag, and field work is by work order, the metric pipeline must map those records to a shared account or asset model. Otherwise the team may report healthy revenue while the expensive devices, noisy customers, or high-retention segments remain invisible.
Churn also needs precise event definitions. Subscription churn may mean payment cancellation, non-renewal, downgrade, device deactivation, loss of connectivity, or non-use. In IoT those states are not equivalent. A customer may keep paying while devices are offline, which hides product risk. A device may stay online while the paying contract is cancelled, which creates entitlement and support risk. A fleet may downgrade from premium analytics to basic monitoring, which changes ARPU, margin, and future expansion probability without becoming full churn.
Cost attribution is the other hard part. AWS Cost and Usage Reports, Azure Cost Management exports, Kubernetes labels, storage lifecycle policies, IoT hub metrics, and support-ticket systems can all help, but only if identifiers are consistent. The model should allocate ingestion, rules, storage retention, analytics jobs, notification traffic, support time, replacement hardware, and installation cost to the same account or device cohort used for revenue. That lets the team distinguish gross margin from contribution margin.
The under-the-hood test is whether a metric can survive a finance review. If an executive asks why payback changed, the team should trace the change to acquisition channel mix, churn movement, margin cost, billing plan, or device behavior. If the answer is only “the dashboard changed,” the metric is not mature enough for a launch decision.
Checkpoint: Cohort Ledger
You now know:
Beginner Example: A smart thermostat subscription should not compare hardware revenue with advertising spend only; it should include attach rate, monthly fee, churn, cloud cost, support, and warranty replacements.
Intermediate Example: A fleet-management vendor can separate paid-search customers from installer-referred customers to see whether lower CAC also brings better retention and lower support load.
Advanced Example: A predictive-maintenance platform should connect asset telemetry, work orders, support tickets, cloud inference cost, avoided downtime, and renewal outcome before claiming a strong LTV:CAC ratio.
This chapter covers the essential financial metrics for evaluating IoT business models:
The layered IoT unit-economics workflow now lives in IoT Unit Economics Metrics Contracts, covering hardware and installation cost, connectivity and cloud COGS, cohort margin, LTV:CAC payback, telemetry and billing identity, and cost attribution for IoT hubs, storage, warehouses, support, and field operations.
Why do numbers matter so much in IoT businesses?
Imagine you run a lemonade stand. You spend $5 on supplies and sell lemonade for $10. Simple! But IoT businesses are more like a lemonade subscription—you deliver fresh lemonade every week for a monthly fee. Now you need to know:
| Lemonade Question | IoT Business Term | What It Means |
|---|---|---|
| How long does a customer keep ordering? | Customer Lifetime | Average months before they cancel |
| How much total money do they pay? | LTV (Lifetime Value) | Total revenue from one customer |
| How much did it cost to get them? | CAC (Acquisition Cost) | Marketing + sales cost per customer |
| How much do they pay each month? | ARPU | Average monthly payment |
| How many quit each month? | Churn Rate | Percentage who cancel |
The Golden Rule: LTV must be bigger than CAC!
If you spend $100 to get a customer but they only pay you $50 total—you lose money on every customer! That is why businesses track the LTV:CAC ratio:
Real example: A smart thermostat company might spend $150 to acquire a customer (ads, sales team, free installation). If that customer pays $10/month for 3 years, they generate $360 total. LTV:CAC = $360/$150 = 2.4:1. Not bad, but they should try to keep customers longer or reduce acquisition costs!
Hey Sensor Squad! Today we are learning about the money side of IoT. Even the coolest smart device needs a good business plan!
Sammy the Sensor says: “Think of it like collecting trading cards!”
Lila the Light Sensor asks: “What is churn?”
Churn is when customers say “goodbye” and stop paying. Imagine you have 100 friends in your club:
See how a tiny difference (just 3 more friends leaving) makes a HUGE difference over time? That is why IoT companies work so hard to keep their customers happy!
Max the Motion Sensor’s Money Tip: “Always check: Is the customer worth MORE than what you spent to get them? If yes, great business! If no, time to fix something!”
Bella the Buzzer adds: “And do not forget hidden costs! An IoT platform might look cheap at first, but extras like data storage, security features, and customer support can add up to 70% more than the sticker price!”
We have the vocabulary now. The next question is how those terms connect into one sustainability signal rather than a list of finance abbreviations.
The following diagram shows how the core IoT financial metrics relate to each other and ultimately determine business sustainability.
Definition: Total revenue a business can expect from a single customer account over the entire relationship duration.
Formula:LTV = Σ(ARPU × Gross Margin × Retention^month), for months 1 to n
Example Calculation (36-month LTV with churn): - ARPU: $20/month - Gross Margin: 70% - Monthly Churn: 5% (95% retention)
Month 1: $20 x 0.70 x 1.00 = $14.00 Month 2: $20 x 0.70 x 0.95 = $13.30 Month 3: $20 x 0.70 x 0.9025 = $12.63 … 36-month sum: approximately $280
Calculate customer lifetime value with different churn scenarios:
Definition: Total cost to acquire a new customer, including marketing and sales expenses.
Formula: CAC = sales and marketing spend divided by new customers.
Example: $1,540,000 annual S&M spend / 50 new customers = $30,800 CAC
Definition: Average monthly revenue generated per customer.
Formula: ARPU = revenue divided by active customers.
Definition: Percentage of customers who discontinue service in a given period.
Formula: Churn = lost customers divided by starting customers.
Churn’s exponential compound effect: If you start with 10,000 customers and have 2% monthly churn, how many remain after 12 months?
Each month, you retain 98% of customers: Customers after 12 months = 10,000 x (0.98)^12 = 10,000 x 0.785 = 7,850.
With 5% churn (95% retention): Customers after 12 months = 10,000 x (0.95)^12 = 10,000 x 0.540 = 5,400.
That 3 percentage point difference results in 2,450 more lost customers over one year. The average customer lifetime is \(1 / \text{churn rate}\), so 2% churn yields 50 months while 5% yields only 20 months—a 2.5× difference that directly multiplies into lifetime value.
The following diagram illustrates how churn compounds over time, showing the dramatic difference between 2% and 5% monthly churn on customer retention.
Definition: Ratio comparing customer lifetime value to acquisition cost.
| Ratio | Interpretation |
|---|---|
| < 1:1 | Unsustainable - losing money on each customer |
| 1:1 - 3:1 | Marginal - barely covering costs |
| 3:1 - 5:1 | Healthy - good unit economics |
| > 5:1 | Excellent - consider investing more in growth |
Target: LTV:CAC ratio should be at least 3:1 for sustainable business.
Evaluate business sustainability with your unit economics:
Definition: Number of months required to recover the customer acquisition cost from monthly profit.
Formula: Payback = CAC divided by ARPU times margin.
Target: Less than 18 months for healthy SaaS/IoT businesses. Shorter payback periods improve cash flow and reduce risk.
Determine how long it takes to recover customer acquisition costs:
Checkpoint: Unit Economics Math
You now know:
“A high LTV:CAC ratio always means a great business.” Not necessarily. If CAC is extremely low (e.g., $10) and LTV is $50, the 5:1 ratio looks healthy, but the absolute profit per customer ($40) may be too small to cover fixed costs like platform maintenance, engineering salaries, and customer support infrastructure. Always evaluate absolute margins alongside ratios.
“Raising prices is the fastest way to improve ARPU.” Price increases often accelerate churn, especially in competitive IoT markets where switching costs are declining. A company that raises ARPU from $20 to $30 but sees churn jump from 3% to 6% will actually lose LTV (from roughly $4,667 to $4,000 using simplified lifetime calculations). Improve ARPU through value-added tiers and cross-selling instead.
“Hardware margin is the real profit driver in IoT.” Most successful IoT companies (Nest, Ring, Peloton) sell hardware at slim margins or even at a loss. The recurring subscription and data services generate the majority of lifetime revenue. Treating hardware as a customer acquisition channel rather than a profit center often produces better long-term economics.
“Monthly churn below 5% is acceptable.” At 5% monthly churn, only 54% of customers remain after 12 months and just 16% after 36 months. For subscription IoT businesses, even 3% monthly churn (roughly 31% annual) is considered high. Best-in-class IoT platforms target below 1.5% monthly churn (less than 17% annual), which yields an average customer lifetime of over 5.5 years.
Different financial metrics take priority depending on where an IoT business sits in its lifecycle. The following diagram maps the critical metrics to each stage, helping teams focus on what matters most at each phase.
The following diagram maps each financial metric to its practical business application and the levers available to improve it.
Model revenue growth with customer acquisition and churn:
The projection calculator checks growth under one set of assumptions. The next financial question is whether the platform cost structure still works when device count, message volume, storage, support, and integrations arrive.
Evaluating IoT platform costs requires looking far beyond the initial quote. This section provides a comprehensive framework for calculating true Total Cost of Ownership (TCO) and avoiding common financial pitfalls.
Most IoT platform vendors quote only the visible portion of costs. The true TCO includes hardware, connectivity, cloud operations, maintenance, support, and integration expenses that accumulate across years:
Year 1 Cost Breakdown (10,000 Device Deployment):
| Cost Category | Vendor A (AWS IoT) | Vendor B (Azure IoT) | Vendor C (Specialist Platform) |
|---|---|---|---|
| Platform Base | $0 (pay-per-use) | $0 (pay-per-use) | $50,000/year |
| Device Connections | $0.08/device/month = $9,600/yr | $0.10/device/month = $12,000/yr | Included |
| Message Ingestion | $1.00/M messages | $1.50/M messages | Included up to 100M |
| Data Storage | $0.023/GB (S3) | $0.018/GB (Blob) | $0.05/GB |
| Analytics/Rules | $0.15/M rule evaluations | $0.20/M rule executions | Included |
| Dashboards | Additional service ($500/mo) | Power BI ($10/user/mo) | Included (5 users) |
| Support | Business: $15K/yr | Professional: $12K/yr | Premium: $20K/yr |
Message Volume Calculation Example:
Devices: 10,000
Messages per device per day: 288 (5-minute intervals)
Monthly messages: 10,000 x 288 x 30 = 86.4M messages/month
AWS IoT Core: 86.4M x $1.00/M = $86.40/month
Azure IoT Hub: 86.4M x $1.50/M = $129.60/month
Specialist: $0 (included in platform fee)| Year | AWS IoT | Azure IoT | Specialist Platform |
|---|---|---|---|
| Year 1 | $185,000 | $210,000 | $145,000 |
| Year 2 | $165,000 | $188,000 | $120,000 |
| Year 3 | $175,000 | $195,000 | $130,000 |
| Year 4 | $190,000 | $205,000 | $140,000 |
| Year 5 | $210,000 | $220,000 | $150,000 |
| 5-Year Total | $925,000 | $1,018,000 | $685,000 |
| Monthly per Device | $1.54 | $1.70 | $1.14 |
Note: Specialist platforms often have lower TCO but less flexibility. Hyperscaler platforms (AWS, Azure) offer more services but a la carte pricing accumulates quickly.
Compare total cost of ownership across IoT platforms:
Integration is consistently underestimated. Budget 2-3x the platform cost for integration in Year 1:
| Integration Component | Time Estimate | Cost ($150/hr blended rate) |
|---|---|---|
| Device provisioning workflow | 80-120 hours | $12,000-$18,000 |
| Data model design and implementation | 60-100 hours | $9,000-$15,000 |
| Dashboard/visualization development | 120-200 hours | $18,000-$30,000 |
| Alert/notification system | 40-80 hours | $6,000-$12,000 |
| ERP/CRM integration | 160-300 hours | $24,000-$45,000 |
| Security implementation | 80-160 hours | $12,000-$24,000 |
| Testing and validation | 80-120 hours | $12,000-$18,000 |
| Documentation and training | 40-60 hours | $6,000-$9,000 |
| Total Integration | 660-1,140 hrs | $99,000-$171,000 |
Choose Hyperscaler (AWS/Azure/GCP) When:
Choose Specialist Platform When:
Choose Build-Your-Own When:
Checkpoint: Platform TCO
You now know:
The platform decision is only one failure mode. The next cases show why apparently strong ratios can collapse when churn, subsidies, or cash timing change.
Peloton’s trajectory from 2019-2023 provides a cautionary case study in IoT subscription economics – illustrating how metrics that look exceptional during growth can conceal structural fragility.
Peak metrics (Q4 2020, pandemic era):
| Metric | Value | Assessment |
|---|---|---|
| Monthly ARPU | $99 (subscription) + ~$50 (amortized hardware) | Strong: $149 effective ARPU |
| Monthly churn | 0.65% | Exceptional: implies 12.8-year average customer life |
| LTV | $99/month / 0.0065 = $15,231 | Outstanding at 60% gross margin = $9,139 gross LTV |
| CAC | ~$1,600 (includes hardware subsidy + marketing) | LTV:CAC ratio = 5.7:1 – healthy |
| Payback period | $1,600 / ($99 x 0.60) = 27 months | Acceptable for premium hardware |
At these metrics, Peloton’s business model appeared exceptional. The company invested heavily in manufacturing capacity, content studios, and a $400 million acquisition of Precor.
Post-pandemic metrics (Q2 2022):
| Metric | Value | Change |
|---|---|---|
| Monthly ARPU | $44 (reduced subscription tiers) | -56% |
| Monthly churn | 1.41% | +117% (2.2x worse) |
| LTV | $44/month / 0.0141 = $3,121 | -79% |
| CAC | ~$1,800 (higher marketing needed post-hype) | +12.5% |
| LTV:CAC ratio | $3,121 x 0.60 / $1,800 = 1.04:1 | Underwater (below 3:1 minimum) |
| Payback period | $1,800 / ($44 x 0.60) = 68 months | 5.7 years (unsustainable) |
What went wrong (structurally):
Hardware subsidy trap: Peloton subsidized bikes by $400-600 per unit to lower the purchase barrier, betting that subscription revenue would recoup the investment. When churn doubled, the payback period exceeded the average customer lifetime – each new customer became a net loss.
Churn sensitivity: The LTV formula (ARPU / churn) means that doubling churn halves LTV. Peloton’s churn moving from 0.65% to 1.41% cut LTV by more than half – a $12,000 per-customer value destruction that no amount of cost-cutting could offset.
Connected hardware lock-in failed: Unlike SaaS products where switching costs are low and churn is expected, Peloton assumed that $2,000 hardware in customers’ homes would create permanent lock-in. Instead, customers simply stopped using the bike – the hardware became an expensive clothes rack, but subscription cancellation was one click away.
Lesson for IoT businesses: Hardware subsidies only work when churn is extremely low AND stable. If your IoT product relies on subscriptions to recoup hardware costs, stress-test your business model at 2x and 3x your current churn rate. If the LTV:CAC ratio drops below 3:1 at 2x churn, your business model has a structural fragility that growth can mask but not solve.
Scenario: Your company sells a smart HVAC control platform to commercial buildings. You need to calculate the 5-year customer lifetime value to justify a high customer acquisition cost.
Given metrics:
Step 1: Calculate monthly LTV contribution with churn
Month 1: $450 × 0.72 × 1.000 = $324.00 Month 2: $450 × 0.72 × 0.982 = $318.17 Month 3: $450 × 0.72 × (0.982)² = $312.44 … Month 60: $450 × 0.72 × (0.982)^59 = $112.08
Step 2: Sum 60 months of recurring revenue
Using geometric series formula: LTV_recurring = ARPU × Margin × Σ(retention^month) from m=0 to 59
With Excel: =4500.72SUMPRODUCT((0.982^ROW(A1:A60))) = $16,847
Step 3: Add one-time setup revenue
Setup LTV = $8,000 × 0.72 = $5,760
Total 5-year LTV = $16,847 + $5,760 = $22,607
Business decision: With this $22,607 LTV, the company can justify spending up to $7,500 CAC (3:1 ratio) or $4,500 CAC (5:1 target ratio) on sales and marketing. At current CAC of $6,200, the business has healthy 3.6:1 unit economics, suitable for moderate growth investment.
Key insight: The 1.8% monthly churn (vs hypothetical 3% churn) adds $5,200 to LTV – a massive difference justifying significant investment in customer success to maintain low churn.
When evaluating which IoT business model to pursue, use this comparison framework to assess revenue potential, risk, and resource requirements:
| Criterion | Hardware Sales | Platform-as-a-Service (PaaS) | Data Monetization | Hybrid (Hardware + Subscription) |
|---|---|---|---|---|
| Upfront revenue | High ($500-5K per unit) | Low ($0-500 setup) | Very low ($0) | Medium ($200-2K hardware) |
| Recurring revenue | None | High ($20-500/mo) | Medium ($5-50/mo) | High ($10-200/mo) |
| LTV:CAC potential | 1:1 to 2:1 (low) | 5:1 to 15:1 (excellent) | 3:1 to 8:1 (good) | 4:1 to 10:1 (very good) |
| Churn impact | N/A (one-time sale) | Critical (3% → 50% LTV loss) | High (5% monthly typical) | Critical (hardware sunk cost if churn early) |
| Cash flow | Immediate positive | Negative for 6-18 months | Slow ramp (year 2+) | Neutral to positive (hardware offsets) |
| Gross margin | 30-50% (manufacturing) | 75-90% (software) | 85-95% (pure data) | 60-75% (blended) |
| Customer lock-in | Low (purchase complete) | Medium (switching cost) | High (data network effects) | Very high (hardware + data) |
| Scalability | Limited (manufacturing) | Excellent (SaaS) | Excellent (marginal cost ~$0) | Good (hardware bottleneck) |
| Best for | Low-tech buyers, one-time need | Enterprise customers, predictable workloads | API consumers, data-driven orgs | Consumer IoT, SMB markets |
Decision tree:
Example application: A smart agriculture startup chooses Hybrid model – sells soil sensors at cost ($150 hardware, 20% margin) to acquire customers, then monetizes via $25/month irrigation management platform. Hardware reduces acquisition friction (farmer gets immediate value), recurring revenue builds over time, and 18-month payback period is acceptable given 4-year average customer lifetime in agriculture.
The mistake: A smart thermostat company celebrates a healthy 5:1 LTV:CAC ratio ($1,200 LTV / $240 CAC) and aggressively scales customer acquisition from 500 to 5,000 customers per month. Six months later, despite “profitable” unit economics on paper, the company runs out of cash and must raise emergency funding at a down round.
What went wrong? The LTV:CAC ratio looked healthy, but the payback period was 22 months:
Payback = CAC / (ARPU × Gross Margin) = $240 / ($15/month × 0.70) = 22.9 months
Cash flow impact:
When scaling from 500 to 5,000 customers/month:
| Month | New Customers | CAC Spend | Cumulative Profit from Previous Cohorts | Net Cash Flow |
|---|---|---|---|---|
| 1 | 500 | -$120,000 | $0 | -$120,000 |
| 2 | 1,000 | -$240,000 | +$5,250 (500 × $10.50) | -$234,750 |
| 3 | 2,000 | -$480,000 | +$21,000 (2,000 previous) | -$459,000 |
| 6 | 5,000 | -$1,200,000 | +$210,000 (20,000 previous) | -$990,000 |
| 12 | 5,000 | -$1,200,000 | +$1,260,000 (120,000 previous) | +$60,000 (first positive month!) |
| 18 | 5,000 | -$1,200,000 | +$3,150,000 (300,000 previous) | +$1,950,000 |
Cumulative cash burn through month 6: $3.2 million – despite every customer being “profitable” in LTV terms!
How to avoid this mistake:
Always calculate payback period: Payback = CAC / (ARPU × Margin). Target <12 months for VC-funded, <6 months for bootstrapped.
Model cash flow, not just profitability: Build a cohort-based cash flow model showing monthly spend vs cumulative revenue collection.
Raise capital before scaling: If payback is 22 months and you want to acquire 5,000 customers/month, you need $1.2M/month × 22 months = $26.4M working capital just to fund growth.
Improve payback before scaling: Reduce CAC (better targeting, referrals) or increase ARPU (upsells, annual prepay with 15% discount). Dropping CAC from $240 to $180 cuts payback from 22 months to 17 months – saving $5M in capital requirements for 5K/month customer acquisition.
Real-world data: A 2018 analysis of 30 failed IoT startups by CB Insights found that 11 (37%) cited “cash flow crisis despite profitable unit economics” as a primary failure factor. The median payback period among these failures was 26 months vs 11 months for successful peers.
Key lesson: LTV:CAC ratio measures eventual profitability, but payback period determines cash requirements. Fast growth with long payback periods demands massive capital. Either improve payback or secure sufficient funding before scaling.
Checkpoint: Cash-Flow Stress Test
You now know:
LTV:CAC says whether a customer can eventually become profitable; it does not say whether the company can afford acquisition today. A 5:1 ratio can still create a cash crisis when CAC is paid upfront and contribution margin arrives over 18-24 months. Always pair LTV:CAC with payback period and cash-burn timing before scaling acquisition.
Calculating LTV from subscription price alone hides device subsidy, connectivity, storage, support, warranty, payment fees, and field operations. A customer with high ARPU can still be unprofitable if video retention, cellular traffic, support calls, or truck rolls exceed the plan margin. Use contribution margin after cost-to-serve for LTV and payback.
Portfolio averages can hide failing cohorts. Self-serve SMB customers, enterprise pilots, reseller-led deals, and subsidized hardware bundles may have different CAC, activation rates, churn, support load, and expansion paths. Review metrics by cohort before changing pricing, channel spend, or onboarding investment.
This chapter covered the financial metrics essential for IoT business model analysis:
| Concept | Relates To | Relationship |
|---|---|---|
| LTV | Churn Rate | LTV inversely proportional to churn; reducing churn from 5% to 2% increases LTV by 2.5x |
| LTV | ARPU | LTV increases linearly with ARPU but multiplicatively with retention improvements |
| CAC | Payback Period | Payback Period = CAC / (ARPU × Gross Margin); faster payback reduces cash requirements |
| LTV:CAC Ratio | Business Viability | Ratio < 3:1 signals unsustainable unit economics; > 5:1 enables aggressive growth |
| Churn Rate | Customer Lifetime | Average lifetime (months) = 1 / Monthly Churn Rate |
Cross-module connection: This connects to Go-to-Market Strategy via customer acquisition channels and pricing strategy. See also IoT Business Model Fundamentals for revenue model selection.
This chapter covers financial metrics, explaining the core concepts, practical design decisions, and common pitfalls that IoT practitioners need to build effective, reliable connected systems.
IoT financial metrics must include the full lifecycle: hardware, connectivity, cloud, support, churn, replacement, and operational savings. A business case that counts only device margin will miss the costs that dominate at scale.