Hardware designs your team can build, or that we build and ship for you.
How this works
Some teams have the people and the bench to build their own boards and want the design done properly. Others would rather receive working boards. We do the electronics design either way, and write it up so your team can order, assemble and bring up the board without needing to call us at every step. If you'd rather not deal with suppliers, we can source the parts and have the boards built and tested for you. In both cases our job is to cut out avoidable board spins, rushed substitutions and assembly surprises before anything is ordered.
A design usually starts from requirements and an architecture we agree on together, then moves to schematic, layout and the BOM. Alternates get picked while the design is still open, because swapping a part after the boards are ordered is where the expensive surprises come from.
The Hardware Design Package page lists what you get at the end, and the Sourcing and Manufacturing page explains how ordering through us works. If the board needs firmware, the same team can write it, or we can hand over example code for your own firmware engineers to build on.
| Checkpoint | What your team can expect |
|---|---|
| Scope and stage | The next defined stage is written before larger work begins, so you can decide what to fund next. |
| Handover | Source files, tests and decision notes are part of the handover, so your team can continue from a known version. |
| Procurement and build | When hardware is involved, you can buy the parts directly or have us source them at itemised cost; alternates and first checks are recorded before any order. |
Request a hardware design package
Pages in this section
- Hardware Design Package
- BOM, Alternates and Procurement Risk
- Assembly, Bring-up and Test
- Sourcing and Manufacturing
Frequently asked questions
Can you supply the boards instead of just the files?
We can source the parts, have the boards made and assembled, test them and ship them to you. The Sourcing and Manufacturing page explains how the quote, payment and customs work.
What do you need from us to start a board design?
A description of what the board has to do, the environment it will run in, how it's powered, and any parts you're already committed to. Rough notes are fine, since turning them into requirements is what the Technical Review is for.
Can our engineers review the design before it is finished?
We'd want them to. We plan reviews with your engineers at the schematic and layout stages, because moving a connector on screen costs far less than moving it on a built board.
Can you also write the firmware for the board?
Happy to, and it saves a round of explaining the hardware to someone new. If you already have firmware engineers, we can hand over example code and bring-up tests for them to build on.
What happens if a part goes out of stock partway through?
That's the reason we pick and check alternates during design. If a part disappears later, the BOM notes show which ones were checked and what changes if you use one.