Skip to content
codebrix

SaaS development

SaaS development with multi-tenancy, billing and admin built in from the start

As a SaaS development company, we build the parts every subscription product needs beyond its core feature: tenant isolation, sign-up and onboarding, billing through Stripe or Razorpay, an internal admin, product analytics and sensible security. We work from Noida with founders in India and abroad, in fixed-price milestones, with the code and every account in your name.

First version
6–16 weeks
Billing
Stripe, Razorpay or both
Default tenancy
Shared Postgres + row-level security
Pricing
Fixed quote per milestone

Updated · By the Codebrix team

The SaaS layer most first builds underestimate

Founders usually scope the feature customers pay for. The surrounding plumbing often takes as long again, and skipping it shows up later as support tickets and lost revenue. This is what we plan for in a first release:

  • Workspaces or organisations, with invitations, roles and transfer of ownership.
  • Plans, trials, upgrades, downgrades and what happens when a card fails.
  • Limits per plan (seats, projects, records, API calls) enforced on the server.
  • Transactional emails: welcome, invite, receipt, payment failed, trial ending.
  • An internal admin for your team to find a customer and fix their account.
  • Data export and account deletion, which customers and privacy laws will ask for.
  • Product events so you can see who activates, who upgrades and who leaves.

Multi-tenancy: choosing how customers are kept apart

Every SaaS product stores many customers' data. How you separate them is hard to change later, so we decide it in week one.

Three ways to isolate tenants
ModelHow it worksSuits
Shared database, tenant columnEvery row carries a tenant ID; PostgreSQL row-level security blocks cross-tenant readsMost B2B SaaS at launch; cheapest to run and simplest to report on
Schema per tenantOne database, a separate set of tables per customerProducts with heavy per-customer customisation
Database per tenantEach customer gets their own databaseEnterprise buyers who contractually require physical separation or a specific region

Our default is the first model. The tenant check lives in the database as well as the application code, so a single forgotten filter in a query cannot leak one customer's data to another. We can move a large customer to a dedicated database later if a contract demands it.

Billing with Stripe or Razorpay

Which provider

If most customers pay with international cards, Stripe is the usual choice. If most are Indian businesses, Razorpay Subscriptions supports recurring payments by card, UPI AutoPay and eMandate, which matters because many Indian buyers prefer UPI. Some products run both and route by country. We do not quote provider fees; check each provider's pricing page for your business type.

How we wire it

  1. Plans and prices live in the payment provider; your database keeps a copy of each customer's current plan and status.
  2. Access is granted from your own database, updated by verified webhooks, not by calling the provider on every request.
  3. With Stripe we follow the subscription status (trialing, active, past_due, unpaid, canceled) and react to events such as invoice.paid and invoice.payment_failed.
  4. Failed payments trigger an email and an in-app banner, with a grace period you choose before features are restricted.
  5. Upgrades, downgrades and cancellations are tested end to end in the provider's test mode before launch.

Onboarding that gets users to the first useful moment

A trial user decides quickly whether your product is worth learning. We design onboarding around one activation event, the action that predicts a user will stay, and remove steps that do not lead to it:

  • Sign-up that asks only for what the first session needs.
  • Sample data or a template so the product is not empty on first load.
  • A short checklist that tracks progress toward the activation event.
  • A prompt to invite a colleague at the moment it becomes useful, not on screen one.
  • Emails triggered by what the user did or did not do, not a fixed drip.

Design for these flows is done in Figma with a clickable prototype first; our UI/UX design team runs that stage.

Admin panel, analytics and security basics

Admin for your team

Search any customer, see their plan, usage and payment history, extend a trial, apply a credit, switch a feature on for one account, and read an audit trail of every change your staff made. Support staff get a narrower role than founders.

Analytics

Server-side events for sign-up, activation, upgrade and cancellation, plus revenue figures read from billing data, give you monthly recurring revenue and churn without exporting spreadsheets.

Security we ship by default

  • Hashed passwords, optional two-factor sign-in, and enforced two-factor for admins.
  • Secrets in environment configuration, never in the repository.
  • Rate limits on sign-in and public endpoints.
  • Daily database backups with a tested restore.
  • Logs that record what happened without storing customer personal data.
  • Built with India's Digital Personal Data Protection Act, 2023 and the privacy laws of your target markets in mind; your legal adviser signs off.

Timeline and cost

A first sellable SaaS version usually takes 6–16 weeks. Our indicative range for a web application is ₹1,50,000–6,00,000 ($5,500–22,000); multi-tenancy, billing and admin push a SaaS build toward the upper part of that range, and complex products can go beyond it. You get a fixed quote after discovery and pay per milestone.

Not sure the market wants it yet? Start with MVP development and a tighter scope, then add the SaaS layer once people pay. If you are adding AI features to the product, see AI integration. We also cover the wider B2B and SaaS industry page with sales-site and portal work.

Frequently asked questions

Does our first version need to be multi-tenant?

If more than one customer company will use it, yes. Adding tenant separation after launch means touching every query and migrating live data, which is slow and risky. Building it in from week one adds little, especially with a shared database and row-level security. A single-customer pilot is the only case where we would skip it.

Should we use Stripe or Razorpay for subscriptions?

Look at where your paying customers are. Razorpay Subscriptions supports UPI AutoPay and eMandate alongside cards, which suits Indian buyers. Stripe is the common choice for international card payments. Products selling in both markets often run both. We set up whichever you choose in your own account and keep plan status in your database.

Can you build usage-based or seat-based pricing?

Yes. Seat-based pricing counts members per workspace and updates the subscription when people are added. Usage-based pricing records usage in your database and reports it to the billing provider each period; Razorpay's subscription docs list usage-based billing among its supported models. We model the pricing with you before building, because pricing changes are costly once customers are on it.

Can you take over a SaaS product someone else built?

Usually. We begin with a paid audit of the codebase, tenant isolation, billing integration and infrastructure, and report what is sound, what is risky and what it costs to fix. Tenant data leaks and webhook handling are the first things we check, because those are the costliest to get wrong.

Who owns the product we build together?

You do. Repositories, cloud accounts, the database, the Stripe or Razorpay account and the domain are all created in your name from the first day. We work with access you grant. Design files are yours too. You can bring in your own developers at any point and they inherit everything.

Do you also build the marketing site and a mobile app?

Yes. A Next.js marketing site with pricing, sign-up and documentation pages is often a separate small milestone. A companion mobile app in React Native or Flutter can share the same backend and auth. We usually advise launching the web product first and adding mobile once you know which features people use daily.

Sources

  • Web applications

    Custom web application development for portals, dashboards and internal tools

    Custom web application development for portals, dashboards and internal tools: roles, Postgres, integrations and tests. Fixed price, code in your name.

    Read more
  • B2B & SaaS

    A B2B software development company for portals, dashboards and integrations

    B2B software development company for customer portals, dashboards, integrations, SSO and audit logs, built so your SOC 2 preparation has evidence to use.

    Read more
  • MVP development

    MVP development: a narrow first product, shipped in 6 to 12 weeks

    MVP development company that cuts scope first, then ships a web or mobile MVP in 6–12 weeks with analytics in place. Fixed-price milestones, your code.

    Read more
  • Product guide

    How to scope an MVP you can build in about eight weeks

    How to scope an MVP: pick the one assumption to test, prioritise with MoSCoW, cut the rest, follow a sample 8-week plan and track the right metrics.

    Read more
  • AI integration

    AI integration services for the software you already run

    AI integration services that add LLM assistants, document search, summaries and classification to your product, tested on your data with cost limits set.

    Read more
  • UI/UX design

    A UI/UX design agency in India that designs what will be built

    UI UX design agency in India: user research, wireframes, Figma screens, a design system and a clickable prototype, designed by the team that builds it.

    Read more
Estimate Call WhatsApp