Overview

Build to learn something specific

The most expensive prototypes are the ones built without a question. They produce a board that mostly works, an inconclusive result and a schedule that has moved without the risk having moved with it.

We define what each prototype must prove before it is built: this power architecture under this load, this sensor chain at this accuracy, this interface at this data rate, this thermal behaviour in this enclosure.

Prototypes are instrumented so the answer is measurable, and findings are written down. Over two or three iterations the design converges on something production-intent, with evidence behind every significant decision.

Prototyping scope

How we use prototypes

Different prototypes answer different questions. Mixing them up wastes iterations.

01

Proof of concept

Minimal hardware built to test whether the core technical idea works at all, before design effort is committed.

02

Functional prototype

A board implementing the intended architecture, used to verify behaviour across the real operating range.

03

Instrumented measurement

Test points, monitoring and controlled conditions designed in, so results are data rather than impressions.

04

Integration prototype

Hardware, firmware and mechanical elements brought together to expose the interactions between them.

05

Iteration management

Each revision driven by specific findings, with changes tracked so the reason behind every decision survives.

06

Production-intent build

A prototype built the way the product will be built, used to validate the design against real assembly conditions.

Prototype process

Running an iteration that produces answers

Short cycles with a defined question at the start and a written conclusion at the end.

Stage 01

Define the question

What this iteration must prove, and what result would count as success or failure.

Stage 02

Design the experiment

Hardware scoped to answer that question, with the instrumentation needed to measure it.

Stage 03

Build

Boards fabricated and assembled, with build notes captured for traceability.

Stage 04

Measure

Structured testing under controlled conditions, results recorded against the expected values.

Stage 05

Conclude

Findings written up: what was proven, what was disproven and what remains open.

Stage 06

Decide the next iteration

The next question defined from the findings, or the design moved toward production intent.

Technical illustration of an instrumented electronics prototype under measurement on a test bench
Instrumented prototype

Instrumentation

Built to be measured

Test points, monitoring and controlled conditions are designed into the prototype before it is fabricated, because a result you cannot measure is an impression.

Each iteration closes with a written finding: what was proven, what was disproven and what remains open.

Applications

When prototyping earns its cost

Prototyping is risk reduction. It is most valuable where the unknowns are technical rather than commercial.

Proof of conceptFunctional prototypesInstrumentationBench measurementIteration trackingProduction-intent builds
Application 01
New product concepts with unproven technical assumptions
Application 02
Measurement chains where accuracy must be demonstrated
Application 03
Power architectures that need real load and thermal data
Application 04
Wireless designs needing real range and interference results
Application 05
Mechanical and thermal integration checks before tooling
Application 06
Component or platform evaluation before committing a design

FAQ

Prototyping questions

How prototyping is usually scoped and what it delivers.

Next step

Have an assumption that needs to become a measurement?

Tell us what you need to prove. We will scope the smallest prototype that answers it.