SaaS MVP Development: From Idea to Paying Users
A SaaS MVP needs three things a normal MVP does not: somebody can sign up without you, somebody can pay without you, and tenants cannot see each other’s data. Everything else can wait. Typical cost £30,000–£80,000, typical timeline eight to twelve weeks.
The distinction matters because a SaaS MVP is testing a different hypothesis. A normal MVP asks whether the product solves the problem. A SaaS MVP asks whether people will pay for it repeatedly without being sold to each time — which means self-service signup and billing are the test, not features you can add later.
- If you have to onboard each customer personally, you have not tested the SaaS model.
- Decide tenancy early. It is very hard to change afterwards.
- Use Stripe. Building billing is a product in itself.
- Cut admin dashboards, granular permissions and scale engineering. Keep signup, billing and isolation.
What to build
| Build | Defer |
|---|---|
| Self-service signup | SSO and enterprise auth |
| Subscription billing on Stripe | Usage-based pricing, annual plans, invoicing |
| Tenant isolation | Database-per-tenant unless genuinely required |
| The one workflow that is the product | The surrounding features you imagine people want |
| Basic usage analytics | A reporting suite |
| A way to support customers manually | A custom admin console |
The tenancy decision
Shared schema with disciplined tenant scoping is right for most SaaS products and is what we would default to. The discipline matters: every query must be scoped, and one missed filter is a data leak rather than a bug. Schema-per-tenant suits fewer, larger customers; database-per-tenant suits regulated data and contractual isolation. Choose deliberately, because retrofitting isolation into a product that assumed none is close to a rebuild.
Getting to the first payment
The sequence that works: build the one workflow that is the product, put signup and Stripe around it, charge from day one even if the price is wrong, and watch what happens at the payment step. Free pilots feel like progress and tell you very little — people will accept something free that they would not pay for, and that gap is the entire question an MVP exists to answer.
Frequently asked questions
Should we charge during the MVP?
Yes. Willingness to pay is the hypothesis. Charge less than you eventually will if you like, but charge — a free pilot proves people will accept free.
How much does a SaaS MVP cost?
Typically £30,000–£80,000. Billing and tenancy are the lines most often underestimated, because they look like solved problems until the edge cases arrive — mid-cycle upgrades, failed payments, refunds.
Can we use no-code first?
Often yes, and we will say so. If a no-code tool plus a payment link tests willingness to pay in two weeks, do that first. Custom development earns its place when the software itself is the thing being tested.
When do we rebuild?
Later than founders expect. A well-built MVP should carry you to meaningful revenue. Rebuilding at the first sign of scale usually means the first version was built without the architecture decisions above, not that rebuilding was inevitable.
We build these as SaaS products and MVPs, scoped around the riskiest assumption rather than a feature list.
