The operating method

Four connected services Six decision gates

How we work

Nothing moves forward until the last decision is evidenced.

Assess, Implement, Enable and Operate are one engagement, not four campaigns. Each stage ends with a gate you can sign, and a record you can keep. You can enter from any point.

Written from systems already in production across 19 financial institutions in 12 countries.

Why this method

A method written from production, not from a course outline.

  1. 01

    We arrive from production.

    Our own systems are already in production across 19 financial institutions in 12 countries. The method on this page is how that kind of work gets done, not a process we wrote for a website.

  2. 02

    We work above your core systems.

    Intelligence sits on the estate you already run. We do not ask you to rip out what works in order to add what is missing.

  3. 03

    People build, they do not watch.

    Enablement is hands-on applied AI. On the builder tracks, participants leave with agents and automations they made themselves, so the system and the team advance together.

Assess

01

Orient

Know where you stand before you spend.

Most AI programmes fail because they start with a use case and discover the organisation later. We reverse that. The first output is a baseline and a sequence, not a prototype.

Decision gate
Leadership agrees the current state, the target, and the first thing to build.
Evidence at handoff
A readiness baseline, a sequenced roadmap, and a strategy written for the people who approve the spend.
Open Assess

Implement

02

Scope

Lock the problem before anyone writes code.

A system without an owner, a success criterion and a human checkpoint is a demo. We make those explicit while the work is still cheap to change.

Decision gate
The problem, owner, systems, data, human checkpoint and expected result are clear enough to build against.
Evidence at handoff
A scoped use case, a delivery shape, and an agreed path into production.
Open Implement

Implement

03

Build

Build in the open, with your team in the room.

The operating context stays close to the work. Regular demonstrations, iterative delivery, and your people inside the process, not waiting at the end for a reveal.

Decision gate
The system demonstrates the intended behaviour against the agreed criteria.
Evidence at handoff
Working increments, demonstration records, and documentation that travels with the build.
Open Implement

Implement

04

Harden

The controls are part of the build.

Evaluation, access, escalation and recovery are not a later phase. They go in while the system is being made, which is the only way they survive contact with production.

Decision gate
Evaluation, monitoring, access, escalation and recovery expectations are addressed.
Evidence at handoff
Tests, observability, human controls, traceability and production preparation.
Open Implement

Enable

05

Enable

People leave using what they built.

A system nobody can operate is a slide. Enablement is hands-on, on your stack, taught by people who ship. The people who will live with the work do the work in the room. Attendance is not the output.

Decision gate
The people who must use the system can demonstrate the work, not only describe it.
Evidence at handoff
A curriculum rebuilt for the engagement, working artefacts from the room, and a named record of who can now run it.
Open Enable

Operating environment

06

Operate

Capability has to survive the week after we leave.

Context, skills, workflows and guardrails stay configured so the work holds after delivery. The operating owner is named here, not discovered when something breaks.

Decision gate
Context, skills, workflows, access and guardrails remain usable after delivery, and the owner is clear.
Evidence at handoff
A configured operating environment and a clear path for support or extension.
Open Operating environment

Ownership

Three delivery models

The operating owner is a design decision.

It is made at the start, not discovered when the system is already live.

See the full delivery models
  1. 01

    Build and handover

    Full documentation and training, then your team takes it from there.

  2. 02

    Build and operate

    We keep it running, under agreed service levels.

  3. 03

    Build with you

    Capability and ownership transfer as you build.