Board-level engineering
From the boardto the dashboard.
Custom PCB design, firmware, connectivity and the cloud backend behind it — one team from the board to the dashboard.
Bring the constraint that worries you most — battery life, range, certification, unit cost — and we will tell you early if it is the one that decides the design.
Why this exists
Connected products usually involve two vendors who each blame the other. The hardware firm ships a board with a protocol the software firm did not expect, and the integration becomes the project.
We take the whole path: schematic, layout, firmware, connectivity, backend and the interface people actually look at. When one team owns both ends, the protocol between them gets designed rather than negotiated.
How it runs
Four steps, and you seework at every one.
- 01
Define the constraints
Power budget, range, duty cycle, unit cost and certification target. These decide the architecture, and getting them wrong is expensive to undo.
- 02
Prototype early
A rough board and rough firmware in the real environment, because bench conditions lie. We would rather find the problem on revision one.
- 03
Build both ends together
Firmware and backend developed against each other, so the protocol is as small as it needs to be. That is usually what makes the battery last.
- 04
Production and fleet
Design for manufacture, test fixtures, OTA update path and a dashboard for whoever operates the fleet.
What you get
Yours to keep,from day one.
Not deliverables handed over at the end. These exist in your accounts, in your name, while the work is happening.
- Schematics and PCB layout files, in your name
- Firmware source with a documented build and flash process
- Bill of materials with sourcing notes and alternates
- Test procedures and any fixtures we build
- Backend, APIs and an operations dashboard
- An over-the-air update path that works in the field
Capabilities
The full list, so you cancheck we do your thing.
Hardware & electronics
- Schematic design
- PCB design and layout
- Circuit design
- Prototype development
- Hardware testing and debugging
Embedded systems
- Embedded firmware development
- RTOS
- Microcontroller programming
- Device driver development
- Bootloader development
Connectivity
- Bluetooth and BLE
- WiFi, Zigbee and LoRa
- MQTT and CoAP
- 4G and 5G IoT modules
IoT cloud
- AWS IoT
- Azure IoT
- IoT gateways
- Data logging
- OTA updates
Applications
- Industrial IoT
- Smart building automation
- Wireless sensor networks
- IoT dashboards and monitoring
Sectors
- Medical IoT
- Automotive embedded
- Agricultural IoT
- Smart energy
How we work together
Pick the shape thatfits the work.
Phased
Priced and approved per phase
For larger builds. Each phase is scoped, priced and signed off on its own, so you can stop or change direction at a known point rather than being locked into the whole thing.
Fixed price
One number, agreed up front
For work we can scope tightly. You get a written scope and a price before anything is built, and the price does not move unless the scope does.
Retainer
Monthly capacity
For ongoing work after launch. A set amount of our time each month, and you decide what it goes on. No minimum term.
Scoping is free in every case, and the written scope is yours whether or not you hire us.
Questions
About iot & embedded.
Do you take hardware projects without the software?
We can, but the value we add is largest when we hold both ends. If you already have a software team we will work to their interface rather than imposing ours.
Why does hardware cost more than software?
Because iteration has a physical cost. Every board revision is a fabrication run and a lead time measured in weeks. We front-load design review to keep revisions down, but it is genuinely more work than a web build.
Can you handle certification?
We design towards your certification target and prepare the documentation, and we work with accredited labs for the testing itself. Tell us the target market early — it changes the design.
What about manufacturing?
We design for manufacture and can hand a complete package to your contract manufacturer, or work with one we have used before. We do not mark up fabrication.