13 Business Model Cases: Transfer and Lighting Services
More
Depth: Practitioner
Progress saves as you read. Mark sections complete as you go; your progress appears in the sidebar.
- Podcast audio coming soon
- Character narration audio coming soon
13.1 Test What Transfers
An IoT business-model case study helps you decide what can transfer to a different product, customer segment, or operating environment. A famous case can fail when its pricing, network, or customer duty changes. Building on Business Model Cases: Evidence Basics, this chapter separates public facts, teaching calculations, and team assumptions before using a case to make a decision.
Consider the managed-lighting example: a team wants to apply Philips/Signify’s service pattern to its own buildings. Efficient LEDs alone do not make the pattern transferable. The provider must measure the outcome, finance the asset, maintain the installed base, and price the service below the customer’s alternative cost. The problem is deciding whether those conditions hold locally. We will first extract the evidence, then compare revenue patterns, and finally test the lighting-service economics.
A transfer test asks whether the mechanism behind a public case can work under a new set of conditions. Ask three questions. What changed in the offer: ownership, risk, payment timing, data rights, or decision support? What connected capability made that change credible: metering, remote diagnostics, firmware updates, identity, billing, or analytics? What evidence would break it here: churn, support cost, financing cost, regulatory limits, poor telemetry quality, or weak customer willingness to pay?
The same questions apply to Rolls-Royce’s Power-by-the-Hour pattern. Charging by usage works because engine hours are measurable, maintenance risk matters to the customer, and the provider has an operational capability the customer is willing to outsource. A case becomes actionable when the review identifies both the attractive mechanism and its failure condition.
KEY CONCEPTS
- Transfer conditions
Test the capability and the failure condition behind the headline.
- Evidence labels
Separate public facts, illustrative economics, and team assumptions.
- Operating obligations
Match the party earning revenue to control of service costs.
- Lighting service
Trace ownership, maintained illumination, and payments over time.
13.2 Learning Objectives
- Separate case-study facts, assumptions, decisions, and outcomes.
- Test Peloton, Ring, and lighting-service patterns in a new context.
13.3 Build an Evidence Record
For the lighting team, the first approach is a record that connects each commercial claim to operating evidence. Begin with the question in the first column, extract the evidence in the second, and apply the local transfer test in the third. Continued customer value supports a recurring-value claim; auditable signals support billing and renewal; control of the largest cost driver supports risk ownership. Naming the fragile assumption makes the record useful for review.
| Case-study question | Evidence to extract | Transfer test |
|---|---|---|
| What value is now recurring? | Subscription fee, usage fee, outcome payment, attach-rate revenue, or governed insight product | Can the customer keep seeing value after the device is installed? |
| What does connectivity prove? | Uptime, consumption, maintenance state, entitlement, environmental condition, or user behavior | Is the signal auditable enough for billing or renewal decisions? |
| Who owns operating risk? | Provider, customer, channel partner, insurer, cloud operator, or data producer | Does the party paid for the service also control the largest cost driver? |
| What can invalidate the economics? | Churn, subsidy payback, cloud cost, field service labor, privacy constraints, or sales cycle length | Which assumption would make the public case fail in this deployment? |
Here is the record filled in for the illustrative lighting service at a large facility. The customer pays for light over time. The provider owns the lights and pays for their care. The table above asks what value lasts, what data can prove, who bears risk, and what could go wrong. The record below gives an answer and a local check for each question.
| Case-study question | Evidence to extract | Transfer test |
|---|---|---|
| What value is now recurring? | The customer pays $18K/month for light as a service. Over 180 months, that is $3.24M. | Check that the customer still values the light and the service after installation. |
| What does connectivity prove? | Uptime and energy data can support billing and renewal. No local readings are yet given. | Check that the meter data can be audited before using it for bills. |
| Who owns operating risk? | The provider owns the lights and handles maintenance and replacements. | Check whether the provider can control those costs under the contract. |
| What can invalidate the economics? | The model assumes a 50% cut in electricity cost and $2.7M in provider costs. | Test the energy assumption, actual maintenance cost, and financing terms. |
Read across each row from the claim to the local test; pilot in three buildings only if the checks support the margin target after six months.
Keep three kinds of claim distinct. Verified facts are what the public source supports: a named customer, model pattern, launch, service scope, pricing mechanism, or stated operational outcome. Illustrative economics are teaching models, such as a 36-month lifetime value (LTV), a hardware subsidy payback, or a 15-year net present value (NPV) comparison. They are not company financials unless the source reports them. Decision assumptions are the numbers the team must own.
Those assumptions include attachment rate, device bill of materials, Stripe Billing or Chargebee subscription cost, LTE-M or NB-IoT connectivity cost, cloud ingestion on AWS IoT Core or Azure IoT Hub, and warehouse and transformation cost in BigQuery, Snowflake, or dbt. Support burden, warranty exposure, churn, and sales cycle belong in the same record. Labeling them keeps a public service launch distinct from modeled savings, a proposed local pilot, and its eventual measured results.
Build one brief per model pattern. State the old and new offer in one sentence each, identify the connected capability that changes the money flow, and trace the evidence from device data to a commercial decision. For lighting, occupancy and energy data lead to uptime evidence, maintenance scheduling, invoices, and renewal proof. For an agricultural data product, machine telemetry and field context lead through aggregation, anonymization, consent records, and analytics outputs to buyer value. For a subsidized consumer device, identity, entitlement, subscription status, engagement, and payment retention support the ratio of lifetime value to customer acquisition cost, or LTV:CAC.
A data contract defines the rules that make these signals usable, including identity, consent, retention, aggregation, and lineage. The technical detail follows the connected obligations so engineering, finance, legal, and customer-success teams can test them together.
13.4 Case Study as Data Contract
An IoT business-model case spans four contracts. The device contract defines captured telemetry, its trustworthiness, and the events usable for operating or billing claims. Usage-priced compressors, lighting systems, and engine services need readings that are timestamped, attributable to the correct asset, resilient to outage, and reconciled when a gateway reconnects.
The data contract covers identity, consent, retention, aggregation, and lineage. A buyer may want benchmarks, but the platform still needs a lawful, trusted path from raw farm, building, home, or fleet telemetry to an aggregated product that cannot expose an individual customer.
The commercial contract turns signals into money. Subscriptions need entitlement state, plan changes, failed-payment handling, taxation, and revenue recognition. Usage pricing needs metering windows, dispute handling, minimum fees, overage logic, and audit trails. Outcome pricing needs a defensible counterfactual or a narrower proxy, such as measured operating hours instead of “failures prevented.”
The operating contract assigns costs when field performance differs from the spreadsheet: device returns, truck rolls, firmware defects, cloud outages, cybersecurity incidents, consent withdrawal, and customer-success labor.
Read the architecture and unit economics together. AWS IoT Core, Azure IoT Hub, MQTT brokers, device identity services, billing platforms, data warehouses, and customer relationship management (CRM) systems determine what the business can prove. The architecture must connect telemetry to entitlement, service cost, customer account, and consent status. A mature review produces a narrative model record for executives and a data-contract checklist for the teams testing launch readiness.
End the review with a decision that names the model, evidence, financial guardrail, and review point. For example: “Pilot outcome-based lighting in three buildings only if metered uptime, maintenance cost, and financing terms keep gross margin above target after six months.” That gives the team a basis to stop, revise, or scale.
13.5 Compare How Value Recurs
With the evidence record in place, compare what changes between the first sale and continued service. A product sale captures most value at purchase; a service captures value repeatedly as the provider maintains outcomes or insights. A lighting supplier can move from fixture margin to recurring payment for maintained illumination. A device maker can discount hardware to grow an ecosystem, but must compare lost device margin with subscriptions, consumables, or platform revenue. A fleet platform selling aggregated operational insights must test consent, data quality, customer segmentation, and support costs before treating the data product as defensible.
The consumer cases expose different risks. Peloton uses premium hardware to create an installed base, while its recurring class subscription carries the long-term margin. High customer acquisition cost and inventory exposure can pull LTV:CAC below a healthy target. Ring uses affordable hardware as a wedge into the home. Optional video storage, multi-device attach, neighborhood/network effects, and ecosystem integration create recurring value; privacy governance is part of that model.
Smart data pricing can charge for connectivity by usage, time, location, priority, transaction, or third-party sponsorship. In cellular IoT, pooled or sponsored connectivity can remove adoption friction and enable service revenue, making it more valuable than charging every user directly. Across these patterns, compare the first sale, recurring revenue mechanism, customer trust boundary, and metric that demonstrates sustainability.
The Sensor Squad’s treehouse offers a smaller version of the same choice. It has smart lights, a weather station, and a snack machine. Temperature Terry proposes selling it for $100: build it, sell it, and finish the job. The LED proposes $2 per week while keeping the lights working. After one year that is $104, more revenue than the sale, with repairs still the provider’s responsibility. The microcontroller proposes a free treehouse with $1/week snacks and weather reports. The battery compares the plans:
| Plan | Sell the treehouse | Maintain it as a service | Offer it free with paid extras |
|---|---|---|---|
| Revenue | $100 once | $2/week = $104/year | $1/week snacks = $52/year |
| Continuing duty | Done after the sale | Fix everything forever | Keep the snacks appealing |
| Ownership | Friend owns it | Provider still owns it | Friend gets it free |
| Scale example | One friend = $100 | One friend = $104+ | Ten friends = $520/year |
Bella’s observation that more users mean more snack sales captures the free-hardware model’s attraction. The recurring totals are revenue, however, and the continuing service or snack duty still matters. Renting, servicing, or bundling a connected product can earn steadier long-term revenue than treating the device sale as the whole business.
A subscription means paying regularly, like a magazine delivery. A razor-and-blade model supplies the handle cheaply and earns from the blades; the treehouse’s paid extras illustrate the same idea. A service provides continuing help. Lifetime value tracks a customer’s value over the relationship; the treehouse’s simple revenue version counts the money one customer pays over many years.
To turn these comparisons into a record, identify the old model, connected capability, money flow, and risk boundary. Separate one-time hardware revenue, recurring service revenue, operating savings, and data-driven value. Financing, churn, maintenance cost, consent, security, and adoption can each invalidate an attractive spreadsheet.
The Business Model Fundamentals canvas supplies the full nine-block view behind a five-field record: customer problem, connected capability, revenue mechanism, cost driver, and renewal evidence. Pricing Strategies connects that logic to pricing and margin decisions. IoT Use Case Case Studies helps compare the commercial mechanism with operating deployment evidence.
13.6 Test the Lighting-Service Shift
Return to the lighting team with the same question: what changes when the provider sells an operating result instead of shipping an asset? Philips Lighting, now Signify, moved part of its commercial business from one-time fixture sales toward managed services. LED fixtures last longer and become easier to compare, creating a reason to earn from performance, maintenance, upgrades, and energy outcomes as well as hardware.
In 2015, Schiphol Group, Cofely, and Royal Philips announced a Lighting-as-a-Service arrangement for Schiphol airport terminal buildings. Lighting-as-a-Service here means paying for light used while the provider retains the fixtures and installation. The public case states that Schiphol pays for the light it uses, Philips keeps ownership, and Philips and Cofely take responsibility for performance, durability, and end-of-life reuse or recycling. Public case material also reports substantially lower energy consumption than conventional lighting.
These verified facts establish the public arrangement. The comparison below shows how the offer changes ownership, operating duties, and incentives. Accounting and tax treatment still depend on the contract and applicable rules.
| Metric | Traditional Fixture Purchase | Lighting-as-a-Service | Change |
|---|---|---|---|
| Revenue Type | One-time hardware sale plus maintenance projects | Recurring service payment for light used | Cash timing differs; accounting treatment depends on the contract |
| Customer Payment | Large upfront fixture purchase | Lower upfront payment; recurring service fee | Adoption friction moves from capital budget to operating budget; tax treatment depends on the contract and applicable rules |
| Asset Ownership | Customer owns luminaires and replacement risk | Provider retains ownership of lighting assets | Provider has incentive to design durable, repairable equipment |
| Maintenance | Customer or facilities contractor manages failures | Service provider manages performance and durability | Operational burden shifts away from the customer |
| Circularity | End-of-life handling is a customer problem | Provider plans reuse/recycling at end of life | Product design and service economics become linked |
| Energy Savings | Customer captures savings after purchase | Contract can align service fee with efficient illumination | Efficiency becomes part of the value proposition |
Now separate that public case from a teaching calculation for a large facility. The following is a Schiphol-style illustrative model, not reported Schiphol contract pricing. It compares two ways to serve the same facility over 15 years, before discounting.
| Cost or obligation | Traditional purchase, illustrative | Lighting service, illustrative |
|---|---|---|
| Upfront hardware | 10,000 LED fixtures at $150 each = $1.5M | Zero upfront hardware cost |
| Maintenance | $75K/year × 15 years = $1.125M | Provider guarantees performance and handles maintenance |
| Service payment | No recurring service fee in this comparison | $18K/month × 180 months = $3.24M |
| Electricity | $500K/year × 15 years = $7.5M | Assumed 50% reduction saves $250K/year; remaining electricity totals $3.75M |
| Customer total | $10.125M over 15 years | $3.24M service + $3.75M electricity = $6.99M |
| Position after 15 years | Customer owns aging equipment | Customer pays for service outcomes instead of owning obsolete hardware |
Against the $10.125M purchase model, nominal customer savings are $3.135M. The 50% energy reduction is an assumption relative to the alternative LED purchase. It is distinct from the public case’s report of lower consumption compared with conventional lighting. Keep that distinction visible: a verified service arrangement does not verify this particular savings forecast.
The provider’s calculation tests the other side of the contract. Illustrative service revenue is $3.24M over 15 years. Hardware costs are $1.5M initially plus $300K in replacements, or $1.8M. In-house maintenance costs another $900K, bringing the modeled cost to $2.7M. Gross profit is therefore $3.24M − $2.7M = $540K, a 16.7% margin on revenue, paid over time. Retaining the customer relationship can also enable future upsell into smart building integration and data analytics.
The customer saving and provider margin answer different questions. The local transfer test still needs metered uptime, actual maintenance cost, and financing terms. Payment over time matters because the provider retains the lighting assets while taking on performance and durability obligations. This is why the review must connect the ownership shift to the evidence and costs that sustain the service.
Summary
A transferable IoT case connects an offer change to a connected capability, a money flow, and a testable risk boundary. Separate public facts, illustrative economics, team assumptions, decisions, and measured outcomes. The evidence record should trace telemetry through data rights, entitlement, billing, service costs, and renewal proof.
The lighting example shifts ownership and maintenance duties alongside revenue. Its illustrative customer savings and provider margin help test a proposal, while metering, financing, and operating evidence determine whether that proposal can work locally.
Transfer the business mechanism only after testing who can measure the promised outcome, control its costs, and carry its operating risk.
Carry this evidence into Business Model Cases: Unit Economics, which begins with “Deep dive: Putting Numbers to It.”

