Clinic CRM · Healthcare
Appointments, records and billing for Indian practices — and why reducing no-shows turned out to be a scheduling problem, not a reminder problem.
01 — The problem
Most clinic software is designed for the clinician's workflow. The person who actually lives in the software all day is the receptionist, juggling a phone, a walk-in queue and a doctor running forty minutes late.
No-shows are the headline complaint, and the reflex fix is to send more reminders. That treats the symptom.
Patient data also raises the stakes on every storage and access decision, which constrains how much can be pushed to third-party services.
02 — Decisions
Every one of these had a cheaper option we deliberately didn't take.
A reminder only helps if acting on it is trivial. Making 'can't make it, move me' a one-tap action converts a would-be no-show into a filled slot, which is the outcome the clinic actually wants.
The trade-off. Harder to market than an SMS reminder feature, and it required the scheduling model to handle cancellation cascades properly from day one.
Health data is the category where 'where does it live' gets asked first and answered badly. Keeping records in the clinic's instance rather than pooling them made the compliance conversation short and honest.
The trade-off. Per-tenant infrastructure is more work to operate and more expensive to run than a single shared database would have been.
Reception staff need to know who is waiting, who is next and who has been sitting there too long. That screen gets used every few minutes; the monthly report gets used once a month.
The trade-off. The product demos less impressively to an owner who wants to see charts.
03 — What shipped
Stack
04 — What we’d do differently
We underestimated how much of a clinic's day happens on a phone rather than a desktop. The reception views were designed desktop-first and retro-fitted to mobile, which cost more than designing for both would have.
One conversation to scope the work, meet the team, and get a proposal — usually within two business days.