The Short Answer
What should a SaaS MVP include?
Sign-up and log-in, a workspace for each customer with their data kept separate from everyone else's, the one core workflow customers will pay for, subscription billing, transactional email and analytics on the core workflow. Buy sign-in, billing and email from proven services; build only the core workflow yourself.
The core workflow is the part that tests your idea. Everything else is the minimum needed to run it as a subscription business without putting customer data at risk. Keep that list short, and you can usually launch a SaaS MVP in weeks rather than months.
What Makes a SaaS MVP Different
| Typical MVP | SaaS MVP | |
|---|---|---|
| Customers | Individual users | Businesses or teams, each with their own workspace |
| Data | Each user sees their own data | Each customer’s data must be isolated from every other customer’s |
| Revenue | One-off purchase, ads or none yet | Recurring subscription, with upgrades, failed payments and cancellations |
| Buyers ask about | Price and features | Security, data location and what happens to their data if they leave |
| Success signal | Usage | Usage, conversion from trial to paid, and retention month to month |
The extra work is real but bounded. It is mostly decisions about how accounts and data are structured, made once at the start. Getting them wrong is expensive to fix later, because every feature you add is built on top of them.
The SaaS MVP Feature List
| Feature | MVP decision | Notes |
|---|---|---|
| Sign-up, log-in, password reset | Must, bought | Use a proven authentication service |
| Workspace per customer | Must, built | Every record belongs to a workspace; see data isolation below |
| Invite a teammate | Should | Needed for team products; one role (member) is enough at first |
| The core workflow | Must, built | The part customers pay for, and the part that tests your idea |
| Subscription billing | Must, bought | Checkout, plans, invoices and failed-payment retries from a billing provider |
| Transactional email | Must, bought | Sign-up confirmation, password reset, receipts |
| Analytics on the core workflow | Must | Activation, conversion to paid and monthly retention |
| Roles and permissions | Could | Add when a customer needs to restrict what teammates can do |
| Single sign-on (SSO), audit logs | Won’t, until a buyer asks | Enterprise features; useful later as a reason to charge more |
| Integrations marketplace | Won’t | Build the one integration your first customers cannot work without |
The Standish Group found half of all software features are hardly ever or never used, so be strict. Our guide to scoping an MVP includes a MoSCoW tool and a scope template for sorting this list.
Data Isolation Is the Biggest Risk
What is multi-tenancy in a SaaS MVP?
Multi-tenancy means one application serves many customers (tenants) while each sees only its own data. It is the standard way to build SaaS because it keeps hosting and maintenance cheap, but every query has to be scoped to the right customer, or one customer can see another's data.
That failure has a name. Broken access control, where users can act outside their intended permissions, is ranked first in the OWASP Top 10:2025, the most widely used list of web application security risks. In a SaaS product, the most damaging version is one customer reading another customer's records.
Three practices prevent most of it, and all are cheap to adopt at the start:
- Every table has a workspace ID, and the application never queries data without it.
- Enforce it in one place, such as database row-level security or a single data-access layer, rather than remembering it in every feature.
- Test it automatically: a test that logs in as customer A and tries to read customer B's data, run on every change.
For more on the security basics business buyers will ask about, see security and compliance for a first product.
Build or Buy Each Part
The rule for a SaaS MVP is to build the part that makes you different and buy the rest. Sign-in, billing and email are solved problems with mature providers; building them yourself costs weeks and adds security risk without testing your idea. The trade-off is fees and some dependence on the provider, which you can revisit once the product works. Our build vs buy guide covers that decision in detail.
Billing and Fees
Subscription billing is more than taking a payment: plans, trials, upgrades, proration, invoices and retrying failed cards. Stripe's UK Billing pricing is 0.7% of billing volume on its pay-as-you-go plan, on top of its standard card fees of 1.5% plus 20p for standard UK cards. See what that means for your price and customer numbers:
Interactive calculator
What Stripe takes from your subscription revenue
Monthly subscriptions paid by standard UK cards, at Stripe’s published UK rates.
- Monthly revenue
- £2,450
- Stripe Billing, 0.7%
- £17.15
- Card fees, 1.5% + 20p
- £46.75
- Share of revenue
- 2.6%
One card payment per customer per month. EEA and international cards cost more. At £29,400 a year, you are under the £90,000 UK VAT registration threshold. Most UK businesses handling personal data also pay the ICO data protection fee: £52 a year for the smallest tier.
The 20p fixed fee matters most at low prices: on a £10 plan it is 2% on its own. That is one reason many SaaS products push annual plans. For choosing a price in the first place, see pricing your SaaS product.
UK Rules to Know Before Launch
| Requirement | What it means | Source |
|---|---|---|
| ICO data protection fee | Most organisations processing personal data pay an annual fee: £52 (tier 1), £78 (tier 2) or £3,763 (tier 3), from 17 February 2025 | SI 2025/63 |
| UK GDPR processor contracts | Your customers are usually controllers and you are their processor, so they will expect a data processing agreement (Article 28 UK GDPR) | UK GDPR, Article 28 |
| VAT registration | Register once taxable turnover passes £90,000 in 12 months, or is expected to within 30 days | GOV.UK |
None of these should delay an MVP, but the data processing agreement often comes up in the first sales conversation with a business customer. Having a standard one ready makes you look established.
What a SaaS MVP Costs
How much does a SaaS MVP cost?
From a specialist studio, typically $15,000 to $60,000 to build, depending on the core workflow, the number of user roles and integrations. Clutch reports most software projects cost $10,000 to $49,999. Running costs, such as hosting and billing fees, come on top and scale with customers.
Clutch's 2026 pricing data puts most software projects between $10,000 and $49,999. Loomstrat Studio publishes fixed prices of $15,000 to $30,000 for a rapid MVP and $30,000 to $60,000 for a full platform. A SaaS MVP with one workflow, one role and bought-in billing usually sits in the first band; multiple roles, complex permissions or several integrations push it into the second.
For a line-by-line comparison of quotes, see what a $15k MVP includes vs a $50k quote. For timelines, see how long an MVP takes. And for SaaS built and handed over on a fixed price, see Loomstrat's SaaS platform development.
Frequently Asked Questions
What is a SaaS MVP?
The smallest version of a subscription software product that real customers can sign up for, use and pay for. It needs accounts, separate data per customer, the core workflow and billing, and little else.
Should a SaaS MVP be multi-tenant?
Usually yes. One application serving many customers keeps hosting and maintenance cheap. It needs every record tied to a customer workspace and access rules enforced in one place, with automated tests that one customer cannot see another’s data.
Do I need to build billing for a SaaS MVP?
You need billing, but you should not build it. Billing providers handle plans, trials, invoices and failed payments. Stripe Billing in the UK charges 0.7% of billing volume on pay-as-you-go, plus card fees of 1.5% + 20p for standard UK cards.
How much does a SaaS MVP cost?
From a specialist studio, typically $15,000 to $60,000 to build. Clutch reports most software projects cost $10,000 to $49,999. Scope is the biggest variable: the number of workflows, user roles and integrations.
What compliance does a UK SaaS MVP need?
Most UK organisations processing personal data must pay the ICO data protection fee, £52 a year for the smallest tier since February 2025. Business customers will expect a UK GDPR data processing agreement, and you must register for VAT above £90,000 of taxable turnover.
What is the biggest security risk in a SaaS MVP?
Broken access control, ranked first in the OWASP Top 10:2025. In SaaS, the worst case is one customer seeing another customer’s data, which is why data isolation should be designed and tested from the first week.
Get the account structure and data isolation right in week one, buy everything that is not your core workflow, and a SaaS MVP is no harder to ship than any other.