Every vendor's feature list looks the same. Patient records, appointments, billing, pharmacy, lab, reports. You could put four brochures side by side and struggle to tell them apart.
That is because the feature list is the least useful part of the decision. What separates software that gets used from software that gets abandoned is almost never a missing feature — it is how the thing behaves on a Monday morning with fourteen people waiting.
Start with your workflow, not their features
Before you look at anything, write down what actually happens in your clinic on a busy day. Not the idealised version — the real one.
Who registers the patient, and what do they type? What happens when the patient has no ID? Who decides the order of the queue, and what happens when a doctor is running late? Where does the prescription go? Who collects payment, and at what point? What breaks most often today?
That page is your evaluation criteria. Everything else is noise.
The most common buying mistake in Indian clinics is choosing software designed for a workflow you do not have — usually a hospital's — and then reshaping your clinic to fit it.
Five questions that eliminate most vendors
Who else uses this, at my size, near me? Not their marquee hospital. A clinic like yours. If they cannot name one, you are the pilot, and you should be paid for that in price or support rather than the reverse.
What happens when the internet drops? In much of India this is not hypothetical. Ask what the front desk can and cannot do while offline, and how data reconciles afterwards. Answers range from "everything queues and syncs" to a shrug.
How do I get my data out? Ask this first, not last. It is covered properly further down, and a vendor's reaction to the question tells you more than the answer does.
What does support actually mean? Ask for hours, channel, language, and what happens at 9pm when the queue is broken. A clinic runs early mornings and evenings; support that ends at 6pm is closed exactly when you need it.
Who is responsible for patient data under the DPDP Act? For a clinic, the records belong to you — you are the fiduciary, and the vendor processes on your behalf. A vendor who cannot explain that distinction has not thought about it, which is itself the answer.
Run the demo on your own day
Vendor demos are choreographed. The data is clean, the patient has an ABHA number, nothing goes wrong.
Insist on running your own scenario instead. Give them five real situations from your week:
- A walk-in with no records and no ID
- A returning patient whose file is under a slightly different name
- A doctor who arrives an hour late with twenty patients booked
- A prescription that needs changing after the patient has left the room
- A refund
How the software handles the messy cases is the entire question. The clean cases all look fine.
Have the person who will actually use it in the room — your receptionist, not just you. They will spot in ten minutes what you would discover in three months.
Ask about the parts nobody demos
Onboarding. Who sets it up, how long, and is training included or billed? Migration and training are where clinic software actually fails, not in the code.
Updates. How often, and do they break anything? Is there a way to know what changed?
Limits. What happens at 200 patients a day? At three doctors? What costs more as you grow?
The mobile experience. Not whether an app exists — whether the day's work is genuinely doable on a phone, since that is where your doctors will be.
Call the references
Ask for two clinics, and actually phone them. Vendors offer references expecting you will not.
Ask them three things: what took longest to get working, what do you still do outside the system, and what would you check if you were choosing again. The third question gets the most honest answer.
Before you sign
Get the total cost in writing, including implementation, training, support and per-user charges as you add doctors — and read what clinic software should actually cost before you compare quotes, because the licence fee is rarely the number that matters.
Get the exit terms in writing. Get support hours in writing.
And start with one module rather than all of them. A clinic that switches everything on the same Monday usually switches most of it back off by Friday.
Bringing your clinic online?
See how Qlinikit and the Qlinio platform fit your workflow — book a short walkthrough.