Chapters

12 Business Model Cases: Evidence Basics

applications
iot
business
models
business-models
subscriptions
economics
Listen
Uses your device's voice. Tap ▶ beside any paragraph to hear just that one.
  • Podcast audio coming soon
  • Character narration audio coming soon
Lecture
Video lecture coming soon. The slides are the lecture for now.
Ask AI
Pick a prompt. We copy it for you and open an AI service; paste it there. Nothing is sent to IoTClass.

12.1 Start with the Service Promise

An IoT business case explains how a connected product creates value, who pays for it, and whether the provider can afford to keep its promise. A useful demo does not prove that a service will save money. That decision needs a stated baseline, measurable change, costs and a test window.

A connected light above a warehouse aisle has stopped reporting. The building still needs safe light, and the service provider still has to send someone. Picture the factory choosing between buying connected lights and paying each month for light as a service. The monthly offer may lower the first cost, but it ties value to long-term operation, repair, data and a supplier that must remain able to serve.

The problem is to connect that continuing promise to evidence of value and the physical cost of delivery. We will follow the customer job and money path, separate observed benefits from assumptions, then price a missing repair visit. These approaches let you analyze a business model transformation, calculate revenue and contribution, assess success factors and extract lessons that another site can actually test.

This chapter assumes familiarity with revenue, margin, capital expenditure (CapEx), operating expenditure (OpEx) and competitive positioning. IoT Business Model Fundamentals explains the value loop; Pricing Strategies helps connect the offer to what customers pay for.

KEY CONCEPTS

  • IoT business model

    How an IoT product or service creates, delivers and captures economic value.

  • Recurring revenue

    Ongoing income from subscriptions, data services or maintenance contracts following the device sale.

  • Total cost of ownership (TCO)

    The complete cost of acquiring, deploying and operating an IoT system over its full lifecycle.

  • Value proposition

    The benefit for a specific customer segment that differentiates the offer from alternatives.

  • Platform business model

    A strategy enabling third parties to build applications on device data or connectivity infrastructure.

  • Hardware-as-a-Service (HaaS)

    Recurring fees for hardware instead of an outright purchase reduce upfront cost barriers.

  • Churn rate

    The percentage of subscribers cancelling in a given period indicates recurring revenue business health.

12.2 Part Objectives

  • Build an IoT business case from a stated baseline and measurable change.
  • Separate observed benefits from assumptions and transfer limits.

12.3 Follow the Value and the Money

Start with the customer job: the result they will pay for, such as safe light, lower energy use or less repair work. Separate that result from a device feature. A live chart has no value if it does not change a useful choice. The service relationship lasts beyond installation, so the supplier must keep delivering that result to sustain the payment relationship.

A business model describes how a company makes money. Moving from a one-time light-bulb sale to an ongoing lighting service changes when revenue is captured, who owns operating risk and how long the provider must deliver value. Like buying a DVD versus subscribing to a streaming service, the recurring model builds a longer relationship and may earn more over time. Hardware becomes a platform for that relationship rather than the end of the transaction.

Lighting-as-a-Service (LaaS) sells illumination outcomes through a subscription instead of selling light fixtures. Other patterns capture continuing value differently: razor-and-blade subsidizes hardware to drive recurring ecosystem revenue, while data monetization converts sensor data into sellable insights with proper consent. Customer lifetime value (LTV) is total revenue from a customer over the entire relationship. It depends on how long that relationship lasts.

Draw the value path before adding benefits. Who buys, uses, installs, supports and benefits? A building owner may pay while tenants feel the change, and a service team may carry the repair cost. Keep each role visible. If a customer pays the subscription while a tenant saves electricity, the benefit and invoice land with different people. The offer must explain why the payer accepts that split. Lower energy use may help the tenant; fewer repair calls may help the owner. Counting the same avoided visit as a saving for both inflates the case.

Then draw the money path for one unit and one year. Include hardware, installation, setup, support, failed visits, replacement, service work and end of life. Price the worst common site as well as the easy pilot. Ask a support worker to price one hard case and a customer to explain the value in their own words. A gap between those answers is a useful warning: the promise and the work required to deliver it may not match.

12.4 Separate Evidence from Transfer Assumptions

With the roles and costs visible, ask what the case actually establishes. State each public fact with its source and date, and mark estimates as estimates. Public examples such as Philips/Signify’s Lighting-as-a-Service at Schiphol show the service pattern. They do not reveal every private cost or guarantee future demand. A success story may omit failed sites as well as costs; missing detail is not proof. The financial example in the next section is illustrative, not reported company economics.

Use the same questions on each case: customer job, payer, benefit, evidence, operating work, data use, failure, exit and scale. This makes unlike offers easier to compare without copying their surface features. Record the transfer limit: a model that works in a dense city may fail at remote sites, an owned-building plan may fail with tenants, and a premium product may carry support costs that a low-price unit cannot.

Test the joined operation. Remove the outside service, change the account owner, replace a unit and end the contract. Ask what the customer can still do, which records they receive and who pays to remove or keep the equipment. Check the data promise too: name each fact collected, why it is needed, who can see it, how long it stays and whether the customer expects that use. Selling or sharing a record creates another value path and another risk; it is not free income.

Run a small scale test by multiplying support calls, failed units, travel, storage and service load by the planned customer count. Add a bad month and a slow-paying customer. Compare cash timing with the cost of keeping the promise. Keep an open-risk list with an owner and next test. A business case is a decision record: it should make the reason to stop as clear as the reason to invest.

12.5 Asset Tracking Unit Economics

Review the case after a year of real service. Compare planned and actual work, loss, exit and customer use, keeping the old plan beside the result. A miss is evidence for the next offer. For the financial record beyond this chapter, Business Model Cases: Proposals and Economics develops the economics. Asset Tracking Unit Economics Contracts covers per-device recurring margin, LTE-M connectivity and cloud costs, hardware subsidy payback, reporting-frequency sensitivity, churn risk, lifecycle state and cost tags that let finance reconcile telemetry with subscription economics.

12.6 Price the Missing Repair Visit

Now apply those evidence questions to the lighting promise. Take an illustrative service with 20 fixtures at £6 per fixture each month. Recurring revenue is 20 × £6 = £120 per month. Assume routine running costs of £40 per month. The remaining £80 is a contribution toward hardware, installation and other costs; it is not yet profit. Over a full year with no cancellations, that contribution is £960.

Include a repair visit costing £160 for travel and labour. One visit consumes two months of contribution: £160 divided by £80 per month equals 2 months. If the model assumed that customers would replace failed lamps while the contract promises provider repair, the economics omit a real obligation. A dashboard cannot close that gap. Provider work must appear in provider costs, alongside the hardware and installation still to be recovered.

Distinguish a measured visit rate from an estimate. Suppose a short pilot observes one failed fixture among 20. That establishes that replacement work occurs; it does not establish an annual failure rate for every building. Older wiring, higher mounting points and travel distance may change the next site’s ownership cost. Measure local repair frequency and cost before using a public case to price the service.

A second £160 visit during the year reduces the £960 contribution to £640 after both visits. If the customer cancels halfway through the year, the provider cannot claim twelve months of recurring revenue. The recurring offer therefore depends on who performs the work, when cash arrives and which risk continues after the device sale. Keep payback, contract length, pricing and data value tied to explicit assumptions as the financial record develops.

Check knowledge

Test the service relationship, contribution calculation and evidence needed to price repairs.

Check knowledge

Summary

A reviewable IoT business case starts with a baseline and customer result, then follows the value and money through every role. Recurring income extends the provider’s obligations. Separate public facts, local measurements and estimates, and keep the limits on transferring a case visible.

The lighting example leaves £80 a month before hardware, installation and other costs. Each £160 repair visit consumes two months of that contribution. Service work, cancellation, cash timing and exit belong in the decision record alongside the promised benefits.

Price the work required to keep the promise, and measure what a borrowed success story cannot establish at your site.

Carry this evidence into Business Model Cases: Transfer and Lighting Services, which begins with Case Studies as Transfer Tests.

Hi, I’m Ada. What do you need?

Find help

Let’s find what you need

Find a lesson or return to your module guide.

Give feedback

Help improve this chapter

Tell us what helped or what needs fixing.

Tips

Try a small next step

A few ways to get more from this chapter.

Ask AI

Continue the conversation

Take the conversation further with your preferred assistant.

AI help is available in supported modules when enabled in Settings.

No live person answers on independent study. Feedback does not promise a personal reply.

For welfare or safety concerns, follow your school’s procedures outside IoTClass.