SAP to open-stack ERP migration
Manufacturer, 500+ employees. Phased migration off SAP ERP onto an open stack with custom modules — run in stages while the plant kept working.
- 0 downtime
- 8 mo migration
- −40% on licences
IoT software development: from the device in the field to the dashboard
The hard part of IoT is not the sensor. It is the connection that drops, the firmware you cannot recall, and a dashboard that has to stay honest when a third of the fleet is offline.
What we can show you
IoT software
Four layers, and a project fails at whichever one you skip
Device agent, transport, ingest, platform. Hardware design, manufacturing and certification are not on that list — and not on ours.
What IoT software development actually covers
An IoT system is four layers of software. The device side buffers, retries and reports its own health. Transport carries messages over a network that will be unavailable more often than anyone plans for. Ingest validates, deduplicates and stores what arrives, including backfill from a device that woke up after two days. The platform handles provisioning, over-the-air updates, alerting and the screens people actually open.
We build all four in software. We do not design boards, manufacture devices or run certification: if that is what you need, you need a manufacturer first and us second. Saying this on the first call saves both sides a month.
When IoT software work is justified
When the device already exists and someone is reading numbers off it by hand; when the fleet has outgrown a spreadsheet; when downtime costs money, so alerting matters more than dashboards. If the device is still a sketch, start with the manufacturer — we will happily join at the point where it can send its first message.
Signals an IoT project is ready for software work
- the device exists, at least as a prototype, and can already send something;
- somebody is reading numbers off it manually, on a schedule;
- fleet size is going past what one engineer can watch;
- downtime of a device costs money, so alerts matter more than charts;
- the data has to reach an ERP, a CRM or billing, not just a screen.
Price
From $18,900
Timeline
4–6 weeks to a working telemetry path
Payment
50/50 by milestone
Comparison
Vendor IoT cloud or a platform of your own
The honest comparison, including the cases where the vendor cloud wins and we lose the deal.
Criterion
Vendor cloudCustom IoT platform
Built for youVendor IoT cloud (AWS IoT, Azure IoT, vendor SaaS)
Time to first telemetry
Days
4–6 weeks
Cost shape
Per message and per device, indefinitely
Capital spend you own, hosting at cost
Exotic protocols and legacy devices
Gateway you write anyway
Normalised in the gateway by design
Business logic on telemetry
Rules engine within vendor limits
Your rules, in your code, tested
Integration with ERP or billing
Connectors where they exist
Built against your data model
Data ownership and exit
Export when the vendor allows it
Your database, your cloud, runbook included
When it wins
Small fleet, standard protocol, fast pilot
Fleet grows, costs per message bite, logic is yours
Process and stack
How an IoT build runs and where these projects break
Four failure modes account for most rescued IoT projects. We design against them in week one.
How a build runs
Week 0 — scoping. Protocols, message volume, cost per device, offline rules and an explicit out-of-scope list. Fixed quote at the end of it.
Weeks 1–2 — telemetry path. One device end to end: agent, transport, ingest, storage. Everything else waits until that path is boring.
Weeks 3–4 — platform. Provisioning, alerting, dashboards, roles.
Hardening. Failure injection: kill the network, replay duplicates, send a device two days late — then ship.
Where IoT projects actually break
Connectivity is assumed, not designed. Buffering, idempotent ingest and backfill are architecture, not bug fixes.
Updates are an afterthought. A fleet you cannot update over the air is a fleet you will replace by hand.
Telemetry has no schema. Six months in, three firmware versions send three shapes of the same field.
Costs scale with messages, not users. Per-message pricing turns a pilot into a budget problem at 10,000 devices.
Stack we are accountable for
MQTT or HTTP for transport; a gateway that normalises Modbus, OPC UA and vendor protocols; PostgreSQL with TimescaleDB for time series; Redis and queues for backpressure; Python or Node for services; Docker and GitHub Actions for delivery.
The platform runs in your cloud account, and infrastructure is code from day one — see DevOps services.
What we integrate telemetry with
ERP and accounting, billing and metering, CRM, maintenance and ticketing systems, BI. Telemetry that never leaves the dashboard is a screensaver.
Integration starts with an audit: what data moves, in which direction, and which system wins when two disagree — see API and integration.
Why us
Why teams bring IoT software to us
Four things we can prove, rather than four adjectives.
Backpressure designed in, not patched on
Queues, retries, idempotent ingest and dead letters before the first device ships. Offline is the normal state of a fleet, not the error case.
Cost per device modelled up front
Message volume, storage and egress estimated during scoping and capped in code. You pay cloud and connectivity providers directly, at cost, with no mark-up.
Your cloud, your fleet, your data
The platform runs in your account, the repository is yours from the first commit, and IP is assigned at delivery with a documented chain of title.
Senior review on every merge
A senior engineer who did not write the code reviews it — including code an AI drafted. In IoT that review is what keeps a silent data-loss bug out of a fleet you cannot recall.
Industries
IoT softwarefor your industry
Telemetry means different things by domain: fleet and cold chain in logistics, line uptime in manufacturing, metering in utilities, occupancy in property.
- IT companies and digital agencies
- Insurers and brokers
- Lenders and microfinance
- E-commerce
- Wholesale and distribution
- Manufacturing
- Freight and forwarding
- Clinics and medical centres
- Dental
- Car dealers and service centres
- EdTech
- Legal and consulting firms
- Equipment rental
- Real estate agencies
- Property developers
- Travel and events
- Beauty and wellness
- Construction and renovation
FAQ
IoT development questions
Seven answers that usually replace a discovery call.
Do you make the hardware?
No. We write the software: device agent, gateway, ingest, platform and integrations. Board design, manufacturing and certification are someone else's job, and we say so on the first call.
Which protocols do you work with?
MQTT and HTTP by default; Modbus, OPC UA and vendor protocols through a gateway. If your device speaks something exotic, the gateway is where that gets normalised.
How do you handle devices that go offline?
Buffering on the device, idempotent ingest on the server and backfill when it reconnects. Offline is the normal state of a fleet, not the error case.
Can you do over-the-air updates?
Yes, with staged rollouts and rollback. Designing OTA after the fleet ships is possible but expensive, so we raise it during scoping rather than after.
What does it cost to run?
Cloud and connectivity are billed by message volume and storage. We model that per device during scoping and put a cap in code; you pay the providers directly, at cost.
Can you integrate telemetry with our ERP or billing?
That is usually the point of the project. It starts with an integration audit — see API development and integration.
Can you take over an existing IoT platform?
Yes, after a paid audit of the ingest path, the data model and the update mechanism — the three places where these systems hurt.
2–4×
faster on the code-writing share
in 3 weeks
from idea to MVP
230+
projects delivered
17 years
of engineering experience
Work
Work we can show you
SMARTWILL
Digital inheritance service (Web3)
AIRDEVELOPPA
Indoor air quality finder driven by sensor data
CAR5
Car-sharing app
APP.DENTAL
Cloud CRM for dental clinics
NEXORA
Warehouse and logistics management platform
As-built docs
Digital as-built documentation
EX211
Telegram Mini App for currency exchange
SMARTWILL
Digital inheritance service (Web3)
Have a device and no platform behind it?
Send the protocol and the expected message volume. You get an architecture sketch, a cost-per-device estimate and a fixed quote for the telemetry path — before any contract.