Step 02 · Automation Report
A plan for every process, in plain language.
For each process on the shortlist, the report sets out exactly how it would be automated: basic code and integrations where the rules are clear, a set of AI agents only where the work needs judgement, and a person wherever a mistake would be costly.
Book an auditWhat's in the report
The right tool for each step
Rule, script, integration, AI agent or a person, chosen step by step, with the reason written down.
Agents only where necessary
Where an agent is proposed, the report says what it reads, what it decides, how sure it must be and who checks it.
Costs and savings
Build cost, running cost and hours saved each month, so every process has a payback you can check.
A rollout order
What to build first, what can wait, and what has to be true before each step goes live.
Every step gets one of three answers.
Most processes end up with all three. The point is to use each one only where it fits.
Automate it with basic code
The logic is known and stable, so a script or an integration does it reliably and cheaply.
Hand it to an AI agent
The input varies or needs reading and judgement. The agent works with a confidence score and escalates when unsure.
Keep a person on it
A mistake would be costly or the decision is yours. The software prepares it; your team decides.
How each process is planned
Written for the people who will approve it, not just for engineers.
- 01
Break it down
Each process is split into steps, inputs, decisions and hand-offs, using the examples collected in the audit.
- 02
Pick the tool
Each step gets the simplest thing that works: a rule, a script, an integration or an agent.
- 03
Set the checks
How sure the software must be before it acts alone, and who reviews it when it isn't.
- 04
Price and sequence
Build effort, running cost and expected savings, then an order you can approve one process at a time.
What the report covers
- The architecture for each process
- Where AI agents are used, and why
- Human sign-off points and confidence thresholds
- The systems it connects to, and what changes for your team
- Build cost, running cost and expected savings
- A rollout plan with a pilot and agreed success measures
Questions
Can our own developers build from the report?
Yes. It's written so an in-house team or another vendor can build from it. Most clients ask us to, because we already know the process.
Why not use AI for everything?
A model adds running cost, monitoring and a chance of being confidently wrong. Where the rules are known, plain code is cheaper and more predictable. Agents earn their place where the input is messy or needs judgement.
Get a plan you can act on
Every report starts with a Discovery Audit. Book one and we'll take it from there.
