Skip to content Start from ₹499/year for your first year
Contact us
Nothing fits?
Build a custom pack

Pick modules, wire your own actions and automations. Live in two weeks.

  • Modules The screens your trade needs, switched on.
  • Your words Customers, orders and bills called what you call them.
  • Automations Reminders and follow-ups that run by themselves.
For example
Laundry & dry cleaning
Order Laundry ticket
Talk to us about yours Browse all 32 packs →
ERP packs
Classes & coaching Corporate training Schools & colleges Clinics Diagnostic lab / pathology Vet clinic & pet shop Contractors & site projects Event & wedding planner Gym & coaching Professional practice Property broker Rental & hire Repairs & field service Salon & spa Security & manpower agency Services & appointments Travel agency & tour operator Website Bakery & sweet shop Caterer & tiffin service E-commerce Hotel / guest house PG & student housing Restaurant Shops & counters Association & club Exporter Farmer producer organisation Housing society & RWA Manufacturing Trusts & non-profits Wholesale & building materials
Modules Pricing Desktop & mobile apps Documentation Blog Partners About
Contact us Sign in
Theme
Product · 2 min read

Designing for a receptionist who has 40 seconds per patient

Keyboard-first screens, fewer confirmations, and the case against the modal dialog.

6 June 2026
Designing for a receptionist who has 40 seconds per patient

At a busy clinic the front desk has about forty seconds per patient. That number shaped more of our interface than any design system did.

Keyboard first, always

A receptionist who has done the job for two years does not look at the screen. She types. Every screen on the critical path is reachable and completable without touching a mouse, and the tab order follows the order the information arrives in - which is the order the patient says it, not the order the database wants it.

Confirmations cost more than mistakes

The instinct is to confirm anything destructive. But a dialog that appears forty times a day is not read by the fortieth time; it is dismissed reflexively, which means it protects nothing and costs a second each time.

So we confirm what is genuinely irreversible and expensive, and we make everything else undoable instead. An undo that works is worth ten confirmations that do not.

Against the modal

A modal steals the screen at the moment you most need what is behind it - the patient's history while you book their follow-up. Where we can, the work happens in place.

What we measure

Time from patient arriving to bill printed. Not clicks, not screens: the number the clinic actually feels. It is currently about forty-one seconds, and we would like it lower.

Clinic Design

Keep reading

Why we refuse to let you edit a module's internals
Product · 2 min

Why we refuse to let you edit a module's internals

Why "we'll customise it later" is the most expensive sentence in ERP
Migrations · 4 min

Why "we'll customise it later" is the most expensive sentence in ERP

The seven automations every clinic should switch on in week one
Automation · 2 min

The seven automations every clinic should switch on in week one