Step 03

Automation

Work you have proven starts running in your own systems. A person still checks every result.

Nothing runs unwatchedIn your own systemsOne build at a time
Before Automation starts

Four things have to be true first

This is the step most people want to start with, and the one that fails hardest when they do.

Tap any card for the detail

The work is written down

Step by step, including the awkward exceptions.

Not just the happy path. The exceptions are where unattended work goes wrong.

It has been run enough times to trust

By different people, on different jobs, with the same result.

Once is an anecdote. A dozen times across a few people is a pattern.

It is measured

You know what it costs, what it saves, and what going wrong would cost.

That third number is the one that decides how tight the review point needs to be.

It has an owner

A named person inside your business, responsible and able to change it.

If nobody owns it, nobody notices when it quietly stops working.

What Automation builds

Set up to run, built to be watched

Tap any card for the detail
01

It runs in the systems you already have

Inside tools your business already pays for and has approved.

Rather than adding another subscription and another login for somebody to manage.

02

A review point before anything counts

Nothing reaches a client, a ledger or a decision without a person approving it.

Designed in from the start, not bolted on later when somebody gets nervous.

03

A record of what happened

What ran, when, what it produced, who signed it off.

So when somebody asks in six months, there is an answer.

04

A stop switch and a way back

One obvious way to turn it off, with the manual process kept intact.

If it needs to stop on a Friday afternoon, it can stop on a Friday afternoon.

05

Handover, so your team can change it

Documented plainly enough that your owner does not need to call us.

If they do, we have built you a dependency rather than a capability.

What this is, in industry terms

Agents run the repeatable steps. A person reviews every result before it counts.

If you have heard the word agent and wondered what it means in practice, this is it: a set of steps you have already proven, running on their own inside your systems, stopping at a review point you control.

The word matters less than the two rules around it. Nothing runs without a review point, and nothing runs that your own team cannot explain, change or switch off.

Where Automation stops

Three things Automation will not do

Nothing runs unwatched

Nothing sends work out with no person accountable for the result.

That is not caution. It is the whole design, and it is why this step is safe to take at all.

No black boxes

If your team cannot explain to a client what happened, we have not finished.

Anything we build has to be explainable in plain words by the person who owns it.

Not before the AI Foundations Sprint has proven it

We will not build on top of work that has not been proven manually first.

Speeding up a broken process only gets you to the wrong answer faster.

How Automation is scoped

One build at a time, priced on its own

Each build is quoted as its own fixed scope piece, with the review points, the record keeping and the handover included rather than treated as extras. Everything runs in your own systems, under your own accounts.

After Automation

Step 04 is Advantage

When AI has changed how the work gets done, the commercials need to catch up.

See Advantage
Start at the bottom

This step is earned, not bought

The check will show you where you actually are.

Get your free AI Readiness Check