Product Prototyping
Prototype to answer a question, not just to make something that looks finished.
We use prototypes throughout development to test assumptions, expose problems and reduce risk before tooling and production commit real money.
Why Prototype
A prototype with no question attached is expensive decoration. Before we build anything we agree what it has to prove: whether the technology works, whether it fits, whether a user understands it, whether the mechanism survives.
That framing changes what gets built. A question about grip does not need working electronics. A question about thermal behaviour does not need a finished surface.
Prototyping runs across both design and engineering, which is why it appears in both loops of our process rather than as a single stage near the end.
What This Includes
01
Test the critical technical assumption early, in the crudest form that gives a trustworthy answer.
02
Evaluate form, scale, proportion, CMF and visual intent at presentation quality — for review, investment and stakeholder decisions.
03
Put the product in real hands. Fit, reach, grip, comfort and workflow are decided by testing, not opinion.
04
Mechanisms, electronics, controls, architecture and assembly exercised together to find where the system disagrees with itself.
05
Prototype PCBs, sensors, power, displays and connectivity built and integrated with the mechanical package, using our retained electrical capability.
06
The transition from separate proof elements to one integrated functioning system — usually the first time the whole product is honest with you.
07
Production materials, architecture, processes, final electronics and the real assembly approach introduced progressively.
08
Build → Test → Learn → Refine. Iteration is how development works; a prototype that revealed a problem did its job.
09
A working prototype can still carry too many parts, expensive processes, temporary fasteners, loose tolerances and non-production materials. Closing that gap is a separate discipline.
Explore Design for ManufacturingWhat Prototypes Can Answer
These are the questions that most often justify a build. Naming the question up front keeps the prototype cheap and the answer trustworthy.
Proof-of-concept, isolated from form and finish.
Ergonomic models tested with real users in real posture.
Packaging and stack-up verified physically, not only in CAD.
Assembly sequence and tool access tried by someone other than the designer.
Featured Projects
Medical Device
Consumer Audio
Industrial Safety
CleanTech / Energy
Adjacent Capabilities
The engineering the prototypes are validating, and the iteration that follows.
Explore Product EngineeringClose the gap between a prototype that works and a product that can be made.
Explore DFMForm, ergonomics and CMF decisions that appearance and ergonomic models resolve.
Explore Industrial DesignFAQ
Yes, provided we can agree what question it has to answer. That is what makes it worth building.
We use the process the question requires, in-house or through vetted suppliers — printing is one option among several.
Yes. Prototype PCBs, sensors, power, displays and connectivity, integrated with the mechanical package.
It depends on unresolved risk. We scope rounds against questions, not against a fixed number.
Usually not. Prototypes optimise for learning; production optimises for cost, repeatability and assembly. DFM closes that gap.
Yes — appearance models and alpha builds are often used exactly that way.
Tell us the question and we will tell you the cheapest honest way to answer it.
Talk About Your Prototype