How we work
Six phases. Each has a concrete deliverable and a specific input it needs from you. You see what you are getting before the next one starts.
The phases
The phases overlap; the boundaries are not sharp. But each one ends with something concrete in your hands — an arrangement where progress is not measured by someone saying it is going well.
| Phase | Deliverable | Needed from you |
|---|---|---|
| Discovery | Scope note, list of open questions | The need, constraints, target cost and volume |
| Feasibility | Technical approach, risk list, time and cost estimate | Priorities, acceptable trade-offs |
| Design | Schematic, BOM, PCB layout | Mechanical constraints, interim approval |
| Prototype | Working board and core firmware | Test environment, field conditions |
| Validation | Test results, EMC/CE preparation notes, revision | Field testing, acceptance criteria |
| Handover | Production files, source code, documentation | Choice of manufacturer |
The phases in detail
Discovery
What you want to build, under which constraints, and why. The output is not a quote but a shared understanding of scope and a list of questions that still need answers. Most projects are damaged not here but by skipping this.
Feasibility
Technical approach, risks and estimate. If something cannot be done, or will cost more than assumed, you hear it here — not after design has started. Some projects stop at this point; that is not a failure but a decision made at the right time.
Design
Schematic, component selection and BOM, then PCB layout. Mechanical constraints need to be settled before this phase begins — an enclosure change arriving after the board is routed repeats most of the work.
Prototype
The board is fabricated, assembled and brought up. Core firmware functions arrive here. Finding corrections in the first revision is expected; the schedule is built around it.
Validation
Functional tests, power measurements, link stability and, where needed, EMC pre-testing. Findings feed a revision. Accredited laboratory measurements and the CE declaration stay with you — those are the manufacturer's obligations and cannot be transferred.
Handover
Production files (Gerber, assembly, BOM), source code and documentation are handed over. The aim is to leave you a package you do not depend on anyone to continue.
How to start
The first step is a discovery conversation. There is no document to prepare beforehand; being able to write down the following is enough — and anything you do not know yet gets settled in the conversation.
- What the device has to do, in a few sentences
- Where it will run: indoors, in the field, on a vehicle, in a hazardous area
- Supply: mains, 12/24 V, battery — and if battery, the expected life
- Mechanical constraints, if any: enclosure, size, connector positions
- Estimated volume and target unit cost
- Timeline, and any fixed deadline
Let us start
You do not need an answer to all of the above. Write down what you have — the gaps get filled in together.