Our work


Each of these was a procedure practised one way, and became a procedure practised another. The lesson sits under each one.

  1. Client work · Nonprofit organisation in Madinah

    From three offices to a single route: the treatment request

    BeforeAfter

    Before: A paper form moving between three offices, and nobody knowing where the request stood.

    After: A single approval workflow with four roles, every transition recorded with its time and its actor.

    The lesson: A request isn't delayed because someone is stalling — it's delayed because nobody knows it's their turn.

  2. Client work · Nonprofit organisation

    From a file handed over by hand to a page opened from anywhere

    BeforeAfter

    Before: A printed file handed over by hand, every update a reprint, and copies drifting apart.

    After: A single source updated in place, visible to everyone at once.

    The lesson: The problem was never that the file was on paper — it was that its copies multiplied.

  3. A system we built

    A system we built in full — not client work. We show it because it demonstrates how we build, not to claim an organisation bought it.

    The balance that is never typed: inventory, sales and transfers

    BeforeAfter=

    Before: Stock in one file, sales in another, and what moved between them in an employee's memory.

    After: A balance derived from recorded movements, with no quantity column ever edited by hand.

    The lesson: If you want a number you can trust, don't build a field to type it into — build a movement log to derive it from.

We work with organisations across all regions of Saudi Arabia and the Gulf.

Submit a requestA written reply within two working days of your request being complete