NexGenTekTalk to us
IoT

Choosing an IoT development partner: what to check before you sign

The right IoT partner is one who can make devices, connectivity, cloud and your business systems work together, and keep them working after launch. Most IoT projects that disappoint fail at those joins: devices drop off the network, sensor data does not match the asset records in the ERP, or nobody owns firmware updates. Choosing a partner is mostly about finding one who can handle the joins.

What makes IoT projects different

A typical software project has one stack and one team. An IoT product has at least five layers, and a problem in any one of them shows up everywhere else:

  • Devices and firmware: sensors, gateways, power, enclosures and the code running on them
  • Connectivity: Wi-Fi, cellular, LoRaWAN or other networks, and what happens when the signal drops
  • Cloud platform: device registration, message handling and storage, often on AWS IoT, Azure IoT or a similar service
  • Data and analytics: cleaning, storing and making sense of high volumes of readings
  • Business integration: getting the results into the ERP, maintenance, CRM or field service systems people already use

A partner strong in one layer and weak in the others will hand you a working demo and a fragile product.

Six things to check

1. Experience across the layers you need

Ask for two or three past projects that covered devices through to business systems, and ask who did each part. If the partner subcontracts firmware or hardware design, meet that subcontractor too. Industry experience helps, because a factory floor, a hospital and a warehouse have very different constraints on power, networks and safety.

2. Security built in from the device up

IoT devices are often the least protected part of a network. Ask how the partner handles:

  • a unique identity and certificate for each device, with no shared default passwords
  • encrypted communication from device to cloud
  • secure, signed firmware updates delivered over the air
  • separating device networks from the rest of your environment
  • what happens when a device is lost, stolen or retired

Vague answers here are a reason to walk away.

3. Integration with your existing systems

The value of IoT data comes from acting on it: raising a work order, adjusting stock, alerting a customer. Ask how they will connect to your systems of record, how device IDs will map to your asset or customer records, and who will own that mapping.

4. A clear way of working

Look at how they gather requirements, how often you will see working software, and how decisions and changes are recorded. A good partner will want to visit the site, see the physical environment and talk to the people who will use the system before quoting a fixed scope.

5. Evidence from real clients

Portfolios show what a partner wants you to see. Ask to speak to two clients, ideally one whose project had problems, and ask how the partner handled them. Repeat clients are a good sign. A partner that only shows polished case studies and no references is a risk.

6. Support after launch

Devices stay in the field for years. Before you sign, agree who monitors device health, who patches firmware and cloud components, how quickly issues are handled, and how the system will scale from a few hundred devices to many thousands. Make sure you will own the source code, device keys and cloud accounts at the end.

How to keep cost under control

IoT costs depend on the number of device types, the connectivity, the features and the integration work, so a figure quoted without a site visit means little. Three habits keep the budget honest:

  • Start with a paid pilot. A small number of devices in one real location, connected to one business system, tells you more than any proposal.
  • Separate the costs. Ask for hardware, development, connectivity, cloud running costs and support to be priced separately, so you can see what grows as you scale.
  • Build only what the pilot proves. Features such as advanced analytics or machine learning can wait until you know which data is useful.

What to do next

Write down the one business decision you want the IoT data to improve, such as when to service a machine or when to reorder stock, and ask every partner you speak to how their design gets that data to the person making the decision.

If you need help designing or building the application and integration side, see our custom application development service.

Related

Custom Application Development

Book a 30-minute call
Contact

Tell us where delivery is stuck

A 30-minute call with someone who has run enterprise delivery. You leave with a clear view of what we would do, even if you don't hire us.

Office1700 Pacific Ave, Ste 3630
Dallas, Texas 75201
Delivery centreGurgaon, India
Dubai officeIRIS BAY, Dubai, UAE
Follow us