Process Intelligence & AutomationFind where the work waits, then remove the wait.
Event data shows where a process waits, then we automate what is worth it: RPA, orchestration or a redesign.

What we deliver in Process Intelligence & Automation
Open a capability to see what it covers, where to start and the work behind it.
Attended and unattended robots for the systems that will never expose an API worth using. Built with source control, environments and exception handling, because a bot without those is a liability with a schedule.
- Start with
- Automation Rescue2 weeks
Ways to start
Named, fixed-scope engagements. Every one has a duration, a named deliverable and an exit, and you keep what we build whether or not you continue.
Start here
Automation Discovery Sprint
Four weeks. We measure what your process costs today and hand back a ranked backlog, including the candidates we tell you not to automate.
- Duration
- 4 weeks
- What you keep
- The backlog and the maps are yours whether or not you continue with us.
Diagnostic
Process Mining Diagnostic
Six weeks of event-log evidence answering where the cost actually sits, often upstream of the process you were told to fix.
- Duration
- 6 weeks
- What you keep
- The mined model is yours, platform licence or not.
Rescue
Automation Rescue
Two weeks to audit an inherited bot estate that keeps breaking, stabilise the worst of it, and tell you what is worth keeping.
- Duration
- 2 weeks
- What you keep
- You get the inventory even if you retire everything in it.
Retainer
Managed Automation Care
Monthly retainer covering monitoring, incident response and the change work that keeps automations alive as the systems underneath them drift.
- Duration
- Rolling, 3-month minimum
- What you keep
- Thirty days' notice, and the runbooks leave with you.
Bars drawn to scale: one block is one week.
Case studies
What we build on
The platforms behind the practice, and the products we hold experience in.
Explore all technologiesHow we see it
Most automation backlogs are ranked by who asked loudest. We rank them by event data: how often a path actually runs, where it waits, and what a fix is worth per year.
Then we build: RPA where the system has no usable API, orchestration where it does, and a redesign where the process should not have existed in the first place.
Tell us which process hurts.
Talk to a partner

