a.1
Intake and data entry
Someone retypes the same order into three systems.
The record is captured once and written everywhere it needs to go.
fig. 00 · the drawing before the build
Business process automation that starts with the process, not the software.
We map how the work actually flows through your team, then automate the steps that never needed a person: the copying, chasing, filing and formatting between systems. AI-powered, human-approved, built for UK SMEs. No RPA licences, no six-month programme.
fig. 01 · the uncomfortable truth
Automating a bad process gives you a faster bad process.
Most automation projects fail for a boring reason. A team automates a process that nobody examined first. The copying and the chasing are wired up faster, but the detours, the double-entry and the workarounds are wired up too. Now they run at machine speed, and they are harder to see.
We have watched it happen. A workflow gets built around how one person remembers the job, not how the work actually moves. Six months of history is missing from the plan. The exceptions that eat the most time were never counted. The tool works exactly as specified and still saves almost nothing.
That is why we draw before we build. A process you can see on one page is a process you can question. Before we automate a single step, we want to know which handoffs are real, which are habit, and which quietly disappear once the work is redrawn. The drawing is cheap. The wrong system is not.
fig. 02 · how we map a process
Four steps, in order, before anything gets automated.
-
01
Observe
We sit with the people who do the work and follow one real case end to end. We count the handoffs and note every workaround, including the ones nobody admits to in a meeting.
-
02
Draw
We produce the honest current-state map on a single page: every step, every system it touches, and a rough minutes-per-week figure against each one. The mess stays in. That is the useful part.
-
03
Decide
We separate the steps that need human judgement from the steps that only need speed. We mark the human-approval gates: the moments where a person signs off before anything moves.
-
04
Automate
We build only what the drawing justifies. Each automated step maps back to a line on the page and a number, so you can see what it was meant to save and check whether it did.
You leave the first engagement with three concrete artefacts: a one-page map, a handoff count, and a minutes-per-week figure per step. Even if you never automate a thing, that is worth having.
fig. 03 · what typically gets automated
The steps that never needed a person, redrawn.
a.2
Document handling and filing
Invoices and certificates sorted by hand into folders.
Each document is read, named, filed and logged the moment it arrives.
a.3
Approval chasing and reminders
A person chases sign-off by email and hopes for a reply.
The system requests approval, waits, and nudges on a schedule.
a.4
Report assembly
Monday morning spent copying figures into a spreadsheet.
The report builds itself from source and lands before the meeting.
a.5
Customer and status updates
Clients ring in to ask where their job has got to.
Status updates go out automatically at each stage of the work.
a.6
Exception flagging
Odd cases slip through until someone eventually notices.
Anything unusual is flagged and routed to a named person.
Notice the pattern. We never automate the judgement. We automate the movement around it, and we keep a person on the exceptions.
fig. 04 · four ways to handle a broken process
AI-powered automation, and the three alternatives.
Us · AI-native
Automation built on understanding. It reads documents, classifies cases, and decides between paths, with a person on every exception. When the layout changes, it adapts instead of snapping.
Trade-off: it needs mapping and judgement upfront. That is the work we do.
RPA suites
Software robots that click through screens on a fixed script. Fast to demo. But they are pinned to exact button positions, so a supplier redesign or a new field quietly breaks them.
Trade-off: licences plus constant repair as the screens beneath it move.
Hire more admin
Add people to absorb the volume. It works, and sometimes it is the right call. But you are paying skilled staff to copy, chase and file, and the cost grows every time the workload does.
Trade-off: linear cost, and good people bored by the dull half of the job.
Leave it
Carry on as you are. Fair enough for a process that runs a few times a month. The bill only really lands when the same manual step repeats hundreds of times and the errors show up late.
Trade-off: invisible cost, paid in hours and in the mistakes nobody caught.
The short version: screen-clicking robots age badly because they copy what a person does without understanding why. We prefer automation that understands the step, so it survives the next redesign. We set out the full argument in RPA versus AI-powered automation for UK business.
fig. 05 · drawn, built, running
Three processes we redrew, anonymised.
Professional services firm · UK · anonymised
Invoice triage that handed back roughly four hours a week.
A clinic was losing part of a bookkeeper's week to sorting invoices by hand. We mapped the intake, then built a workflow that polls the inbox every few minutes, reads and classifies each invoice, files it into two document stores and writes an audit-log entry. Anything it is unsure about is flagged for a person, not guessed.
Read the full case study →Multi-location services group · UK · anonymised
CRM hygiene and one inbox for three channels.
A multi-site group was tracking the same enquiries across WhatsApp, SMS and email, with records drifting out of date across locations. We drew the pipeline, unified the messaging into a single Kanban view, and added stage automations so a lead moving forward updates the record and the next action without anyone retyping it.
Read the full case study →Regulated services sector · UK · anonymised
Compliance renewals that chase themselves.
Managed properties carry a stack of dated obligations: EICR every five years, an annual gas safety certificate, EPC, alarm checks, deposit protection deadlines. We mapped the renewal calendar, then built reminders that fire ahead of each expiry, track what has been booked, and escalate the ones nobody has actioned. The judgement stays with the manager. The chasing does not.
Names redacted out of respect for our clients. We are happy to share full details on a call.
fig. 06 · the quote
Priced to the drawing, not the sales call.
Process map & first automation
Three to five weeks
- One process observed, drawn and costed.
- A one-page map with a handoff count.
- First automated step built in production.
- A fixed quote drawn from the map.
Full process rebuild
Eight to twelve weeks
- End-to-end redesign across the systems involved.
- Human-approval gates where judgement belongs.
- Exception handling and escalation built in.
- Quoted fixed before the build begins.
Managed & measured
Rolling monthly
- We host, monitor and adjust as the process shifts.
- Changes handled without a rebuild.
- Monthly review against the minutes-per-week baseline.
- One named point of contact.
Model usage and hosting are passed through at cost. The quote is fixed after the map is drawn, so the number you approve is the number you pay.
fig. 07 · what you keep
The drawing is yours. So is everything we build from it.
We are a consultancy, not a platform you rent forever. The process map, the automation and the documentation belong to you from the start. We can host and run it for you, or hand the whole thing over with the notes to operate it. If you ever want to bring it in-house or connect it to something new, nothing is locked behind our login. See how we wire it into the tools you already run on our AI integrations page.
- The map is yours
- The system is yours
- The documentation is yours
fig. 08 · questions we get asked
Process automation, answered plainly.
What is business process automation?
Business process automation is handing the repetitive, rules-based parts of a workflow to a system instead of a person. Think of the copying between apps, the chasing for sign-off, the filing, the status updates and the report assembly. Done well, it starts with a clear picture of how the work flows today, then automates only the steps that never needed human judgement in the first place.
How do you audit our current process before automating?
We sit with the people who actually do the work and follow one real case end to end. We count the handoffs, note every workaround, and put a rough minutes-per-week number against each step. That becomes a one-page current-state map. It is deliberately honest about the mess, because the mess is where most of the wasted time hides. We only propose automation after that map exists.
What is the difference between RPA and AI-powered automation?
Traditional RPA clicks through screens the way a person would, following a fixed script. Change a button, a form or a supplier layout and the script breaks. AI-powered automation works from understanding instead of screen positions: it can read a document, classify an email, or decide which of three paths a case should take, then pass anything unusual to a person. We wrote a longer comparison if you want the detail.
Which processes should we automate first?
The best first candidate is high-volume, well-understood and low-judgement: the same task, done many times a week, where the rules are clear and a mistake is easy to catch. Invoice intake, enquiry routing and status updates are common starting points. We usually recommend one narrow process for the first build, prove it in production, then widen from there. Our workflow automation service covers that rollout.
What happens if the process changes later?
Processes change, so we build for it. Because the automation is driven by understanding rather than a brittle screen script, small changes (a new supplier, an extra field, a different approver) are usually a configuration edit, not a rebuild. You keep the process map, so when something shifts you can see exactly which step to adjust. On a managed plan we make those changes for you.
How do you measure ROI on process automation?
We anchor to the minutes-per-week numbers captured during mapping. After launch we compare the before figure against the after: hours returned to the team, faster turnaround, fewer errors caught late, fewer chase emails sent. We would rather show one honest, measured number than a headline percentage nobody can trace back to source.
Which industries see the best results?
Any UK business with a lot of structured back-office work sees the quickest return: professional services, property, healthcare admin, finance operations and multi-site groups juggling the same task across locations. The common factor is not the sector. It is having a process that repeats often enough that the copying and chasing add up to real hours.
Is our data safe under UK GDPR?
Yes, when it is designed in from the start. We map where personal data flows, define lawful basis and retention, restrict access, and log usage so you can see what happened. We can run the automation on UK or EU infrastructure we operate, and we document the data handling so a data protection review has something real to check.
fig. · 03 · Business Process Automation enquiry
Bring us your messiest process.
30 minutes. We will tell you what we would map first and what it would honestly cost.