A minimum viable product should be small, but it should not be fragile. The goal is to learn from real users quickly while keeping the foundation solid.
Decide the one core job
Write down the single job your product does for a customer. Every feature in version one should directly support that job. Everything else goes on a later list.
Get the foundations right
- Separate each customer’s data properly from day one.
- Choose a billing approach early, even if it is simple.
- Add basic analytics so you can see what users actually do.
Launch, then listen
Put the product in front of a small group of real users, watch where they struggle, and improve in short cycles. The second version should be shaped by what you learn, not by guesses.

