Architecture
Six stages. One data model.
Every stage writes into the same model. Nothing is re-entered, re-drawn or re-typed between them.
Why it is built this way
The handover between stages is where hardware projects die
Requirements written in one document, drawn in another tool, programmed against a third. Every gap is a place for a detail to be lost. There are no gaps here.
One model, not six files.
A decision taken at research is still readable at build. Change a requirement late and the stages downstream of it know.
You review at every stage.
Nothing moves forward because the platform decided it should. Each stage ends with something you look at and accept.
Everything leaves in standard formats.
Each stage produces files your existing toolchain and your fabricator already accept. Nothing is trapped.
The pipeline
What happens, in order
01
Research — You describe the product you want to exist.
The platform researches it properly — what comparable products do, which component families are appropriate, what the constraints of the category actually are, and where the hard problems sit.
You end the stage with: A researched product definition, with the reasoning visible and the sources attached.
02
Specify — The research becomes requirements.
Functional behaviour, electrical envelope, mechanical envelope, interfaces, environment, and the things the product must never do. Written as requirements an engineer can argue with, not as prose.
You end the stage with: A specification you can challenge line by line before anything is designed.
03
Design — Requirements become an architecture.
Component families are chosen against the specification and against real availability. Trade-offs are made explicitly and recorded, so that in eight months you can still find out why a part was chosen.
You end the stage with: A system architecture with the decisions and their reasons kept beside them.
04
Draw — The architecture becomes drawings.
Schematics, then multi-layer board layout, then the outputs a fabricator needs. Manufacturability is checked as part of the work rather than discovered at the fab.
You end the stage with: Schematics, layout, fabrication outputs, assembly data and a bill of materials graded by what could be verified.
05
Program — The board becomes a thing that runs.
Board support, peripheral configuration, drivers and application firmware written against the same model that produced the schematic — so the firmware and the hardware cannot disagree about a pin.
You end the stage with: Firmware and board support, generated against the design rather than beside it.
06
Build — The design becomes a manufacturable package.
Everything a manufacturer needs, assembled into one handover: fabrication, assembly, test, sourcing references and the documentation that has to travel with a product.
You end the stage with: A complete package you can hand to a manufacturer without a phone call.
Control
Six stages, six places you say yes or no
The platform assists your engineering judgement. It does not replace it, and it does not proceed past you.
You accept the product definition, or you send it back with what it missed. Nothing is specified against a definition you have not read.
You accept the requirements. This is the cheapest place in the whole pipeline to change your mind, and the platform is built to make changing it here easy.
You accept the architecture and the component families. Trade-offs are shown with their reasoning so you are approving a decision, not a result.
You review the schematic and the layout the way you would review a colleague’s. Nothing goes to a fabricator without you.
You review the firmware against the specification you approved at stage two.
You accept the manufacturing package. Then it is yours.
Questions
Five straight answers
Can I start at stage three with a specification I already have?
Yes. The stages run in order when you start from an idea, but you can enter the pipeline wherever your project already is. Tell us where you are in the access request and we will start there.
Can I stop after a stage and take what I have?
Yes. Each stage ends with real outputs in standard formats. If you only want the specification, you take the specification.
What if I disagree with a decision the platform made?
Send it back. The reasoning behind every choice is recorded beside it, which means the disagreement is about something specific rather than about a black box.
Does my design ever get used to improve the platform for other people?
Your project is worked on for you. Anything beyond that is set out in the agreement you sign before onboarding, and you read it before you commit to anything.
How is this different from a design service?
A service gives you the output. This gives you the output and the reasoning, in a model that stays live — so a change in month nine does not mean starting month one again.
Bring a real project
The onboarding session runs your own product through the stages that are ready for it. That is the only honest demonstration there is.