How Much Does a SaaS MVP Cost in India?

A SaaS MVP in India is not “an app in a month for ₹50,000.” A credible first version with authentication, a core workflow, and billing typically starts from ₹4 lakh for a fixed scope. Full multi-tenant platforms with advanced workflows and integrations often sit between ₹8 lakh and ₹25 lakh+. Those ranges are the ones we already state on SaaS development.

What belongs in an MVP

One persona, one job-to-be-done, sign-up, permissions, the smallest data model that is true, and a way to get paid or collect a waitlist. Analytics and crash reporting should be in v1. A public marketing site can launch in parallel via website development so the product repo stays focused.

What does not belong: every competitor’s feature list, native apps for both stores, and a custom billing engine if Razorpay or Stripe subscriptions already fit. Founders often smuggle a second product into “MVP” - reporting suites, white-label, and marketplace both-sides - then wonder why the calendar looks like a series A roadmap. Write the sentence “a user can accomplish X and we can charge for it.” If you cannot, you are not scoping an MVP.

Permissions look small and explode. A single-tenant internal tool is not multi-tenant SaaS. If only your company will ever log in, you may want a web application instead of tenant isolation, seat billing, and a public sign-up funnel. That distinction is the difference between a four-lakh first version and an eight-lakh platform.

Multi-tenant and billing are the expensive parts

Tenant isolation, role models, and invoices are where amateur MVPs leak data or stall at the first paying customer. We treat them as product requirements, not “phase 2 if we have time.” Isolation is not only a database column named company_id; it is queries, file storage, emails, and admin tools that cannot see the wrong tenant.

Billing is product design: plans, trials, prorations, failed payments, GST invoices for Indian customers, and what happens when a tenant churns. Using a payment provider’s subscriptions is usually faster than writing a ledger. Writing a ledger because “we might need it later” is how MVPs miss the market window.

Integrations should be listed as first-class stories: Google login, Slack, a specific accounting export. “We’ll API everything” is not a story. Each integration has a sandbox, a review, and a failure mode. Budget them or cut them.

Timeline and team shape

A focused MVP is usually a multi-sprint engagement (weeks to a few months), not a weekend hackathon. Discovery still comes first: we will tell you if an off-the-shelf product is cheaper than building. Dedicated engineers on a retainer (see hire dedicated developers) make sense after the MVP when the backlog is continuous.

For the first version, a small squad with a product owner on your side beats a large rotating bench. You need someone who can accept or reject stories in days, not a committee that meets monthly. If you cannot staff that owner, a scoped agency engagement with a PM is safer than “just developers” staring at an empty backlog.

What we need from you to quote honestly

• The persona and the one job the product must do
• Whether other companies will log in (true multi-tenant) or only your staff
• How you intend to charge, including GST if you sell in India
• Must-have integrations versus a spreadsheet import for v1
• Who will answer product questions twice a week

MVP anti-patterns we see in India briefs

“Build Uber for X” with maps, wallets, two mobile apps, and a vendor portal is not an MVP. Neither is rebuilding an incumbent’s entire settings screen. A credible first version lets a defined user complete one paid (or waitlisted) job, then tells you with analytics whether anyone cares. Native apps can wait until the web workflow is true. Admin tools can be ugly. Email can be transactional and plain.

Another anti-pattern: hiring a large bench before the problem is written down. That is the dedicated-developers conversation after a scoped v1, not instead of one. If you already have paying design partners and a repo, skip the greenfield agency theatre and staff a retainer. If you do not, do not buy months of idle capacity.

Bring a problem statement and who will pay - not a 40-page spec - to a product quote. We would rather cut scope on paper than ship a demo that cannot invoice.

Straight answers on MVP cost

Why not ₹50,000? That budget might buy a clickable prototype or a template. It does not buy authentication, tenant-safe data, billing, and a deploy you can operate. Our published SaaS starting range for a credible first version is from ₹4 lakh for fixed scope. Treating that as optional is how products stall at the first paying customer.

Do I need native apps in v1? Almost never. Prove the workflow on the web. Stores add review time, push certificates, and a second codebase. If the job-to-be-done is mobile-heavy (field capture), a responsive web app or a later dedicated mobile track is the usual sequence.

Can we skip billing? You can collect a waitlist. You cannot learn pricing. If you sell in India, GST invoices are part of “we got paid,” not a later surprise. Payment-provider subscriptions are usually enough for v1.

What if an off-the-shelf product already does 80%? Buy it. We will tell you that in discovery. Building a clone of a mature vertical SaaS because a founder dislikes the UI is how ₹8–25 lakh platforms still lose to the incumbent’s integrations.

How do you quote without a 40-page spec? Persona, one job, tenant model, charge model, integration list, and a product owner. That is enough to propose a sprint-shaped v1 or to say the brief is still a vision deck. Use the quote form rather than a teaser PDF.

When do dedicated developers replace the MVP contract? After the first version is in production and the backlog is continuous. Do not staff a retainer to discover the problem. Discover, ship a thin v1, then add capacity. That sequence is in our dedicated developers comparison as well.

Write one paragraph: who the user is, what they can finish, and how you charge. If you cannot, you are not ready to spend ₹4 lakh. If you can, attach it to a product quote and say whether other companies will log in. That is enough for us to propose a v1 or to tell you to buy an existing tool. Either answer is a successful discovery.

Founders often confuse a pitch deck with a product. Slides can promise AI, marketplaces, and mobile in the same breath. Software cannot, not in one MVP, not at the published ₹4 lakh floor. We will cut the deck until a user can finish one job. If that feels too small, you are not buying an MVP - you are buying a platform, and the ₹8–25 lakh band on SaaS development is the honest conversation. Attach the paragraph and the “who pays” sentence; we will answer with a v1 shape or a buy-not-build recommendation, not a vanity prototype. A paid discovery week is cheaper than a confused start.