# Why run a pilot batch after the prototype works? — SyntaForge

Canonical: https://syntaforge.com/en/blog/prototype-to-pilot/
Language: en

> This is a text rendering of the same public webpage. Use the canonical URL for citation. Private inquiry records and administrator data are never included.

[← All articles](https://syntaforge.com/en/blog/) Prototypes & production 2026-11-04 SyntaForge editorial

# Why run a pilot batch after the prototype works?

A working prototype shows that an implementation can function. The next question is whether another set of parts and another assembly operator can produce a unit that meets the same requirements.

In this article

[A prototype and a pilot build answer different questions](https://syntaforge.com/en/blog/prototype-to-pilot/#journal-section-0) [Agree on the version used for this batch](https://syntaforge.com/en/blog/prototype-to-pilot/#journal-section-1) [Turn inspection into steps someone can follow](https://syntaforge.com/en/blog/prototype-to-pilot/#journal-section-2) [Bring field feedback into the next build](https://syntaforge.com/en/blog/prototype-to-pilot/#journal-section-3)
Why run a pilot batch after the prototype works?
Illustrative development scene

## A prototype and a pilot build answer different questions

A functional prototype helps test the core connection, interaction and wearing experience. A pilot batch puts more attention on repeatability: component versions, assembly order, software loading and outgoing checks.

These do not need to become isolated stages. Prototype feedback should inform design changes, and a pilot build can also reveal issues that lead back to mechanical, electronic or software design.

## Agree on the version used for this batch

Before a pilot build, confirm which hardware, mechanical and software versions are being used and which changes have been checked. Keep an explicit list of unresolved questions rather than letting different people work from their own idea of the latest version.

Batch size and timing depend on the project. The purpose is to answer concrete questions, rather than simply make a larger number of prototypes.

## Turn inspection into steps someone can follow

“Check that it works” is too broad. Break it into observable actions such as power-on, button operation, display, connection, charging and other agreed checks. The conditions and results should be traceable to the device being checked.

If a judgement relies entirely on individual experience, ask whether the design, test conditions or device feedback can make that judgement clearer. These details affect consistency in later deliveries.

## Bring field feedback into the next build

Record the context, manner of use and software version alongside a reported problem. This helps distinguish an unusual action, a poor fit for the use case and a design issue that needs to change.

After reviewing the batch, agree on the changes for the next one, the checks still needed and the delivery plan. Flexible production works best when product decisions can develop without losing track of versions and inspection.

For your next discussion

Before the next build, agree on the version, assembly steps, inspection method and how feedback returns to the design.First published 2026-11-04 [Discuss a product](https://syntaforge.com/en/contact/)

## Keep reading.

[All articles](https://syntaforge.com/en/blog/)

[What should you define before building your first wearable?](https://syntaforge.com/en/blog/defining-first-wearable/) Product definition 2026-11-04

## [What should you define before building your first wearable?](https://syntaforge.com/en/blog/defining-first-wearable/)

Agree on the user, the moment of use and one essential task before choosing screens, sensors and first-version features.

[Read article](https://syntaforge.com/en/blog/defining-first-wearable/)

[Starting from a wearable platform: what carries over?](https://syntaforge.com/en/blog/choosing-a-wearable-platform/) Hardware platforms 2026-11-04

## [Starting from a wearable platform: what carries over?](https://syntaforge.com/en/blog/choosing-a-wearable-platform/)

Assess wearing, interaction, connectivity and software separately. A familiar form is a starting point, not proof that a product fits the use case.

[Read article](https://syntaforge.com/en/blog/choosing-a-wearable-platform/)