Every integrator wants recurring revenue. A managed service promises it: instead of being paid once to install a system, you are paid every month to run it. Done well, it turns a lumpy project business into a predictable one and raises the value of the whole company.
The problem is that recurring revenue and recurring profit are not the same thing. Plenty of IoT managed services bring in a steady monthly fee and still lose money, because support load and infrastructure costs grow faster than the revenue does. The model leaks margin in places that do not show up until you have signed enough customers to feel it. Here are the unit economics that separate a profitable managed service from a busy one.
The revenue layers
A healthy managed service is not one fee. It stacks:
- Platform access, the base monthly fee per device, site, or seat.
- Monitoring and support, the service of watching the system and responding when something breaks.
- Outcomes, higher-value work like reporting, optimization, and compliance evidence that customers pay a premium for.
The base fee keeps the lights on. The margin lives in the upper layers, so a model built only on platform access is the hardest one to make profitable.
The costs that leak margin
Two cost drivers quietly eat managed-service margin.
The first is support. Every customer call, every manual fix, every “can you just check this” is unpriced labor if you have not accounted for it. A handful of high-touch customers can erase the profit from a dozen low-touch ones.
The second is infrastructure. If you build and run your own cloud platform under the service, you carry the cost of hosting, securing, scaling, and patching it forever, plus the engineers who do that work. That cost grows with every customer and rarely shrinks.
Gross margin targets
Treat the managed service like the software business it is, not like a reseller markup. The goal is a gross margin where the recurring revenue comfortably covers the cost to deliver, with room left to invest in growth. If a new customer adds as much cost as revenue, you have a busier business, not a better one. Model the margin per customer before you sign, including support time, not just the platform fee.
What to automate
Profit in a managed service comes from serving more customers without adding people. That means automating the work that does not need a human: device onboarding, health monitoring, alerting, routine reports, and the first response to common issues. The more of the support layer you automate, the more customers each person can carry, and the more the margin holds as you grow.
Manual heroics do not scale. Automation is the difference between a service that gets more profitable with size and one that gets more painful.
Pricing tiers that protect margin
Flat pricing punishes you for your best customers and rewards your worst. Tier the service so heavy users pay for the load they create: by device count, by data volume, by support level, or by the value of the outcomes you deliver. Give customers a clear reason to move up a tier as they grow, so your revenue grows with their usage instead of lagging it.
The traps to avoid
Underpricing support to win the deal. Building your own platform when you could run on one and keep your engineers on customer value. Flat fees that ignore usage. Saying yes to bespoke work for every customer until you are running a custom shop with a subscription invoice. Each one feels like growth and quietly removes the profit.
TagoIO is built to be the platform layer under a managed service, so you carry the recurring revenue and the customer relationship while the platform carries hosting, security, scale, and multi-tenant separation. Your engineers stay on the work customers pay a premium for.
Model your managed service on the free plan, or book a demo to talk through the economics for your customer base.
