When finance teams audit technology spend, they scrutinise software licences, cloud bills, and vendor contracts. They almost never audit the cost of the work those tools were supposed to eliminate.

That gap is where most operational waste lives.

The three cost categories nobody tracks

  • Direct labour — hours spent on work that a system should handle: copying data between tools, generating reports, chasing approvals, re-entering information that already exists somewhere.
  • Error remediation — time spent finding and fixing mistakes introduced by manual handling. Conservative estimates put this at 20–30% of the original task time.
  • Opportunity cost — the high-value work that did not happen because the team was occupied with the above.

A simple audit method

Ask each team member to track their last five working days at 30-minute intervals. Categorise each block as: strategic work, operational work, or administrative overhead. The last category is your target.

Most operations teams are shocked to find that 35–50% of their tracked time falls into administrative overhead.

What "administrative overhead" actually covers

In practice this includes: updating status in three different systems, exporting data from one tool to reformat it for another, attending synchronisation meetings that exist because systems do not talk to each other, and manually checking whether a previous task completed correctly.

Calculating the real cost

Take the average fully-loaded hourly cost of your operations team. Multiply by the hours spent on administrative overhead per week. Multiply by 52. That is your annual overhead cost — before you count error remediation or opportunity cost. For a 10-person operations team at $40/hour with 40% overhead, the annual figure is over $330,000.

What to automate first

The highest-return targets share three characteristics: they happen frequently (daily or weekly), they follow a consistent pattern, and the inputs and outputs are already in digital form. Data transformation, approval routing, and status synchronisation almost always qualify.

The goal is not to eliminate your operations team. It is to free them to do work that machines genuinely cannot do.