Prototype vs MVP: Which One Your Product Actually Needs
A prototype answers whether it can work. An MVP answers whether anyone will buy it. Building the wrong one first is one of the most expensive mistakes a founder can make.
June 10, 20243 min read
Written by Konstantin Dolgan, Ph.D., NPDP
Founder & CEO, Product Development Engineer
Published June 10, 2024Updated August 18, 2026
A prototype is a build made to answer a technical or experiential question — can it work, does it fit, does it feel right — and is usually shown only to your team, testers and investors. An MVP is the smallest sellable version of the product, released to real customers to test whether they will actually buy and keep using it. One de-risks feasibility; the other de-risks demand.
The core differences
Prototype | MVP | |
|---|---|---|
Question it answers | Can it work? Does it fit? | Will people pay for it? |
Audience | Team, testers, investors | Real paying customers |
Build quality | Throwaway, often hand-built | Production-intent, supportable |
Feature scope | One question at a time | One complete job, end to end |
Regulatory burden | Minimal | Full compliance for the market |
Typical timeline | Days to weeks | Weeks to months |
Typical cost (hardware) | $500 to $50,000 | $50,000 to $500,000+ |
Failure means | Change the approach | Change the business |
Types of prototypes, and what each one proves
- Proof of concept — isolates the one physics or technology question everything else depends on. Ugly by design.
- Looks-like model — appearance, size, weight and finish, for buyer feedback and photography.
- Works-like model — the functional mechanism, usually in a housing nobody would ship.
- Looks-like-works-like — both together, for user testing, trade shows and pre-orders.
- Engineering prototype — production materials and processes, used for regulatory pre-testing and DFM.
Our guide to getting a prototype made covers the files, costs and timelines for each level.
What a real hardware MVP looks like
In software an MVP can be a stripped-down release shipped in a week. In hardware the minimum viable product still has to be safe, certifiable and repairable, which sets a floor on cost and time.
- A small production run — 50 to 500 units, often bridge-tooled or 3D-printed at production quality rather than injection molded.
- Real compliance — FCC, CE, UL or FDA pathways as applicable. This is not optional because you sold only a few.
- Packaging, instructions and support — returns and questions are part of the test.
- A price — a free unit measures curiosity, not demand.
- Instrumentation — you must be able to see usage, failures and churn, or the MVP teaches you nothing.
The order that saves money
Stage | What you build | Spend before proceeding |
|---|---|---|
1. Concept validation | Sketches, renders, landing page | $0 to $5,000 |
2. Proof of concept | Bench prototype of the hard part | $2,000 to $25,000 |
3. Looks-like-works-like | Testable, demonstrable unit | $10,000 to $60,000 |
4. Pilot / MVP run | 50 to 500 sellable units | $50,000 to $300,000 |
5. Scale | Hard tooling and volume manufacturing | $100,000+ |
Each stage should either produce a decision to continue or kill the program cheaply. Skipping stage two to reach stage four faster is the classic hardware failure, because tooling cannot be un-cut.
Not sure whether you need a prototype or an MVP?
Talk to our teamWhere patents fit
Prototypes and patents interact, and the timing matters more than most founders realize.
- You do not need a working prototype to file. US patent law requires an enabling written description, not a physical unit.
- Public disclosure starts a clock. In the US you have a 12-month grace period after public disclosure or sale; most other countries have none, so file before you show it publicly.
- A provisional application establishes a priority date for around $130 to $320 in USPTO fees plus attorney time, and gives you 12 months to test the market.
- Prototype first, patent the version that works. Filing on your first idea often protects the concept you later abandon.
- Use NDAs for private testing and keep dated records of development.
If you are budgeting the IP side, our breakdown of the trademark application fee covers the brand-protection half of the same question.
Common mistakes
- Calling a prototype an MVP. If nobody can buy it, it is not testing demand.
- Polishing a prototype nobody asked for. Fidelity should match the question.
- Shipping an MVP with no way to measure it. No instrumentation, no learning.
- Filing patents before the design settles. Expensive protection for the wrong embodiment.
- Treating certification as a later problem. Compliance shapes design and cannot be retrofitted cheaply.
Ready to build the right version first?
Request a quoteFrequently asked questions
What is the difference between a prototype and an MVP?
A prototype is built to answer a technical or experiential question and is shown mainly to the team, testers and investors; it is usually thrown away. An MVP is the smallest complete, sellable version of the product released to real paying customers to test whether demand exists.
Should I build a prototype or an MVP first?
Build the prototype first. It costs far less and answers whether the product can work at all. Only once feasibility, form and usability are settled does an MVP make sense, because an MVP requires production-quality units, compliance and support.
How much does a prototype cost compared to an MVP?
Hardware prototypes typically range from $500 for a simple appearance model to $50,000 for a full engineering prototype. An MVP pilot run of 50 to 500 sellable units generally runs $50,000 to $300,000 once compliance, packaging and support are included.
Do I need a prototype to get a patent?
No. US patent applications require a written description that enables someone skilled in the field to make and use the invention, not a physical prototype. Building first is still often wiser, because prototyping reveals the version actually worth protecting.
Can an MVP be a prototype?
Only if customers can buy it and it is safe and compliant for the market. A demonstration unit sold to a friendly early adopter under a pilot agreement can serve as both, but a giveaway or demo unit tests curiosity rather than willingness to pay.
How many prototypes will I need?
Most hardware programs go through three to five prototype rounds: a proof of concept, one or two functional iterations, a looks-like-works-like unit for testing and demos, and an engineering prototype in production materials before tooling.
Frequently asked questions
What a real hardware MVP looks like?
In software an MVP can be a stripped-down release shipped in a week. In hardware the minimum viable product still has to be safe, certifiable and repairable, which sets a floor on cost and time. A small production run — 50 to 500 units, often bridge-tooled or 3D-printed at production quality rather than injection molded.. Real compliance — FCC, CE, UL or FDA pathways as applicable. This is not optional because you sold only a few.. Packaging, instructions and support — returns and questions are part of the test.. A price — a free unit measures curiosity, not demand.. Instrumentation — you must be able to see usage, failures and churn, or the MVP teaches you nothing.
What is the difference between a prototype and an MVP?
A prototype is built to answer a technical or experiential question and is shown mainly to the team, testers and investors; it is usually thrown away. An MVP is the smallest complete, sellable version of the product released to real paying customers to test whether demand exists.
Should I build a prototype or an MVP first?
Build the prototype first. It costs far less and answers whether the product can work at all. Only once feasibility, form and usability are settled does an MVP make sense, because an MVP requires production-quality units, compliance and support.
How much does a prototype cost compared to an MVP?
Hardware prototypes typically range from $500 for a simple appearance model to $50,000 for a full engineering prototype. An MVP pilot run of 50 to 500 sellable units generally runs $50,000 to $300,000 once compliance, packaging and support are included.
Do I need a prototype to get a patent?
No. US patent applications require a written description that enables someone skilled in the field to make and use the invention, not a physical prototype. Building first is still often wiser, because prototyping reveals the version actually worth protecting.
Can an MVP be a prototype?
Only if customers can buy it and it is safe and compliant for the market. A demonstration unit sold to a friendly early adopter under a pilot agreement can serve as both, but a giveaway or demo unit tests curiosity rather than willingness to pay.
How many prototypes will I need?
Most hardware programs go through three to five prototype rounds: a proof of concept, one or two functional iterations, a looks-like-works-like unit for testing and demos, and an engineering prototype in production materials before tooling.
Filed under:Uncategorized
Related articles
All articles
Invention Prototype to Production: The Steps That Actually Matter
A working invention prototype proves the idea. It does not prove the product can be made a thousand times, at a price, without failing.
Product Packaging Design Companies: How to Choose One (and What They Actually Do)
Packaging is the last thing many teams plan and the first thing a buyer judges. Here is what packaging design companies do, what it costs, and how to pick one.
Before you prototype your AI generated invention, read this
← Back to blog LA NPDT / Editorial Blog / AI Invention / 9 min read Before you prototype yourAI generated invention, read this Before you prototype an AI generated invention, run
Recent Posts
Insights blogDive deep into the dynamic world of new product development with LA NPDT Insights Blog.
- Geopolitical Risk in New Product Development
- Consumer Product Design: Process, Costs and Timeline
- You used Chatgpt to develop a product idea. Now what?
- Industrial Design Portfolio Examples: What Reviewers Look For
- Component Lifecycle Management: Designing for Obsolescence
- Material Qualification Strategy: Reducing Risk Before Production