What does a manual process really cost?

Every established business runs on dozens of manual processes that nobody has ever priced. Invoices are keyed in from PDFs. Sales reports are rebuilt in a spreadsheet every Monday. Purchase orders wait for three signatures. Each one feels small, and because the cost is spread across salaries the business already pays, it never appears as a line in the profit and loss statement.

That is exactly why manual work survives. A CFO asked to approve spending on automation sees a clear cost on one side and a vague promise on the other. The way through is to price the manual process with the same discipline you would apply to any other expense. It takes a spreadsheet, an honest conversation with the people who do the work, and about an afternoon.

Start with the direct labour cost

The base formula is simple:

Hours per run x loaded hourly cost x runs per year

Hours per run is how long the process takes each time, including the small steps people forget: finding the file, chasing a missing number, checking the output. Ask the people who do the work, then watch them do it once. Estimates from managers are usually too low.

Loaded hourly cost is not salary divided by contracted hours. Include salary, allowances, gratuity or end-of-service provision, visa and insurance costs in the GCC, statutory contributions in India, office space, equipment and software. Divide by the hours someone is actually productive in a year. Runs per year is frequency: daily, weekly, per order or per invoice.

Imagine a distributor whose accounts team spends a few hours every week matching supplier invoices to purchase orders and goods received notes. Multiply those hours by the loaded rate and by fifty-two, and you have a figure, in rupees or dirhams, that a CFO can put next to a supplier's quote.

Add the costs that hide outside the timesheet

Direct labour is often the smallest part of the true cost. The rest sits in places that are harder to see but just as real:

• Errors: estimate how often the process produces a mistake, and what each mistake costs to find and fix. A wrong price on an invoice can mean a credit note, a delayed payment and an unhappy customer.
• Rework: count the times work is sent back for correction, approval or missing information, and add those hours.
• Delays: if a manual step holds up billing, collections or dispatch, price the delay. Cash that arrives later has a financing cost, and late dispatch costs customer goodwill.
• Management time: senior people reviewing, chasing and checking are part of the process, at a higher hourly cost.
• Key-person risk: if only one person knows how the process works, note the cost of disruption when they are on leave or move on.

You will not get these exactly right. That is fine. A reasonable range, agreed with the process owner, is far better than an unspoken assumption of zero.

Count the opportunity cost

The most important question is what those hours would be spent on instead. If a senior accountant spends two days a month on a reconciliation that software could do, the real cost is not just two days of salary. It is two days not spent on cash-flow forecasting, supplier negotiations or margin analysis.

The same applies in sales. Every hour a sales coordinator spends copying enquiries between WhatsApp, email and the CRM is an hour not spent following up with buyers. Be careful here: only count opportunity cost where you have a real, higher-value use for the time. Otherwise you are inflating the case, and a good board will notice.

A manual process is never free; its cost is simply hidden inside salaries you already pay.

Rank automation candidates by payback

Once you have priced several processes, put them in one table with these columns:

1. Annual cost today: direct labour plus errors, rework, delays and any opportunity cost you can defend.
2. Expected saving: the part of that cost automation would realistically remove. Most processes still need some human review, so be conservative.
3. One-off cost: build, integration, data clean-up, training and the time your own team spends on the project.
4. Running cost: software licences, maintenance and support each year.
5. Payback period: one-off cost divided by net annual saving, expressed in months.

Sort by payback. The candidates at the top are usually frequent, rules-based and tedious for the people who do them: invoice entry, report preparation, enquiry routing, approval reminders and data transfer between systems. Processes that need judgement, happen rarely or change every month usually sink to the bottom, and that is useful information too.

Check the numbers with the people who do the work

Before you take the table to the board, walk through it with the process owners. They will tell you about steps you missed and exceptions that break simple automation. They also need to trust the outcome. If the team believes automation is a way to cut their jobs, adoption will be slow and the savings will not appear. Frame it as removing the work nobody wants to do, so people can spend their time on work that genuinely needs them.

A practical first step

Pick five processes, price them this month using the method above, and rank them by payback. That single table often settles debates that have run for years. If you would like help building it, our complimentary one-week Cost Review maps your most expensive manual processes and gives you a 90-day plan, whether or not you go on to work with us.