We measure, not guess
Every recurring job gets a time cost, a frequency and a fully loaded hourly rate, so "chasing invoices" becomes "£640 a month". Decisions get easier when the numbers are on the table.
Two weeks with your team. We map every repeatable job in the business, put an hours-and-pounds figure on each, and hand you a 90-day plan for what to automate first, what to do later, and what to leave alone.
They automate what's visible rather than what's expensive, or they buy a tool before they know the job. A roadmap fixes the order.
Every recurring job gets a time cost, a frequency and a fully loaded hourly rate, so "chasing invoices" becomes "£640 a month". Decisions get easier when the numbers are on the table.
Some jobs are worth a lot but sit on messy data or awkward systems. Each one is scored for how hard it is to automate well, so the plan starts with the quick, high-value wins.
Some jobs should stay with people: the ones that need judgement, a relationship or a signature. The roadmap names them so nobody wastes money trying.
Value on one axis, ease on the other. The top-right corner is where your first agents go. The bottom-left stays human, and we say so in writing.
An hour with each team, and a short time diary for the week. We're looking for the jobs people do on autopilot, because those are the ones nobody mentions.
Each job is written up as a workflow with its systems, handoffs and failure points, then costed in hours a month and pounds a year.
Value against ease for every job, with a first draft of the order we'd tackle them in and what each step would need.
A 60-minute session with the owner and managers, the written plan, and a straight answer on what we'd do if it were our business.
Two weeks, and a plan you can act on with or without us.
Illustrative. Your plan is built from your numbers and will name the systems, owners and dates for each step.
About six hours in total across the business: an hour per team for the interviews, a light time diary that takes a few minutes a day, and the walkthrough at the end.
No. The plan is written so any competent provider, or your own team, can act on it. It names jobs, systems and order, not our products. Many clients do go on to build with us.
Then that's what the plan says, with the reasons and the things to fix first. It happens more often than you'd think, usually where the underlying data or process isn't ready.
Yes, same product. Some clients call it an audit, others a roadmap. Same two weeks, same output.
Yes. We interview each site or team separately and show where the jobs are the same and where they differ, which is usually the most useful page in the document.
A 45-minute call to see whether a roadmap would be worth your time.
Book a call