How to build a SaaS MVP: scope, cost, and timeline for founders
Most SaaS products die not because the idea was wrong, but because the founder spent a year and a fortune building version one before a single customer touched it. The fix is the MVP — a minimum viable product: the smallest version that delivers real value and lets you learn from real users. Here's how to scope, cost, and time one properly.
What an MVP actually is (and isn't)
An MVP is not a half-broken version of your full vision. It's a complete, working product for a narrow slice of the problem. It does one core thing well.
- It is: the single workflow that makes users say "I'd pay for this."
- It isn't: a prototype, a clickable mockup, or a feature-stuffed v1 with rough edges everywhere.
The goal is learning, not completeness. Every feature you add before launch is a bet you're making without evidence.
How to scope your MVP
Cut ruthlessly. For every feature, ask: does the core value work without this? If yes, it waits.
- Find the one job. What's the single outcome a user hires your product for? Build the shortest path to that.
- List features, then halve the list. Twice. Most first-cut MVP specs are 3× too big.
- Fake what you can. Manual onboarding, a human in the loop, a spreadsheet behind the scenes — all fine at MVP stage. Automate once you know it matters.
- Keep the non-negotiables. Auth, secure data, and billing usually have to be real from day one if you're charging.
What an MVP typically costs and takes
For a genuine SaaS MVP built by a competent team in India:
- Timeline: roughly 6–12 weeks for a focused product. Longer means the scope wasn't cut enough.
- Cost: typically ₹4,00,000 – ₹12,00,000, depending on how much real backend, billing, and integration the core workflow needs.
A tightly scoped MVP sits at the lower end. Scope creep is what pushes it up — which is exactly why cutting hard pays off twice.
The parts you shouldn't cut
Some things feel like "later" but aren't, if you're launching to real, paying users:
- Authentication and access control — data leaking between accounts kills trust instantly.
- Billing — if you're charging, integrate real subscriptions (Razorpay for India, Stripe globally) rather than bolting it on later.
- Basic reliability — it doesn't need to scale to a million users, but it must not fall over for the first ten.
After launch: build on evidence
Once real users are in, let their behaviour — not your roadmap doc — decide what's next. The features you were sure you needed often go unused; the ones users actually ask for weren't on your list. That feedback loop is the entire point of shipping an MVP first.
The honest bottom line
Scope your SaaS MVP to one core job, build it in 6–12 weeks for a mid-five-to-low-six-figure budget, keep auth and billing real, and launch. Then iterate on evidence. Building the "complete" product first is the expensive way to learn what you could have learned in three months.
XYOS Tecnologies builds web apps and SaaS platforms — MVP-first, on a stack that scales when you do. We build our own products too, so we know what it takes to maintain one. Tell us your idea.