The line

How a prototype becomes a product

01 Start
Idea
Most projects arrive as a working prototype and a rough sense of who wants it. We look at both before anything else: what problem it solves, how others solved it, and whether it should exist a thousand times.
The brief you send usStart yours ↗
02 Review
Design
Two engineers go through the schematic and the layout with whoever designed it. Most of what turns up is cheap to fix now and expensive to fix once a thousand of them exist.
Example: a flight-controller schematicSee it on the site ↗
03 DFM
Prototype
The board gets laid out again for a factory instead of a pair of tweezers: panels, test points, and parts that can still be sourced when you need ten thousand of them.
Example: six copper layers, one boardSee it on the site ↗
04 Bench
Verify
A capture connects measurements to a procedure and to particular hardware. The bench records every unit, and the record travels with the release.
Example: a motor-controller capture, 25.5 sSee it on the site ↗
05 Paperwork
Certify
Radio, electromagnetic compatibility, safety, and the paperwork trail behind all three. The hardest gate for one person to clear alone, and the piece most worth building once and reusing forever.
The index of a real technical file
06 Partners
Produce
Bare boards and volume assembly from partners who already own the machines. Final assembly, calibration and functional test in Leuven, on our own bench.
We buy
- Bare board fabrication
- Volume board assembly
- Moulding, machining and metalwork
- Any machine nobody our size should own yet
We make
- Small-run board assembly
- Final assembly
- Functional test on every unit
- Calibration and firmware
- Quality control and packing
- Shipping, returns and repairs
Preview: capabilities moving in-houseSee it on the site ↗
07 Storefront
Ship
Stock, customs, VAT, packaging, shipping and returns. The unglamorous half of selling hardware inside the EU, and the half that quietly ends most small hardware projects.
Example: opendrone.be, the first storefrontThe first storefront ↗
08 Loop
Support
Documentation, firmware updates, replacements, and a person who answers. For as long as the product is in the catalogue. What comes back feeds the next revision.
Example: one board, five revisions in 19 daysSee it on the site ↗

Stops 02 to 05, automated

The tooling that runs between design and release

Every project through the line uses the same scripts: design checks, manufacturing exports, recorded evidence and a controlled handoff. Below, one example board runs through them.

Shared automation