Fewer logos.
More systems that run.

The problem

HR in a growing company in the Kingdom is usually a spreadsheet, a shared drive, and one person who knows where everything is. Leave balances drift, documents expire unnoticed, and onboarding depends on someone remembering the checklist.

What we built

We built a complete HR platform rather than another form: employee records with real relationships, onboarding and offboarding as tracked processes, leave with policy behind it, document management with expiry awareness, and org structure that reflects who actually approves what. Authentication runs on Microsoft Entra ID single sign-on, with Microsoft Graph handling directory and mail integration, hosted on Azure.

Where it stands

It runs. It is also our reference build — the pattern we reuse when a client needs an internal tool, which is why we can quote those projects in weeks rather than quarters.

The problem

An operating company was collecting driver and vehicle telemetry continuously and using almost none of it. The data arrived faster than anyone could look at it, and the only view of it was a map with too many dots on it.

What we built

Instead of another map, we built analysis that answers operational questions: which routes are behaving abnormally, which trips do not reconcile, and which drivers look unusual today relative to their own baseline. Streaming ingestion, spatial analysis in PostGIS, and an interface aimed at a dispatcher on shift rather than an analyst with an afternoon.

Where it stands

In pilot. The useful finding so far is unglamorous: most of the value was in anomaly and reconciliation flags, not visualisation.

The problem

Public participation in infrastructure and planning is usually run as a formality: a portal nobody can use, comments nobody reads, and a summary written by whoever has the deadline.

What we built

The design comes directly out of our founder's masters thesis on public participation and stakeholder engagement in GIS: comment collection tied to place, multilingual outreach as a first-class requirement, and AI summarisation that clusters what people actually said instead of counting responses.

Where it stands

Designed and specified, not yet built. We are honest about that. It is the practice we most want a first client for.