IoT Solutions
Where the software meets something you can hold.
Prototyping, embedded firmware, connected devices and small-batch production. The rarest thing we do, and the reason the rest is different: when a team has shipped a physical product, deadlines stop being abstract.
Firmware, enclosure and the software that talks to it
How we think about it
This is the rarest thing we do, and it changes how the rest of the studio works. Physical products cannot be patched on a Friday afternoon: tooling has lead times, a board revision costs weeks, and a wrong decision becomes a box of wrong parts. Working that way makes software deadlines concrete for everyone who sits near it.
Firmware, the app that pairs with it and the film that launches it are made by one team, so the device's behaviour and the story about it stay in sync.
What this covers
The work, specifically.
- 01
Embedded C
Firmware written for hardware that has to run unattended for years.
- 02
PCB design
Schematic through layout to assembly, designed so it can actually be manufactured.
- 03
CAD & enclosures
Enclosures designed for the process that will make them, printed or moulded.
- 04
IoT connectivity
Devices that talk to a backend our own team wrote, including how they fail and recover.
- 05
Short-run manufacture
Small batches — the awkward middle between one prototype and a factory order.
Need IoT Solutions for something specific?
Tell us what you're trying to ship and we'll say plainly whether this is the right service for it — including when the answer is no.
How it runs
The same four steps, whatever we're building.
No account-manager relay. The lead on your project is someone who builds, and they stay on it from the first call to the last deploy.
Scope
A week of hard questions. We map what you actually need and say plainly which parts we'd cut.
Prototype
Something real in front of you early, not a document about it. Opinions get cheaper.
Build
Two-week cycles, a demo at the end of each. You see progress, not status reports.
Hand over
Documentation, a walkthrough, and the keys. Support if you want it — never as a hostage.
Questions
The things people ask before they enquire.
Yes — firmware, enclosure, connectivity and the software that talks to it. Because the app team sits next to the firmware engineer, the device and its interface get designed together rather than across a contract boundary.
We plan for it from the start rather than discovering it at the end, and we will tell you plainly which certifications your product needs and what they cost in time and money.
It depends on scope, but we will give you a number before you commit to anything. Most engagements start with a paid discovery — a fixed fee, a week or two — which ends in a written scope and a real budget. If the budget does not work, you leave with the scope document and no obligation to continue.
A typical first ship is around six weeks. Larger builds run in two-week cycles after that, each ending in a demo of something that actually runs. You will know within the first cycle whether the timeline is holding, rather than finding out near the deadline.
The people you meet. The lead on your project is someone who builds, and they stay on it from the first call to the last deploy. There is no account manager relaying messages between you and an unseen team.
You own everything — code, assets, accounts, domains. We hand over with documentation and a walkthrough, and your team can run it without calling us. If you would rather we stayed on for maintenance or a next phase, that is a separate agreement, not something buried in the original contract.
Yes. Most of our work is remote, and we keep a few hours of overlap with your working day for calls. Timezone has not been the hard part; unclear scope has.
Where it meets the others