Notes from the bench,and the field.
What we have learned building connected products: the method, the devices, and what it takes to keep a fleet alive in the field. Practical writing, newest first.
5 minHow to brief a connected product5 minRescuing a stalled connected product5 minData, decision, action: what a connected product is for4 minSouth Africa's 2G and 3G switch-off: what happens to your connected devices5 minLife after 2G and 3G: choosing a network for a device that has to last ten years4 mineSIM for IoT fleets: what SGP.32 changes, and what it doesn't4 minAI on the device: what edge AI can do on a microcontroller in 20264 minElectricity up 8.76%: how energy monitoring finds the waste4 minSecurity rules for connected products: the EU's Cyber Resilience Act and the UK's PSTI4 minThe EU Data Act and connected products: what access by design means for your device5 minThree vendors, one product, and the gaps between them5 min800 stations, 100 million sprays: what running a fleet unattended taught us5 minWhat a working slice of an IoT product looks like after ten days4 minAI-assisted delivery, without the hype5 minWhy we discount our fees for a share of the product7 minDesigning connected devices for South African conditions7 minThe real cost of an IoT product: beyond the build
5 minHow to brief a connected product5 minRescuing a stalled connected product5 minData, decision, action: what a connected product is for4 minSouth Africa's 2G and 3G switch-off: what happens to your connected devices5 minLife after 2G and 3G: choosing a network for a device that has to last ten years4 mineSIM for IoT fleets: what SGP.32 changes, and what it doesn't4 minAI on the device: what edge AI can do on a microcontroller in 20264 minElectricity up 8.76%: how energy monitoring finds the waste4 minSecurity rules for connected products: the EU's Cyber Resilience Act and the UK's PSTI4 minThe EU Data Act and connected products: what access by design means for your device5 minThree vendors, one product, and the gaps between them5 min800 stations, 100 million sprays: what running a fleet unattended taught us5 minWhat a working slice of an IoT product looks like after ten days4 minAI-assisted delivery, without the hype5 minWhy we discount our fees for a share of the product7 minDesigning connected devices for South African conditions7 minThe real cost of an IoT product: beyond the build
Your brief
Have a product in mind?
Have a product in mind?A few lines is enough. Tell us the problem, the people who will use it and where it has to work, and we'll help you work out the first step.
- 01Talk directly to the people who will design and build it
- 02An honest view on what to prototype first, and what to leave out
- 03A clear next step, whether or not we end up working together
What happens next
- 01We read your briefWe come back to you, usually with a few questions of our own.
- 02A first callWe talk through the problem, the users, the devices and the data.
- 03A clear proposalScope and cost for a first phase, so you know exactly what you're committing to.





