What IoT consulting services cover, what they cost and when you need them

IoT consulting services are the assessment, design and planning work that takes a fleet of connected devices from an idea, or a stalled pilot, to a platform that collects, secures and uses their data in production. The consulting is the part that decides what the platform is before anyone builds it. Done well, it is short, it is priced before it starts, and it ends with a scope and a number for the build.

This guide is for the people who end up owning an IoT project, usually a product lead, an operations director or a head of engineering, and who are trying to work out what a consulting engagement should contain, what it should cost, and whether they need one at all. It is written from the delivery side. Dedicatted designs and builds IoT platforms on AWS, so the examples and the prices below are ours, and the checklist at the end is the one we would want a customer to hold us to.

Why IoT projects stall after the pilot

Most IoT projects do not fail at the device. They fail in the gap between a demo and a platform. A pilot connects a handful of sensors to a dashboard and it works. Then the fleet grows to a thousand devices in the field, the firmware needs updating, two of them start sending malformed readings, the network at one site drops every afternoon, and the security team asks who can see the data. None of that was in the pilot, and the architecture that carried the pilot cannot carry it.

Cisco’s survey of IoT decision makers, the one still quoted in most of the industry’s planning decks, found that about 60 percent of IoT initiatives stalled at the proof of concept stage and only about a quarter were judged a complete success by the people who ran them. The reasons the respondents gave were not technical. They were time to completion, the quality of the data, internal expertise and integration with existing systems. Those are exactly the questions a consulting engagement exists to answer before the build starts.

So the useful way to think about IoT consulting is not as advice. It is as the work that makes the second project, the real one, start from a design that already knows about the fleet, the firmware, the bad readings, the flaky network and the security review.

What IoT consulting services cover

Whatever the provider calls them, the services fall into six areas. A good engagement touches all six, even if it only goes deep on two.

• Strategy and roadmap. Which use case pays first, what it is worth, and what the phases are to get there. The output is a target architecture and a priced plan, not a vision deck. If the engagement cannot say what the first production release contains and roughly what it costs, it has not finished.
• Device connectivity and edge. How controllers, sensors and gateways reach the platform. Protocols such as MQTT and OPC UA, device identity and certificates, over-the-air updates, and which logic has to run at the edge because it cannot wait for the cloud. This is where a consultant earns the fee, because the choices are hard to reverse once ten thousand devices are in the field.
• Platform architecture. Provisioning, fleet management, telemetry ingestion, storage tiers and the data lake, designed as code on managed services such as AWS IoT Core so the platform scales without a rebuild. The platform should live in your own cloud account from the first day.
• Industrial IoT. Plants, factory floors and vehicle fleets have their own constraints. Production must keep running when the network does not, and telemetry has to feed maintenance, quality and manufacturing execution systems that already exist. Services such as AWS IoT SiteWise and Greengrass are built for this, and the consulting decides how they fit around what is already on the floor.
• Data platform and analytics. Telemetry on hot, warm and cold paths into a governed data lake, with dashboards, alerts and machine learning on top. This is the part that makes the platform pay back. A fleet that only reports is a cost. A fleet whose data predicts a failure a week early is an asset.
• Security and the operating model. Who runs the platform after launch, under what service levels, with what monitoring, patching and incident response. A unique certificate identity per device, encryption in transit and at rest, least-privilege access, and an audited practice behind it. The classic IoT breach is a flat network where any device, or anyone impersonating one, can see the whole fleet.

What IoT consulting services cost

There are two honest ways to price this work and one dishonest one. The honest ones are a fixed-scope package with a defined output, or a day rate against a defined number of days. The dishonest one is an open-ended retainer that produces documents until the budget runs out. Ask for the first, accept the second, walk away from the third.

Dedicatted prices the work as three packages, and each one de-risks the next, so a customer can stop after any of them.

What moves the number inside those ranges is predictable. The count of device types and protocols, because each one is an integration. The data volume and how fresh it has to be, because a threshold alert that fires in seconds costs more to run than a nightly report. The compliance profile, because telemetry that touches patient data, payment systems or safety controls carries audit requirements. And the amount of logic that has to run at the edge, because offline-first design is more work than a device that simply publishes to the cloud.

For scale, a recent engagement of ours delivered a fully operational AWS data lake for IoT telemetry within three months of starting. The Proof of Concept connects the device types and demonstrates the pipeline before any of that scale-out is paid for.

When you need an IoT consulting company, and when you do not

You probably do not need one if you are connecting a dozen devices of one type to a dashboard, the data is not sensitive, and nobody’s safety or revenue depends on it. Buy a platform subscription, connect the devices, and see what you learn.

You probably do need one when any of the following is true.

• The pilot worked and the next step is a fleet of hundreds or thousands of devices in the field, often of more than one type.
• The devices already exist, were made by someone else, and speak protocols the cloud platform does not understand natively.
• Production, safety or revenue depends on the platform, so it has to work with the network down and recover without a person on site.
• The data has to feed systems that already exist, maintenance, quality, billing or a manufacturing execution system, rather than live in its own dashboard.
• There is a security or compliance review in the way, and the architecture has to pass it the first time.
• Your engineers can build the product but have never run a device fleet, and nobody wants to learn fleet management, certificate rotation and firmware rollouts in production.

The difference between an IoT consulting company and a platform vendor is where they start. A vendor starts from its platform and fits your devices to it. A consulting company starts from your devices, protocols, data and operations, picks the services that fit, and builds the platform in your own cloud account. The second kind is the one worth paying for, and the test is simple. Ask who owns the platform at the end. The answer should be you.

What to ask before you hire one

• What is the output of the first engagement, and what does it cost? A target architecture, a proof of concept scope and a price for the next phase is a good answer. A workshop series is not.
• Which of our real devices will be in the proof of concept? Two to four real device types, not a simulator, unless simulators are explicitly part of the scope because the hardware is not ready.
• Whose cloud account does the platform live in? Yours. Infrastructure as code, in your repositories, from the first commit.
• How is a device identified and how is a firmware update rolled out? If the answer does not include a unique certificate per device and a staged rollout with a rollback, keep looking.
• What happens when a site loses its network for an afternoon? Edge buffering and local safety logic should be in the design, not a future phase.
• Who runs it after launch, under what service levels? A managed service with monitoring, fleet health, patching and incident response is one answer. Your own team, trained during the build, is another. Silence is a problem.
• What is the partner standing behind the design? Delivery designations from the cloud provider in the specific IoT categories mean the provider has had its IoT work validated, not just its sales deck.

How Dedicatted does it

Dedicatted is an AWS IoT Delivery Partner in three IoT categories, alongside its Premier Tier Services Partner status, and designs and builds IoT platforms end to end on AWS. Every platform follows the same five-stage spine, devices and edge, connectivity, streaming, data lake, and insight and action, hardened at each stage so that scale never means fragility. The consulting is attached to delivery. A two-week Discovery produces the target architecture and a priced proof of concept, the Proof of Concept connects your real device types, and the IoT Foundation package builds the production platform in your AWS account and hands it over. After launch our managed services team can run it under a service level agreement, with 24/7 monitoring, fleet health, security patching and cost control, so your engineers keep the roadmap.

The full offer, the six consulting services, the industrial and smart-building solutions and the questions customers ask are on the IoT consulting and platforms page. The data side of the platform, the lake and the analytics on top of it, is described under data architecture services, and the operating model under DevOps as a Service.

The survey figures are as published by Cisco in its study of IoT decision makers. Package prices and timelines are Dedicatted’s own, current at the time of writing.