MVP (Minimum Viable Product)
The simplest version of your product that delivers core value and can be tested with real users.
What it means
A Minimum Viable Product strips your idea down to its essential core - just enough functionality to solve the main problem and get feedback from early adopters. It's not about building something bad; it's about building the smallest thing that's genuinely useful. The MVP approach lets you validate demand before investing months or years into a full product.
Why it matters
Building without validating is the most expensive mistake in startups. An MVP lets you test your hypothesis with real users, iterate based on feedback, and avoid building features nobody wants.
How to scope an MVP this week
An MVP is a test, not a small version of your dream product. Start from the question you want answered, then build the least you need to answer it.
- Write the one problem you solve in a single sentence, in the buyer's words.
- Write the riskiest assumption: usually that people will pay to solve this.
- List every feature you planned. Cross out everything that is not needed to solve the one problem once.
- Decide how you will know it worked: a number of people who pay, or use it again within a week.
- Set a deadline of weeks, not months. If the scope does not fit, cut more.
Talk about it before it exists
Start telling people what you are building while you build. Post the problem, a rough screenshot, the decision you made today. Ask who wants early access. The replies tell you whether the problem is real, and the people who replied are your first users.
A worked example: one founder, several products
A founder with a few products running gets an idea for a new one. Instead of building it fully, the founder writes a short page describing the result, posts about the problem from the existing founder account and offers early access.
Some people sign up and a few reply with their own version of the problem. The founder builds only the core flow, onboards those people by hand, and watches what they actually do. Features the founder thought were essential turn out unused. One small thing nobody planned becomes the reason people return.
Because the founder already had an audience from the other products, the test took weeks, not months. That is the hidden benefit of running several products: each new MVP starts with people to ask.
Common mistakes
- Building in silence for months, then launching to nobody.
- Calling a half-finished product an MVP. Minimum is about scope, not quality. The one thing it does should work well.
- Testing with people who will never pay.
- Adding features when users stall, instead of asking why they stall.
- Treating launch day as the finish line. It is the start of the test.
What to measure after launch
An MVP is only useful if you decided in advance what success looks like. Otherwise every result can be explained away. Pick a few signals before launch and check them weekly for the first month or two.
- How many people sign up from the people you reached. This tests the message.
- How many reach the core result once. This tests the product.
- How many come back and do it again. This is the strongest early signal.
- How many pay, or say yes when you ask them to pay.
- What people say when you ask what almost stopped them from signing up.
- Which feature requests repeat. One request is noise; the same request from several users is a signal.
When to stop or keep going
Set a review date before launch, a few weeks out. On that date, look at the signals you chose and make a clear call. If people use it, return and pay, keep going and widen the scope a little. If people sign up but do not return, fix the core experience before adding anything else. If almost nobody signs up even after real distribution effort, the problem or the message is wrong.
Stopping an MVP is not failure. It is the test doing its job. You saved months of building something people did not want, and the audience you built while testing is still yours for the next idea.
How an MVP connects to distribution
An MVP only teaches you something if people use it. That means distribution matters from day one, and it matters most in the weeks after launch, when the first buzz fades.
Keep posting what changes: every fix, every user insight, every small milestone. Forgefy turns that product activity, or a quick screenshot or voice note, into draft posts per platform plus an email and blog draft for you to approve.
What is an MVP?
An MVP (Minimum Viable Product) is the simplest version of a product that delivers enough value to attract early users and validate your business idea with minimal investment.
How long should it take to build an MVP?
Ideally 2-8 weeks. If it takes longer than 3 months, you're probably building too much. Focus on the single core feature that delivers the most value.
How do I know my MVP is minimal enough?
If you can describe it in one sentence and build it in weeks, it is probably right. If you keep saying it also needs another feature first, it is too big.
Should an MVP be free?
Charging early, even a small amount, is the strongest test of demand. Free users tell you what they like. Paying users tell you what they need.
Related