Enterprise Systems & Digital Platforms

We build the systems that actually run your organisation — not off-the-shelf templates that force you to change how you work to suit them. From analysing the process to operating and supporting it, with one Saudi team accountable for the result.

20 daysto a first usable release
1,000 userson the largest system we delivered
8 systemsunder our operation today

When do you need a custom system?

  • Your process is unlike anyone else’s. Ready-made systems ask you to bend your operation to fit them, and the real cost shows up a year later, in the workarounds.
  • Your work is run on scattered spreadsheets. Excel files, WhatsApp groups and email — fine until volume grows, when every task becomes a hunt for the latest correct version.
  • You have a system that has reached its limit. It works, but resists every new addition, or it was built for a stage you have outgrown.
  • You need to connect to a regulator or a government platform with defined requirements that leave no room for improvisation.

What exactly we build

  • Internal operations systems: requests, approval routes, document cycles, permissions and audit trails.
  • Platforms serving people outside the organisation: portals for clients, applicants or partners, with accounts, permissions and notifications.
  • Dashboards and operational reporting built on your live data, not on a manual monthly export.
  • Automation of repeated steps: rule engines that carry out what was being done by hand, leaving the judgement to people.

How we work

  1. Understanding before writing. We sit with the process as it is actually practised — not as the policy describes it — and identify the users, the data and the bottlenecks.
  2. A first usable release within 20 days. A small system that works and is tested by the people who will use it, rather than one delivery months later where everyone discovers the understanding was incomplete.
  3. Successive releases adding functions by operational priority, with the system remaining usable at every release.
  4. Operation and support: a four-hour response to critical incidents, 99.5% availability, and eight systems under our operation today.

Our work

  • The Aljdwa platform — we developed the platform and automated the preparation of feasibility studies, and we provide its ongoing technical support.
  • ACCBS (Arabian Grants) — we automated the full grants process from application to issuance, and extended the system with AI capability.
  • Flowtech — we built the entire system, integrated its data sources, and extended it with AI.
  • WonderFatoora — an e-invoicing platform we own and operate, compliant with ZATCA requirements.

Frequently asked

How long does building a system take?

A first usable release within twenty days of the understanding being complete, then the system grows over successive releases. The full duration follows the scope, and we set it after the analysis session — not before it.

Do you use a ready-made system or build from scratch?

We choose what serves the need: it may be a custom system, an improvement to one you already run, or an integration between platforms you own. And we say plainly when a project is not worth building right now.

Where is the system hosted?

As the work requires and the contract specifies, including hosting inside the Kingdom — as with the infrastructure and local hosting we provide for the College of Law and Islamic Sciences.

What happens after delivery?

The work does not end at delivery: we operate the system, monitor it and keep developing it, with a four-hour response to critical incidents and 99.5% availability.

Tell us about your case

Send a short description of what you want done, and we reply with a first reading of the scope and the path — including saying plainly if the project is not worth building right now.