Every SaaS cost estimate I read quotes one number: the build. ₹1,50,000 to ₹5,00,000 for an MVP in India, 10 to 24 weeks, thanks for reading.
That number is real. It is also not the bill.
A website is a one-time purchase that then sits there. A SaaS is a running process with a monthly invoice attached, and the gap between those two facts is where first products die. Not in the build. In month four, when the card on the hosting account declines.
Here is the year-one arithmetic, in actual rupees, for a small Indian SaaS.
What year one costs on top of the build
| Running cost | Typical year one | What actually drives it |
|---|---|---|
| Cloud hosting | ₹18,000 – ₹96,000 | ₹1,500–₹8,000/month. An early SaaS rarely needs more than one small server plus a managed database |
| Domain + SSL | ₹1,000 – ₹3,000 | Domain renewal. SSL is free via Let's Encrypt — never pay for a basic cert |
| Transactional email / SMS | ₹6,000 – ₹36,000 | ₹500–₹3,000/month. Signup, reset, invoices. Scales with users, not features |
| Maintenance & updates | ₹33,000 – ₹1,65,000 | ₹3,000–₹15,000/month × 11 |
| Payment gateway | ~2% of revenue | Not fixed — you only pay when a customer pays you |
| Year-one total (excl. gateway) | ₹58,000 – ₹3,00,000 | On top of the ₹1,50,000–₹5,00,000 build |
Run it honestly and the headline changes:
- A lean ₹1,50,000 MVP is really about ₹2,10,000 in year one.
- A ₹5,00,000 build on a full maintenance plan is closer to ₹8,00,000.
If your entire budget is the build number, you have funded a launch, not a product.
Why the infra line is not optional the way founders think it is
The instinct is to treat hosting as the thing you cut. It is the smallest line on the table and the one that looks most like someone else's markup. But it is the only line that is load-bearing for the thing you actually sold: uptime.
A brochure site being down for an hour is embarrassing. A SaaS being down for an hour loses customers permanently, because the customer's work stopped. That asymmetry is the entire reason a SaaS costs more than a website with the same screen count, and it shows up everywhere in the codebase:
- Accounts, roles, permissions. Signup, login, reset, sessions, and rules about who may see what. Every rule is a thing to build and a thing to test.
- Data isolation between tenants. Customer A must never see customer B's rows. This shapes your schema on day one and it is the one bug you genuinely cannot ship.
- Subscriptions and billing. Recurring payments, failed cards, upgrades, refunds, GST invoices. Billing is a product in its own right, and it is where "two more weeks" comes from.
- An admin console. You will need to fix customer accounts by hand in month one. It is a second application, and it is why scope quietly doubles.
- Uptime and backups. See above.
None of that is visible to the user. All of it is why the number is what it is.
Where the build calendar actually goes
Same split as any medium project: roughly 10% discovery, 20% design, 45% development, 15% testing, 10% deployment.
Only about 45% of what you pay for is someone writing product code. That is not padding — it is the reason fixing scope early saves more money than any negotiation over the hourly rate ever will. You cannot rate-negotiate your way out of a discovery phase you skipped.
The five things to cut, with numbers
The fastest way to bring a ₹4,00,000 quote to ₹2,00,000 is not a cheaper developer. It is deleting the things that do not answer the only question an MVP exists to answer: will anyone pay for this?
| Feature | Verdict | Roughly what it adds | Do this instead |
|---|---|---|---|
| Mobile app alongside web | Cut | ₹50,000 – ₹1,50,000 | A responsive web app reaches every user on day one |
| Custom analytics dashboard | Cut | ₹40,000 – ₹1,00,000 | CSV export + a spreadsheet answers the same questions at ten users |
| SSO / SAML | Cut | ₹30,000 – ₹80,000 | Email + Google login. Build SSO when an enterprise buyer asks and pays |
| Multiple pricing tiers | Cut | ₹30,000 – ₹70,000 | Launch with one price. You don't yet know what anyone will pay |
| Public API | Cut | ₹40,000 – ₹1,00,000 | Nobody integrates with a product that has no users |
Cut all five and a mid-band quote drops by roughly ₹1,90,000 to ₹5,00,000 of scope. Not one of them makes the product more likely to find a paying customer. Every one of them can ship in phase two, with revenue, once you know which ones customers actually ask for.
The uncomfortable part
Some of you should not build this yet. Specifically, if:
- You haven't spoken to ten potential users. Not friends — people with the problem and a budget. Costs ₹0 and a fortnight, and it changes the scope of most products.
- A spreadsheet and an existing tool could fake it. Run the workflow manually for three to five paying customers first. If they won't pay for it done by hand, they won't pay for it automated. If they will, you now have revenue, real requirements, and a cheaper build.
- You need revenue within three months. An MVP takes 10–24 weeks. The arithmetic does not work, and anyone who tells you otherwise is not being straight with you.
- A no-code prototype could prove the workflow. Bubble, Glide or an Airtable flow can validate a single workflow for ₹0–₹30,000. They won't scale — that's fine, that isn't the job yet.
Writing the code is the fun part. It is also the part you should be most willing to postpone.
Disclosure: I work with ZoopCoder, an Indian dev agency, so treat the "when not to build" section knowing we'd be turning down that work. The ₹ bands above are our published prices, not an estimate — hosting/email/gateway figures are typical Indian market rates you should verify with each vendor. Full breakdown with the scope tiers and year-one table: How much does a SaaS MVP cost in India?
Top comments (0)