We are an operating partner.

An implementation partner is measured on delivery: modules live, users trained, project closed. An operating partner is measured on the operation — the close is faster, the audit is cleaner, throughput is higher, the cost per unit is lower. We work to the second standard, and we write the metric into the engagement before the work starts.

That changes what we do first. We begin in the operation — the warehouse floor, the finance desk, the admissions counter — and map how the work is actually done before any platform decision is made. The technology follows the operating model, never the reverse.

It also changes who we answer to. Our sponsor is the executive whose operating metric moves if the programme succeeds: the COO, the CFO, or a sector-line CEO. We report against that metric monthly, for the life of the engagement.

Most firms are one thing or the other: consultants who hand over a recommendation, or engineers who implement a specification someone else wrote. The gap between those two roles is where most transformation programmes are lost.

Our teams carry both. A principal who can read a P&L works alongside an architect who can build the integration — same engagement, same accountability, same room. Nothing is handed across a boundary, because there is no boundary to hand it across.

This is what allows us to commit to an operating metric at all. A firm that only advises cannot control delivery. A firm that only implements cannot change the operating model. We do both, so we can be held to the result.

Al Jawad is the Arabic word for the noble horse — an animal that carried weight, moved over difficult ground, and was trusted where failure had consequences. In the Arabic tradition it stands for speed, strength and judgment. We chose it for what it demands of us.