SaaS development in Chennai
Chennai's SaaS tradition is self-serve: a small business anywhere in the world finds the product, signs up, and pays by card without ever speaking to sales. That model depends on engineering most people never see. Sign-up has to be quick and resistant to abuse, pricing has to change without a billing migration, usage-based plans need accurate metering, and invoices have to be right in every currency a customer pays in.
We build and extend that machinery. Plans, trials, upgrades and downgrades handled by billing through Stripe or a merchant of record, with the trade-offs explained before you choose. Usage metering that customers can check against their invoice. Tenancy that holds as accounts grow from one user to hundreds, and the SSO and activity logs larger accounts eventually ask for. We work inside your product and your release process.
Chennai is where Indian SaaS learned to sell to the world. Zoho is headquartered here and has grown without venture capital. Freshworks was founded here in 2010 by two former Zoho employees, and Chargebee was started in a Chennai apartment a year later by a team with Zoho roots, with Freshworks as an early customer. That lineage produced a distinctive kind of company: product-led, careful with money, selling to small and mid-sized businesses on several continents from offices in Chennai. Chennai's SaaS teams tend to be strong on product and short on specific capacity, not on talent in general.
The city's second identity is industrial. Chennai is often called the Detroit of Asia, with vehicle plants including Hyundai's and BMW's on its outskirts, a large base of component and electronics manufacturers, and a major port. Those firms have the same problem as manufacturers everywhere in India: their operations have outgrown the spreadsheets and older systems that run them, and their information arrives late and in the wrong format. Around the port, freight forwarders, customs brokers and warehouse operators face the same problem with paperwork instead of parts, and the cost of a lost document is a container that sits on the quay.
Its third is healthcare. Chennai is often called the health capital of India, and hospital groups such as Apollo Hospitals and specialist centres such as Sankara Nethralaya draw patients from across the country and abroad. Healthcare software here has to earn trust. Health records are among the most sensitive data there is, and hospital systems increasingly need to exchange data with each other and with the national digital health stack rather than sit in isolation. Referrals, international patient coordination, patient apps and group-wide reporting all need building. Getting consent, access logging and integration right matters more than the interface.
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 that morning. You talk directly to the engineer who writes the code. Most of the work happens in your repository, your issue tracker and a shared chat channel, which suits teams used to working in writing, and the runbooks and architecture notes are written as we go.
We are the right fit for a defined piece outside your team's usual specialism, a migration with an end date, or the gap while your next hire serves their notice. Start with a fixed-price two-week piece and judge us on what ships. Chennai agencies and product studios can also bring us in white-label, under their own 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 Chennai teams.
How do you work with teams in Chennai?+
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 most of the conversation happens in writing, where it lasts. You talk directly to the engineer writing the code, from the first 30-minute call onwards, and runbooks and architecture notes are written into your repository as we go.
Can you work inside a mature SaaS product without slowing our team down?+
Yes. We read your code and conventions before changing anything, follow your review and release process, and take a defined piece of work, such as a billing migration, a new integration, a performance problem or an infrastructure move, so the changes stay in one place rather than spreading across the product. We work in Node, Python and TypeScript, inside your repository, and leave runbooks and architecture notes for your team.
How does your rate compare to hiring in Chennai?+
PayScale puts a mid-career software engineer in Chennai at about ₹12 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. Begin with a fixed-price two-week piece at $2,800 and judge us on what ships.
Can you build software for Chennai's hospitals?+
Yes. FM360, the platform we built for a healthcare estate, runs its facilities and maintenance in production. For hospitals and diagnostic chains we build referral and patient-coordination platforms, patient apps in Tamil and English, and warehouses that join every branch's systems into one set of numbers. Consent is recorded per purpose, every access to a record is logged, and integrations use standards such as FHIR where the other side supports them.
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.