Here is a question most business owners never ask in concrete terms: how many hours per week does your team spend on work that could be automated?

Not a vague sense that things take too long. The actual number, in hours, multiplied across your team.

When we do this exercise with new clients, the number almost always surprises them. Not because they were unaware that manual work was happening, but because they had never counted it.

The calculation

Start with one process. Pick something your team does repetitively. A weekly report. Client onboarding. Lead follow-up. Invoice processing.

For each process, write down: how many times it runs per week, how many people touch it, and how many minutes each person spends. Multiply it out. That is your weekly cost for one process.

Now do it for five more. Add them up. Multiply by 52.

Most businesses find somewhere between 500 and 2,000 hours per year being absorbed by work that has no reason to exist.

What that actually costs

Take your average hourly rate for the people doing this work. Even at a modest figure, 1,000 hours of avoidable manual work per year represents a significant real cost. Not just in money, but in what that time could have been used for instead.

A sales team spending 6 hours a week on CRM updates is a sales team spending 6 hours a week not selling. An operations manager spending half a day on reporting is an operations manager spending half a day not managing.

Manual work is not just inefficient. It occupies the people you hired to do other things.

Where it hides

The processes that cost the most time are rarely the obvious ones. They are the small tasks that run constantly and never feel worth fixing because each individual instance is only 10 minutes.

Ten minutes, twelve times a week, across three people. That is six hours a week. That is 312 hours a year.

The highest-leverage automation work almost always comes from identifying these invisible drains and dealing with them first.

The other cost

Beyond hours, there is the error rate. Manual processes fail. Data gets entered wrong. Steps get skipped when someone is busy. Follow-ups fall through. These failures are hard to measure but they are real, and they compound.

An automation does not get tired. It does not skip a step because it had a difficult morning. It runs the same way at 3am on a Tuesday as it does at 9am on a Monday.

Consistency has a value that the hour calculation does not capture.

A starting point

If you want to run this exercise on your own business, pick your five most repetitive internal workflows. Time them. Count the people involved. Do the math.

If the number you arrive at is large enough that it surprises you, that is the signal. That is when the conversation about what to do next becomes easy.