About these numbers
What this tool does
Most teams can feel that repetitive admin is costing them, but few have ever put a number on it. This page does both halves of the sum: what the manual work costs today, and what fixing it returns. Use the number to decide whether automation is worth a proper conversation, with us or with anyone.
How the maths works
Nothing here is a black box, so here is every formula the page uses.
- Weekly hours are the hours you tick for one person, multiplied by the number of people doing that work.
- Annual cost is those weekly team hours × your loaded hourly rate × 52 weeks. The monthly figure is that divided by twelve.
- Full-time capacity is weekly team hours ÷ 40, because a full-time week is 40 hours.
- Annual labour recovered is people × hours per week × rate × 52.
- Year-one net return is annual labour recovered, minus the one-time build, minus twelve months of running cost.
- Break-even divides the build cost by the weekly net saving and rounds up to the next whole week. If running costs swallow the saving there is no break-even, and the page says so rather than showing a number.
- Five-year value is five years of recovered labour, minus the build, minus sixty months of running cost.
A worked example
One person losing 20 hours a week at £35/hour is 20 × 35 × 52 = £36,400 a year. Across a team of 5, that’s £182,000, and a typical build at £15,000 breaks even inside week 5.
Recomputed live in the currency you have selected, using that currency’s default rate. Change the switcher above and this paragraph changes with it.
Where to go next
If the number looks big enough to act on, the two services that usually address it are Workflow Automation and Custom AI Solutions. Or book an audit and we will work through it with you, on your real processes.