Sam Wall

What does Sam actually build?

The system underneath the promise. When AGMM agrees to remove an operating constraint, somebody has to decide how the data will be shaped, which of the existing tools are worth keeping, where a model may be used and where it must not be, what happens on the day a supplier changes a file format, and how the thing gets into production without stopping the business for a week. That is Sam's half of the work.

In practice that means:

• The architecture: what is built, what is bought, what is connected and what is left alone.
• The engineering itself, including the integrations into software a business already pays for.
• AI behaviour: where a model genuinely earns its place, what it is allowed to decide and what a person keeps.
• Testing against real data, real rules and the exceptions your team already works around.
• Deployment, and the handover that leaves your team able to operate the system without AGMM in the room.

Adam Gillett owns the other half: the process, the people and the adoption. Neither half works on its own, which is the whole argument for forward deployed engineering and the reason AGMM sells AI consultancy that does not stop at a document.

How does he run the £2,000 audit?

The AI Constraint Audit is fourteen days and three sixty-minute working sessions. Sam is in all three, and the sessions are the smaller part of it. His job between them is to test whether each candidate opportunity can actually be built against the systems and the data the business really has, rather than the systems and the data it believes it has.

That means asking for the awkward things early: the export nobody can produce, the field three departments fill in differently, the rule that lives in one person's head. An opportunity that cannot survive those questions does not reach the economic cases, because a business case built on a dependency that does not exist is a way of losing money slowly.

The audit fee is not deducted from a build, so there is no financial reason for Sam to arrive at a recommendation to build. Where the honest answer is a process change, an integration or nothing at all, that is the answer that gets written down, and you keep the four documents either way.