Prototype, MVP, and Production Product
A prototype proves that an idea can be represented. An MVP tests whether a small but usable product creates value. A production product is prepared for continued use, operational failures, real data, and ongoing maintenance.
What You Will Be Able to Decide
- Distinguish a prototype from an MVP.
- Explain why an MVP is more than an unfinished product.
- Identify when production safeguards become necessary.
- Classify a proposed product stage.
- Ask a consultant what risks have intentionally been deferred.
A founder asks a consultant to build an application.
The founder may describe the first version as an MVP. The consultant may hear a prototype. The users may assume they are receiving a production product.
All three parties can use the same words while expecting different levels of reliability.
The difference matters because product stage changes what should be built, tested, documented, protected, and maintained.
Prototype
A prototype is used to explore or demonstrate an idea.
It may show how screens connect, how a technical concept could work, or how a user might complete a task. A prototype can be interactive without being dependable.
Think of it as a model apartment. It helps someone understand the layout and appearance. It does not prove that the full building has reliable plumbing, fire exits, legal approvals, or long-term maintenance.
A prototype may contain:
- hard-coded sample data
- incomplete workflows
- temporary integrations
- limited error handling
- no user permissions
- no backup strategy
- no operational monitoring
This can be reasonable when the purpose is demonstration or learning.
The danger begins when a prototype quietly becomes the live product without its risks being reviewed.
Technical term
MVP
MVP means minimum viable product. “Minimum” limits the scope. “Viable” means that the product is useful enough to test with its intended users. “Product” means that the core workflow is complete enough to be used rather than merely demonstrated.
A Complete Core Workflow
An MVP for a booking product may allow a user to:
- find an available time
- make a booking
- receive confirmation
- allow the business to view the booking
It may exclude:
- advanced analytics
- multiple calendar providers
- loyalty programmes
- complex team permissions
- automated marketing
- extensive personalisation
The excluded features reduce scope. The included workflow still needs to function coherently.
An MVP should test a meaningful assumption, such as:
A collection of incomplete features does not answer that question.
Will independent consultants use a simpler booking system if it reduces administrative work?
Production Product
A production product is prepared for continued real-world use.
“Production” refers to the live environment used by real users. It does not mean that the product is finished forever.
Production readiness usually introduces concerns such as:
- authentication
- authorisation
- backups
- monitoring
- error reporting
- data recovery
- deployment rollback
- privacy
- security updates
- documentation
- support
- account ownership
Risk Determines the Required Standard
The stage cannot be chosen through appearance alone.
A basic internal tool used by three employees may tolerate several hours of downtime.
A product processing payments or medical information requires stronger safeguards even when it has very few users.
Ask:
- Does it store sensitive data?
- Can it move money?
- Can one user access another user’s information?
- What happens if the data is lost?
- What happens if the service is unavailable?
- Can the team recover from a failed deployment?
- Who is responsible for maintenance?
The answers determine which production controls are already necessary.
Warning Signs
- Nobody can clearly state whether the current build is a prototype or live product.
- Real users are entering data into a system built only for demonstration.
- “We will add security later” has no defined review point.
- The product has no documented backup or recovery process.
- Critical accounts are owned by an individual contractor.
- A polished interface is being used as proof of production readiness.
Questions to Ask a Consultant
- What stage is the current product actually prepared for?
- Which risks have been deliberately deferred?
- What would prevent us from giving this to real users today?
- Which production controls are already required because of our data or workflows?
- What must be completed before the next user group is invited?
- How would we recover if the next deployment failed?
Key takeaway
Key Takeaway
A prototype demonstrates an idea. An MVP tests a useful assumption. A production product accepts responsibility for continued real-world use.