The files your team needs to order parts, build the board and test it.
How this works
We write a package so that an engineer on your team who never sat in our design reviews can order, build and power up the board from the files alone.
It starts with the obvious pieces: schematic, layout and fabrication files in Gerber or ODB++. What makes it buildable is the rest. The BOM lists checked alternates and flags minimum order quantities and parts at risk of going end-of-life. The assembly notes cover the steps that are easy to get wrong, and a checklist covers the minutes before first power-on, when a shorted rail is still cheap to find.
Bring-up and test procedures tell your team what to measure and which reading passes, with test points marked on the board and notes for a fixture if you plan to build one. Where the board needs firmware or calibration, example code and calibration steps come with it. Every file carries a version, and the change log and known limits travel with the package. The source files stay with your team, so later revisions start from a known version instead of another round of reverse-engineering.
| 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
Frequently asked questions
Can we change the design ourselves after handover?
Your engineers receive the design source files alongside the fabrication outputs, so they can open and change them. The change log records what each revision changed and why.
What if the first boards don't power up?
The bring-up procedure is written for exactly that moment: what to check first, in what order, and what each measurement should read. If you're still stuck, we can debug it with you remotely as part of the support we've agreed.
Is this a reference design, or something designed for us?
A custom design is built around your requirements, with ownership agreed before work starts. A reference design is shared non-exclusively and you validate it for your own product, so the two are licensed separately.
Will the design be ready for certification testing?
It can be, if we know your target standards early. Choices like layout around a radio or clearances for mains voltage are best settled while the design is still open, and the testing itself is done by an accredited lab you choose.