The short answer: what a SaaS MVP costs in India in 2026
A serious SaaS MVP built in India in 2026 costs Rs. 3,00,000 to Rs. 30,00,000 plus 18 percent GST. A single workflow product lands near Rs. 4,00,000. Multi-tenant SaaS with subscription billing sits at Rs. 8,00,000 to Rs. 15,00,000. A two sided marketplace crosses Rs. 20,00,000.
That is a wide band because “MVP” is not a size, it is a decision about how much you are willing to leave out. Two founders can ask for the same product and get quotes four times apart, and both can be honest. The difference is almost never the hourly rate. It is the number of user roles, whether many companies share one database, whether money moves inside the product, and how much operational tooling you want on day one.
What belongs in an MVP, and what does not
The most expensive mistake in Indian SaaS is not a costly vendor. It is building version three before anyone has paid for version one. An MVP exists to buy information, not to impress a demo audience.
The three questions an MVP has to answer
Every rupee should go towards answering these: will a specific user complete the core workflow without hand holding, will they come back next week, and will they pay. If a feature does not move one of those three, it is not MVP scope. That single filter typically removes 30 to 40 percent of a founder’s original feature list and saves Rs. 2,00,000 to Rs. 5,00,000.
The features that can wait until you have paying users
Cut these from round one without guilt: a mobile app when a responsive web app will do, in-app chat, granular permission matrices, custom report builders, multi-currency, multi-language, a public API, gamification, and integrations nobody has asked for in writing. If you genuinely need native apps later, read our breakdown of mobile app development cost in India before committing budget.
What you must not cut: real authentication, an admin panel your own team can operate, error logging, and data export. Those four are what separate a product from a prototype.
Cost by scope: the three MVP shapes
Almost every SaaS MVP request falls into one of three shapes. Price the shape first, then argue about features inside it.
| MVP shape | What is included | Build time | Cost before GST |
|---|---|---|---|
| Single workflow tool | One user type, one core job, basic admin, manual onboarding | 6 to 9 weeks | Rs. 3,00,000 to Rs. 6,00,000 |
| Multi-tenant SaaS with billing | Workspaces, roles, self signup, plans, subscriptions, invoices, admin console | 10 to 16 weeks | Rs. 7,00,000 to Rs. 15,00,000 |
| Two sided marketplace | Two onboarding flows, matching, escrow or split payouts, disputes, moderation | 16 to 26 weeks | Rs. 12,00,000 to Rs. 30,00,000 |
Single workflow MVP: Rs. 3,00,000 to Rs. 6,00,000
One role, one screen that matters. A clinic queue manager, a quotation generator for a niche trade. You onboard customers manually, invoice them offline, and the software only does the job nobody wants to do in a spreadsheet. This is where most bootstrapped founders should start.
Multi-tenant SaaS with billing: Rs. 7,00,000 to Rs. 15,00,000
The moment strangers can sign up and pay without you, cost roughly doubles. You now need tenant isolation so Company A can never see Company B’s data, an invite and roles system, plan limits enforced in code, a gateway with recurring mandates, dunning for failed payments, GST compliant invoices, and an internal console to refund, extend trials and impersonate a user for support. Gateway choice matters more than founders expect, so compare payment gateway options in India before the build starts, not after.
Two sided marketplace: Rs. 12,00,000 to Rs. 30,00,000
Two audiences means two products. Supply onboarding with verification, demand onboarding, matching or search, money held and split, refund rules, ratings, and a moderation queue for the fraud that arrives in month two. Our comparison of an ecommerce website versus a marketplace in India will tell you whether you can start on one side only and halve the first build.
The line items founders forget to budget
Most founder budgets cover screens and ignore the machinery behind them. The project then runs 40 percent over and everyone blames scope creep, when the scope was never written down.
| Forgotten item | Why you cannot skip it | Typical cost |
|---|---|---|
| Auth, sessions, password reset, OTP | Security and account recovery on day one | Rs. 40,000 to Rs. 90,000 |
| Roles and permissions | Owner, manager and staff never see the same data | Rs. 50,000 to Rs. 1,50,000 |
| Billing and subscription logic | Plans, proration, failed payments, GST invoices | Rs. 1,00,000 to Rs. 3,00,000 |
| Admin panel for your team | Support without a developer running database queries | Rs. 80,000 to Rs. 2,50,000 |
| Email, SMS and WhatsApp notifications | Onboarding, invoices, alerts, deliverability setup | Rs. 40,000 to Rs. 1,20,000 |
| Product analytics and error tracking | You cannot iterate on an MVP you cannot measure | Rs. 30,000 to Rs. 80,000 |
| Deployment, backups, staging | Safe releases and a restore path that has been tested | Rs. 40,000 to Rs. 1,00,000 |
| Documentation and handover | So the next developer is productive in days, not months | Rs. 25,000 to Rs. 60,000 |
Cloud cost at 50 users versus 5,000 users
At pilot scale, an Indian hosted SaaS runs on Rs. 3,000 to Rs. 12,000 a month: one application server, a managed database, object storage, a transactional email service and a monitoring tier. The real jump comes later, at a few thousand active users with file uploads and reports, where Rs. 25,000 to Rs. 70,000 a month is normal. Budget twelve months of infrastructure inside your MVP number, and decide early whether Indian data residency is a customer requirement, because moving regions later is a paid migration.
Realistic build timelines
A single workflow MVP takes 6 to 9 weeks. Multi-tenant SaaS with billing takes 10 to 16 weeks. A marketplace takes 16 to 26 weeks. Anyone promising a billing enabled SaaS in four weeks is either reskinning a template, planning to skip testing, or has not read your requirements.
Add two weeks that no proposal shows: your own review cycles. The client side, not the vendor, is the most common cause of delay in Indian software projects. Name one decision maker who can approve designs within 48 hours. Insist the timeline is milestones with demo dates, not a single delivery date, so slippage is visible in week three instead of week thirteen.
Fixed scope or dedicated team: how to decide
Fixed scope means an agreed feature list, a fixed price and fixed milestones. A dedicated team means you pay per developer per month, typically Rs. 1,20,000 to Rs. 2,50,000, and direct the work yourself. Both are legitimate. Choosing wrong costs money.
Fixed scope protects you when requirements are stable and you want a predictable number for a board or a bank. Its weakness is change: every alteration becomes a priced change request, and a defensive vendor slows down. A dedicated team suits ongoing discovery and an in house owner who can prioritise weekly. Its weakness is drift that you pay for monthly.
Why most MVPs should start fixed and then move to a retainer
The pattern that works for a Rs. 5,00,000 to Rs. 15,00,000 build: fix the first release, then convert to a monthly retainer of Rs. 60,000 to Rs. 2,00,000 once real users arrive and priorities start changing every fortnight. You get a firm number for the part investors ask about and flexibility for the part that actually determines whether the product works. Get the change request rate written into the fixed contract so mid-project additions are never a negotiation from zero.
Equity for build offers, and why they usually go wrong
Founders often ask a development company to build for equity, or a discounted fee plus a stake. It sounds aligned. In practice it fails for both sides more often than it works.
The agency’s incentive is delivery, and equity pays only on an exit that is years away and statistically unlikely. So the equity project quietly becomes the lowest priority queue in the studio, worked on between paying clients, while the founder resents slow progress on what they consider a partnership. On your side, a cap table with a service provider holding 8 or 10 percent, unvested and with no operational role, is a genuine problem in your first institutional round. Investors read it as a founder who paid for a commodity with the most expensive currency they had.
If you still want alignment, structure it properly: cash at a reduced rate, plus advisory equity of 0.5 to 2 percent with vesting and a defined ongoing role, plus a success fee tied to a milestone. Never hand over founding shares for a delivery contract, and never sign an equity build without the IP assignment clauses you would demand in a paid one.
GST, payment terms and what a clean commercial looks like
Software development services attract 18 percent GST. A Rs. 10,00,000 build is Rs. 11,80,000 out of your account. If you are GST registered that input credit is claimable, so the real gap between a registered vendor and an unregistered freelancer is smaller than it looks, while the accountability gap is enormous. Ask for the GSTIN on the proposal, not after the first invoice.
Healthy payment terms here: 25 to 30 percent to start, milestone payments tied to demonstrable deliverables, and 10 to 15 percent held until handover and warranty end. Reject a 100 percent advance, and reject 50 percent on a Rs. 15,00,000 project. Expect a 30 to 90 day warranty covering defects in delivered scope at no cost, kept separate from new feature requests.
Get your MVP scoped before you spend a rupee
Send us your idea and we will come back with a written feature list, a milestone plan and a fixed price for release one, so you know exactly what you are buying and what we deliberately left out.
IP, source code ownership and escrow
Assume nothing. Unless the agreement assigns intellectual property to you on payment, the developer can retain rights in what they wrote. For a SaaS company the code is the company, so this is not a formality.
The clauses to insist on before the first milestone
- Assignment on payment: all IP in deliverables transfers to your company as each milestone is paid, including designs and database schema.
- Repository in your name: the Git organisation is owned by your company from commit one and the vendor is added as a collaborator, not the other way round.
- Infrastructure in your accounts: cloud, domain, email service and gateway accounts are registered to you, with the vendor given access.
- Licence disclosure: a written list of every library, template and paid component used, with its licence.
- Exit and handover: a defined 30 day transition with documentation, credentials and a walkthrough.
Software escrow, where a third party holds a copy of the source and releases it if the vendor fails, is worth arranging above roughly Rs. 15,00,000 or where the vendor also hosts your production system. Below that, owning the repository yourself gives you most of the same protection for free. Our custom software page lists the artefacts we hand over at each stage.
What technical due diligence will look for later
If you raise beyond an angel round, a reviewer will spend two days in your codebase and accounts. What you decide now decides how that goes.
They check who legally owns the code and whether assignment paperwork exists for every contributor including freelancers. They check the repository history, because a single commit dated last week says the vendor kept the real history. They look for secrets committed in plain text, a tested backup and restore, how tenant data is isolated, and whether critical logic has any automated tests. They look at dependency age and licences, and at your data handling against Indian data protection expectations.
None of this needs enterprise engineering at MVP stage. Keep five artefacts from day one: the signed IP assignment, the repository under your organisation, a short architecture note, an up to date environment and credentials list, and a written scope and change log. Founders who have those clear a technical review in a week. Founders who do not spend Rs. 3,00,000 on a remediation sprint under time pressure.
When you should not build a custom MVP at all
An honest development partner will sometimes tell you to spend nothing. Custom code is the wrong first move in four situations.
You have no committed users yet. If you cannot name ten businesses who have said they will pay, run the service manually first. Spreadsheets, forms and WhatsApp will validate demand in three weeks for under Rs. 25,000, and the learning will change your feature list beyond recognition.
An existing SaaS already does 80 percent of it. If a Rs. 2,000 per month tool covers most of the workflow, use it and pay for a thin integration or automation layer at Rs. 50,000 to Rs. 2,00,000. Rebuilding a mature product to save a subscription fee is the most common way founders lose a year.
Your workflow is simple and internal. No-code and low-code platforms handle internal tools, approval flows and simple portals well, at Rs. 40,000 to Rs. 2,50,000 to configure. The honest limits: per record pricing gets painful at scale, deep customisation hits a wall, and the platform vendor controls your product. Start there anyway if the alternative is not starting.
Your budget is under Rs. 3,00,000 for a multi-tenant product. Either narrow the scope until it fits, or wait. A half funded SaaS build produces something that cannot be sold and cannot be extended, which is worse than nothing. If it turns out you needed a strong web presence rather than a product, our web development service is the cheaper and faster answer.
Codelith Lab is based in Pune and builds SaaS products, custom software and web platforms for founders and companies across India. We would rather tell you to spend Rs. 50,000 on validation than take Rs. 10,00,000 for a product with no buyer.
Also read: compare budgets in our guides to mobile app development cost in India and ecommerce website development cost in India, and see how we run a build on our custom software page.
