How to calculate the real cost of repetitive work

A fifteen-minute task repeated every morning costs a business more than sixty hours a year. That expense never lands on a budget line, because nobody labels a cost center “manually copying numbers between two systems.” So it survives for years, eating hours that go uncounted.

To judge whether a fix is worth pursuing, you need a real number you can weigh against the cost of changing it. A vague sense that the task is annoying won't tell you which one costs more.

The formula, without the jargon

Start with three things: how long the task takes each time, how often it happens, and what an hour of that person's time is worth to the business. Multiply them together and you have a weekly or monthly cost. It sounds almost too simple, and it usually is. The hard part is being honest about the inputs.

People consistently underestimate frequency and duration. A task that “only takes a few minutes” often takes fifteen once you count the interruption, the context switch back into it, and the small errors that need correcting afterward. Multiply that undercount across a year and the gap becomes significant.

Two examples, same hidden cost

A construction contractor's office manager reconciles subcontractor invoices against project budgets by hand, across three separate spreadsheets, about forty minutes a day. Valued conservatively, that one habit runs to thousands of dollars a year in labor spent on data entry instead of oversight.

Now picture a solo consultant who copies client notes from each call recording into a CRM by hand. Twenty minutes a call, ten calls a month: more than three hours every month spent on typing that could have been billable work.

Neither task feels dramatic in the moment, which is exactly why it persists. Repetitive work stays expensive because it never feels expensive day to day.

What the number should include

• Direct time spent on the task itself, measured honestly.
• Time lost to context-switching, both the ramp-up before and the recovery after.
• Error correction time, if the manual process produces mistakes that someone else has to catch and fix.
• Opportunity cost: what would this person do instead if the hours were freed up?

Before you trust the number

First, a few honest checks: have you timed the task recently or are you working from memory, and does the frequency you used reflect a normal week rather than a slow one? Confirm you are counting the interruptions and corrections around the task and not only the task itself, then multiply the total across a year and see whether it still feels small. Hardest of all, ask whether fixing this would free up time for work that grows the business or would only shift the tedium somewhere else.

That last question matters more than people expect. Freeing up five hours a week is only valuable if those hours go somewhere useful. Otherwise you've reduced friction without changing outcomes.

The real cost of repetitive work is almost always larger than it feels, because it's paid in small, unlabeled installments. Run the calculation (time per task, times frequency, times the value of that time) and a vague annoyance turns into a number you can act on. Once you have that number, you can weigh it against the cost of a fix, whether that means new software, a process change, or handing the work to someone else.