SaaS development in Mumbai
Selling SaaS to Mumbai's banks, insurers and asset managers is its own discipline. The buyer's technology team wants to know where the data lives and who can reach it, expects single sign-on into its own directory, and sometimes wants a dedicated deployment in its own cloud account rather than a shared one. Many SaaS products win the demo and then stall, because the product cannot yet do what the bank's team asks.
We build SaaS that wins that conversation. Tenancy designed so a customer can be moved to a dedicated deployment without a fork of the codebase, SSO into the bank's directory, role models detailed enough for a large organisation, and activity logs that export cleanly. The same product still runs multi-tenant for smaller customers. The work happens in your codebase, in increments that ship, so the next enterprise conversation starts with the answers ready.
Mumbai is India's financial capital. Both major stock exchanges are here, and so are many of the country's banks, NBFCs, brokers, wealth managers, insurers and fintechs. For these companies software is judged first on whether the money is right. A loan ledger that drifts from the bank statement, a payout released twice because a partner timed out, a portfolio screen showing yesterday's price: each one lands on an operations desk the next morning. What they need built is rarely a new product from nothing. It is a lending or payments backend that reconciles, a platform where each role sees exactly what it should, and approvals that need two people before money moves. Engineers who have built those systems are in demand across the city, so the work often waits for a hire.
The city's second industry is attention. The Hindi film industry, most of the country's television networks and many of its large publishers are based here, and their software problems are specific: traffic that arrives all at once on a release or a match day, rights and metadata that decide what can be shown where, and archives that are valuable only if someone can search them. A slow page on a publisher's site is lost revenue, because the readers came from search and will go straight back to it.
The third is consumer business in every size. Mumbai has D2C brands selling beauty, fashion and food through their own stores and every marketplace at once, and it is home to large family-owned groups and conglomerates whose older divisions still run on spreadsheets and exports from their accounting software. In the bigger groups the buyer is usually a digital team with a mandate, a budget and a procurement process, and the work has to survive that process as well as production.
We are in Bengaluru and share your time zone, so the working day is the same on both sides and a question asked in the morning is answered the same morning. You talk directly to the engineer who writes the code. The work happens in your repository and a shared chat channel, where every decision is written down, and the runbooks and architecture notes are written as we go rather than at the end.
We are the right fit when a Mumbai team has a defined piece of work and wants a senior engineer on it within days: a ledger that has to reconcile, a migration with an end date, or extra capacity while you hire. Start with a fixed-price two-week piece, or bring us in white-label for your agency's clients under your name.
Four ways this arrives.
Then SCIM, then role mapping, then a security questionnaire. We add SAML and OIDC through a provider or your own identity stack, provision users from their directory, and keep the permission model working for the self-serve customers who never asked for any of it.
Shared tables with a tenant column and every query trusted to filter on it. We enforce isolation below the application, with Postgres row-level security or separate schemas, and write tests that try to read across tenants and must fail.
Moving from seats to usage, adding a free tier, or selling annual contracts beside monthly plans. We model plans and entitlements separately from the payment provider, meter usage into a ledger you can audit, and make proration and dunning tested code rather than a monthly surprise.
Every larger customer asks who changed what, who can reach production and how access ends when someone leaves. We build exportable audit logs, least-privilege access and change control through pull requests, so your answer is a screen, not a spreadsheet.
A multi-tenant platform scoped per organisation, with admin screens for users, access and login alerts, and a way for an administrator to view the app as any user.
Read the write-up →Asked by Mumbai teams.
How do you work with teams in Mumbai?+
We are in Bengaluru and share your time zone, so calls, reviews and releases fit inside your normal working day. We work in your tools, Slack, GitHub and Linear or whatever your team already uses, and every decision is written down in the repository or the channel. You talk directly to the engineer writing the code, from the first 30-minute call through to handover, with runbooks and architecture notes written as we go.
Do you build for Mumbai lenders, brokers and fintechs?+
Yes. We build the parts where the money has to be right: loan and payment ledgers that reconcile against the bank's records every day, retries that cannot turn a timeout into a double payout, maker-checker approvals where a second person signs off before money moves, and a full history of every change of state. We work inside the system you already run, in Node, Python and Next.js, and ship in increments.
How does your rate compare to hiring in Mumbai?+
PayScale puts a mid-career software engineer in Mumbai at about ₹15 lakh a year. Our published rate is $35 an hour, with a $5,000 minimum. That buys a senior engineer who writes the code, works in your Slack, GitHub and Linear, and starts within days, with no recruiting round, notice period or employment overhead. Start with a fixed-price two-week piece at $2,800 and judge us on the output before committing to more.
Can you work white-label for our Mumbai agency?+
Yes. Mumbai's digital and media agencies bring us in when a client needs a backend, a mobile app or a data pipeline alongside the design and campaign work. We work under your name, in your client's repositories and your channels, and sign an NDA before specifics. The code belongs to the client from the first commit. You keep the relationship, we write the code and the runbooks, and your team presents the work.
Shared database, separate schemas, or a database per tenant?+
Shared tables with row-level security for most products, because it is the cheapest to run and the simplest to migrate. Separate schemas or databases when a customer contractually needs isolation, data kept in a particular region, or its own backup schedule. We design so a large tenant can move to its own database later without rewriting the application, because that request usually arrives with the biggest contract.
When should we add SSO and SCIM?+
Before the deal that needs them, not in the first month. Design the user and organisation model so SSO slots in without a data migration, then switch it on when a paying customer asks. A provider such as WorkOS saves you building SAML and SCIM yourself, which rarely pays off until enterprise customers are a large share of your revenue.
Stripe, or a merchant of record like Paddle?+
Stripe gives you the most control over plans, invoices and the checkout. A merchant of record such as Paddle takes a larger fee and becomes the seller, handling tax wherever you sell. For a small team selling internationally from the start, the merchant of record is often the simpler path. We lay out both at your price point before you choose.
Can you make the product ready for enterprise buyers?+
Yes. Enterprise buyers ask for the same things every time: single sign-on, directory provisioning, roles they can define, an audit log they can export, and admin screens their IT team can use. We design those into the data model early, so saying yes to the next large customer is a configuration change rather than a quarter of rework.
What have you built that carries over to SaaS?+
Multi-tenancy, per-organisation access and admin tooling run through most of what we build. FM360 is a multi-tenant platform with all three: organisations, apps and access managed per customer, usage analytics and login alerts. Subscriptions and billing logic we build inside the product, tested like any other code rather than left to a dashboard.