Webbit

The Real Cost of Manual Work: A Simple Worksheet for Business Owners

A simple formula, a worked example and a worksheet to put a number on repetitive work before you decide what, if anything, to automate.

Most people can feel when a task is eating their week. Few can say what it costs. Putting a number on it's useful for two reasons: it helps you decide whether automation is worth it, and it tells you which task to fix first.

The basic formula

For any repeated task, multiply four things together.

The formula. Time per task × tasks per week × working weeks per year × loaded hourly cost = yearly direct cost.

Use the loaded hourly cost, not just the salary. Loaded cost includes taxes, benefits, equipment and a share of overheads. If you don't know it, a rough multiple of base pay is better than ignoring it. Write the assumption down so others can challenge it.

A worked example (illustrative numbers)

These numbers are invented to show the method. Replace them with your own.

Input	Value
Time to copy an enquiry from email into the CRM and notify the owner	6 minutes
Enquiries per week	60
Working weeks per year	48
Loaded hourly cost	$25

Time per week is 60 × 6 minutes = 360 minutes, or 6 hours. Over 48 weeks that is 288 hours. At $25 an hour the direct cost is $7,200 a year, for one small task done by hand.

The costs that never show up on a timesheet

Errors and rework. A mistyped phone number or a missed field leads to a follow-up that never happens, or to time spent fixing the record later.
Delay. If an enquiry waits two hours for someone to copy it across, the customer waits too. Slow responses lose business quietly.
Interruptions. Small manual tasks break concentration. The real cost is more than the minutes spent.
Opportunity. Time spent on data entry is time not spent on customers, quality or improvement.
Key-person risk. If only one person knows how a manual process works, their absence stops it.

These are harder to price. Resist the urge to invent numbers for them. Note them next to the calculation and rate each as low, medium or high. A short, honest note is more credible than a made-up figure.

A worksheet you can copy

Open a spreadsheet and create one row per task with these columns.

Task name and who does it.
Minutes per run, from a quick timing of three real examples.
Runs per week.
Weeks per year.
Loaded hourly cost.
Yearly direct cost, using the formula above.
Error or delay note: low, medium or high.
Can the rules be written down? Yes or no.

Sort by yearly cost, then look at the top five. The tasks that are both expensive and rule-based are your candidates. If you need help choosing between them, read how to choose the first process to automate.

Compare against the cost of fixing it

Automation has its own costs: the build, the tools it runs on, and the time people spend reviewing exceptions. A fair comparison looks at the first-year total and the running cost after that. A workflow that saves several thousand dollars a year in direct time can still be worth building, but only if it is simple, reliable and owned by someone.

Be conservative. If the case only works when you assume the best outcome in every column, it is probably not a good first project. Choose tasks where the saving is clear even with cautious numbers.

Common mistakes when estimating

Using the best case. Time the typical case and one awkward case, then average them.
Forgetting the review time. Most automations still need a person to check exceptions. Include that time in the comparison.
Counting the same hour twice. If two tasks overlap, count the shared time once.
Ignoring maintenance. Rules, forms and systems change. Budget a little time each month to keep a workflow healthy.
Treating saved minutes as saved money. Five minutes saved across ten people is only valuable if the time is used on something useful. Decide what that is.

What to do with the result

Rank your tasks by yearly cost and by how rule-based they are.
Pick one or two to examine more closely, starting with the most expensive that's also simple.
Write down the current time, error rate and delay so you have a baseline.
Agree what success looks like, such as hours saved, same-day replies or fewer corrections.
Set a review date, and compare the real results with the estimate.

Turn the numbers into a plan

If you bring your worksheet to an automation audit, we can review it with you, check which tasks are realistic to automate and describe a first scope with the systems involved. We'll tell you if the numbers don't justify a build. For connected tools and repeated admin, business process automation is the usual starting point.

Frequently asked questions

How accurate does the estimate need to be?

Close enough to compare tasks with each other. Time three real examples instead of guessing, and use round numbers. The goal is a ranking and a sense of scale, not an audit-grade figure.

Should I include management time?

Include it if managers repeatedly check, chase or correct the task. That time is real. Keep it as a separate line so the base calculation stays easy to defend.

What if the saving looks small?

Small tasks that run many times a day can still add up, and small tasks that cause delays or errors can matter more than their minutes. If both the cost and the risk are low, leave the task alone.

Home · Blog · Book an Automation Audit