Start with an audit

Let’s talk.

Tell us what you’re working on. A person from the team replies to every enquiry, with a time for a 30-minute call.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.
Cost guide · 9 min read

SaaS development cost: build, billing and running costs

By the Red Balloon team · Updated · Part of SaaS development

SaaS development cost has two halves that founders often price as one. The build cost follows the number of modules, the complexity of billing, the integrations customers expect and the security evidence enterprise buyers will ask for. The running cost follows tenant count, data volume and the third-party services each customer uses. A product can be cheap to build and expensive to run, or the other way round.

This guide breaks both halves into line items: tenancy design, subscriptions and invoicing, compliance work, infrastructure and the fees payment and billing providers charge. It is written for founders and product leaders in India and abroad who are budgeting a new SaaS product or turning an internal tool into one.

What drives SaaS development cost

A SaaS product is an application plus the machinery that lets many customers use it safely and pay for it automatically. That machinery is where first-time SaaS budgets go wrong. A team that has built a good single-company tool can underestimate tenant isolation, role management, billing edge cases and the admin console needed to support hundreds of accounts.

Cost driverWhat it involvesQuestions that set the effort
Core modulesThe workflows customers pay forHow many modules are needed before the first paying customer?
Multi-tenancyKeeping each customer's data and settings separateShared database, separate schemas or separate databases?
Authentication and rolesUsers, teams, permissions, SSO for larger buyersDo enterprise customers need SAML or Google Workspace sign-in?
Billing and invoicingPlans, trials, upgrades, usage metering, dunning, tax invoicesFlat plans, per-seat or usage-based pricing?
IntegrationsCRM, accounting, messaging, the customer's own systemsWhich integrations decide the sale, and which can wait?
Admin and support consoleTenant management, impersonation with audit, usage viewsHow many accounts will one support person handle?
Security and compliance evidenceAudit logs, access reviews, policies, penetration testsWill buyers send security questionnaires or ask for audits?

Our SaaS development discovery prices each of these drivers separately, so you can see which ones the first paying customer truly needs and which can follow once revenue arrives. For each driver you get the effort, the risk of deferring it and the signal that would bring it forward, such as a prospect who will only sign with SSO.

Tenancy model: the architecture choice that shapes cost for years

How you separate customers' data affects build cost, running cost and what enterprise buyers will accept. Most early-stage products start with a shared database and a tenant ID on every row, enforced in code and ideally by database row-level security. Separate schemas or databases per tenant give stronger isolation but multiply the work of migrations, backups and monitoring.

ModelCost to build and runBest for
Shared database, tenant ID on every rowLowest; one schema to migrate and monitorSelf-serve products with many small customers
Schema per tenantModerate; migrations must run across every schemaMid-market buyers who want stronger separation
Database per tenantHighest; per-tenant infrastructure and operationsEnterprise or regulated customers with strict isolation or data residency demands
HybridVaries; shared by default, dedicated for large accountsProducts selling to both small teams and enterprises

Billing, subscriptions and payment fees

Billing looks like a feature and behaves like a product. Plans, trials, upgrades mid-cycle, seat changes, usage metering, failed payments, refunds, credit notes and tax invoices each need logic and testing. Buying a billing platform reduces build effort but adds a percentage fee; building your own saves the fee but costs engineering time every time pricing changes.

As of November 2026, Stripe's billing pricing page lists pay-as-you-go Stripe Billing at 0.7% of billing volume, on top of payment processing. In India, Razorpay's pricing page lists a standard platform fee of 2% per successful domestic transaction and up to 3% for international cards, with 18% GST charged on the fee. Check current rate cards and negotiated pricing before you model margins, because these change.

  • Plan and price catalogue that marketing can change without a release.
  • Trials, upgrades, downgrades and proration rules.
  • Usage metering if you charge per seat, per transaction or per unit of data.
  • Dunning: retries, reminders and grace periods for expired cards and cancelled mandates.
  • GST-compliant invoices and credit notes for Indian customers.
  • Revenue reporting: monthly recurring revenue, churn and expansion.

Dunning deserves its own line in the budget. Expired cards and cancelled recurring mandates quietly erode revenue in every subscription business, and the cost of building retries and reminders is small next to the revenue they recover. Test the unhappy paths as carefully as the happy ones: a card declined on renewal, a mandate cancelled by the customer's bank, and an upgrade that fails halfway through payment.

Security and compliance work buyers will ask for

Selling to larger companies brings security questionnaires, and sooner or later a request for an independent report. SOC 2 is the AICPA's assurance framework for service organisations, built around criteria for security, availability, processing integrity, confidentiality and privacy. ISO/IEC 27001 is the international standard for an information security management system. Both cost money in audit fees, tooling and staff time, so decide early whether your market will demand one.

For products handling personal data of people in India, the Digital Personal Data Protection Rules were notified in November 2025, with most obligations phasing in over 18 months. Consent records, purpose limits, security safeguards, breach response and deletion requests are far cheaper to design in than to retrofit across every module later.

  • Audit logs for sign-ins, permission changes and data exports.
  • Role-based access and regular access reviews for your own staff.
  • Encryption in transit and at rest, with managed secrets.
  • Backups that are actually restored in tests.
  • Written security policies ready for buyer questionnaires.
  • Periodic penetration tests by an independent party.

Running costs: what a tenant costs you each month

An illustrative example makes the point. A Gurugram team selling scheduling software to clinics adds WhatsApp reminders to every plan. Hosting barely changes as clinics join, but the messaging bill grows with every appointment booked. Unless reminders are capped, metered or priced into higher plans, the busiest customers, the ones the team is proudest of, quietly become the least profitable.

Running cost is where SaaS unit economics are won or lost. Track the monthly cost to serve each tenant from the start, because pricing decisions depend on it. Infrastructure is often not the largest item; per-tenant third-party services, such as messaging, email, AI model calls or data enrichment, can grow faster than hosting.

Running costWhat makes it growHow to control it
Cloud compute and databaseActive users, heavy reports, background jobsRight-size instances, cache reports, schedule heavy jobs
Storage and backupsFiles, logs and data retentionRetention policies and tiered storage
Third-party APIs (messaging, email, AI, maps)Usage per tenantPass usage-heavy features into higher plans or metered pricing
Monitoring and logging toolsLog volume and retentionSample logs and set retention by environment
Support and successOnboarding effort and tickets per tenantSelf-serve onboarding, in-app help, usage alerts
Maintenance and security updatesDependencies, OS and framework releasesAutomated dependency updates checked by CI

Infrastructure as code, automated deployments and good observability keep running costs predictable as you grow. Our DevOps and cloud team sets these up so that adding a tenant does not mean adding manual work. Tenant provisioning, environment set-up, alerts and cost reports run automatically, and a tenant ID on every log line lets you trace one customer's problem without searching through everyone else's data.

How the budget splits across phases

SaaS products are best funded in phases, each ending with something you can sell or learn from. The first target is a paying design-partner customer, not a full product. The second is self-serve onboarding. Spreading the budget this way keeps you from funding modules nobody has asked for.

PhaseGoal
Discovery and pricingWorkflows, pricing tiers, tenant model, compliance map
Platform foundationAuth, roles, tenancy, billing hooks, CI/CD, monitoring
Core productModules the first paying customers need
Launch readinessSelf-serve onboarding, load tests, status page, policies
Scale and operateFeature sprints, cost and performance tuning

If you already have a working product sold as separate installations, the foundation phase looks different: the work is consolidating code and data into one multi-tenant platform. Our legacy-to-SaaS modernisation service covers that path, including migrating existing customers without downtime.

Ways to keep SaaS development cost under control

  1. Sell to a few design-partner customers before building beyond the core module.
  2. Use a shared-database tenancy model unless buyers demand stronger isolation.
  3. Buy billing, authentication and email services rather than building them first.
  4. Add SSO, audit exports and advanced roles when a deal requires them, and price them into higher plans.
  5. Track cost to serve per tenant from the first month.
  6. Keep integrations to the ones that decide the sale; use connectors for the rest.

Cost control on the build side only pays off if the product finds customers. Our guide to SaaS marketing strategy for Indian startups covers the go-to-market work that should run alongside development, so the first paying tenants arrive as the platform becomes ready for them.

Getting a SaaS estimate you can plan around

A useful estimate separates build cost from running cost, names the tenancy and billing assumptions, and shows which modules are needed for the first paying customer. Ask every vendor for it in that shape. If they cannot explain how cost to serve changes at ten, a hundred and a thousand tenants, they have not thought about your margins.

We run a scoping workshop as part of the Growth Audit on how we work, a two-week paid diagnostic whose fee is credited to the next engagement. Together we map modules, tenancy, billing and compliance, and leave you with a phased estimate for both build and running costs.

To see how we build and operate SaaS platforms after that, visit our SaaS development company page. It covers multi-tenant architecture, subscription billing with GST invoicing, and the security evidence enterprise buyers ask for, with the code and cloud accounts in your name.

FAQ

Questions people also ask

Straight answers from the practice lead. Highlighted text marks Red Balloon figures we confirm before publishing.

How much does it cost to build a SaaS product?

It depends on the number of modules, the tenancy model, billing complexity, integrations and the security evidence your buyers need. A single-module product for small teams and an enterprise platform with SSO and audits are very different budgets. Red Balloon sets its estimate after a scoping workshop that also estimates running costs.

    What are the ongoing costs of running a SaaS application?

    Cloud hosting and databases, storage and backups, third-party services such as email, messaging and AI calls, monitoring tools, billing and payment fees, support staff, and maintenance for security and framework updates. Track cost to serve per tenant monthly; it tells you whether your pricing leaves a healthy margin as you grow.

      Should we build our own billing system or use Stripe or Razorpay?

      Most early SaaS products should use a billing provider. Building plans, proration, dunning and invoicing yourself costs engineering time every time pricing changes. Stripe lists Stripe Billing at 0.7% of billing volume on its pricing page, and Razorpay offers subscriptions in India. Build your own only when fees at scale clearly exceed the engineering cost.

        Do we need SOC 2 or ISO 27001 before launching?

        Not usually before launch, but you should build the controls those frameworks check for from the start: access control, audit logs, encryption, backups and written policies. Pursue a formal report when target customers require one. Building the controls early makes the eventual audit far cheaper and faster.

          Is multi-tenant SaaS cheaper than single-tenant?

          Usually, yes. A shared, multi-tenant platform has one codebase and one set of infrastructure to update, monitor and back up, so each new customer costs little to add. Single-tenant deployments give stronger isolation but multiply operations work. Many products start multi-tenant and offer dedicated environments only to large customers, at a higher price.

            Sources checked for this guide (4)
            1. Stripe: Billing pricing
            2. Razorpay: Pricing
            3. AICPA and CIMA: SOC 2 (System and Organization Controls)
            4. Press Information Bureau: Digital Personal Data Protection Rules, 2025

            Platform prices and rules change. We recheck these sources when we update the guide; confirm anything critical with the source before you act on it.

            Start with an audit

            Ready for
            lift?

            A paid two-week Growth Audit covers your funnel, ads, site, tracking and automation gaps, and ends with a 90-day plan you can run with or without us. The fee is credited against your next engagement.

            Prefer to talk? Call +91 97114 48083, or email info@redballoon.in.

            A person from the team replies to every enquiry.

            What do you need?
            Your details are sent over a secure, encrypted connection and only used to reply to you.