Real appointment slots
Per doctor, with actual durations, so a patient is given a time rather than a session.
CASE STUDY
Example buildWeb AppClinic Appointments & Records
Appointments, patient history and prescriptions in one place, with reminders that cut the empty slots.
- Type
- Web app
- Build time
- 10–14 weeks
- Platforms
- Desktop at the desk, phone for patients
- Starts at
- ₹1,00,000*
This is an example build. Tavzuran is a new studio with no client work to show yet. This page describes how the project would be scoped and built — the same thinking you would get on a real one. Nothing here is a past client, and no number on this page is a result.
The price follows the feature list. The number above buys everything scoped on this page. Take features out and it comes down — the shortest route to a smaller number is a shorter list, and deciding what to drop is what the free call is for.
THE SITUATION
What's actually broken.
A two-doctor clinic books appointments in a paper diary and keeps patient history in files. Patients are given a vague time and wait. Records are hard to find when someone returns after a year.
Patient data raises the stakes here. This is health information: it needs proper access control, an audit trail, and an honest conversation about where it is stored before a line is written.
Appointments in a diary that only the front desk can see
Patient history in paper files that go missing
Waiting rooms full because everyone was told “morning”
No reminder, so a fifth of slots are no-shows
VERSION ONE
What we'd build first.
Every item here earns its place by being something a real user would miss on day one.
Patient records
History, visits, prescriptions, and uploaded reports, searchable by phone number — the only identifier patients reliably remember.
Prescriptions
Written on screen, printed on the clinic's letterhead, and kept against the visit.
Reminders
A message the day before and an hour before. This alone typically pays for the system.
Access control and audit
Reception sees the schedule, not clinical notes. Every record opened is logged, with who and when.
DELIBERATELY NOT IN V1
What we'd leave out.
Not because these are bad ideas. Because each one is designed better once the first version has told you something.
- Insurance claim processing — a specialist domain with its own integrations and its own experts.
- Lab and pharmacy modules, unless the clinic runs them in-house.
- Video consultations. Link an existing tool from the appointment.
UNDER THE HOOD
How it's put together.
- Web app
- React, used at the desk and in the consulting room
- Backend
- Node with Postgres, with access logging built in rather than bolted on
- Storage
- Reports encrypted at rest, in an Indian cloud region
- Reminders
- SMS or WhatsApp, with the clinic name in the message
- Backups
- Automated daily, and restored once in front of you so you know the restore works
HOW IT RUNS
Week by week.
-
01
Week 1
The visit flow, and a decision about where patient data lives and who may see it.
-
02
Weeks 2–7
Appointments, the schedule and the front-desk view.
-
03
Weeks 8–11
Records, prescriptions and uploads.
-
04
Weeks 12–14
Reminders, access logs, backup restore test, live.
THE HARD PART
Records that are private and findable
Every build has one problem that decides whether the rest of it matters. This is that problem, written out.
These two requirements pull against each other, and most clinic software picks a side. Locked down so tightly that the doctor cannot find last year's visit during a consultation, or so open that reception can read everyone's history.
The resolution is that access is by role and by relationship, not by a single switch. Reception sees the schedule, contact details and fee status. The doctor sees clinical history for the patient in front of them. Every record opened is logged with who and when — not because anyone expects misuse, but because an access log is the only way to answer the question honestly if it is ever asked.
Finding a record is its own problem. Patients return after a year, having forgotten any identifier except their phone number, and sometimes give a relative's. So search works on phone number, name and approximate date together, and the system tolerates a patient existing twice by making merging easy rather than by pretending duplicates cannot happen.
BEFORE A PRICE EXISTS
What we'd ask you first.
A quote given without these answers is a guess. These are the questions that actually move the number.
- 01How many doctors, and how long is a real consultation versus a booked one?
- 02Who takes bookings today — front desk, phone, WhatsApp, all three?
- 03What records exist now, and do old paper files need to come across?
- 04Where is patient data allowed to be stored, and who has decided that?
- 05Who besides the doctor needs to see clinical notes?
AFTERWARDS
How we'd know it worked.
Agreed before the build starts, so there is something to judge it against other than whether it looks nice.
- Patients are given a time and waiting room time falls.
- No-shows drop once reminders are running.
- A returning patient's history is on screen in under ten seconds.
- The access log has been reviewed at least once, by you.
BEFORE YOU START
Worth knowing.
Patient records carry legal obligations in most places, including India. I build the access control, encryption and audit trail; you should still have someone confirm your specific compliance duties. I will tell you what the system does and does not cover, in writing.
Websites and apps start at ₹20,000*. Final pricing depends on features and project scope. Third-party costs — cloud hosting, domains, external libraries, APIs, app-store fees and any other paid service — are billed separately and are not included.
KEEP LOOKING
Other example builds.
Mobile App
Gym Membership App
Digital membership, quick check-in, class booking and renewal reminders that actually go out.
Read the case study Mobile AppField Service Job App
Dispatch, on-site checklists, photo proof and an invoice raised before the technician leaves.
Read the case study New BusinessFirst Website for a Social-First Business
You built an audience on Instagram and TikTok. This is the address, the inbox and the page that are actually yours.
Read the case studyWant this built for your business?
Tell us what you're thinking. We'll figure out the next step together.
Free 20-min idea call · No obligation