Keel3 · AI Transformation

Most AI programmes never get
below the waterline.

Licences. Pilots. A chatbot on the website. All of it visible, none of it load-bearing.

We work underneath: the process itself, the knowledge your company keeps losing, and the decisions that no longer need a person to start them. That is the weight that lets you carry sail without going over.

Where programmes stall

Three levels. Most companies stop at two.

The first two make a company faster. Only the third makes it different. It is also the only one that requires changing the organization, which is exactly why most stop just short of it.

0m

Give people tools

Everyone gets a licence and finds a few hours back. Useful. Invisible on the income statement.

20m

Speed up the process

The same workflow runs faster, or with fewer hands. Efficient. Still the same business.

60m

Redesign the work

Rebuild the process around what AI can now do and what it needs to know. The only level that changes outcomes, and the only one that asks the organization to change.

A keel is not the part you show people.

It is the part that lets you carry sail without going over. Institutional knowledge, redesigned process, and clear ownership are the same kind of weight. Nobody sees them in a demo. Everything above them depends on them.

We place a company honestly on a five-stage maturity model, then move it. The hard part is never the technology.

ABOVE THE WATERLINEWATERLINEThe keelBELOW THE WATERLINE
Where most teams live

The work that quietly eats the week

A status update nobody reads. The same report rebuilt every month. A summary written after every deploy because somebody has to.

None of it is hard. All of it is yours. And because it is never the most important thing, it is never the thing anyone fixes.

What actually changes

Stop being the trigger

Redesign the process around what a system can now do on its own, then give it the context it needs to do it well. Put a gate wherever judgment belongs.

The work does not get faster. It changes hands. That is a different thing, and it is the only version that survives you being busy.

What it buys

Judgment, which was the point

The part of your job nobody can hand off is deciding what matters, what good looks like, and when the answer is wrong.

Everything else was overhead you had learned to live with. Heads down to heads up is not a slogan. It is a description of where your attention goes once the toil has an owner.

The difference

Same task. Different owner.

By hand
With a Shadow
Who starts it
A person remembers
The event itself
When it happens
When someone has time
Every time, immediately
Consistency
Varies by author and mood
Same standard on run 40 as run 4
Record of the work
A Slack message, then nothing
A full run trace
When it is skipped
Nobody notices
Reported honestly

The task did not get smaller. It changed hands.

What level three looks like

This is Oliver. It does the work you keep redoing.

Oliver is the AI system we run our own company on. A Shadow is a workflow it owns end to end: it watches for the moment, gathers the real context, reasons about it, and delivers the result. You stop being the trigger and start being the editor.

Every run leaves a trace. Anything that ships to a human waits for approval. When there is nothing worth reporting, it says so rather than inventing something.

Get access
Shadow rundeploy-blurbs
  1. TriggerDeploy event received from GitHub
  2. GatherRead the diff, the commit history, and the release notes
  3. ReasonDraft a plain-English summary for the team
  4. GateHold for approval before anything is posted
  5. DeliverPost to the channel, and record the full run trace
Questions

The ones we actually get asked.

Ask one question about any process you run.

Why is a person still the trigger for this? If you cannot answer it well, that process is where your transformation actually starts. We are happy to work through the first one with you.