Industries

Where our work lands

We are not sector-agnostic. Each of these carries a constraint that shapes the architecture before anything else does — a regulator, a safety case, a calendar, or a network that was designed never to be reachable. Knowing which one applies is most of the work.

01

Government & Public Sector

Public bodies are measured on service completion, not on features shipped. The hard part is rarely the interface — it is the integration with registries that were never designed to be called, and the audit trail that has to hold up years later.

The constraint that shapes it

Data residency, accessibility and Arabic as the primary language are requirements, not preferences.

Common use cases

  • End-to-end digital service journeys with status visible to the applicant
  • Case management with SLA clocks and escalation
  • Arabic assistants that answer eligibility questions from published policy
  • Document verification and automated completeness checks
  • Operational dashboards for service performance reporting
02

Banking & Fintech

Every model in a regulated institution has to be explainable to someone who did not build it. We favour approaches that a risk committee can interrogate over marginally more accurate ones that nobody can defend.

The constraint that shapes it

Model explainability and change control take precedence over raw accuracy.

Common use cases

  • Onboarding and KYC document extraction with review queues
  • Transaction monitoring with false-positive reduction
  • Credit and limit models with reason codes per decision
  • Complaint classification and routing in Arabic
  • Reconciliation across core banking and third-party ledgers
03

Energy & Industrials

Operational technology networks are deliberately isolated, and rightly so. Most of the engineering effort goes into moving data out safely and into deployments that survive intermittent connectivity at the edge.

The constraint that shapes it

Safety cases and OT/IT segregation shape the architecture before anything else does.

Common use cases

  • Failure prediction on rotating equipment from vibration and thermal data
  • Production loss attribution across process stages
  • Vision-based PPE and exclusion-zone monitoring
  • Energy consumption optimisation per unit of output
  • Maintenance planning that respects shutdown windows
04

Healthcare

Clinical software is judged on whether it saves a clinician time without adding risk. We keep the model on the documentation and logistics side of the line, and leave diagnosis to clinicians.

The constraint that shapes it

Patient data never leaves the Kingdom, and every generated clinical note is clinician-approved before it counts.

Common use cases

  • Ambient documentation and discharge summary drafting
  • Coding support and claim completeness checks
  • Bed, theatre and clinic capacity forecasting
  • Appointment no-show prediction and overbooking policy
  • Arabic patient assistants for preparation and follow-up instructions
05

Retail & E-commerce

Arabic search is where most regional storefronts quietly lose revenue. Diacritics, plural forms, transliterated brand names and a shopper who types half the query in English all break a default search index.

The constraint that shapes it

Seasonality here is driven by the Hijri calendar as much as the Gregorian one; models that ignore that are wrong twice a year.

Common use cases

  • Arabic-aware search with synonym, transliteration and typo handling
  • Demand forecasting by SKU and location, including Ramadan and season effects
  • Recommendation and bundling based on real basket behaviour
  • Dynamic markdown and inventory allocation
  • Review and complaint mining across Arabic and English
06

Logistics & Mobility

Optimisation only pays when the plan survives the street. We build in the constraints dispatchers actually work around — driver hours, gate windows, and the customer who is never there before noon.

The constraint that shapes it

A plan drivers ignore is worth nothing; adoption is designed alongside the algorithm.

Common use cases

  • Route and load planning with real constraint modelling
  • ETA prediction from historical traffic and delivery patterns
  • Customs and bill-of-lading document extraction
  • Fleet health monitoring and maintenance scheduling
  • Warehouse slotting and pick-path optimisation
Talk to an engineer

Tell us what you are trying to build.

Send a short note and one of our engineers — not a salesperson — will reply within one business day.