Team Automation Savings Dashboard

What this tool does and who it is for

The dashboard sums what your automations have saved — hours reclaimed, cost avoided, and payback against what they cost to run — across your whole stack rather than one workflow at a time. Add each automation once, with the hours it removes per week and the hourly cost of the person who used to do the work, and the totals accumulate against elapsed time.

It is for whoever has to justify the automation spend: an operations lead, an agency owner, or the one technical person who quietly built six workflows and is now being asked what they were worth. If you are still deciding which process to automate first, the employee time waste calculator is the better starting point. That one finds the target; this one tracks the result.

How to read the output, with a worked example

Take an administrator on £30,000 a year, and say your automations remove six hours of their week: invoice chasing, appointment reminders, copying form submissions into the CRM.

The obvious sum is the wrong one. £30,000 across a 37.5-hour week is £15.38 an hour, six hours a week is 312 hours a year, so the saving reads as £4,800.

Now add what employing that person actually costs. Employer secondary Class 1 National Insurance for 2026 to 2027 is 15% on earnings above a secondary threshold of £5,000 a year — £3,750 here. The minimum employer contribution to an automatic-enrolment pension is 3% of qualifying earnings, and in most schemes that band runs from £6,240 to £50,270, giving £712.80. The employee costs £34,462.80, not £30,000.

That puts the real hourly cost at £17.67 and the same 312 hours at £5,514. Any figure built on gross salary understates the saving by 14.9%. Across a team of eight on similar money, the automations you already have are worth roughly £5,700 a year more than the naive sum says.

Understating your own savings is the safer direction to be wrong in, but it is still the wrong number to carry into a budget conversation, and it is the number almost every savings calculator produces.

One caveat cuts the other way. The Employment Allowance is £10,500 for 2026 to 2027 and is set against an employer's secondary Class 1 bill, so a small business claiming it may pay no employer NI at all. For them the loaded rate carries pension but not NI: £15.75 an hour, £4,914 for the year. Check which case you are in before fixing a rate — the two answers are £600 apart on one person.

The method: what each figure is made of

Loaded hourly cost = (gross salary + employer NI + employer pension + per-head software) ÷ paid hours per year. Use 1,950 hours for a 37.5-hour week, 1,820 for 35. Do not deduct holiday from the divisor; the salary is paid whether the hour is worked or not, so removing holiday silently inflates the rate.

Cumulative saving = hours removed per week × loaded hourly cost × weeks live. It is a running sum over elapsed time, not a forecast, which is why the number climbs between visits and why a switched-off automation has to be marked inactive or it keeps earning.

Payback = running cost ÷ monthly saving, where running cost means the platform tier, API and token spend, hosting, and the hour or two a month someone spends on repairs.

Three ways to value an hour saved

Common mistakes

Valuing the hour at gross salary. Roughly 15% low for a UK employee once NI and pension are counted.

Counting the same hour twice. If a reminder workflow and a no-show workflow both claim the receptionist's follow-up time, one is double-counting. Assign each task to exactly one automation.

Leaving retired automations active. Totals accrue against elapsed time, so a workflow disabled in June is still paying you back in December.

Ignoring the running cost. A dashboard that counts only the upside is marketing, not measurement.

Treating saved hours as cash. Unless headcount fell or overtime stopped, no money left the bank differently — the capacity was redeployed. Report capacity released and cash separately. AI automation for coaches and consultants covers what redeploying those hours looks like when they are your own.

Frequently Asked Questions

What hourly rate should I use for automation savings?

Use the fully loaded cost of employing the person, not gross salary divided by hours. For a UK employee, add employer National Insurance at 15% above the £5,000 secondary threshold and the minimum 3% employer pension contribution on qualifying earnings. On a £30,000 salary that moves the rate from £15.38 to £17.67 an hour.

Does an hour saved by automation count as money saved?

Only if the wage bill actually fell. If nobody's hours were reduced and no overtime stopped, the correct description is capacity released rather than cost saved. Both are worth reporting, but a finance team will reject a cash claim no bank statement supports, and losing that argument costs you the whole dashboard.

How do I calculate employer National Insurance on a salary?

For 2026 to 2027, employer secondary Class 1 National Insurance is 15% of earnings above the secondary threshold of £96 a week, £417 a month or £5,000 a year. The Employment Allowance of £10,500 can offset some or all of that bill, so check whether your business claims it before adding NI to an hourly rate.

Should the dashboard include what the automations cost to run?

Yes, or the payback figure means nothing. Count the platform subscription, model and API spend, hosting, and realistic maintenance time. Most small automation stacks need an hour or two a month of repair when an API changes, and that hour is priced at the same loaded rate as the work being replaced.

How long before the savings figure is trustworthy?

Wait until the automation has run a full reporting cycle, usually a month, then reconcile claimed runs against the platform's own execution logs. Anything shorter measures the launch week, when volumes are unusual and someone is still watching the workflow closely.

What to do with the result

Two things this dashboard cannot do. It measures automations that already exist, so it will not tell you which remaining manual process is worth doing next — run the time waste calculator across the work that is not on the dashboard yet for that. And it takes your word that each workflow still fires; a scenario that broke silently in March keeps accruing savings until somebody checks, so reconcile against execution logs quarterly. What is workflow automation covers the vocabulary if you are presenting this to people who do not build these things.

If the gap between those two lists is the real problem — plenty of manual work left, nobody with time to build the next workflow — that is the work I take on: n8n and Make.com builds, GoHighLevel automation, and the logging layer that makes savings auditable rather than assumed. You can see how I scope projects on Upwork or Fiverr, or email iam.mbilalvirk@gmail.com with the two or three processes at the top of your list. Bring the figures this dashboard gives you; it is a much shorter conversation when the hours are already counted.