Nine departments and eight staff roles moved off Excel and WhatsApp forwards onto one system. The front desk logs into it every morning.
Why does a clinic need an operating system?
A clinic is nine businesses in a trench coat. Front desk, doctors, pharmacy, diagnostics, billing, staffing, memberships, care programs, admin — each one usually gets its own software, its own login, and its own Excel sheet nobody updates.
At Solace Life Clinic that meant a receptionist juggling a booking app, a billing tool, a WhatsApp group for the doctor and a notebook for the pharmacy. Nothing talked to anything. The doctor walked into every consultation without the patient's last visit in front of them.
ELTH puts the whole clinic on one screen, with eight staff roles that each see exactly what their job needs and nothing else.
How I built it
Two of us, no spec, one clinic willing to be the guinea pig. Ganesh stood up the initial frontend; I took it from there. The process had to be cheap, fast and honest.
Step 1 — Map the clinic's actual day
Before writing anything I sat with the front desk and traced a patient from the phone call to the pharmacy counter. Every handoff that needed a screenshot or a shout across the room became a feature on the list. That list became the department map — the eight portals below.
Step 2 — Ship feature by feature, while they used it
I shipped it the uncomfortable way: live, in weekly increments, while the clinic was running on it. Real receptionists filing real complaints beats any user research I could have bought. Sixty-plus features later, nobody has opened the old Excel sheet.
Step 3 — Hunt the infra bill
At one point the system was burning ~1.9 million Firestore reads a day — invisible to users, brutal on the bill. I profiled every screen, restructured queries and caching, and killed the waste. Nobody claps for this work. It's also the difference between a SaaS that survives and one that quietly bankrupts you — a lesson I'd already paid for once, in the obituary.
the flex isn't the feature count — it's that nobody went back to Excel.
What shipped
Four surfaces, one database. Here's what each of them does and why it matters to the clinic.
Eight doors, one building
Every role gets its own portal — reception can't see accounts, pharma can't see consultations. Permission-scoped by design, not by policy document. Multi-clinic tenancy is built in, so a second location is a config change, not a rewrite.
8 roles, 9 departments
Each portal shows a role only its own job — less training, fewer mistakes.
Audit log on everything
Every action is attributable. When money or medicine moves, there's a name on it.
The Elth Card: the whole patient on one screen
Trends since the last visit, diagnoses, current medications and a one-tap "Write Prescription" — the doctor sees it before the patient sits down. Vitals are charted against the last six readings, with deltas, not just today's numbers.
app.elthclinic.com
Trends, not numbers
Six-reading history per vital; red/green deltas versus the previous visit.
Visit history in one scroll
Every past prescription, diagnosis and PDF, newest first.
Prescription templates mined from the clinic's own history
ELTH scans past prescriptions and surfaces medicine combinations that were prescribed together before — one tap applies the whole set. Doctors can save their own templates too. The finished prescription previews as a clinic-branded, signed PDF and goes to the patient on WhatsApp the moment the visit ends.
app.elthclinic.com
926 visits scanned
Suggested templates come from what this clinic actually prescribes, not a generic drug list.
Rx on WhatsApp, instantly
Accessible anytime — the channel patients already open fifty times a day.
The clinic in the patient's pocket
Half of a clinic's work happens after the patient walks out. The portal tracks care programs week by week — weekly GLP-1 doses, weight logs, doctor reviews — and coaches exercise with video, reps, and a "why it helps" for every movement. It's a PWA: no app store, opens from a WhatsApp link.
Care programs, structured
Diabetes and weight-loss programs with phases, dose schedules and review dates.
Coaching, not a PDF
Sixteen-step exercise routines with video — the plan patients actually follow.
Embedded on the clinic's own website
Patients book a doctor, a blood test or a health camp straight from the clinic's site. The phone number is the identity — type it and the record fills itself in. Paying online earns a 10% discount, because a paid slot is a kept slot.
Phone number = identity
No accounts, no passwords — returning patients are recognised instantly.
10% off to pay online
Cashfree-integrated. Prepaid slots show up; the discount pays for itself.
ELTH · WHAT'S INSIDE
one clinic os — itemised
- Appointments & schedulingbooking to follow-up
- Pharmacy & diagnosticsstock to dispensing
- Billing & paymentsCashfree integrated
- Care-program enginediabetes · weight-loss · GLP-1 tracking
- Patient portal (PWA)plan, doses, exercise, Rx on WhatsApp
- Booking engineembedded on the clinic's site
- Staff & roles8 roles, permission-scoped
- WhatsApp + email automationreminders that get read
- Audit logsevery action, attributable
- Multi-clinic tenancybuilt to franchise
Total60+ features
thank you, come again (they do — daily)
Results & what I learned
- A whole clinic runs on it, daily — nine departments, eight roles, no Excel.
- 60+ features in production, shipped in eight months — Ganesh on the first frontend, me on everything after — while the clinic was using it.
- ~1.9M wasteful database reads a day eliminated — the infra bill decoupled from growth.
- Patients on WhatsApp and the web — prescriptions, care plans, bookings, without an app store.
Watch the infra bill like it's your own money — because it was. The reflex I brought from GetMyCreative. It's the one that keeps ELTH alive.
What this taught me isn't a stack. It's that the operator loop — talk to the users, ship, watch the money, repeat — works on software exactly the way it works on an agency. That loop is what I'm bringing to whoever hires me next.