From Prototype to Production: Seven Questions to Resolve
A working prototype proves an idea, but repeat production needs decisions about specifications, revisions, test coverage, sourcing, and change control.
3 September 2026 · 5 minute read
A prototype and a production product have different jobs
A prototype exists to generate learning. Production exists to produce the same acceptable result repeatedly. That shift requires more than ordering a larger quantity of the current board.
The release should capture what the product must do, which revision is approved, and how each unit will be shown to meet the requirement.
Seven points to close before release
- Is the intended product specification written and testable?
- Are the PCB, firmware, mechanical parts, and documentation on compatible revisions?
- Which components create lifecycle, lead-time, or single-source risk?
- What must be inspected, programmed, calibrated, and functionally tested?
- What production tooling, fixtures, and programming equipment are required?
- How will engineering changes be requested, reviewed, and approved?
- What information must be traceable for service and future builds?
Use a controlled pilot build
A pilot build is a valuable bridge between engineering prototypes and repeat production. It allows the team to exercise the released data, confirm process assumptions, refine work instructions, and collect evidence before scaling.
Treat issues found during the pilot as inputs to the product record. Close them deliberately and release the updated baseline before the next build.
Bring us the requirement, the design, or the production challenge.
Tell us what you are building, where the project currently sits, the expected quantities and the timing. We typically respond within 24 hours.