Web platform development in Chennai
Chennai's hospitals see patients who travel from across India and from abroad, and much of their coordination still happens by email, phone and messaging apps. Referring doctors send reports as attachments, international patients' coordinators juggle travel dates and estimates in spreadsheets, and nobody can say, for a given patient, who has seen which record and why.
We build web platforms in Next.js for that coordination, with health data treated as the sensitive data it is. Patients, referring doctors, coordinators and clinicians each see only what their role requires, consent is recorded for each purpose, every access to a record is logged and reviewable, and documents are shared through expiring links rather than attachments. Where the hospital's own systems can exchange data, we integrate with them instead of creating another copy.
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.
We replace the role column with a permission model that can express teams, access to individual resources and roles the customer defines, add SAML or OIDC sign-in, and write the audit log their security questionnaire will ask about.
Or very nearly did. We find every query that can cross a tenant boundary, enforce the tenant in one layer rather than in every handler, and add tests that try to read across that boundary on purpose.
We build the admin side properly: search across organisations, an audited view-as-user mode, and screens for access and usage. Support stops asking an engineer to run a query against production every time a customer says something looks wrong.
An early Next.js app with auth stitched into middleware, a custom server, and a release process that lives in someone's head. We move it forward in small steps, with preview environments and a pipeline anyone on the team can ship from.
A Next.js platform scoped per organisation, where an administrator can view the app as any other user and each Tableau report opens only for people granted it.
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.
What is wrong with a role column?+
Nothing, until you have more than one kind of customer. A role says who a user is; most real questions are about what they can do to one specific thing, inside one specific organisation. Encoded as role checks, every new requirement becomes a code change in many places. We model permissions as data, check them in one place, and test them like any other logic.
Should we use an auth provider or build our own?+
Use a provider for identity: passwords, magic links, SSO and multi-factor. It is a solved problem and getting it wrong is expensive. Authorisation, meaning what a signed-in user may do, is specific to your product and usually belongs in your own code and database. We wire the first to the second and keep the line between them clear.
How do you handle multi-tenancy?+
Usually one database with a tenant ID on every row, enforced in one place: Postgres row-level security, or a data-access layer every query has to pass through, rather than each handler remembering. A separate database per tenant is sometimes right, for one very large customer or strict isolation, and we will say if that applies to you.
Where does it get hosted?+
Wherever suits your team. Vercel is the least effort for Next.js and fine for most platforms. If cost or long-running background work make that awkward, we run it in containers on Railway, AWS or your own Kubernetes. The repository, the cloud accounts and the bill are in your name either way.
What do enterprise customers ask for, and can you build it?+
Single sign-on through SAML or OIDC, audit logs, role management, session controls, encryption and data export. We build each of them into the platform and help you answer the technical questions on a customer's checklist accurately, so the security conversation speeds the deal up instead of stalling it.