Two practices, one method
One team, two disciplines that keep meeting in the same place: an operation that needs to know what happened, and a record that proves it.
Software the operation runs on
Hospital and clinic systems, pharmacy chains and the field forces that supply them, procurement and receiving, stock and scheduling. Every action leaves a record, every record has an owner, and the audit trail is not an add-on.
Pharmacies · administration and field sales
Two representatives working a day's route, eleven pharmacy accounts, and the orders, stock counts and expiry alerts they leave behind them.
Street and river geometry © OpenStreetMap contributors, ODbL. Pharmacy accounts, routes and order values are synthetic.
Software that watches the floor
Vehicle and plate recognition for garages and service centres, and site supervision for people: headcount, zones, protective equipment, dwell time. It runs on the cameras already installed, on your own hardware, without sending video anywhere.
Site · people supervision
Headcount by zone, dwell time, protective-equipment checks and restricted-area alerts — from the cameras already on the wall.
Identities are not stored. Tracks are anonymous, hold no face data and expire with the session.
Synthetic data. Names, plates and identifiers are generated and refer to no real person, vehicle or patient.
On your hardware, on your terms
On-premise first
Video and patient data stay inside the building. Cloud is an option, never a requirement.
Arabic and English
Both interfaces, both directions, from the first release rather than a translation layer added later.
Existing cameras
The vision work runs on standard IP cameras. In most sites no new hardware is needed beyond one machine.
Weak connectivity
Built for sites that lose power and internet. Local first, sync when the line comes back.
How the work is scoped
It should look like something that keeps working after the people who set it up have moved on.
Scoped work
A written scope before anything is built: what the system does, what it does not do, and what counts as finished. Changes to the scope are priced and dated, not absorbed quietly.
Fixed measures
Fixed price against a fixed scope, in stages you can stop between. You know what the next stage costs before it starts, and no stage depends on a decision nobody has made yet.
Written handover
Source code, schema, deployment steps and operating notes, handed over in writing. Trained staff on your side. Nothing about running the system lives only in our heads.