Most teams can name the job that eats their week. Re-keying purchase orders from one system into another. Matching invoices by hand. Rebuilding a quote from last month’s. What they usually can’t say is what that job costs, and without a number, every conversation about fixing it stalls on the same question: is it worth it?
So before I suggest building anything, I put a yearly pound value on the work. It comes after mapping how the job really happens and finding the tasks that take the time, and before deciding what to change. It takes an afternoon, and you can do it yourself.
Time it, don’t guess it
Ask someone how long a task takes and you’ll get a guess. Guesses are fine for deciding what to look at, but not for deciding what to spend. So time it:
- Pick one ordinary week. Not month-end, and not a week when someone’s off.
- Ask everyone who does the task to note the time they spend on it each day, to the nearest quarter of an hour.
- Add it up across the team and round to the nearest half hour a week.
If the task is seasonal, time a typical week and note the busy periods separately. One honest week beats a month of estimates.
Turn hours into pounds
The sum is deliberately simple, so anyone in the business can check it:
yearly value = hours a week × hourly cost × 52
Use the full hourly cost of the people doing the work: their pay plus employer’s National Insurance, pension and other on-costs, not just the hourly rate on their payslip. Here’s an example for four tasks in one team, at £35 an hour:
| Opportunity | Hrs/wk | £/year |
|---|---|---|
| PO re-keying | 6.5 | 11,830 |
| Invoice matching | 4.0 | 7,280 |
| Quote drafting | 3.0 | 5,460 |
| Rota updates | 2.5 | 4,550 |
| Total | 16.0 | 29,120 |
Sixteen hours a week is easy to shrug off. £29,120 a year isn’t. You can put in your own tasks and rates in the savings calculator.
What the number is for
The figure isn’t a promise of savings. It’s a ceiling: the most a fix could ever be worth if the task disappeared completely. Most fixes take a task down rather than out, so the real saving is a share of it. That’s still enough to make the next decisions straightforward:
- Compare it with the cost of the fix. If a fix costs more than a year of the value, it needs a very good reason.
- Start with the biggest row, even when a smaller one is more annoying. Annoyance is a poor guide to cost.
- Keep the figures. Once something changes, time the same task again. The difference is your saving, measured the same way as the original number.
Where to start
Pick the one task your team complains about most and time it for a week. If the yearly figure surprises you, that’s the one worth a closer look. If you’d like a second pair of eyes on it, book a free intro session and bring the numbers.