Ways to start
Start small. Prove it. Then scale.
Fixed-scope first steps with a set length and something you keep, whether or not you continue.
Four stages, one path
Most clients enter at the first stage. Some arrive with a pilot that stalled or automations that keep breaking, so every stage has its own way in.
Diagnose
Find where AI and automation will pay, with evidence before anything is built.
Typical length: 2 to 6 weeks
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.
Start here
AI Readiness Assessment
Three weeks to separate the processes where AI changes the economics from the ones where it is an expensive way to run a rule.
- Duration
- 3 weeks
- What you keep
- You leave with a defensible position for the board, built or not.
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.
Blueprint
Integration Blueprint
Three weeks mapping the systems, the data contracts and the failure modes, before anyone writes integration code.
- Duration
- 3 weeks
- What you keep
- The blueprint is implementation-ready by any competent team, not just ours.
Pilot
Prove one thing works on your own data, systems and rules.
Typical length: 2 to 6 weeks
Pilot
Agent Pilot: one process to production
Six weeks, one process, an agent that actually goes live behind guardrails, with the evaluation harness to prove it works.
- Duration
- 6 weeks
- What you keep
- The harness and the runbook stay with your team.
Lab
Emerging Tech Sprint
Two weeks testing one emerging technology against one of your real processes, ending in a recommendation you can act on or drop.
- Duration
- 2 weeks
- What you keep
- 'Walk away' is a legitimate outcome and we will say it.
Programme
Scale what the pilot proved across teams and systems.
Typical length: Quarters, in phases
Transformation programme
Multi-quarter delivery, planned with you from what the first step proved and priced phase by phase.
Run
Keep it working as systems, vendors and volumes change.
Typical length: Monthly, rolling
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.
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.
Bars drawn to scale: one block is one week.