Selected work
Engineering · MENA · 2026
Selected engagements across software, AI and digital infrastructure — with the outcomes, systems and delivery behind them.
25 min → 45 sec · 6 h → 4 s · 3.5 days → 10 h
Precision 0.61 → 0.88 · Failures 14% → <1%
11 tools → 1 workspace · Duplicated infrastructure → shared core

Thirty-three PDF volumes of 1622–1810 Gulf history — 1.94M words over 5,657 pages — existed only as unsearchable prose, alongside a parallel Arabic edition whose text layer was unrecoverable. No structure, no entities, no map, no way to cite a passage.

Two AI products (one retrieval-heavy, one vision-heavy) were being built as separate backends. Duplicated auth, duplicated RBAC, duplicated observability, and diverging fast.

Research could require hours of manual searching across regulatory material before an adviser could begin working with the answer. Staff were handling the same 40-50 recurring UAE corporate-tax questions by hand, each one pulling two or three regulatory PDFs, and cross-references between VAT and corporate-tax documents were easy to miss.

Customers sent inspiration photographs through WhatsApp and expected matching products in return. Finding a visually similar item meant searching manually through a catalogue of roughly 40,000 SKUs - around 20 to 30 minutes per enquiry, by which point most customers had moved on.

Publishing work was distributed across eleven separate tools, with handoffs and document-based processes between them. Turnaround was unpredictable, and an outage in any one tool stalled the whole pipeline. The engagement needed more than another editorial tool: it needed the publishing operation to work as one connected environment.

A corpus of 676 Arabic doubled-verb conjugations needed to become useful as a research environment rather than remain a collection of disconnected records. The tools that existed required CSV wrangling and produced static images nobody could interact with.
Project delivery
The people shaping the solution stay close to the people building it, from scope through delivery.
Scope & decisions
Technical decisions are tied back to the outcome, constraints and priorities of the project.
Built for growth
Each engagement is structured around the problem, delivered through visible milestones, and designed with what comes next in mind.
Our ApproachA scoping conversation gives us the context to assess the work, identify what needs to be understood, and recommend the right next step.
Book a scoping call