IoT Business Model: From Projects to Recurring Revenue

An IoTITermIoT (Internet of Things)The IoT (Internet of Things) is the network of physical objects with sensors, software and connectivity that collect and exchange data and act autonomously.View profile business model built only on installation projects makes an integrator start from zero every quarter, and recurring services change that math.

Tomás runs a 12-person integration firm that installs irrigation and greenhouse monitoring for farms. Spring is always busy. By September, the order book is empty again, and his team spends autumn chasing new projects while the systems they installed keep running for free.

Then a cooperative asked him a question he couldn't answer: who watches the alarms on a Sunday in August? Nobody did. That question became his first monitoring contract, and three years later monthly services pay his fixed costs before the first project of the season.

This guide explains how integrators and device manufacturers can shift their IoT business model from one-off projects toward recurring revenue: the revenue layers available, how to package services, which pricing models work, how cash flow changes, and what to put in the contract. The partnership side, meaning how to work with a platform provider, is covered in the article on IoT partnership models.

Why Project-Only Revenue Stalls an IoT Business Model

Selling services around products is an old idea. Sandra Vandermerwe and Juan Rada called it the servitization of business in 1988, long before sensors were cheap enough to connect. IoT makes that shift easier, because the product reports its own condition and the service can be delivered remotely.

Project-only revenue has three problems for an IoT integrator:

• It's lumpy. Revenue arrives when projects close, while salaries arrive every month.
• It ignores the longest phase. An IoT system runs for years after installation. Updates, alarms, battery changes, and new users all happen after the project invoice.
• It undervalues the company. A business with contracted monthly revenue is easier to plan, to finance, and to sell than one that depends on next quarter's wins.

Clients also change their expectations once the system runs. In Cisco's 2017 IoT survey, the most successful organizations were the ones that worked with partners at every stage, from strategic planning to data analytics after rollout. That later work is where recurring revenue lives.

Five Revenue Layers in an IoT Business Model

Most integrators already sell the first two layers. The other three are where recurring revenue comes from.

Hardware and Projects Still Matter

Hardware margins get thinner every year, and projects remain the way most clients start. Keep both, and use them to open the door. A well-run first project is the best argument for the monthly contract that follows.

The Three Recurring Layers

The platform subscription is the easiest to add, because the client already understands software licenses. Selling it under your own brand, with your domain and your logo, makes it your product. The guide to white-label IoT platforms explains what that requires.

Managed services are the layer clients value most and competitors copy least. They include alarm handling, device health checks, battery replacement planning, user support, and monthly reports. Each one saves the client a task they don't want to staff.

Data and optimization services come last, once you have history. A report that shows which pumps run outside their range, or how much energy a building wastes at night, turns data into a decision the client is willing to pay for.

Packaging Recurring Services Clients Will Pay For

Clients buy outcomes they can explain to their managers. A list of 40 features is hard to approve. Three clear tiers are easy.

Rules That Keep Tiers Profitable

• Price per device or per site, per month. Both scale with the installation and are easy to check.
• Set a minimum term. Twelve to 36 months covers onboarding costs and gives both sides time to see results.
• Write down the hours. "Monitoring" without hours invites calls at 3 a.m. that the price doesn't cover.
• Include an annual price review. Connectivity, salaries, and platform costs change.
• Define what's extra. New integrations, extra dashboards, and site visits outside the plan should have a published rate.

Back to Tomás. His Monitored tier covers alarm handling from 7:00 to 22:00, every day of the year, and a monthly report per farm. Nights are covered by automatic calls to the farmer. Clients who want 24-hour coverage move to Managed, which costs more and includes an on-call technician.

Selling the First Monitoring Contract

The easiest clients to convert are the ones you already installed. They know your team, the system is running, and you can see their data. Offer three months of the Monitored tier at no charge, and send a monthly report that lists every alarm your team handled and what happened next. At the end of the trial, the conversation is about a service they have already used.

The Team Behind the Service

A monitoring service needs people with defined roles, even in a small company. Someone watches alarms and follows the escalation list. A technician handles site visits and device replacements. An account manager reviews the monthly report with the client and spots new needs. In a firm of 12, those can be three people who share the work, as long as the rota is written down and every alarm has an owner.

Pricing Models: Per Device, Per Site, or Per Outcome

The pricing unit shapes how clients perceive the service and how your revenue grows.

Per Device or Per Site

Per-device pricing is transparent and grows with the installation. It works well for sensors that are similar and numerous, such as meters or tank level probes. Per-site pricing fits better when the number of devices varies but the service effort depends on the location, such as a building or a farm.

To set the number, start from your own cost per device per month, including platform, connectivity, and the hours your team spends. The guide to IoT platform cost shows how to calculate it over five years.

Product as a Service

Some manufacturers go further and keep ownership of the hardware. In their 2014 article in Harvard Business Review, Michael Porter and James Heppelmann described product-as-a-service models, where the manufacturer retains ownership and takes responsibility for operating and servicing the product in return for an ongoing charge.

The model removes the client's upfront purchase, which helps sales. It also shifts the financing to you, and the same article notes that it can lower the client's cost of switching to another supplier. Before offering it, make sure you can fund the hardware and that the contract term covers its cost.

Per Outcome

Outcome-based pricing ties the fee to a result, such as a share of the energy saved. It can win large contracts, but it requires a baseline both sides accept, reliable measurement, and a client who won't change the process without telling you. Most integrators should start with per-device or per-site pricing and add an outcome bonus once they have a few years of data.

Want to see how other partners have built services on the platform? The success cases show projects in several sectors.

Cash Flow and the Metrics That Matter

Moving to recurring revenue changes when the money arrives. A project pays most of its value within a few months. A subscription pays the same value over three years. During the transition, cash gets tight.

A Simple Model

Assume an integrator signs 10 new clients a year, each with 200 devices, and earns a net margin of €3 per device per month on services. Each client adds €600 of monthly margin. If one client leaves every year from the second year on, the monthly margin looks like this:

The figures are illustrative, but the shape is real. Each year starts with more contracted revenue than the one before. The first year is the hardest, because the team is doing the work while the margin builds up slowly.

Ways to Ease the Transition

• Charge installation up front. Keep one-time work as a one-time invoice.
• Offer a discount for annual prepayment. Cash arrives earlier, and the client saves.
• Start with your installed base. Converting existing clients costs less than winning new ones.
• Use leasing for hardware. A financing partner can carry the devices while you keep the service.
• Keep some project work. Projects fund the team while monthly revenue grows.

Clara's company learned the importance of these rules the hard way. It makes air quality sensors and decided to include the hardware in a monthly fee. Twenty contracts in six months left the company paying for 3,000 sensors up front with income spread over three years. The fix was to charge installation and a hardware deposit at signature and keep the service in the monthly fee.

Five Numbers to Track Every Month

1. Monthly recurring revenue (MRR). The contracted monthly income from services and subscriptions.
2. Churn. The share of recurring revenue lost to cancellations or downgrades.
3. Gross margin per tier. Revenue minus platform, connectivity, and team hours for each tier.
4. Payback on acquisition. How many months of margin it takes to recover the cost of winning the client.
5. Average contract length. Longer terms protect the cash spent on onboarding.

Contracts, Data, and Responsibilities

A recurring contract lasts years, so the details matter more than in a one-off project. These clauses prevent most disputes:

• Service levels. Response times per severity, hours of coverage, and what counts as an incident.
• Scope of monitoring. Which alarms your team handles, and which ones go directly to the client.
• Connectivity. Who pays for SIM cards or network fees, and what happens when a site loses coverage.
• Hardware lifecycle. Who replaces batteries and failed devices, and how end-of-life models are handled.
• Data. Who owns the data, how long it's kept, and how it's returned when the contract ends.
• Termination and handover. Notice periods, what happens to devices you own, and how the client's users keep access during the transition.

Write these clauses in plain language. The person who signs the renewal in three years probably wasn't in the room when the contract was negotiated, and a clear page saves a long meeting.

The data clause has a legal side in the European Union. According to the Commission's Data Act explainer, users of connected products, whether they own, rent, or lease them, can access the data those products generate and share it with third parties. A business model that depends on keeping the client's data locked away won't work there. The value has to come from the service, the analysis, and the response time.

Integrations deserve their own clause too. If your service sends billing reads to the ERP or opens work orders, the guide to IoT platform API integration lists what to agree before you connect systems.

Choosing a Platform That Fits a Recurring Model

The platform decides how much each new client costs you to serve. For a recurring IoT business model, check these points:

• White-label. The client sees your brand on the web, in the mobile app, and in notifications.
• Multi-tenancy. Each client has an isolated space, and your team manages all of them from one place.
• Alarm routing. Alarms can go to the client, to your operations team, or to both, depending on the tier and the time of day.
• Usage visibility. You can count devices and data per client, which makes billing simple.
• APIs. Your billing, ticketing, and reporting tools can read from the platform.
• Deployment options. Cloud for most clients, and on-premise for those whose rules require it.

A pilot that grows into a monitored service follows the same path described in the guide to taking an IoT prototype to production. In industrial clients, the guide to industrial IoT implementation shows where a running service fits after the project ends.

Cloud Studio IoT was built for this B2B2B model: we provide the platform, partners build and sell their own solutions on it, and the end client sees the partner's brand. Plans are based on devices and variables, which makes it easier to price your own tiers. The pricing page shows the current plans.

Key Takeaways

• A project-only IoT business model leaves revenue lumpy and ignores the years the system runs after installation.
• Recurring revenue comes from three layers: platform subscription, managed services and monitoring, and data and optimization services.
• Three clear tiers with written hours, minimum terms, and an annual price review are easier to sell and to run than a long feature list.
• Per-device or per-site pricing is the safest start. Product-as-a-service and outcome-based pricing need funding and reliable baselines.
• The transition squeezes cash in the first year. Track monthly recurring revenue, churn, margin per tier, acquisition payback, and contract length.
• Under the EU Data Act, value has to come from the service, not from holding the client's data.

If you want to add recurring services to your IoT projects under your own brand, see the partner program or talk to the team and bring your current service catalog.