Approvals
Quotes, discounts, purchase orders and timesheets routed to the right approver with reminders and an audit trail.
✦ Process automation
Business process automation for B2B operations
Automation is not about removing people. It is about removing the twenty minutes a day each of them spends copying, chasing and checking - and the errors that come with it.
✦ Candidates
Processes worth automating first
High frequency, clear rules and a real cost when they go wrong. Start there.
Document generation
Quotes, contracts, certificates, delivery notes and invoices produced from live data instead of a template someone edits.
Notifications and chasing
The follow-ups a person currently remembers to send: overdue jobs, expiring certificates, unsigned documents.
Data entry between systems
The re-typing that exists purely because two tools do not talk to each other.
Scheduled reporting
The Monday morning spreadsheet, built automatically and sent to the people who need it.
Onboarding checklists
New customer, supplier or employee setup, with tasks assigned and nothing quietly skipped.
✦ Method
How we approach an automation project
1
Map what actually happens
Not the documented process - the real one, including the workaround everybody uses and nobody mentions.
2
Cut before you automate
Some steps exist because of a decision made years ago. Removing a step is cheaper than automating it, and we will say so.
3
Automate the repetitive middle
Keep human judgement where judgement is needed. Automate the fetching, formatting, routing and chasing around it.
4
Keep a human override
Every automated path needs a way for a person to intervene, with a record of who did and why.
5
Measure it
Time per transaction before and after, error rate, and how often the override gets used. If it did not move, we change it.
✦ Boundaries
What we won't automate
Judgement calls. If a decision depends on knowing a customer, reading a situation or weighing risk, automating it produces confident nonsense.
Processes that are about to change. Automating a workflow three weeks before you reorganise the department wastes the build.
Rare exceptions. If something happens twice a year, a person handling it manually is cheaper than the code and the maintenance.
Anything where the automation would be harder to check than the task itself. If nobody can tell whether it worked, it will silently stop working.
✦ Included
What an automation build includes
- A written map of the current process and the proposed one, agreed before any code
- The automation itself, built into your systems rather than bolted onto a fragile connector
- Human override and escalation paths for every automated step
- Alerting when something needs a person, and logging of every automated action
- Training for the team, including what to do when the automation stops
- Monitoring and maintenance under the monthly retainer
✦ Questions we get asked
Automation questions
Will this replace jobs?
In our experience it moves people onto work that needed doing anyway. The typical result is the same team handling more volume without recruiting, not a smaller team.
How do we know it's actually working?
We agree the measures up front - time per transaction, error rate, how often a human overrides it - and instrument the system so you can see them without asking us.
What happens when there's an exception?
It routes to a person with the context attached, rather than failing silently or forcing a bad decision. Exceptions are designed in, not treated as a defect.
Can you automate inside our existing software?
Often yes - through APIs, workflow features you already pay for, or an integration layer. Building new software is not always the answer, and we will tell you when it is not.
Is this the same as RPA?
Not usually. Robotic process automation drives a user interface as if it were a person, which breaks whenever the screen changes. We prefer to work at the data layer, and only use UI automation where there is genuinely no other route in.
Tell us what isn't working. We'll tell you what we'd build.
Thirty minutes. Bring the process, the systems it touches and the deadline. You'll leave with an approach and an honest answer on whether custom software is the right call.
No pitch deck · We map your process · You own the software