A prototype answers the engineering question: does this actually work? An MVP — minimum viable product — answers the business question: does anyone actually want it enough to pay? The difference isn't quality or polish; it's the question each one is built to answer. Both tools are legitimate, but founders who confuse them pay twice: once for unnecessary development, and once for a wrong decision made on the wrong evidence. Here's how to tell them apart and sequence them correctly for a physical product.

Prototype: Technical Proof

A prototype is an engineering tool. It exists to remove technical risk, so it's allowed to be ugly, oversized, tethered to a bench power supply, or 3D printed in a material that will never reach production. Success is measured in measurable terms: the mechanism withstood the required force, the sensor returned a stable reading, the battery lasted the planned number of hours. Its audience is the team itself, sometimes a technically minded investor, sometimes a grant reviewer. In practice it's almost never a single build — you make several successive versions, each testing one risk and ignoring everything else, using whatever is fastest, as covered in rapid prototyping techniques. And before the first full prototype there's often an even leaner step, explained in proof of concept vs prototype.

MVP: Demand Proof

An MVP is a marketing and business tool. It has to be complete enough that a real user can use it alone, in their own environment, with no engineer standing nearby. That means basic packaging, instructions, reasonable reliability, and often an app. What it sacrifices is most of the features and any cost optimization. Success is measured in behavior: how many ordered, how many were still using it two weeks later, how many told a friend. A simple rule of thumb: if you have to be in the room for the product to work, it's still a prototype — not an MVP. We cover the hardware-specific playbook in how to build a hardware MVP.

The Differences in Practice

  • Goal. A prototype removes technology risk; an MVP removes market risk.
  • Audience. A prototype serves the team and investors; an MVP serves paying end users.
  • Success metric. A prototype is judged on measured performance; an MVP on conversion, repeat usage, and feedback.
  • Required reliability. A prototype can work ten times in the lab; an MVP must work hundreds of times in a stranger's hands.
  • Budget and time. A prototype is focused and relatively cheap; an MVP needs a small production run, support, and logistics — significantly more expensive. See what a prototype costs for realistic ranges.

The Right Order Between Them

In most hardware projects the natural order is prototype first, MVP second — you can't sell a product that hasn't been shown to work. But there are important exceptions. When the technology is well-known and carries no real risk, you can nearly skip the prototype and test demand with cheap tools: a landing page, a video, pre-orders, or a non-functional appearance model — the toolkit described in how to validate a product idea. Conversely, when the core of the project is a physics breakthrough, investing in an MVP before the physics is proven is guaranteed waste. There's also a useful middle path: a small batch of prototypes placed with a handful of selected users under close supervision. It isn't a sale, but it yields much of the behavioral data an MVP would collect, at far lower cost and without exposing your brand to public reviews.

Where It Breaks Down in Practice

At Projects House we see two recurring mistakes. The first is a founder expecting the prototype to look and perform like a retail product, inflating the budget several times over without adding any business information. The second is shipping a lab prototype to real customers as an "MVP" — burning the first shot at the market on failures that were entirely predictable. The way to avoid both is to define in advance which question the build is supposed to answer, and budget accordingly. The distinction gets sharpest exactly when you must decide how many units to make and who receives them — the moment covered in from prototype to production. A successful MVP, incidentally, is also the strongest possible asset for a crowdfunding launch. More guides live in our prototyping hub.

Not sure which of the two you need right now? Contact Projects House and we'll map your project's biggest risk — and the cheapest build that removes it.