BYD TechThe short answer
A SaaS MVP is the smallest version of a subscription software product that real customers can sign up for, use for its one core job, and ideally be charged for. It needs fewer parts than most founders expect: sign-up, one core workflow, a way to take payment, and a simple admin view. Everything else, including teams, settings, reports and integrations, waits until customers ask for it.
Key points
- Four things are enough: accounts, one core workflow, billing, a basic admin view.
- Charging early is part of the test. A free product proves interest, not demand.
- Use ready-made services for sign-in, payments and email.
- Watch activation and retention, not sign-ups alone.
- Keep each customer’s data separate from the first day.
What makes an MVP a SaaS MVP
SaaS, software as a service, is software customers use in a browser and pay for on a subscription. An MVP is the smallest version real users can use. Put together, a SaaS MVP has to prove something a simple demo cannot: that a customer will sign up, come back, and pay again next month.
That is why it is more than a prototype. The differences are set out in MVP vs prototype vs proof of concept.
What a SaaS MVP needs
| Part | First version | Leave for later |
|---|---|---|
| Accounts | Email sign-up and sign-in, password reset | Single sign-on, social login |
| Core workflow | The one job the product exists for | Second and third workflows |
| Billing | One paid plan, cards, a receipt | Tiers, coupons, annual plans, usage billing |
| Admin | See customers, fix a problem by hand | A full back office |
| Welcome and essential notices | Campaigns and digests | |
| Support | A contact address and fast replies | Chat widgets, help centers |
Sign-in, payments and email are solved problems. Use an established provider for each, such as Stripe Billing for subscriptions, and spend your own effort on the workflow that is unique to you.
What usually gets cut
- Team accounts and roles, unless the product only makes sense for teams.
- A settings page for options nobody has asked to change.
- Reports and exports beyond one useful view.
- Integrations. Offer a manual import first.
- A mobile app. A responsive web app tests the same demand.
- Onboarding tours. Onboard the first customers yourself and learn where they get stuck.
What not to skip, even in an MVP
Small is not the same as careless. A few things are far cheaper to get right at the start than to repair later.
- Separate each customer’s data properly. One customer must never be able to see another’s.
- Backups, and one test that a backup restores.
- Error alerts, so you hear about a failure before a customer tells you.
- Accounts in your company’s name: code repository, cloud, domain, payment provider.
- A privacy policy and terms that match what the product actually does.
How to tell whether it is working
- Activation: of the people who sign up, how many complete the core job once?
- Retention: of those, how many come back and do it again?
- Conversion: how many start paying, and how many are still paying after the first renewal?
- What they ask for: the requests you hear repeatedly are your roadmap.
Sign-ups alone tell you your marketing works. Retention tells you the product does. We build this kind of product in web app development, and the first version in MVP development.
Sources
Checked when this guide was written.
