Too many hardware teams frame the decision as prototype route versus final production route. In practice there is usually a more sensible sequence: prototype, bridge, and scale. Each phase is buying a different kind of confidence.
Useful framing: prototype manufacturing buys learning speed, bridge manufacturing buys evidence, and scaled manufacturing buys repeatable economics.
What each stage is for
| Stage | Primary goal | Main risk if skipped |
|---|---|---|
| Prototype | Learn fast and change often | Teams lock decisions before the design has earned it |
| Bridge | Test demand, process capability, and quality repeatability | Scale investment arrives before the product proves itself |
| Scale | Reduce recurring unit cost and increase throughput | Capex gets committed against weak evidence or unstable geometry |
What should trigger movement between stages
- demand certainty improving, not just optimism increasing
- product geometry stabilising enough that tooling changes are unlikely
- quality requirements becoming clear and testable
- the team being able to tolerate the lead time and capex of the next commitment
A product may appear ready for tooling because the cost curve is attractive, yet still benefit from a bridge run if the quality regime is immature or demand is not proven. That extra stage can prevent a much more expensive mistake.
The Production Strategy Planner is useful here because it connects volume, stability, quality, lead time, and capex posture in one staged recommendation.