The most honest conversation in IoT is rarely the one that happens during the sales pitch. It happens later, usually mid-project, when an engineer is three weeks deep into writing custom middleware that should not have been necessary, or when a client asks why the dashboard cannot carry their brand name, or when a platform that performed beautifully in a proof of concept starts to show cracks at production scale. By that point, the platform decision has already been made, and walking it back is expensive in every sense of the word.
IoT deployments are failing not because the engineers are incompetent and not because the hardware is unreliable. They are failing because the platform layer, the connective tissue between devices and decisions, was chosen for the wrong reasons. It was chosen because a vendor offered a discount, because a competitor was already using it, or because someone read an industry report and pointed at the top-right quadrant of a magic quadrant chart.
For system integrators specifically, this is not just a technical inconvenience. It is a business risk that compounds with every project added to the portfolio.
The integrator is not the end user, and that distinction matters enormously
Most IoT platforms are designed with the end customer in mind. The factory manager. The building operator. The city planner. The user interface is polished. The marketing materials are glossy. But the system integrator, the company that actually has to wire everything together, connect the legacy systems, manage the API handshakes, and deliver a working solution on time and within budget, is largely an afterthought in how these platforms are architected.
System integrators need something fundamentally different from what end users need. They need a platform that can be white-labelled so their own brand remains front and centre. They need multi-tenant architecture so one deployment can serve many clients without turning into a management nightmare. They need device management that works across heterogeneous hardware ecosystems, because no client ever has a clean, single-vendor device portfolio. And they need reliable, well-documented APIs that do not require a team of specialists to interpret.
Most enterprise IoT platforms fail on at least two of those four requirements. And when they fail, it is the integrator who absorbs the consequences.
The hidden cost that never shows up in the RFP
Procurement teams evaluate IoT platforms on connectivity protocols, pricing tiers, and uptime guarantees. What rarely appears in a request for proposal is the cost of integration friction. The hours spent writing custom middleware to bridge incompatible data formats. The client relationship strain when a dashboard cannot be customised to reflect the client’s branding. The technical debt that accumulates when a platform’s architecture was not designed for multi-site rollouts from the beginning.
These costs are invisible during the sales cycle and painfully visible during delivery. For a system integrator managing five or ten simultaneous projects, the multiplied effect of those friction points is significant enough to erode margin entirely.
The integrators who are winning in the current market are not necessarily those with the most sophisticated engineering teams. They are the ones who made a smarter platform decision early and built their entire service delivery model around it.
What a purpose-built platform changes in practice
There is a growing recognition in the industry that the platform question deserves more strategic attention than it typically receives. Platforms like Favoriot have emerged specifically to address the system integrator’s workflow rather than the end user’s dashboard experience. The architecture is designed around multi-tenancy, white-labelling, and device interoperability from the ground up, which means an integrator can onboard a new client without rebuilding the underlying stack from scratch each time.
For a system integrator managing recurring deployments across multiple clients and sectors, this kind of platform design is not a luxury. It is a practical necessity. A platform that reduces integration time by even twenty percent across a portfolio of projects is not a marginal improvement. It is the difference between a profitable business and one that is perpetually scrambling to recover margin.
The conversation around IoT platform selection needs to shift from feature checklists to deployment economics. How many engineering hours does this platform save per project? How much of the client-facing experience can be customised without touching the core infrastructure? How does the platform handle scale when a pilot of fifty devices needs to expand to five thousand?
The pilot trap and how platform choice creates it
One of the most documented phenomena in enterprise IoT is the pilot that never scales. A company runs a proof of concept. The numbers look promising. Leadership approves expansion. And then the project stalls, sometimes for months, sometimes permanently.
Platform architecture is one of the primary culprits behind this pattern. Platforms that are optimised for demonstration and evaluation tend to surface problems only at production scale. Authentication and authorisation structures that worked for twenty devices start to buckle at two thousand. Data pipelines that handled one site’s telemetry become bottlenecks when ten sites are streaming simultaneously. The integrator, caught between a client expecting momentum and a platform revealing its limits, finds themselves in an impossible position.
Choosing a platform that was designed for production scale from day one is not a conservative choice. It is the only rational one for a system integrator whose business model depends on repeatability.
The strategic question that should come before the technical one
Before an integrator evaluates a single feature or benchmarks a single API response time, there is a more fundamental question worth asking. Is this platform built for someone like us, or is it built for someone we are trying to serve?
The distinction sounds philosophical but it has very concrete operational consequences. A platform built for integrators will have documentation written for developers, not marketing teams. It will have support channels staffed by engineers who understand deployment complexity, not onboarding specialists who know how to run a product demo. It will have a pricing model that reflects the integrator’s margin structure, not just the enterprise procurement cycle.
The IoT market in 2026 is not short of platforms. It is short of platforms that understand what it actually means to build and deliver connected solutions at scale on behalf of someone else. That gap is where the most interesting opportunities, and the most avoidable disasters, currently live.
A question worth sitting with: If the platform currently at the centre of your IoT delivery stack were replaced tomorrow with one designed specifically for system integrators, how much of the friction in your last three projects would simply disappear? What would your engineers do with those recovered hours, and what would your clients say about the difference in delivery speed? The answer to those questions might be the most important platform decision your business makes this year.
Dr. Mazlan Abbas is the CEO of Favoriot, an IoT platform company focused on helping organisations in ASEAN turn operational data into decisions. He writes on IoT strategy, AIoT deployment, and the future of intelligent infrastructure at iotworld.co.
Leave a Reply