Home / Industries
Sectors where we already know the failure modes
Domain experience is not a nice‑to‑have in embedded work. Knowing which protocol an estate already runs, and what an inspector will ask for, removes months from a programme.
Building automation
Buildings are long‑lived, mixed‑vendor estates. A new controller has to speak to equipment installed a decade ago, be commissioned by an electrician rather than an engineer, and keep working when the building's network changes owner. We build for that constraint rather than around it.
What we build here
- Controllers for shading, lighting and HVAC
- BACnet, KNX, DALI and Modbus integration
- Installer commissioning apps that work offline
- Portfolio consoles for facilities teams
What decides success
Commissioning time and update safety. A controller that needs a site visit to change a setting costs more over its life than it did to buy.
Industrial automation & robotics
Plants do not stop for software. Anything added to a line has to fail safely, integrate with what is already on the floor, and give maintenance a way to diagnose a problem without calling the vendor. Robotics adds fleet coordination and battery logistics on top.
What we build here
- Gateways and protocol translation for legacy equipment
- OPC‑UA and Modbus data paths to plant systems
- AMR and AGV control over ROS 2 and CANopen
- Fleet dispatch, charging and battery management
What decides success
Determinism and diagnosability. When a line stops, the question is which component caused it, and the system has to be able to answer.
Energy & metering
Metering devices are installed once and expected to report accurately for years, often on a battery and a weak link. The engineering problem is rarely the measurement — it is power budget, data integrity and getting readings out of an awkward location.
What we build here
- Metering and submetering devices
- Ultra‑low‑power design and battery life modelling
- LoRaWAN, NB‑IoT and cellular backhaul
- Consumption analytics and reporting portals
What decides success
Power budget and data integrity. A gap in a billing series is a commercial problem, not a technical one.
Healthcare devices
Connected instruments carry documentation obligations that shape how software is written, not just how it is filed. We work in a way that produces the evidence trail as a by‑product of development rather than as a scramble before an audit.
What we build here
- Connected instruments and data capture
- Traceability, audit trails and access control
- Documented development and verification records
- Integration with hospital and laboratory systems
What decides success
Traceability. Every requirement should link to a test, and every release should link to the evidence that it passed.
Consumer connected products
A consumer product is judged in the first ten minutes. If setup fails on a dual‑band router or a captive‑portal Wi‑Fi network, the product is returned regardless of how good the engineering underneath is.
What we build here
- Connected appliances and personal devices
- Provisioning flows an ordinary person can finish
- Companion apps for iOS and Android
- Fleet updates across large installed bases
What decides success
Setup completion rate and update reach. Both are measurable, and both are usually ignored until support volume makes them urgent.
Retail & commerce operations
Selling across several channels multiplies every operational task. The engineering job is reconciliation: one accurate view of stock, orders, returns and margin, assembled from systems that each report differently.
What we build here
- Multi‑marketplace order and inventory sync
- Settlement reconciliation and margin reporting
- Warehouse, packing and dispatch tooling
- In‑store devices and back‑office integration
What decides success
Reconciliation accuracy. If the numbers do not agree, every downstream decision is made on a guess.
Working in a sector not listed here?
The engineering constraints usually transfer. Describe your environment and we will tell you honestly where our experience is thin.