Practice 02 · INTELLIGENCE : AI Automation

Get AI out of the pilot and into the operating model.

Most AI projects stall between demo and production. The model works. What's missing is who can see what, who approves what, and how anyone knows it's paying off. We build that layer.

Why pilots stall

The model is rarely the problem.

Most people assume AI projects stall on capability. In practice they stall on three questions nobody designed answers for: who can see what, who answers for it, and whether it is working. Answer those three, and production stops being a debate.

Document by document
Designed as a system
A system that retrieves across the whole company shows someone a document they should not see, so security says no.
Retrieval that respects the access rights people already have.
An agent sends, signs, or spends, and no one is accountable, so legal says no.
A named human accountable for each consequential action.
No baseline and no measure, so finance says no.
A baseline per workflow, so value is measured, not estimated.
When people call

Usually it's one of these.

01

The pilot worked, and nothing happened next.

The demo impressed people. Six months later it's still a demo.

02

Security or legal keeps saying no.

Usually with good reason: nobody can show what the system sees, or who's responsible when it acts.

03

Your agents are about to act, not just answer.

Sending email, updating records, approving spend. The stakes changed, and the controls have not.

04

Nobody can say what AI is saving you.

Lots of tools, lots of usage, and no number you'd put in front of a board.

Deliverables

Three layers between a model and production.

01 /

Workflow economics

What it is

A map of where work actually happens, which steps AI should take on, and a baseline for each one, so value is measured, not estimated.

What it prevents

Automating the wrong thing, then being unable to prove anything paid off.

02 /

Permission-aware knowledge systems

What it is

Retrieval over your private data that respects the access rights people already have, connected to the systems where work gets done.

What it prevents

The assistant that shows an intern the board deck.

03 /

Authority, approval & monitoring

What it is

Defined limits on what each agent can do, human approval where decisions are consequential, and monitoring that catches drift after launch.

What it prevents

An agent acting outside its authority, with no record of why.

Delivery

Clarity at every gate.

Nothing reaches production until you've approved how it behaves, what it sees, and how it will be measured.

01

Map

We document the workflows, data, and decisions in scope, set a baseline for each, and rank candidates by value and risk.

Approval gateYou approve the shortlist and the success measures.
02

Build

We connect the system to your data and tools, with permissions, approval steps, and logging designed in from the start.

Approval gateYou approve its behavior on your own test cases before it touches live work.
03

Run

A controlled rollout with monitoring live from day one, then a readout against the original baseline.

Approval gateYou decide whether to scale, adjust, or stop, based on numbers.

Guardrails, built in.

Each system sees only the data its users are already allowed to see, keeps nothing longer than it needs, and sends consequential decisions to a human. Every model evaluation and approval is logged, so you can show an auditor what happened and why.

Work

We build the controls we recommend.

Built experience

Agent compliance middleware

Open-source middleware that checks every agent action against encoded corporate-law rules before it executes, and writes each decision to a hash-chained evidence log.

Book a call

30 minutes to establish whether there's a fit. No pitch.

If you're stuck where strategy, AI, and regulation collide, the call is free and short. If we're not the right partner, we'll tell you and point you somewhere better.

Backlit mechanical keyboard on a desk, representing the tools of legal engineering work