Operations
Cost of operations: how to work out what your processes actually cost
Most businesses can tell you their headcount cost to the penny and have no idea what any individual process costs. Those are different questions, and only the second one tells you where the money goes.
Last updated: July 2026
The short answer
Take each process, estimate the hours it consumes per week, multiply by a loaded hourly rate for the people doing it, annualise, and add an estimate for leakage — the rework and chasing it causes elsewhere. Do that per process and per entity, then rank them. The ranking is the useful part, not the total.
Why most companies don't know this number
Finance systems are built to report by cost centre, because that is how budgets are set and how accounts are filed. A cost centre tells you what a department costs. It cannot tell you that invoice matching costs £40,000 a year, because that work is spread across four people in three departments and none of them log it separately.
The result is a familiar situation: everyone agrees a process is painful, nobody can say what it costs, and so it never competes for budget against things that have a number attached.
The method
Five steps. A spreadsheet is enough to start; the discipline matters more than the tool.
List the processes, not the departments
Order intake. Goods in. Invoice matching. Month-end close. A department is not a process — it is a group of people running several. You want the unit of work that has a start, an end, and a handover.
Estimate hours per week
Ask the people who do it, not their manager. You are after the honest number including the parts nobody writes down: the chasing, the re-keying, the checking that the other system agrees.
Apply a loaded rate, not a salary
The full cost of an hour — employer taxes, pension, benefits, licences, a share of overhead. Salary divided by hours is the most common reason these numbers come out far too low.
Add leakage
The cost the process causes elsewhere: rework, corrections, credit notes, expedited shipping to fix a miss, the hour three other people spent because a handover failed. Estimate it rather than skip it — skipping it is not neutral, it is an assumption that leakage is zero.
Roll it up
Per process, per entity, then across the group. The total matters less than the ranking: which three processes cost more than everything else combined.
A worked example
Illustrative figures, to show the shape of the calculation rather than to describe any particular business.
| Process | Invoice matching |
| Hours per week | 12 |
| Loaded rate per hour | £38 |
| Direct cost per year (12 × 38 × 52) | £23,712 |
| Leakage — credit notes, corrections, chasing | £9,000 |
| Annual cost of this one process | £32,712 |
The point of the exercise is what happens next. Once one process has a number, every other one becomes comparable — and the conversation moves from "this is annoying" to "this is a £33,000 line item, and fixing it costs less than that."
Five ways this goes wrong
- Using salary instead of a loaded rate. Understates everything by roughly a third, sometimes more.
- Costing departments rather than processes. You end up with a headcount budget you already had, not a picture of where the work goes.
- Excluding leakage because it is hard to measure. Leaving it out is not caution — it is an assumption that it equals zero, which is never true.
- Asking managers rather than operators. Managers describe the process as designed; operators know the version that actually runs.
- Chasing precision. A number you can defend to one significant figure this month beats a perfect number next quarter.
What the number is actually for
Not for reporting. For deciding. A costed process list does three things a pain-points list cannot:
- • It ranks. You stop fixing whatever was complained about most recently and start with what is most expensive.
- • It justifies. A fix that costs £15,000 against a process costing £33,000 a year is an easy decision, and an easy one to take to a board.
- • It compares across entities. The same process costing three times more in one subsidiary is a finding you cannot get any other way.
Common questions
What does it cost to run my operations?
Add up each process's annual cost: hours per week times a loaded hourly rate, annualised, plus an estimate for leakage. Do this across every process and every entity. There is rarely one number that matters; it is usually a handful of processes costing far more than the rest combined, and those are the ones worth fixing first.
How do you calculate the cost of a business process?
Multiply the hours the process consumes each week by a loaded hourly rate for the people doing it, annualise it, then add an estimate for leakage — the rework, chasing and error correction the process causes elsewhere. The result is an annual cost for that process.
What is a loaded hourly rate?
The full cost of an hour of someone's time, not their salary divided by hours. It includes employer taxes, pension contributions, benefits, software licences and a share of overhead. Using bare salary is the single most common way these calculations come out too low.
How accurate does this need to be?
Directionally right is usually enough to make a decision. You are trying to learn which processes cost ten times more than you assumed, not to close the books. If a process is costing six figures a year, a twenty percent error in the estimate does not change what you do about it.
Why not just use time tracking data?
Time tracking captures the time people log against projects, not the time absorbed by the process itself — the chasing, the re-entry, the reconciliation between two systems. Those are the expensive parts and they rarely appear on a timesheet.
Related
- What is an operations OS? — the category this method sits inside.
- Process mining alternative — when event-log analysis fits, and when it cannot reach the work.
- Espresso for private equity — this same cost model, rolled up across a fund's whole portfolio.
- For COOs — how this cost figure fits into the wider job of running operations.
Do this across every process
Espresso runs this calculation for every process in every entity, keeps it current, and rolls it up across the group — so the ranking stays live instead of ageing in a spreadsheet.
See how Espresso works