A SaaS MVP must have four things from the first release: accounts with at least two roles, a subscription billing integration, the one workflow the product is sold on, and a way for you to see what each account is doing. It should leave out a public API, integrations beyond one, advanced reporting, a mobile app and a free tier. Built on one platform, a SaaS MVP costs $35,000 to $80,000 (€30,000 to €70,000, £26,000 to £60,000) and takes 10 to 16 weeks, and it is validated by ten paying accounts, not by sign-ups.
Prices are in US dollars. Euro and pound figures in parentheses are approximate, rounded conversions. Quotes are issued in the currency of your contract.
Software as a service is the most common thing founders ask us to build and the one where MVP scoping goes wrong most predictably. The product is a subscription, which means billing, accounts and tenancy are not optional, and founders either skip them and cannot charge, or build a complete platform before anyone has paid. This post sets out the minimum that makes a SaaS product sellable, what to leave for later, and what it costs.
What must a SaaS MVP include?
- Accounts and roles. An organisation, with an owner who pays and members who use. Two roles is enough. Invitations by email. This is the shape of every SaaS product and it is painful to add later, because every record in the system has to belong to an organisation from the first day.
- Subscription billing. A hosted billing provider, one or two plans, card payment, invoices sent automatically, a page where the customer can change the plan or cancel. Do not build billing yourself and do not launch without it. A SaaS product that cannot charge is a demo.
- The core workflow. The one job the product is sold on, complete from start to finish for one user type. Not three jobs partially.
- Your own view of usage. An internal admin page listing accounts, their plan, when they last used the product and what they did. You will use it every day for the first year.
Everything else is a candidate for later, and the method in how to scope an MVP decides which candidates make it.
What do founders build too early?
| Feature | Why it waits | When it earns its place |
|---|---|---|
| Public API | Nobody integrates with a product that has ten customers | When a paying customer asks and will build against it |
| Multiple integrations | Each costs weeks and most go unused | One in the MVP if the workflow needs it. Others when customers name them. |
| Advanced reporting | You do not yet know which numbers customers care about | After customers have exported the CSV a few times and told you what they do with it |
| Mobile app | Most SaaS work happens at a desk | When usage data shows the job happens away from one |
| Free tier | Attracts users who will not pay and costs support time | When you have a proven conversion path from free to paid, usually never for B2B |
| Single sign-on | Only enterprise buyers require it | When the first enterprise deal depends on it |
| White labelling, multi-language, custom domains | Each is a product of its own | When a paying segment needs it |
What does a SaaS MVP cost and how long does it take?
A SaaS MVP on one platform, usually the web, with accounts, billing, one core workflow and an admin view costs $35,000 to $80,000 (€30,000 to €70,000, £26,000 to £60,000) and takes 10 to 16 weeks. The lower end is a single-role product with a simple workflow. The upper end has two roles, one integration and a workflow with several steps. Add an integration-heavy workflow, a regulated data type or a second platform and it moves into the $80,000 to $150,000 (€70,000 to €130,000, £60,000 to £110,000) band. How much MVP development costs has the full breakdown, and the timeline follows the phases in the MVP development process.
What technical decisions matter most?
- Tenancy from the first table. Every record belongs to an organisation. Enforce it in the data layer, not in the interface. Retrofitting this is the single most expensive SaaS mistake.
- A hosted billing provider. It handles cards, invoices, tax, failed payments and plan changes. You handle the webhook that tells your product what happened.
- Boring, well-supported stack. A mainstream web framework, a relational database, managed hosting. Choosing a tech stack for an MVP gives the defaults.
- Email that works. Invitations, receipts, password resets. Use a transactional email service and test deliverability before launch.
- Backups and a delete path. Customers will ask whether their data is backed up and whether you can delete it. Both must be true and testable.
How do you validate a SaaS MVP?
Ten paying accounts. Not a thousand sign-ups, not a waiting list, not a free tier full of users. Ten organisations that entered a card and are still active a month later tell you the product is sellable. Get there by selling personally: demos, onboarding calls, weekly check-ins. The founder is the sales team until ten, and the MVP exists to support that selling with a demo environment, a clear price and a product that does the one job reliably. B2B MVP vs B2C MVP covers the design partner approach in detail, and getting your first 100 users covers the channels.
What should the pricing be at MVP stage?
Simple and not free. One or two plans, priced per seat or per account, at a level that a customer with the problem would not blink at. You will change it. The point at MVP stage is to find out whether anyone pays at all, and a price that is too low teaches you nothing. Annual plans and enterprise tiers wait until you have monthly customers who ask for them.
SaaS MVP scope
- In: organisations, two roles, invitations, billing with one or two plans, the core workflow, your admin view, transactional email, backups.
- Out: public API, more than one integration, advanced reporting, mobile, free tier, single sign-on, white label.
- Done when: ten accounts pay and stay.
How 7L builds SaaS MVPs
SaaS is the product shape we build most often, and the account, billing and admin layer is a pattern we have refined over many builds, which is why those parts cost less from us than from a team starting fresh. Discovery concentrates on the core workflow and on what the first ten customers will need to pay. If you have a SaaS idea and want the number and timeline for its first release, tell us what the workflow is.
Frequently asked questions
Can I launch a SaaS MVP without billing and add it later?
You can, but you should not. Without billing you cannot learn whether anyone pays, which is the question a SaaS MVP exists to answer. Hosted billing providers make it a week of work. Build it in.
Should a SaaS MVP have a free trial?
A time-limited trial with a card on file works well. A free tier without a card attracts users who will never pay and consumes support time. For B2B, a demo and a paid pilot usually beat both.
Do I need multi-tenancy in the MVP?
Yes, in the sense that every record belongs to an organisation from the first day. You do not need separate databases per customer. A single database with organisation ownership enforced in the data layer is the standard and scales a long way.
Web app or mobile app for SaaS?
Web, almost always. SaaS work happens at a desk, a web app serves every device, and it avoids the app store cycle. A mobile app is version two or three, when usage data shows a job that happens away from a desk.
How many customers does a SaaS MVP need before raising?
Ten paying accounts with a month of retention is a credible pre-seed story. Our post on what investors want to see in your tech before seed covers what they check beyond the customer count.