Why we're building MediSero+
A scribe is the smallest part of clinic software. We started with the queue and worked outward — and that decision shaped everything else.
Most clinical software companies you can name today started with the note. Voice in, SOAP out, paste into the EMR — that's the wedge. It's a real wedge: the doctor saves 60 to 90 minutes a day on documentation, and that alone justifies the price tag in most countries. So you can build a billion-dollar company around that one feature.
But if you stand in a single Indian clinic for one full day — the kind that sees 60 walk-ins, three families with multiple patients, an FD juggling phone bookings while another patient asks for the previous month's lab report on WhatsApp, a pharmacy attached at the back, a doctor with a queue spilling into the corridor — you realise that the doctor's note is the smallest thing on fire.
What's actually broken
Before MediSero+, here's what a typical clinic day looks like in software:
- The queue lives in someone's head, plus a paper register.
- Bookings come in over phone, WhatsApp, sometimes a Google form, sometimes the receptionist's personal number.
- Walk-ins are token slips ripped from a printed pad.
- The pharmacy uses a different app — or just Excel.
- Billing is a separate desk with a separate machine.
- Patient records live in a stack of OPD cards filed by phone number, last seen by anyone two visits ago.
- The lab report from yesterday is on someone's WhatsApp.
- The patient's family member has the previous Rx as a photo from when the patient broke their wrist last August.
A scribe doesn't help any of this. It saves the doctor an hour, but the clinic still loses an hour somewhere else — to a phone call asking "doctor available kya?", to a missed follow-up because no one remembered to call, to a no-show because the patient lost the slip and didn't know where to come back, to a Rx written on a different system than the one the pharmacy uses.
If you only fix the doctor's note, the clinic stays broken. The patient still doesn't see their record. The FD still juggles a paper register and three WhatsApp threads. The pharmacy still works on a parallel rail.
Where we started instead
We started with the queue. Not because it's glamorous — it's the least glamorous thing on the list — but because it's the spine of the clinic. Once the queue is digital, everything else gets a hook into it: the FD, the patient app, the pharmacy, the doctor's note, the billing.
The first version of MediSero+ was, embarrassingly, a queue manager. Doctor sees who's next, FD checks people in, walk-ins get tokens, bookings hold their slot. That's it. We shipped it to two clinics in Punjab who agreed to put their paper register away for a week and tell us what broke.
Lots broke. The most useful thing that came out of that pilot wasn't the queue — it was the realisation that the patient app was a free byproduct. Once the queue is digital, the patient can see where they are in line. Once they see where they are in line, they don't need to call to ask. Once they don't need to call, the FD has half their day back.
One feature pulls in three others
This kept happening. We'd build something for the doctor, and a side-effect would unlock the FD or the patient. We'd build something for the FD, and the doctor's life got easier two surfaces over. The clinic isn't five separate problems; it's one problem viewed from five seats.
Voice notes came next, because once we had a queue and a patient timeline, every dictation had a place to land. Rx came after that, because the doctor was already in the visit screen and the inventory needed to be checked anyway. Pharmacy stock check fed back into Rx. FD billing came naturally because the line items were already there. Clio AI showed up only when there was a record big enough to retrieve from.
The order matters
If we'd started with the scribe, we'd have built a great scribe and then bolted on a bad queue, a bad patient app, a bad billing system. You can see this pattern in most of the existing tools — the original feature is excellent, the rest is afterthought, and the clinic has to glue them together.
Starting with the queue forced us to think about handoffs: doctor to FD, FD to pharmacy, doctor to patient, patient back to clinic. Most clinic software treats handoffs as data sync — same patient ID across screens. That's necessary but not sufficient. The handoff is a UX problem: who sees what, when, and what action lands in their queue when the previous person finishes their part.
When the doctor signs an Rx, the line item appears in the FD's billing screen and the pharmacy's dispense queue, and a notification fires to the patient's phone — all from one tap. That's not a feature. That's the architecture.
What we got wrong
We optimised for solo doctors first. They were the easiest to onboard, the easiest to support, the easiest to delight. We spent six months making the solo experience feel obvious. Then we tried to add a second doctor to the same workspace and watched our model fall over.
Single-tenancy crept into a hundred small assumptions: doctor IDs in URLs, settings stored against a workspace that only had one practitioner, queue logic that assumed one consultation room. We rewrote a chunk of the data model in early 2026 and have been earning back the multi-doctor case since. The work paid off — Clinic-plan adoption is now half our pipeline — but it would have been less painful to design for it from day one.
What's coming
The thing we're not done with is the patient. The patient app today is a viewer — it shows your record, your Rx, your bookings, your family. The next version is a participant: the patient logs vitals at home, books their own follow-up, requests a refill, asks a question in the same Clio chat that lives in the doctor's app. Two-sided AI. The doctor sees what the patient asked, and Clio answers from their chart, not the open internet.
And we want pharmacies as their own role. Right now, FD doubles as pharmacist in the typical Indian clinic. As we sell into standalone pharmacies, we need a Pharmacist role that owns dispense, stock, and substitution rights but doesn't see clinical history. That's a 2026 H2 build.
Why bother writing this
Two reasons. First, every doctor who tries MediSero+ asks "why is this so different from the last thing I tried?" — and "we started with the queue" is a more honest answer than any feature list. Second, we're hiring engineers and clinicians who care about the problem more than the technology, and these posts are how we filter for that.
If you want to see the queue we built, the rest of the product is at /for-doctors. If you want to argue with us about the architecture, write to hello@medisero.com — we read everything.