One accountable principal, start to finish

Three commitments, and they are worth stating precisely rather than as a slogan.

A named principal owns the engagement

One senior person is accountable for your project from the first scoping conversation to handover. They are named at the outset, they do not change midway, and they are the person you escalate to. They are not a figurehead who appears at kickoff and at the final presentation.

Specialist involvement is disclosed in advance

Some engagements need depth we bring in deliberately: governance and assurance, security review, a particular platform. Where that happens you are told who is involved and what they are doing before they start, not after you spot an unfamiliar name on a call. The principal stays accountable for their work either way.

The people who scope it are the people who build it

Scoping is done by the people who will have to deliver against it. That is the whole reason our fixed prices tend to survive contact with a real business: nobody is quoting work they will then hand to someone else to figure out.

The economics of a traditional consultancy require leverage. A senior name sells the work and a team of juniors delivers it, because that is what makes the margin work. It is a rational business model. It is just a poor fit for operational AI, where the value sits almost entirely in understanding how one specific business actually runs.

You cannot delegate the understanding and keep the result.

So we stay small on purpose, take fewer engagements at a time, and quote fixed rather than by the day. A day rate would pay us to be slow. A fixed fee pays us to understand your operation quickly and build the right thing.

The practical consequence is that we sometimes do not have capacity, and we say so rather than staffing an engagement with whoever is free.

We operate from Abu Dhabi, London and Riyadh, and our clients are concentrated in the UK, the UAE and Saudi Arabia. That focus is deliberate, because operating patterns differ across those markets in ways that change the build. In the Gulf, WhatsApp is frequently the primary operational channel rather than a side channel, and data residency expectations shape whether a workload runs in your own cloud tenant or self-hosted on your own hardware.

We design for that rather than importing one pattern and hoping it lands. If timezone or on-site requirements make us the wrong fit, we will say so on the first call.

Every engagement runs through the same delivery standard: two assurance layers and four gates, ending in an evidence pack rather than an invoice and a handshake.

• Technical assurance. Data protection, classification, architecture, cybersecurity, AI controls, development control, release management and cost control.
• Transformation assurance. Process, people, data and value. A build nobody adopted is not a finished project.
• Four gates. Intake, design, build and release, then handover and value.

The rule we hold ourselves to: if we have not improved the process, clarified who owns it, strengthened the data and stated the value clearly, the project is not complete.