Updated
Use case · SaaS Products & MVPs
SaaS MVP
The first version of a SaaS product: the smallest set of features that lets real users do the core job, built to be extended.
What is a SaaS MVP?
A SaaS MVP, or minimum viable product, is the first version of a software-as-a-service product: the smallest set of features that lets real users complete the core job and pay for it. Its purpose is to test whether people want the product, so it is built to be learned from and extended, not to be complete.
When it is needed
An MVP is the right step once a founder can name the user, the problem and the one workflow that solves it, ideally with interviews or a waiting list to support the claim. Before that point, discovery work or a clickable prototype answers the open questions for less money than code.
What it includes
- A discovery sprint that fixes scope before the build starts
- Sign-up, login and the core workflow
- Billing for at least one paid plan
- Hosting, monitoring and a release pipeline from the first week
Before the build
Decisions to make early
The single core workflow
Choose the one job the first version must do well. Every other feature is judged by whether that job fails without it.
What to buy instead of build
Authentication, payments, email and hosting are solved problems. Use providers for them and spend the build on what is unique.
How success will be measured
Decide before launch which behaviour would show the product is working, such as repeat use or a paid conversion.
What tends to go wrong
- Adding features to delay the moment real users see the product.
- Cutting quality in the core workflow, when scope was the thing to cut.
- Building without analytics, so that the launch produces opinions instead of evidence.
Where it fits
Typically connects to
- Stripe
- Auth provider
- PostgreSQL
- Vercel
Teams that use it
Industries
Terms worth knowing
Services involved
FAQ
SaaS MVP: questions and answers
What should a SaaS MVP include?
A SaaS MVP should include sign-up and login, the one workflow that delivers the product's main value, a way to pay for at least one plan, and basic analytics to show how people use it. Anything that does not serve that workflow, such as settings, integrations and admin tools, can usually wait.
What is the difference between a prototype and an MVP?
A prototype demonstrates how a product would work and is used to test an idea with users or investors; it is not built to run a business. An MVP is working software that real customers use and pay for. A prototype answers whether the idea is understood; a SaaS MVP answers whether it is wanted.
Related use cases
All 40 use casesSaaS Products & MVPs
Multi-tenant SaaS platform
A product in which each customer organisation has its own data, users and settings, on one shared codebase.
SaaS Products & MVPs
Subscription billing
Plans, trials, upgrades, invoices and failed-payment handling, wired into the product so access always matches what was paid for.
SaaS Products & MVPs
User onboarding flow
The first-run experience that takes a new user from sign-up to the moment the product becomes useful to them.
Build it. Ship it. Grow it.
Book a free 15-minute call. No sales pitch, just an honest conversation about where you are and what it would take to get where you want to be.
Book a call. It's free15-minute call. No commitment.