All work
Multi-tenant SaaS · Elder care~3–4 months
Multi-tenant elder-care SaaS
A care ecosystem: patient app, caregiver app, tenant and super-admin consoles, and the API — multi-tenant RBAC, a booking-to-medication loop, geo-validated service areas, and GST-aware invoicing.
I built the patient app, caregiver app, and tenant/super-admin console end-to-end. I owned the NestJS API with other engineers on the backend.
Stack
FlutterNext.jsNestJSMySQLBullMQAzure
Surfaces I owned
- Patient app
- Caregiver app
- Tenant + super-admin
- API
Decisions
- One patient codebase with per-tenant flavors instead of a fork per organization.
- The care loop is one product across patient app, caregiver app, and console — not a patch on a single surface.
- Billing is gated: no payment recorded until an invoice exists, with GST split correctly for Indian orgs.
What I built
- White-label patient Flutter app (flavors, themes, assets) covering onboarding, bookings, schedule, medications, vitals, SOS, family, and tickets.
- Caregiver app: shift OTP clock-in/out, tasks, medication schedule/history, special needs, tickets, earnings.
- Next.js tenant and super-admin console: CASL abilities, org/center onboarding, role-scoped nav, roster, attendance export, billing.
- Multi-tenant RBAC: orgs, centers, staff, scoped data — the wrong role never sees the wrong patient.
- Care loop aligned across all three clients: booking → package/shifts → tasks, meds, handoffs, vitals, SOS.
- GST invoicing (CGST/SGST/IGST), multi-payment receipts, branded PDFs. Geo: map picker and service radius enforced on booking assessment.
- Docker, Azure Blob with org-scoped paths, BullMQ notifications.
Outcome
Live across tenant organizations. Private walkthrough on request.