Build
- Custom Software DevelopmentWeb apps, SaaS, integrations
- Custom E-Commerce Web DevelopmentStorefronts, checkout, payments, marketplaces
- Mobile App DevelopmentiOS + Android + cross-platform
- Application DevelopmentEnd-user products from MVP to scale
- Web Design & DevelopmentMarketing sites + e-commerce + portals
Grow
Our products
Case studies
Blog
More
- All case studiesHow we design and build custom software
- All articlesPlanning, building and running software
- Free guides and reviewsBrief template, e-invoicing review, scoping call
- Free toolsRequirements planner, e-invoicing checker and more
- Email signature generatorFree, Arabic and English
- How we workOur philosophy and project management process
Our product · Healthcare operations software
From the delivery box to the treatment room.
Clinics lose money and confidence when consumables expire on the shelf or cannot be traced to the treatment that used them. We started AFIYORA there, with an application built for how clinics actually work.

- LAN
- Runs on the clinic’s own network, no internet needed for daily work
- FEFO
- First-expiry-first-out allocation for every batch
- 1st
- Suite available; booking and payments are next
- Signed
- Licence bound to the machine it was activated on
01
The brief
Clinic managers wanted to know what is in stock, what expires soon and which treatment used which batch — without another cloud subscription, and without patient-adjacent data leaving the building.
It had to be simple enough for clinic staff, strict enough for an audit, and the first piece of a larger clinic platform rather than a dead end.
02
What made it hard
Many clinics do not want routine work to depend on an internet connection, so the application runs on the local network — which means backup, recovery and licensing have to work without a cloud service behind them.
Clinical items are not like retail stock: the same product arrives in several batches with different expiry dates, some equipment is reused across many treatments, and each use must be traceable.
03
How we approached it
Every movement is recorded — received, allocated, issued — and linked to the treatment that consumed it. Allocation picks the batch that expires first, and watch lists bring low stock and near-expiry items to the top before they become a problem.
Reusable equipment is tracked across its life. Permissions follow each person’s role, the licence is signed and bound to its machine, and the clinic holds its own data with backup and recovery built in. The product site says plainly what is available, what is coming and what is still planned.
04
What is available today
- Batch and expiry tracking with FEFO allocation
- Low-stock and near-expiry watch lists
- Usage linked to the treatment that consumed it
- Reusable equipment tracked across its life
- Role-based permissions
- Machine-bound activation with a signed licence
- Clinic-held data with backup and recovery
What went into it
What we would tell the next team
- — Start where the customer loses the most control — for clinics, that was stock, not scheduling.
- — Local-first software still needs a recovery story; design backup before the first install.
- — Labelling features as available, coming soon or roadmap builds more trust than a long feature list.
Building something similar?
Tell us what it has to do. We reply within one business day with questions and a way to scope it.


