A prototype is a working representation of a product or part, built to validate a design before production, and the type is chosen by the question being asked. This page focuses on the definition and the prototype types; the rapid prototyping strategy and its processes are covered in the Rapid Prototyping Process Guide, and the transition to production is covered in the Prototype vs Production Parts guide.
What a Prototype Is For
The purpose of a prototype is to make the design testable. A design that exists only in CAD cannot answer questions about feel, fit, or function; a prototype makes those questions physical. The prototype collects feedback, exposes problems, and provides data, and each of those outcomes needs a different kind of part.
The key discipline is matching the prototype to the question. A prototype that is too simple for the question produces no useful data, and one that is too elaborate wastes time and money. The question comes first, and the type follows.
The Prototype Types
The prototype family spans the development stages, and each type has a defined role.
| Type | What it proves | Typical form |
|---|---|---|
| Concept model | Look, feel, and design direction | Printed or modeled appearance part |
| Visual prototype | Appearance and finish, sometimes no function | Painted, finished model |
| Functional prototype | Mechanism, fit, and performance | Machined or printed working part |
| Engineering prototype | Detailed technical validation | Production materials, real tolerances |
| Pre-production prototype | Manufacturing and assembly | Production process, pilot run |
The types are not a strict ladder; a program may skip a type or combine them. A simple part may go straight from a concept model to a pre-production build, while a complex device may cycle through several functional prototypes. The principle is the same: each prototype answers the question the stage needs answered.
Concept Models: The Look and Feel
The concept model answers design questions: does the product look right, feel right, and fit the hand. It is often 3D printed or carved from modeling material, with little or no function, and it is used for design reviews, user feedback, and early marketing. The concept model should be cheap and fast, because the design is still moving and the model will be revised.
The concept stage is where the brand and the ergonomics are decided. The model's appearance communicates product quality before the engineering is complete, and a painted and textured model can be used for packaging mock-ups and stakeholder reviews while the functional design continues.
Functional Prototypes: The Working Part
The functional prototype answers engineering questions: does the mechanism work, does the board fit, does the part carry the load, and does the assembly hold together. This stage needs real materials and real tolerances, which is why functional prototypes are machined or printed in production materials rather than modeled in foam.
The functional prototype produces the data that transfers to production. Measurements from the machined part, thermal data from the working build, and the failure modes found in testing become the acceptance criteria for the production supplier, so the prototype should be as representative as the stage allows. A functional prototype that is not representative produces data that does not transfer.
Pre-Production Prototypes: The Process Check
The pre-production prototype validates manufacturing, not just design. It is built with the production process, production tooling, and production materials, and it checks the tooling, the assembly sequence, and the quality plan before volume. This stage catches the expensive problems: draft angles that bind, gates that mark visible surfaces, and tolerances that stack past the fit.
The pre-production build is the first honest look at production, and its data becomes the acceptance baseline for volume. A prototype made by a different process cannot predict the molded part's shrinkage or the machined part's tolerance, so the pre-production build uses the real process.
Prototypes in Hardware and Software
The prototype concept applies differently across product types. Hardware prototypes are physical parts, made by printing, machining, or casting, and they test geometry, materials, and manufacturing. Software and interface prototypes are interactive models, from paper sketches to clickable demos, and they test workflows and user experience. The two worlds use the same word for the same purpose, making the design testable, but with different tools and different iteration speeds.
The crossover matters for connected products. A hardware device with an interface needs both prototype tracks: the physical enclosure and the interface, and the two must converge before production. The program that prototypes only the hardware discovers the interface problems at the worst time, and the one that prototypes only the interface ships a device that cannot be built. The prototype plan should cover both.
The Value of a Failed Prototype
A prototype that fails is a successful test. The purpose of the prototype is to expose problems while they are cheap to fix, and a failure at the prototype stage is a failure avoided at production. The team that treats a failed prototype as a wasted order misunderstands the process; the team that records what failed and why has bought the information for the price of the prototype.
The discipline is to design the prototype to fail informatively. The test should isolate the variable under question, so a failure identifies the cause rather than a general "it did not work." The prototype program that plans for informative failures converges faster than one that hopes for success.
The failed prototype also protects the production schedule. Every problem it exposes is a problem the production line does not have to discover, and the cost of the failure is the price of that insurance. The program that budgets for informative failures spends less overall than the one that treats failure as a mistake.
How Many Prototypes Do You Need?
The number of prototypes follows the risk and the stage. High-risk, complex designs need more iterations early, when the changes are cheap; low-risk parts need fewer. The discipline is to run cheap iterations in the early stages and reserve the expensive builds for frozen designs, because the cost curve favors early changes.
The metric is cost per learning, not cost per prototype. A prototype that answers the question is worth its cost; one that repeats what the last one showed is waste. The program should name the question before each build, so the iteration has a purpose.
The quantity also follows the test plan. A test that needs five samples needs five prototypes, and the order should carry the quantity the test requires rather than a single part. The sample count is a test decision, and it belongs with the test plan.
Conclusion
A prototype is a testable representation built to answer a question, and the type, concept, visual, functional, engineering, or pre-production, follows the question. Match the prototype to the stage, keep the early iterations cheap, and use production-representative builds for the data that transfers. A rapid prototyping partner that helps name the question before the build is the one that delivers learning, not just parts.
FAQs
What is a prototype in product development?
A prototype is a working representation of a product or part, built to validate a design before production. It exists to answer a question about look, fit, function, or manufacturability, and the type follows the question.
What is the difference between a concept model and a functional prototype?
A concept model proves the look, feel, and design direction with little or no function, and it is cheap and fast. A functional prototype proves the mechanism, fit, and performance in real materials, and it is the build that produces data that transfers to production.
What is a visual prototype used for?
A visual prototype shows appearance, finish, and color without full function, and it is used for design reviews, user testing, and marketing samples. It is often made in resin or cast urethane with a painted finish, and it validates the look, not the load.
What is a pre-production prototype?
A pre-production prototype is built with the production process and tooling to validate manufacturing, assembly, and quality before volume. It catches the problems that design prototypes cannot, such as draft, gates, tolerance stack, and yield, and its data becomes the production baseline.
Can a prototype be called a model?
Yes, in common use: a concept model and a visual prototype are often the same object described differently. The useful distinction is the question, a model for appearance and a prototype for function, and the drawing or the order should state which purpose the build serves.
Sources
- 6CProto Rapid Prototyping Services
- 6CProto 3D Printing Services
- 6CProto CNC Machining Services
- ISO 9001:2015 – Quality management systems
- ISO 2768-1:1989 – General tolerances for linear and angular dimensions