How to build a product MVP and test demand before a full launch
The main reason startups fail is a product nobody needs. Teams spend months building features, burn through their budget and only after launch discover that the market is not willing to pay. An MVP helps you avoid this trap: it lets you test an idea on real users with minimal time and money.
What an MVP is — and what it is not
An MVP (Minimum Viable Product) is the simplest version of a product that allows you to test the key hypothesis and get feedback from real users. The concept was popularised by Eric Ries in his book The Lean Startup.
It is important to understand what an MVP is not:
- it is not a “raw” product full of bugs — whatever is there must work reliably;
- it is not a cut-down version of the final product with a little of every feature;
- it is not a prototype for internal demos — an MVP must reach real customers.
A good MVP solves one main user problem and does it well enough that people want to come back or pay.
Types of MVP
- Landing page (smoke test). A page describing the product with a “Buy” or “Request access” button. The sign-up conversion rate shows interest before development even starts.
- Video MVP. A short video demonstrating how the future product will work. Dropbox used such a video to build a waiting list of tens of thousands of people.
- Wizard of Oz. To the user the product looks automated, but in reality people perform the processes manually.
- Concierge MVP. The service is delivered manually and openly, as a personal service. This helps you deeply understand the needs of your first customers.
- Single-feature product. Only the key feature that solves the main pain point is built.
- Pre-sales. Collecting prepayments or running a crowdfunding campaign is the strongest proof of demand.
A step-by-step plan for building an MVP
- Formulate hypotheses. Who your customer is, what problem they have and why they are willing to pay for a solution. Write the hypotheses down in a testable form.
- Conduct problem interviews. Talk to 15–20 potential customers. Ask about past experience and actual behaviour, not whether they would buy the product in the future.
- Define the core feature. Use the MoSCoW prioritisation method: must have, should have, could have, won’t have. Only the must-haves go into the MVP.
- Choose the fastest way to build. No-code platforms, website builders, off-the-shelf services and manual processes let you launch a test in a few weeks instead of months.
- Set success criteria in advance. For example: “10% of landing page visitors submit a request” or “30% of users come back after a week”.
- Launch and collect data. Bring your first users to the MVP through communities, personal contacts and a small test ad budget.
- Analyse and decide. Persevere, pivot or shut the idea down.
This process repeats in a loop: build — measure — learn. Each iteration should bring the product closer to the real needs of the market.
How to tell whether demand is real
Interest and demand are different things. Compliments from friends and likes on social media prove nothing. Focus on actions that require effort or money from people:
| Signal | What it shows | Strength of evidence |
|---|---|---|
| Joining a waiting list | Initial interest | Weak |
| A request with contacts and task details | A conscious need | Medium |
| Repeat use after a week | The product delivers value | Strong |
| Prepayment or purchase | Willingness to pay | Very strong |
The Sean Ellis test is also useful: ask users how disappointed they would be if the product disappeared. If 40% or more answer “very disappointed”, it is a good sign of product–market fit.
Common MVP mistakes
- Too many features. Every extra feature delays the launch and blurs the test results.
- Chasing perfection. If you are not a little embarrassed by your first version, you probably launched too late.
- Testing on friends. Friends and relatives rarely give honest feedback and are not your target audience.
- No metrics. Without success criteria set in advance, any result can be interpreted as a success.
- Ignoring negative signals. A negative result is still a result. It saves months of work and money.
Conclusions
An MVP is a learning tool, not a scaled-down copy of the future product. Formulate a hypothesis, choose the cheapest way to test it, set measurable criteria and launch as early as possible. Validated demand will be a strong argument when attracting investors and a solid foundation for fast growth strategies.
