Service · SaaS development company

SaaS development

Build cost follows modules, billing complexity and integrations; running cost follows tenant count, data volume and third-party services. Both are estimated before you commit.

Product Engineering practice: abstract red and ink artwork from the Red Balloon reel

Turning an internal tool or a desktop product into a subscription business takes more than moving it to the cloud, and a SaaS development company should know the parts founders tend to discover late. Red Balloon helps founders and established firms build a SaaS platform with multi-tenancy, subscriptions, GST invoicing, role-based access and the security evidence enterprise buyers ask for. SaaS product development runs in short cycles towards a first paying customer, then towards self-serve onboarding and scale. We set up tenant provisioning, billing, dunning and infrastructure as code so growth does not mean more manual work. Architecture choices are made with your unit economics in view, and the code and cloud accounts belong to you.

Specialist services

Go deeper

Also covered on this page

Multi-tenant architectureBilling & subscriptions
Where this works

Real-world situations we're built for

Illustrative · not a client
Restaurants / hospitality

Gurugram team built an inventory tool for its own outlets and wants to sell it to other chains

What we'd do
Multi-tenant rebuild with tenant isolation, Razorpay subscription billing, GST invoices and self-serve onboarding
What moves
Paying tenants up, onboarding time per tenant down; tracked as onboarding time per tenant before and after, over a fixed period
Coaching institutes

Delhi founder sells batch-management software installed separately for each coaching centre

What we'd do
One SaaS codebase with tenant settings and usage-based plans
What moves
Net revenue retention up, support tickets per tenant down
Industrial equipment

Ludhiana machine-tool maker wants a paid machine-monitoring service for its customers

What we'd do
IoT data ingestion, per-customer dashboards, alerts and annual subscription billing
What moves
Subscription revenue up, customer machine downtime down
How a project runs

5 phases, each with a deliverable

What happens, how long it takes, what you get and what we need from you.

Discovery

2–3 weeks

Customer workflows, pricing, tenant model, compliance needs

You get: Scope, architecture and pricing plan

We need: Founders and design-partner customers

Platform foundation

3–5 weeks

Auth, roles, tenancy, billing hooks, CI/CD, observability with the tenant ID on every log line and trace

You get: Tenant-ready skeleton

We need: Cloud account and domain in your name

Product build

8–16 weeks

Core modules, admin console, integrations, automated tests

You get: Beta product

We need: Sprint reviews and beta customers

Launch readiness

2–4 weeks

Billing, onboarding, security policies, load tests, status page

You get: Paid plans live

We need: Legal terms and pricing approval

Scale and operate

Ongoing

Feature sprints, cost and performance tuning, compliance work

You get: Monthly roadmap and metrics review

We need: Product priorities

A typical engagement

From first call to result

Illustrative · not a client

Gurugram founding team of 3 with clinic-management expertise, ₹1.5 crore seed, targeting 500 clinics in two years

Weeks 1–3Discovery and pricingClinic workflows, pricing tiers, tenant model, compliance map for health data under DPDPScope, pricing plan, shared-database design with tenant IDs
Weeks 3–7FoundationRole-based auth, row-level tenant isolation tested by requesting another tenant's IDs, audit log, CI/CD, AWS Mumbai region setupTenant-aware platform skeleton
Weeks 6–14Core productAppointments, patient records, billing, WhatsApp reminders via a BSPBeta-ready product
Weeks 12–16Billing and onboardingRazorpay Subscriptions, GST invoices, free trial, onboarding checklist; most common billing failure: expired cards and cancelled UPI mandates, so dunning ships with billingPaid plans live
Weeks 16–20Beta10 clinics onboarded, usage tracked, support set up in FreshdeskFix list and validated pricing
Weeks 20–24Launch readinessLoad tests, backup restores, status page, security policies for buyer questionnairesGeneral availability
Where it starts20 clinics on a waitlist, spreadsheet-based pilot, no product, planned price ₹2,500 per clinic per month
Where it endsA multi-tenant SaaS with paid plans and self-serve onboarding. Weekly watch: MRR, trial-to-paid conversion, logo churn.
What we measure

The numbers we report on

Every metric has a formula, a target, a source and a reporting rhythm.

MetricHow it's calculatedTargetSourceCadence
Monthly recurring revenue (MRR)Sum of active subscriptions normalised to a month; split into new, expansion and churnedSet growth targets from your business planChartMogul, Baremetrics or billing exportsWeekly
Logo churnCustomers cancelled in the month ÷ customers at start of monthRule of thumb for SMB SaaS: under 3% a month; record a cancellation reason for every churned accountBilling systemMonthly
Net revenue retention(Starting MRR + expansion − contraction − churn) ÷ starting MRR, per cohortAbove 100% means existing customers grow revenue on their ownChartMogul or a spreadsheet modelMonthly
CAC paybackCAC ÷ (monthly revenue per account × gross margin %), in monthsSet a target from your runway; shorter is betterCRM plus billing dataMonthly
Trial-to-paid conversionTrials converting to paid ÷ trials startedSet from first cohorts, then aim upwardBilling plus product analyticsWeekly
Uptime against SLAAvailable minutes ÷ total minutesKeep an internal SLO above the SLA you sell, e.g. 99.9%Better Stack or a public status pageWeekly
Infrastructure cost per tenantMonthly cloud cost ÷ active tenantsRule of thumb: under 10% of that tenant's subscription revenue; flag any tenant whose cost grows faster than its usageAWS Cost Explorer with tenant tagsMonthly
Automated by default

What runs itself after launch

The manual work we take out of this service, and the tools we use.

When: New sign-up or deal marked wonTenant provisioningSign-up or closed deal triggers workspace creation, default data and welcome emails via app jobsRemoves: Manual setup delays and inconsistent configurations
When: Renewal date or failed paymentSubscription billing and dunningRazorpay Subscriptions or Chargebee with payment retries and reminder emailsRemoves: Revenue lost to failed mandates and manual chasing
When: Payment capturedGST invoicingBilling system generating GST invoices, with IRN from the e-invoice portal where applicableRemoves: Invoice errors and compliance gaps
When: Merge to mainInfrastructure as codeTerraform plus GitHub Actions with staged rolloutsRemoves: Configuration drift between environments
When: ContinuousSecurity evidence collectionVanta, Drata or Sprinto pulling evidence from cloud, code and HR toolsRemoves: Weeks of manual preparation before SOC 2 or ISO 27001 audits
Rules we work to

Standards and regulations

ISO and IECISO/IEC 27001:2022

Certifiable information security management system, often requested by Indian enterprises and global buyers

AICPASOC 2 (Trust Services Criteria)

Attestation report on security controls, common in US enterprise procurement

MeitYDPDP Act 2023 and DPDP Rules 2025

As a data processor for customers, you need contracts, security safeguards and breach support; main duties apply from 13 May 2027

PCI Security Standards CouncilPCI DSS v4.0.1

Applies if you touch card data; hosted payment pages keep most of the scope with the gateway

What's changing

Platform and policy updates that affect this work

We track: MeitY notifications, GSTN news and advisories, AWS What's New, PCI SSC blog.

PCI Security Standards CouncilFuture-dated PCI DSS v4.0 requirements became mandatory

Payment-page script controls and stronger authentication now apply to card-handling SaaS

GSTNBusinesses with aggregate turnover of ₹10 crore or more must report e-invoices to the IRP within 30 days

SaaS billing must submit invoices to the IRP promptly

ISO certification bodiesTransition period from ISO/IEC 27001:2013 to the 2022 version ended

Certify on the 2022 version and ask vendors for 2022 certificates

MeitYDPDP Rules 2025 notified; main duties apply from 13 May 2027

Enterprise buyers will ask how your SaaS supports their DPDP duties

Before you hire anyone

Questions to ask any agency, including us

How will you test that tenants can never see each other's data?

Why ask

One leak can end enterprise deals

A good answer

Automated isolation tests every release, row-level security and pen-test scope covering it

What will our cloud bill look like at 10, 100 and 1,000 tenants?

Why ask

Margins depend on cost per tenant

A good answer

A cost model by tier with assumptions you can update

How do you change the database schema for all tenants without downtime?

Why ask

Migrations are a common cause of live SaaS outages

A good answer

Backward-compatible migrations, feature flags and staged rollouts

Can you help us answer enterprise security questionnaires?

Why ask

Deals stall on security reviews

A good answer

Prepared policies, architecture diagrams and experience with SIG or CAIQ questionnaires

How will we release features to some tenants first?

Why ask

Big-bang releases put every customer at risk at once

A good answer

Per-tenant feature flags with tools like LaunchDarkly, Unleash or Flagsmith

FAQ

Questions buyers ask us

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

How long until a SaaS product can take paying customers?

A first sellable version with onboarding, the core workflow, billing and an admin console typically takes 4–6 months; a design-partner beta can start earlier, around month two or three.

  • Billing, invoices and plan limits take longer than founders expect, so we schedule them in early sprints.
  • Enterprise buyers may need SSO and audit logs before signing, which adds a few weeks.
How do you architect a multi-tenant SaaS platform?

Our default is one shared PostgreSQL database with a tenant ID on every row, enforced by row-level security, moving large or regulated customers to their own schema or database when contracts require isolation.

  • Tenant context is set per request in middleware, so one missing filter can't leak another customer's data.
  • Feature flags and plan entitlements live in configuration, not in code branches per customer.
  • Per-tenant usage metering feeds both billing and cost monitoring.
Which security certifications will enterprise buyers ask our SaaS for?

Indian enterprises and overseas buyers commonly ask for ISO/IEC 27001:2022 certification or a SOC 2 Type II report, plus a security questionnaire, a recent VAPT report and DPDP data processing terms.

  • A SOC 2 Type II report covers an observation period, usually 3–12 months, so start collecting evidence soon after launch.
  • Vanta or Drata automate evidence, but the architecture must already log access and changes.
  • BFSI clients may also assess you against RBI or SEBI outsourcing and cybersecurity expectations.
  • Keep your first completed security questionnaire as a living document; the same questions return with every enterprise deal.
Which SaaS metrics should we track from day one?

Start with MRR and net revenue retention, then activation rate, trial-to-paid conversion, churn and CAC payback, all computed from billing and product events rather than spreadsheets.

  • Billing data from Razorpay, Stripe or Chargebee feeds MRR and churn; product events feed activation.
  • Define activation as one measurable action, such as the first invoice sent, not just a login.
  • Push account usage into the CRM so sales sees expansion and churn risk.
Who owns the SaaS platform, tenant data and cloud accounts?

Your company owns the codebase, cloud accounts, domains, billing accounts and all tenant data; we work inside them with access you can revoke at any time.

  • Payment gateway, app store and email-sending accounts are registered to your entity, since they carry your KYC.
  • Your customer contracts name your company as data fiduciary; we act only as your processor.
  • Infrastructure-as-code and runbooks mean another team can operate the platform.
  • Keep the AWS root and billing-owner logins with two of your own staff; a single founder's email as root is a recurring due-diligence finding.
Back to the practice

Product Engineering →

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.