Months at the counter, before one line of code.

Before we wrote the first line of code for Hospital Pharmacy OS, we spent two months doing nothing but standing behind pharmacy counters in Haryana.

We didn't bring mockups. We didn't ask people what they wanted. We just watched.

If you sit at a desk in an office, it is easy to draw up beautiful, clean user flows. You imagine a pharmacist sitting at a desk, opening an email report, analyzing inventory trends, and typing out purchase orders.

But when you stand behind the counter, you see the real world:

• The pharmacist has two phones ringing, a patient waving a prescription, and three distributors asking for payments—all at the same time.
• The power goes out twice a day, and the system needs to recover its state instantly.
• The computer screen is positioned so patients can't see it, but the pharmacist needs to glance at it while talking.

Standing there changed everything we planned to build.

The Ideas the Field Killed

Here is a look at the features we were certain we needed when we were designing on a whiteboard, and why we threw them away after a week in the field:

| Whiteboard Idea | What the Field Taught Us | The Decision | | :--- | :--- | :--- | | Digitize the Prescription | Doctors have written on paper for 20+ years. Asking them to use a screen slows down consultations and fails immediately. | Rejected — Design the system to ingest paper scripts at the counter instead. | | Daily Email Dashboards | Pharmacy owners do not look at their inbox. Reports sent there go unread and become useless clutter. | Rejected — Send critical operational warnings and alerts directly to WhatsApp. | | On-Premise Server Install | Small clinics don't have server rooms or IT teams. A hardware failure means total downtime. | Rejected — Build a zero-install, cloud-native system accessible from any phone or browser. |

Designing with the Grain

Shadowing pharmacists taught us a simple rule: Good software does not invent new workflows. It designs with the grain of the habits that already exist.

We noticed that the paper prescription is not a problem to be solved; it is the natural center of the transaction. A doctor writes it, a patient carries it, and the pharmacist reads it.

Instead of trying to eliminate the paper, we built the software to accept it. The pharmacist bills the items written on the paper, and the software handles the database registration, GST calculations, and stock depletion in the background.

We spent more time understanding the problem than building the solution.

This is the philosophy we bring to every project we build.