MVP Launch: How to Launch a Minimum Viable Product
An MVP launch puts the smallest version of your product that solves one problem in front of real users, so you can learn whether they want it before you build more. It’s ready when a stranger can sign up, reach the one useful result and pay (if you’ll charge) without your help. Launch it in two or three places where your users already are, then watch what they do and talk to them before adding features.
Why do so many MVPs never launch?
The list keeps growing. One more feature so the first users won’t leave, a nicer dashboard so it looks serious, an import so switching is easy. Each one feels like the thing that will make the launch work, and three months later the MVP is still on your laptop.
The cost is the one thing an MVP exists to give you: real feedback. Every week you don’t launch is a week of building on guesses, and some of what you’re polishing may be features nobody needed.
What does minimum viable mean?
- Minimum: it does one job. Not the full vision, one problem solved end to end.
- Viable: it does that job well enough that someone would use it again, or pay for it.
| In the MVP | Can wait |
|---|---|
| The one core action, working every time | Secondary features |
| Signup and the first run, tested by strangers | Settings for every preference |
| Payments, if you’ll charge | Multiple plans and annual billing |
| A way for users to reach you | A help center |
| A landing page that says what it does | A full marketing site |
| Basic analytics: signups, activation, sources | Dashboards |
If a missing feature would stop a user from getting the core result, it’s in. If it would only make the product nicer, it waits.
How do you know your MVP is ready to launch?
Run this test: give the link to three people who’ve never seen the product and say nothing. If at least two get to the core result on their own, it’s ready. If they get stuck at the same step, fix that step and test again.
Our SaaS launch checklist has the full pre-launch list, and soft launch vs hard launch explains how to run a quiet first release before the public one.
Where should you launch an MVP?
Places that welcome early products and give feedback:
- Launch platforms that accept new and unfinished products. Product launch platforms compared by how they work explains the formats.
- Show HN, if it’s technical. The guidelines say it doesn’t need to be finished, but it must be ready to try. Show HN: how to post your product on Hacker News covers the rules.
- Communities where your users discuss the problem, following each one’s rules.
- Pre-launch directories, if it isn’t public yet and you want signups.
Be upfront that it’s an MVP. “This is an early version, here’s what it does, here’s what’s missing” gets more patience than pretending it’s finished.
What should you measure after an MVP launch?
Three things matter at this stage:
- Activation: how many signups reach the core result.
- Return: how many come back after a week.
- Reasons: what people say when you ask why they signed up and why they left.
Numbers tell you where people drop off; conversations tell you why. SaaS metrics to track after launch covers the formulas, and how to keep users after launch covers what to do with what you learn.
Can you launch an MVP on LaunchGP?
Yes, if it’s live and has a website. We run LaunchGP, and an MVP gets this there:
- A week, not a day. Each Grand Prix runs Monday to Monday with 32 cars, ranked by votes over the whole week.
- A free seat with the LaunchGP badge on your site, one of 20 per round. A front slot (P1 to P6, $59 down to $9) needs no badge.
- A reason to ship. After the race, your MVP joins LaunchGP Endurance. Each update you log as a pit stop refuels your car and adds pace for three days, which suits the weekly rhythm of a product that’s still taking shape.
- Another round when it’s better. A product can take a free seat in any round, one per round, so you can race again after a big release.
What’s the next step?
Cut the feature list to the one core job, run the three-stranger test this week, and launch the version that passes.
A seat is free with the badge, and a front slot starts at $9.
Get your seat in the next Grand Prix
FAQ
What is an MVP launch?
Releasing the smallest version of a product that solves one problem to real users, to learn whether they want it before building more.
How long should it take to build an MVP?
As long as it takes to make one core job work reliably, and no longer. If the list keeps growing, cut it back to that one job.
Should I charge for my MVP?
If you plan to charge later, yes, because payment is a stronger signal than free use: it shows the problem is worth money to someone.
What if nobody uses my MVP?
Ask the people who signed up and left what they expected. The answer is often about the message or the first step, and both are cheaper to fix than the product.
Is an MVP the same as a beta?
Not quite. A beta is a testing phase with people who expect rough edges. An MVP is the smallest real product, and it can go through a beta before its public launch.