When to launch your MVP

The actual bar

One real person, who is not you, can complete the one job your product exists to do, without you sitting next to them, and give you money for it.

That is it. Break it down, because every clause is doing work:

1. One real person. Not a persona. A named human who has the problem and did not previously owe you a favour.
2. The one job. The single outcome you would put on the landing page. If you cannot name it in a sentence with no "and", the scope is still too big to launch.
3. End to end. From arriving to getting the result. Not the interesting middle part while you manually handle the start and the finish.
4. Without you intervening. You can do the delivery by hand behind the scenes, but the user should not need you on a call to get through it.
5. And pay you. Money is the measurement. Launching without a way to pay is running the experiment with the instrument switched off.

What is not the bar

None of the following has ever determined whether a product worked, and all of them are excellent places to hide:

I have seen beautifully architected products make $0 and absolute spaghetti code disasters do $80k MRR. The difference was never the tech stack.

via r/SaaS

The hiding test

Here is the question that settles it. Name the specific thing you are waiting on, then ask: did a user ask for this?

If a real person said "I cannot use this until it does X," that is a blocker and you should build X. If the answer is that it does not feel finished, that you would be embarrassed, or that you want it to be good before people see it, that is not a launch criterion. That is a feeling, and building another feature will not resolve it, because the feeling is not about the feature.

At some point I realized I was probably just hiding behind development because it’s easier to sit down and code than to actually find people and ask them to use something you’ve built.

via r/SaaS

The tell is a moving finish line. If shipping the last must-have produced a new must-have, and that has happened more than twice, you are not converging on a launch. You are generating reasons not to have one, and you will keep generating them indefinitely because it is safer than finding out.

What genuinely must work

"Launch before you are proud of it" gets misread as permission to ship something broken. It is not. There are three things that have to be right, because getting them wrong does damage you cannot undo with an apology:

1. Money moves correctly. The right amount, once, from the right person, with a receipt they can find. Billing errors are the fastest way to turn a forgiving early user into someone who warns other people about you.
2. Data does not disappear. Whatever they put in stays there. You can lack features; you cannot lose their work.
3. The promise on the page is true. Under-promise freely. Claiming something the product does not do is the one category of early mistake that reads as dishonesty rather than immaturity.

Everything else is negotiable on day one. Ugly is fine. Narrow is fine. Slow is survivable. Manual behind the curtain is often better than automated, because it teaches you what to automate.

What happens after you launch

Mostly, nothing. This is the part nobody prepares you for and it is the single most common post-launch experience:

Building the app was much, much easier than getting people to discover it.

via r/SaaS

A launch is not a distribution strategy. It is the moment the real work starts, and the quiet afterwards is normal rather than a verdict on the product. Context for expectations: the median tracked startup with any revenue at all sits at $145 a month from 8 subscribers, and those are the ones that got somewhere.

So plan the week after launch before you plan the launch. Who are you contacting, where are you answering questions, what are you watching. The SaaS launch checklist covers the mechanics, and how to get your first 10 customers covers what to do when the silence sets in.

BigIdeasDB Research. (2026). When to launch your MVP. BigIdeasDB. Retrieved from https://bigideasdb.com/guides/when-to-launch-your-mvp