The AI Software Factory

We build what we recommend.

Advice that stops at the slide changes nothing. The AI Software Factory is the engineering discipline behind every recommendation we make: the same team and the same method, from the first working prototype to the system your people use every day.

What the Factory builds

Four kinds of system.

Requests arrive in many vocabularies. They resolve into four kinds of system, and naming which one is the first useful act.

01 · Knowledge

Knowledge systems

Document intelligence and knowledge graphs that connect your records and cite their sources, in Arabic and English.

02 · Workflow

Agent workflows

Agents that read, act and stop for approval, with every action recorded and reviewable.

03 · Integration

Integration layers

Published interfaces into ERP, CRM and cloud, so AI works where the records already live.

04 · Modernisation

Platform modernisation

Legacy systems rebuilt or wrapped behind a contract, so AI can rely on them.

How it is built

Four stages, and what each one owes you.

Every system passes the same four stages. Each one produces something you can inspect before the next begins.

Domain model before code.

Work starts on the boundaries rather than the framework. We map the entities the business already argues about, the invariants that must hold across them, and the seams where one team's data stops being another team's concern. Those seams become service boundaries; getting them wrong is the decision that costs the most to reverse later, so it is the one made first and in writing.

Domain modelAPI contractsService boundsDecision record
STAGE · shapeOPEN
  • entities mappeddone
  • invariants writtendone
  • service bounds agreeddone
  • decision recordedin flight

The domain model and its boundaries are agreed before a service is written.

Standards

The parts that are not negotiable.

These hold on every engagement, whatever the stack or the deadline. They are expensive to add afterwards and cheap to start with.

Approval where it matters.

A person approves every action with consequences outside the system.

Delivery automation.

Every change is built, tested and released by the same pipeline.

Secure by design.

Access, data handling and residency follow the PDPL obligations that apply to the client.

Evaluated before release, watched after.

Answers and actions are tested against agreed examples, then monitored in production.

Start here

Bring us the decision you are weighing.

A briefing is a conversation about one process and the systems around it. If there is a fit, we propose a diagnosis or a defined build.