In 2026, SaaS development in India costs roughly 4 to 10 lakh for a lean MVP, 12 to 35 lakh for a first version you can actually sell, and 35 lakh to a crore for a multi-tenant platform with integrations and enterprise requirements. Those are the ranges established agencies quote. The number that matters more is the gap between the first two rows, because it explains why two quotes for "the same SaaS" can differ by five times, and it is the gap most first-time founders fall into.
The quick-reference table
| Stage | What it includes | Typical range (INR) | Typical range (USD) | Timeline |
|---|---|---|---|---|
| Lean MVP | Sign-in, one core workflow, a basic dashboard, payments by link or invoice, one company at a time | 4 to 10 lakh | $5,000 to $12,000 | 6 to 10 weeks |
| First sellable version | Self-serve sign-up, plans and subscriptions, organisations and roles, one core workflow, an admin panel, transactional email | 12 to 35 lakh | $15,000 to $42,000 | 10 to 20 weeks |
| Multi-tenant platform | Several workflows, multiple user types, integrations, usage metering, reporting, audit logs, single sign-on for enterprise buyers | 35 lakh to 1 crore | $42,000 to $120,000 | 4 to 8 months |
| Regulated or at scale | Compliance work (DPDP, GDPR, SOC 2), data residency, multi-region hosting, mobile apps alongside the web product | 1 crore and up | $120,000 and up | 8 months and up |
The hourly rates behind these numbers run $15 to $40 for an experienced Indian agency team, against $80 to $150 in the US and Western Europe, the same band as in our app development cost guide. SaaS work sits in the upper half of that band more often than mobile apps do, because it is heavier on backend, billing and security and lighter on screens.
Why quotes for the same SaaS differ by five times
Look at the difference between the first two rows. The feature is identical. What changes is everything around it: self-serve sign-up instead of accounts you create by hand, subscriptions that renew, fail and upgrade mid-cycle instead of a payment link, organisations with owners and members instead of a single login, and an admin panel your support team can use instead of asking an engineer to run a database query.
On most projects roughly half the build is that supporting software. It is also the half that cheap quotes leave out, and not always dishonestly: an agency that has never run a subscription product does not know the failed-card path exists until a customer hits it. The 4 lakh quote and the 20 lakh quote are usually both accurate. They are pricing different products, and only one of them can take a stranger's money on a Tuesday night without anyone from your company being awake.
Where the money goes: a worked estimate
Tier tables hide the arithmetic, so here is an estimate for a concrete product. Take a field-service SaaS: companies sign up, add their technicians, schedule jobs on a calendar, their customers get an SMS or WhatsApp update, and the company pays per technician per month. This is the shape of a large share of Indian B2B SaaS, and the estimate is how we would break it down after discovery.
| Work package | Person-days | Share of budget |
|---|---|---|
| Discovery and scoping | 5 | 4% |
| Design: flows, screens, a clickable prototype, including settings and admin screens | 15 | 12% |
| Accounts, organisations, roles and invitations | 12 | 10% |
| Plans, subscriptions, invoices and failed-payment handling | 15 | 13% |
| The core workflow: technicians, jobs, calendar, assignment | 25 | 21% |
| Customer notifications: SMS, WhatsApp, email | 6 | 5% |
| Admin panel and support tools | 10 | 8% |
| Reporting and dashboards | 6 | 5% |
| Testing, security review and tenant isolation tests | 12 | 10% |
| Deployment, monitoring, backups and launch | 6 | 5% |
| A month of fixes after launch | 8 | 7% |
| Total | 120 |
At a blended rate of 16,000 rupees per person-day, which is mid-band for an experienced Indian team, that is about 19 lakh. With three people on it, a designer front-loaded and two engineers through the middle, it takes 14 to 16 weeks. Both numbers land inside the second row of the table above.
Two things are worth noticing. The feature the founder pictured, scheduling, is 25 of the 120 days. Add its share of the design and it is about a third of the budget. The other two thirds is what turns a working demo into a product a stranger can buy, use with their team and get help with. And a quote that skipped accounts, billing, the admin panel and the month after launch would come in near 11 lakh for what looks like the same product on a slide. That is the five-times spread, explained.
The seven things that move a SaaS price
- The number of user types. Owner, admin, member, billing contact, read-only. Every screen and every API endpoint needs an answer for each role, and enterprise buyers eventually ask for roles of their own.
- The pricing model. A flat fee per company is the cheapest to build. Per-seat pricing adds seat management and proration. Usage-based pricing adds metering you can trust, usage dashboards and alerts before a bill surprises someone, which is a small product in itself. Tiered plans add feature flags and limits enforced in the API, not only hidden in the interface.
- Tenancy. How you keep one customer's data away from another's is the decision that prices everything after it, so it has its own section below.
- Integrations. Each outside system, accounting software, a payment gateway, WhatsApp, an ERP, adds between a week and a month of work that is invisible in the design and real in the build, plus approval timelines that run on other companies' clocks.
- Real-time behaviour. Live dashboards, collaborative editing and chat need WebSockets, state synchronisation and conflict handling, and cost meaningfully more than screens that load on demand.
- Compliance. The DPDP Act for Indian users, GDPR if you sell into Europe, SOC 2 once enterprise procurement asks. Each means audit logs, encryption, data export and deletion, and questionnaires that someone has to answer.
- Decisions not yet made. Changing the pricing model in week nine is the most expensive feature there is. A week of discovery is the cheapest insurance on this list, which is why we fix price only after it.
Multi-tenancy: the decision that prices everything after it
Multi-tenancy means one running system serves many customer companies, each seeing only its own data. Almost every business-to-business SaaS needs it. There are three ways to build it, and they cost very different amounts at very different times.
| Model | How it works | Build cost | Where it hurts |
|---|---|---|---|
| Shared database, tenant column | Every row carries the customer's id and the application and database enforce it | Lowest; adds little if designed in from day one | One missed filter is a data leak, so it needs tests and row-level security rather than discipline |
| Schema per tenant | One database, a separate schema for each customer | Moderate; every migration runs once per tenant | Hundreds of tenants make every deployment slow |
| Database per tenant | Each customer gets its own database | Highest; provisioning, backups and monitoring multiply | Only worth it for data residency or very large enterprise accounts |
Most Indian SaaS products should start with the first model, with row-level security in PostgreSQL doing the enforcing, and offer the third to the one enterprise customer who insists, at a price that reflects it. What you should not do is start with a single-company database "to move fast" and add tenancy later. Every query, every background job and every report has to be revisited, and the retrofit routinely costs more than doing it at the start would have. This is the mistake we see most often in platforms that come to us for rescue.
Billing in India is harder than the demo suggests
Subscriptions are where first-time SaaS builds most reliably underestimate the work, and India adds rules that the international tutorials do not cover.
- Recurring payments need mandates. Under the Reserve Bank's e-mandate framework, auto-debit on cards and UPI has to be registered by the customer with additional authentication, and debits above 15,000 rupees need authentication each time. The "save the card and charge it monthly" flow that works in the US does not translate. Many Indian B2B products end up on annual invoices paid by UPI or bank transfer, with card autopay only for the smaller plans.
- GST on your invoices. Every invoice needs the customer's GSTIN, the place of supply and the right tax treatment, and sales to foreign customers are zero-rated only with the paperwork in place. Your billing system either produces compliant invoices or your accountant redoes them by hand every month.
- Failed payments are a feature. Retries, grace periods, dunning emails, downgrade rules and the screen a customer sees when their card fails are all work. A product with no failed-payment path has a churn rate it cannot see.
- Proration and plan changes. Upgrading mid-cycle, downgrading at renewal, adding seats halfway through a month, refunds. Each is a small rule with a test behind it.
Razorpay Subscriptions or Stripe Billing handle the mechanics for a share of each transaction, around 2 percent domestic plus GST on the fee and more for international cards. What they do not handle is your rules, and the rules are the 15 person-days in the estimate above.
What a SaaS costs to run, month by month
Unlike a mobile app, a SaaS product has a monthly bill from day one, and the bill grows with customers. Budget for it before launch, not after the first invoice arrives.
| Cost | Early stage, under 500 users | Growth, 500 to 5,000 users | At scale |
|---|---|---|---|
| Hosting, database, storage | 3,000 to 10,000 a month | 10,000 to 40,000 a month | 40,000 to several lakh a month |
| Transactional email, SMS and WhatsApp | 1,000 to 5,000 | 5,000 to 25,000 | Metered with volume |
| Monitoring, error tracking, logs | Free tiers to 3,000 | 3,000 to 15,000 | 15,000 and up |
| Payment processing | About 2% of revenue plus GST on the fee | The same | Negotiable at volume |
| Authentication, billing and support tools bought as services | Free tiers | 5,000 to 30,000 | Per-user pricing bites here |
| AI features, if any | A few thousand, per request | Tens of thousands | The line that surprises people |
| Maintenance and small improvements | Commonly 15 to 25% of the build cost per year |
Two lines deserve a sentence. The services that were free at launch, authentication, billing, support desks, analytics, are mostly priced per monthly active user, which means they grow with exactly the number you are trying to grow. Check what each one costs at 10,000 users before you adopt it at 100. And AI features split into a build cost and a running cost; the full arithmetic for the second is in what an AI agent costs to run, and it is the line most 2026 budgets get wrong.
The costs that are not in the quote
| Cost | Typical size | When it surprises you |
|---|---|---|
| GST on the development invoice | 18% | On a 20 lakh build that is 3.6 lakh, claimable as input credit if you are registered, but the cash goes out first |
| Terms of service and privacy policy | 25,000 to 75,000 for lawyer-drafted documents | When the first enterprise customer's legal team reads the template you copied |
| DPDP Act compliance | 50,000 to 2 lakh of legal and technical work | Consent records, deletion requests, a breach process |
| SOC 2 readiness | 3 to 8 lakh | When enterprise procurement asks, and the deal waits until you have it |
| A companion mobile app | 3 to 8 lakh on top of the web product | In month two, when customers ask for it |
| Data migration | Days to weeks per customer type | When customers arrive with spreadsheets and a competitor's export |
Build, buy or assemble the boring half
In 2026 you do not have to build the account layer from scratch. Authentication can be bought from Clerk, Auth0 or Supabase. Billing mechanics come from Stripe Billing, Razorpay Subscriptions or Chargebee. Transactional email is Postmark or Amazon SES. An admin panel can be assembled in Retool or Forest Admin on top of your database.
Assembling on these services pulls the "first sellable version" row toward its lower end, and it is usually the right call for a first version. The trade-offs are real, though. Per-user pricing grows with you, your rules still have to be written and tested whichever service enforces them, and Indian billing rules and invoice formats need custom work on top of a global product. The pattern we recommend: buy authentication and email on day one, buy the billing mechanics but own the rules and the invoices, and build the admin panel for your own product, because it is where your support team will spend its life.
How agencies charge, and which model to pick
| Model | How it works | Best when |
|---|---|---|
| Fixed price after discovery | One week of discovery, then a fixed scope and a fixed price | The scope is definable, which covers most first versions |
| Time and materials | Hourly or monthly billing against a backlog that evolves | The scope is genuinely unknown, or you are rescuing a platform |
| Dedicated team | A named team on a monthly retainer, managed by you | You are building continuously for a year or more |
All three are legitimate. What is not legitimate is a fixed price quoted before anyone has asked you a hard question; it will be recovered later as change requests. We work on the first model, and when a client's roadmap is long enough that the third makes more sense, we say so; the trade-offs are on our dedicated teams page.
How to read a SaaS quote
Five checks separate a real quote from an optimistic one, and they take ten minutes.
- Find the account layer. Sign-up, organisations, roles, invitations and the admin panel should each be a line. If they are not, ask where they live.
- Ask for the billing edge-case list. Failed cards, proration, refunds, GST invoices, annual plans. A vendor who has built billing before has this list ready.
- Ask how tenant isolation is tested. The answer should involve automated tests and database-level enforcement, not "we are careful".
- Check for the month after launch. Monitoring, backups tested by restoring them, and a fixed period of fixes. A quote that ends on launch day is incomplete.
- Ask who owns the accounts. The cloud account, the domain, the payment gateway and the code should be in your company's name from day one. Agencies that keep them are building a switching cost, not a product.
How to spend less without a worse product
- Start with a flat fee per company. Add seats and usage pricing once you know what customers value; it is the cheapest model to build and often the right one to launch with.
- One workflow, finished, beats three half done. The sequencing logic is in how long an MVP takes.
- Buy the account layer, own the rules. See the section above; it is the single largest saving available on a first version.
- Web first, mobile later, unless the job is done in the field. Building both together is cheaper than a year apart, but building neither until the web version has paying customers is cheaper still.
- Validate before you build. A landing page with a payment link and a manual service behind it has proved demand for less than a lakh more than once; our MVP development page is honest about when that is the right answer.
- Start integration paperwork on day one. Payment gateway KYC, WhatsApp Business approval and bank sandboxes run on other companies' clocks, and delays are free when parallel and expensive when serial.
Questions people ask
How much does it cost to build a SaaS platform in India?
A first version with self-serve sign-up, subscriptions, one core workflow and an admin panel typically costs 12 to 35 lakh with an experienced Indian agency. A lean MVP without automated billing or multi-tenancy can be built for 4 to 10 lakh, and a multi-tenant platform with several user types and integrations runs 35 lakh to a crore. Where you land inside a band is decided by user types, pricing model, tenancy and integrations, not by the feature list.
How much does it cost to run a SaaS per month?
Under 500 users, budget 5,000 to 25,000 rupees a month for hosting, email, monitoring and tools, plus around 2 percent of revenue in payment fees. Between 500 and 5,000 users the bill rises to somewhere between 25,000 and a lakh a month, and the per-user services you adopted for free become the largest line. Maintenance on top is commonly 15 to 25 percent of the build cost per year.
Can a SaaS MVP be built for under 5 lakh?
Yes, if it is honestly an MVP: one company at a time, one workflow, sign-in, payments by link or invoice, and no self-serve subscriptions. That version is enough to find out whether anyone will pay. It is not enough to let a stranger sign up and buy without talking to you, which is what the 12 lakh and above versions are for.
What does a micro SaaS cost to build?
A micro SaaS, a small product solving one narrow problem for a niche, sits in the lean MVP row: 4 to 10 lakh with an agency, less if a technical founder builds it. The saving comes from having one user type, one plan and no integrations; the moment it needs teams and roles, it is priced like any other SaaS.
How long does it take to build a SaaS product?
Ten to twenty weeks for a first version real customers can pay for: a week of discovery, three weeks of design, eight to fourteen weeks of building, and a launch period. Cutting scope shortens it; cutting steps does not. The week-by-week version is in how long an MVP takes.
Can SaaS development costs be capitalised?
Often, partly. Indian accounting standards allow development-phase costs to be capitalised as an intangible asset once technical feasibility and the intention to complete are established, while research and early exploration are expensed. Many early-stage companies expense everything for simplicity. The treatment affects your reported profit and your tax, so decide it with your chartered accountant before the first invoice, not at year end.
Is it cheaper to build a SaaS with AI coding tools in 2026?
The build is faster, and good agencies pass that through; it is part of why these ranges have held steady while products have grown more capable. What AI tools do not remove is the expensive part: the pricing decisions, the integrations, the billing rules and the tests that prove one customer cannot see another's data. Our own three-day website rebuild is an honest case study in both halves of that sentence.
Getting a real number
Ranges end where your actual scope begins. We quote a fixed price after a one-week discovery, so the number you approve is the number you pay, and we design tenancy, billing and the admin panel into the first half of the build rather than the last week. What that looks like is on our SaaS and web development page.