Case studies
Built, deployed, still running.
The internal systems staff open every working day, and the public sites in front of them. None of this was designed in a vacuum — every module started as a real requirement from a real client, and got hardened by daily use.
A hospital website off end-of-life PHP
The public site for Aayush Group of Hospitals was running on an old PHP codebase that had stopped receiving security patches. That is a bad place for any site to sit, and a worse one for a hospital — it is the first thing a patient sees, and it carries enquiry forms.
Rather than patching around it, the front end was rebuilt in React and Next.js. The legacy PHP stack came out entirely, taking its unpatched dependencies with it. What replaced it renders fast, works properly on a phone, and is served over HTTPS from infrastructure the group controls.
- End-of-life PHP removed — no unpatched dependencies left behind
- Server-rendered pages, so departments and doctors stay searchable
- Responsive from desktop down to a small phone
- Existing content carried across, nothing lost in the move
- SSL, backups and hosting handed over documented
Applix — one login for eighteen internal systems
The staff portal a multi-unit hospital group opens every morning. Behind a single sign-in sit eighteen modules — daily schedule, OT planner, asset manager, HR recruitment, SCM item master, recognition and rewards, document folders — plus a link straight into the hospital information system. Each user only sees the modules their designation allows.
Building this is where the inventory, purchase, recruitment, asset and permission modules came from. It is also where most of the rest of this page starts.
- Quick-launch home with live and upcoming module status
- Designation-driven access, module by module, per user
- Internal news, announcements and staff celebrations built in
EaseBuddy HRMS — when a module became a product
The attendance and staff side of Applix was the piece every other business asked about. So it was rebuilt as a standalone multi-tenant HRMS: subdomain routing per company, biometric device import, selfie and GPS check-in from a Flutter app, eight leave types, gate passes, grace-period shift rules and an employee self-service portal.
- One deployment serving multiple companies
- Bulk import of employees and historical attendance
- Calendar attendance view for every employee
An importer that doesn't time out
The hospital's billing export is a 126 MB CSV with 132 columns and over one lakh rows. Most tools give up on it. This one loads it in a single pass using a COPY-based bulk loader driven by a generated column map, tracks every upload so a failure can be retried cleanly, and feeds the revenue dashboards and doctor incentive engine behind it.
- 1,17,000+ rows per file, loaded without timing out
- Incentive calculation as PostgreSQL stored procedures
- Materialised views so dashboards stay fast
Getting the data out when there is no export
The hospital's management platform held every bill and pharmacy line finance needed, and offered no usable way to get them out. No export API, no scheduled feed — someone signed in and clicked through a report by hand each time anyone wanted numbers.
The platform's own reporting API was reverse-engineered from its network traffic. Where its file-storage layer refused programmatic access, a headless browser was pointed at the same screens a person uses — it signs in, applies the filters and takes the genuine download. The rows land in PostgreSQL through an upsert that is safe to run again, hourly, with every run written to a log. Checked against the platform's own export, it matched on all 75 bills and every monetary column.
- Undocumented reporting API mapped from network traces
- Browser automation picks up where the API is blocked
- Idempotent hourly upsert, every run logged for audit
- 100% reconciliation against the platform's own export
- A schema-agnostic explorer alongside it — point it at any JSON endpoint and get a filterable, sortable table with Excel, CSV and PDF export, no field names hardcoded
The OT list, current wherever the team is standing
Operation theatre scheduling and ward handover for surgeons, nurses and OT staff, with a Flutter app so the list is never out of date on the floor. Role-based flows for doctor, nurse, OT staff and admin, procedure search with scrub-nurse assignment, and a push notification the moment anything on the schedule moves.
- Ward handover and discharge intimation workflow
- Push notifications on every schedule change
- Automated daily database backups
Procure-to-disposal, on its own domain
An asset and procurement system running at its own address for a hospital group: purchase requisition, quotation, purchase order, asset register and asset disposal, with user management and MIS reports behind it. The director dashboard opens on a unit-wise summary of every pending and completed request across seven units — Morbi, Oswal, Sava, Mehsana, Bhuj, Junagadh and Samarpan — plus total asset count and portfolio value.
- Full lifecycle: requisition → quotation → PO → register → disposal
- Every request tracked by number and status, unit by unit
- Live asset count and portfolio value on the director's home screen
Reorder levels that write the purchase order for you
The item master behind a hospital unit's stock: 974 items across eight categories, each with its own reorder level, order type and conversion rate. The screen flags the 929 items sitting below ROL, works out an order quantity for each, and generates the purchase order — one run came to 84,713 units and just over ₹18.5 lakh, calculated rather than typed.
- Bulk upload of item master, actual stock, PO quantity and rates
- Filters for below-ROL, refill, auto and order-required items
- Fifteen toggleable columns, PO history and Excel export
Whether the work actually got logged
A daily activity module inside the staff portal, so a manager can see at a glance who is logging their day and who is not. Each person gets submitted and missed counts, a success rate against a target, hours logged split between office and personal, and a month calendar where every day is marked. Activity breaks down by group, category, sub-category and location, over 7, 30 or 90 days.
- Per-day calendar view of submitted, missed and pending slots
- Success rate against a stated compliance goal
- All-users analytics view for managers, not just self-service
Also in production: an asset and purchase requisition system across seven units and head office, and a Docker Compose platform running several of these side by side with PostgreSQL, MongoDB, Redis and MinIO.
Something here look like your problem?
If your process resembles one of these, there is a good chance most of the work is already done.