Approach
Not every task should be automated, and not every problem needs AI. Before any delivery starts, we decide what technology can take on and where a person stays accountable, then design for the cases nobody planned for.
Good automation fits the business it serves. Before we design anything, we take the time to understand four things.
Its language, its pressures, its customers and its regulators. The workflow has to make sense to the people who live in it.
Who holds the knowledge, who will use the workflow, and whose day it must not disrupt. They help shape it.
How fast the business, and the people in it, can realistically move. We pace the work to that, not to us.
Accreditations, customer contracts and audit trails are design inputs. Nothing we build should put a certificate or a contract at risk.
No big bang. One workflow, done properly.
The boundary isn’t a job title. It’s whether the whole responsibility can actually be delegated, including the consequences and the explanation.
Clear rules for repeatable work: validate a record, apply an agreed routing rule, send a routine update or trigger the next step. Actions stay within defined limits.
AI and automation interpret information, assemble context, summarise activity and prepare a recommendation or response for someone to review.
Judgement, relationships and consequential decisions stay with the people accountable for them. The administration around them is what gets reduced.
Most automation breaks on the case nobody planned for. We design for it from day one: every unusual case has a route and a named owner, so nothing fails quietly.
Within limits you have agreed.
Interpreted, checked and made ready for review.
A named owner, with the context already assembled.
RPA runs on rails. AI runs on wheels. People choose the destination. Complementary parts of one system, not competing beliefs.
| Approach | When it fits | For example | What to watch |
|---|---|---|---|
| APIs | Where a dependable connection exists between systems. | Case system updates the finance record directly. | Permissions and rate limits agreed up front. |
| RPA | Where an existing interface needs to be operated and there is no API. | Copying an approved value into a legacy screen. | Interfaces change; exceptions need somewhere to go. |
| AI | Where interpretation earns its place: language, variation, summaries. | Summarising a thread and drafting a reply for review. | Outputs are checked. Confidence is not authority. |
| A person | Where responsibility, relationships or consequence matter. | Deciding what can be promised to a customer. | Give them the context and the authority to act. |
Inwardly automated. Outwardly human.
Authority comes from the rules and permissions you agree, not from how confident an AI-generated answer sounds. Routine actions may run automatically, within an explicitly agreed boundary.
Authorised access, and only the permissions the workflow needs.
Your accreditations and obligations shape the design from the start.
Relevant source material stays available for review where practical.
A route to inspect, edit, reject or approve important outputs.
Failures are understandable, with a clear route to resolution.
The original baseline stays visible so the result can be assessed.
workflow: customer-query
trigger: inbox.new_message
permissions:
read: [case_system, crm, supplier_mail]
write: [case_system.notes]
never: [payments, hr_records]
automate:
- validate_reference
- send_acknowledgement # agreed template
augment:
- recover_history
- draft_response # for review
people_decide:
change_to_commitment: ops_lead
conflicting_information: case_owner
on_failure:
route_to: service_desk
notify_within: 15m
measure_against: discovery_baselineNo number before the evidence. We measure how the work happens today, then show what changed against it.
Hours back.
Measured against the baseline taken in Discovery, not estimated from a brochure.
Standard held.
Accuracy, compliance and response times are checked, not assumed. Faster only counts if it is still right.
Exceptions owned.
Every unusual case has a route and a named owner. Nothing fails quietly.
What is the time for? The backlog. The customers. The improvements nobody has had room for. The judgement you hired them for.
A free conversation, thirty to forty-five minutes. No deck, no obligation.