A focused B2B SaaS MVP built in India typically costs ₹10–18 lakh and ships in 12–18 weeks, covering sign-up and login, subscription billing, the core workflow and a basic admin. The fastest MVPs solve one job for one type of customer, use proven services for auth and billing, and build multi-tenancy in from day one.
This playbook walks through the decisions that decide whether your SaaS MVP ships on time and survives its first paying customers: scope, stack, hosting, billing, compliance and a realistic week-by-week plan.
1. Scope: one customer, one job
Most SaaS MVPs run late because they try to serve everyone. Write down:
- Who the first paying customer is, as specifically as possible (“operations managers at 20–200 person logistics firms”).
- The one job they hire your product for.
- What they use today instead: spreadsheets, WhatsApp, an old tool. Your MVP only needs to beat that.
Everything that does not help that customer do that job goes on a “later” list. Reporting dashboards, integrations with five tools, mobile apps and custom roles are common candidates for later.
2. What a SaaS MVP must include
| Must have at launch | Can usually wait |
|---|---|
| Sign-up, login, password reset, team invites | SSO and SAML |
| Multi-tenant data separation | Dedicated databases per customer |
| Subscription billing with a trial | Usage-based pricing and complex proration |
| The core workflow, done well | Secondary workflows |
| Basic admin to manage customers and plans | Full back-office tooling |
| Error monitoring, backups, product analytics events | Custom analytics dashboards |
| Transactional email | In-app guides and automation |
3. Multi-tenancy: decide on day one
Retrofitting multi-tenancy later is one of the most expensive rewrites in SaaS. For most B2B products we default to a shared database and shared schema in PostgreSQL, with a tenant ID on every row and row-level security, so every query is scoped to one customer. Enterprise customers who need stronger isolation can later get their own schema or database. Enforce plan limits and feature flags in the backend, not just in the UI.
4. Stack: boring and proven
An MVP is the wrong place to experiment. A common, well-supported setup:
- Frontend: React with Next.js and TypeScript.
- Backend: Node.js with TypeScript for most product APIs, or Python if AI and data work are central. Our Node.js vs Python guide covers the trade-offs.
- Database: PostgreSQL.
- Auth: a proven auth library or service rather than hand-rolled login.
- Billing: Razorpay for Indian customers, Stripe or Paddle for international ones.
- Monitoring: error tracking and uptime alerts from the first deploy.
5. Hosting and data location
If your customers are Indian businesses, hosting in India keeps latency low and simplifies data-residency questions in sales calls. AWS, for example, has two Indian regions: Mumbai (ap-south-1) and Hyderabad (ap-south-2). For global customers, pick the region closest to most of your users and keep backups in a second region.
6. Billing and tax
Billing becomes a core product surface the day you have paying customers. Plan for trials, upgrades and downgrades, failed-payment retries, invoices and refunds. In India, SaaS and software services are taxed at 18% GST, and services exported to customers outside India are zero-rated when supplied under a Letter of Undertaking, so your invoices need to handle both. Payment fees matter too: Razorpay’s standard plan, for example, charges a 2% platform fee on domestic payments plus GST on the fee.
7. Data protection from the start
India’s Digital Personal Data Protection Rules were notified in November 2025 with compliance phased in over 18 months. A SaaS MVP built now should include clear consent and privacy notices, the ability to export and delete a user’s data, access logs for admin actions, and encryption in transit and at rest. Building these early is far cheaper than retrofitting them before an enterprise deal.
8. A realistic 16-week plan
| Weeks | Focus | You should be able to see |
|---|---|---|
| 1–2 | Discovery, user flows, data model, architecture | Clickable prototype of the core workflow |
| 3–4 | Auth, tenants, team invites, base UI | Sign up, create a workspace, invite a colleague |
| 5–10 | Core workflow in two-week sprints | A working demo at the end of every sprint |
| 11–12 | Billing, plans, trial, admin | Subscribe, upgrade and manage customers |
| 13–14 | Onboarding, emails, analytics events, hardening | New users reach the first useful result on their own |
| 15–16 | Testing, performance, security review, launch | Live with first pilot customers |
Plans with heavy integrations or compliance work run longer; plans with a very tight scope can finish closer to 12 weeks.
9. What it costs
Based on the ranges we publish for SaaS development:
- Focused B2B SaaS MVP: from ₹10–18 lakh, typically 12–18 weeks.
- Production SaaS with multi-tenant architecture, subscription billing, role-based access and 3–5 integrations: ₹20–45 lakh, typically 5–8 months.
- Enterprise SaaS with SOC 2 or ISO 27001 posture and a large integration surface: more, depending on scope.
Running costs such as hosting, email, monitoring and payment fees are separate. Our guide to the cost of custom software development in India covers those in detail.
10. Corners you can cut, and corners you cannot
Safe to cut: custom design for every screen, native mobile apps, advanced reporting, SSO, integrations nobody has asked for yet.
Do not cut: tenant isolation, backups, error monitoring, secure auth, automated tests for billing and the core workflow, and a clean way to deploy and roll back.
If you are deciding whether to build at all, our SaaS vs custom software comparison may help. When you are ready to scope your MVP, book a free discovery call and we will turn it into a written, milestone-based plan.
Frequently asked questions
How much does a SaaS MVP cost in India?
A focused B2B SaaS MVP typically starts at ₹10–18 lakh. Production SaaS with multi-tenancy, billing, role-based access and several integrations runs ₹20–45 lakh.
How long does it take to build a SaaS MVP?
Usually 12–18 weeks for a focused MVP with auth, billing, the core workflow and a basic admin. A production-grade platform typically takes 5–8 months.
Should my SaaS MVP be multi-tenant from the start?
Yes. A shared database with a tenant ID on every row and row-level security is simple to build on day one and very expensive to add later.
Razorpay or Stripe for SaaS billing?
Razorpay is the usual choice for Indian customers and UPI payments. Stripe or Paddle suit international customers. Many Indian SaaS companies use one for domestic and one for international billing.
Do I charge GST to international SaaS customers?
Exports of services are generally zero-rated under GST when you supply under a Letter of Undertaking. Confirm your specific case with your chartered accountant.
Do I need a mobile app for my SaaS MVP?
Usually not. A responsive web app covers most B2B users at launch. Add mobile apps once you know which workflows customers need on their phones.
