Services for IoT and connected-device companies

IoT automation that turns device data into the right action

Make It Flow builds automated business solutions for IoT companies, hardware startups, facility operators, cold-chain businesses and manufacturers with sensors: a CRM that links trials and device activations to sales, sensor alerts that become tickets and on-call texts, offline device and gateway detection, cold-chain temperature excursion records, predictive maintenance, an AI support agent for troubleshooting and RMAs, and dashboards for your fleet and customers. People decide anything that touches safety, money or a customer promise.

Your platform stays the source of truth

Readings stay in AWS IoT Core, Azure IoT Hub, ThingsBoard, The Things Stack, Particle or your own time-series database. Our workflows react to events and read what they need through documented APIs and webhooks.

People own safety, money and promises

Automation detects, groups, drafts and reminds. Engineers and ops leads decide on dispatching technicians, rejecting stock, approving returns and anything that affects safety or a customer contract.

Security and data rules built in

We design for the EU Cyber Resilience Act and Data Act, the UK PSTI regime and privacy law where device data identifies people, with least-privilege access and logs of every automated action.

Services

IoT automation, from signal to action.

Each one is a focused project with a fixed quote, a written plan and a handover you own.
Case Study Case Study: IoT Cold-Chain Monitoring & Support Automation We built a connected set of automations for a company selling wireless temperature sensors to food distributors and cold-storage sites: cold-chain exc... How we built it

Case Study

Case Study: IoT Cold-Chain Monitoring & Support Automation

Read the full case study

We built a connected set of automations for a company selling wireless temperature sensors to food distributors and cold-storage sites: cold-chain excursion detection and records, offline device and gateway monitoring, an AI support agent for troubleshooting and RMA intake, and a CRM that links pilots and active fleets to sales. Customers now hear about problems from the company first, and support works from complete cases.

Sensors Temp, heartbeat Web and orders Trials, support IoT platform LoRaWAN, API n8n Four workflows Support agent Guides, RMAs Help desk Tickets, RMAs CRM Accounts, pilots Ops and support Act and approve Quality adviser Limits, disposition
  • Input
  • Logic and services
  • AI step
  • Data
  • People

What changed for the practice

  • Excursions now reach the right person while there is still time to act, and each one has a consistent record.
  • Offline gateways are found by the company before customers notice, as one incident per site.
  • Routine setup questions are answered from approved guides, and RMA cases arrive complete.
  • Sales sees which pilots have gone live, stalled or expanded without asking support.

Platform integrations

The software you already use, connected.

Practice systems, CRMs, phones, payments and reviews, connected through documented APIs, webhooks, n8n and custom code.
All integrations

AWS IoT Core

IoT platform

Threshold events, device status and readings for alerts, offline checks and dashboards.

AWS IoT rule actions such as HTTPS, Lambda, SNS and Timestream.

Azure IoT Hub

IoT platform

Device telemetry and events for alerts and dashboards.

IoT Hub message routing and Event Grid integration.

ThingsBoard

IoT platform

Devices, telemetry and alarms.

ThingsBoard REST API.

The Things Stack

LoRaWAN network server

Uplinks and last-seen times for LoRaWAN sensors.

The Things Stack webhooks.

Particle

Device cloud

Device events and status for alerts and support.

Particle webhooks on published device events.

MQTT brokers

Messaging

Alert and status topics from devices and gateways.

n8n MQTT Trigger and MQTT nodes.

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

Tech we work with

Any language, any stack.

Make It Flow delivers automated business solutions: workflows, integrations, AI assistants and the apps around them. Our team works in whatever language and stack fits the job and the systems you already run.

Automation

n8nWebhooksREST and GraphQL APIsScheduled jobs and queues

Backend

PythonPHP and LaravelNode.js and TypeScriptJava

Data

SQL (MySQL, PostgreSQL)Google Sheets and AirtableData sync and ETLReporting dashboards

Frontend and mobile

JavaScript and TypeScriptTailwind CSSJava and Kotlin for AndroidBrowser extensions

AI

Claude, Gemini and OpenAI modelsRetrieval on your own documentsModel Context Protocol (MCP)Evaluation sets

Cloud and DevOps

DockerLinux serversGitHub ActionsMonitoring and backups

FAQ

IoT automation answered.

IoT automation is what happens after a device sends data: a ticket opened, a technician texted, a customer told, an excursion recorded, an invoice prepared. We build the workflows, dashboards and models that carry each signal to the right system and person, with people deciding what matters.

Business workflows such as offline monitoring, cold-chain records or a device CRM are fixed-quoted at $1,000 to $2,500 each, and an AI support agent at $2,500 to $7,500. Sensor alert pipelines, dashboards and predictive maintenance depend on your devices, data volumes and platform, so we scope those after a free call, often as a pilot on one site or device type.

AWS IoT Core through rule actions such as HTTPS, Lambda and SNS; Azure IoT Hub through message routing and Event Grid; ThingsBoard through its REST API; The Things Stack through webhooks; Particle through webhooks; and MQTT brokers through n8n MQTT nodes. We confirm the route for your setup before quoting.

No. We build the software around the device: workflows, dashboards, data pipelines and models. We work alongside your firmware engineers or hardware partner.

Yes, remotely and worldwide. In the EU, Cyber Resilience Act reporting duties apply from 11 September 2026 and its main requirements from 11 December 2027; the UK PSTI security requirements have applied since 29 April 2024. We design processes with those in mind.

A single workflow usually goes live in three to five weeks. A connected set is delivered in one-week Scrum sprints, one workflow at a time, in about eight to ten weeks, often after a pilot on one site.

Free 20-minute call

Walk us through your device data

Book a free 20-minute call. Tell us where your readings land, who acts on alerts and where support and billing get stuck. We tell you honestly what is worth automating and how we would scope it.

Book a free 20-minute call