Cost of invisible work
The calculation, with a table you can read your own row from.
Read the articleWorth reading
When does business
automation pay off?
Automation pays off when a stable, repeatable process produces a benefit you can realise after ongoing costs. Compare that net benefit with the full upfront cost, rather than multiplying all admin hours by a billing rate.
At a glance
- The three conditions
- Repetitive, material, and not going away on its own
- The test
- Could you write the steps down and would they hold for the next fifty times
- When to skip it
- Unstable processes, rare tasks, and decisions that are the valuable part
- Where it starts
- A free conversation, then a £350 Process Review or a broader Review from £650
Condition one
The task is
genuinely repetitive.
Automation works on patterns. If a task follows the same steps with different data, the same process with a different client name, invoice number and date, it is a candidate. If it needs fresh judgement each time, or varies so much that no template holds, a system adds complexity rather than removing it.
The test is blunt and it works: could you write down the exact steps in order, and would those steps still be right the next fifty times you did it? If yes, it is probably worth looking at.
Condition two
The annual cost
is material.
Building anything has a cost, and that cost has to be justified by the value of the time it frees. This is why the calculation comes before the build rather than after it.
Work out the annual cost of the task at your own rate, then compare it against a real quotation for fixing it. Not an estimate, not a rule of thumb, and not a figure from a website. A ratio you can defend to yourself is the only evidence that matters here.
Condition three
The task is not
going away on its own.
Some admin problems solve themselves. A new hire absorbs the work, or a change in the business model makes the process obsolete. If that is likely within six to twelve months, the window shortens and the case weakens.
Many do not go away. Client onboarding does not get easier as you take on more clients. Invoicing does not simplify as revenue grows. What is frustrating at ten clients is still frustrating at twenty, and by then it takes twice as long.
The honest part
When it does not pay off
Being clear about when this is the wrong answer matters as much as knowing when it is right.
Do not automate
- A low-volume task with little benefit may not justify a custom build. An inexpensive built-in rule, reduced risk or prevention of a costly error can still make it worthwhile.
- A process that is not stable. If the steps change often, you will spend longer updating the system than doing the work.
- Work that needs nuanced judgement that shifts with context. If the decision is the valuable part, keep the decision.
- A business that is very early. Processes still being discovered should not be set in concrete yet.
- A genuine capacity problem. Sometimes the right answer is a person.
What good looks like
- It runs reliably without anyone watching it
- It is transparent enough that a failure is obvious
- It handles the common case and routes the exceptions to a person cleanly
- It was built after someone mapped the process, not after someone chose a tool
- Your team can run it without the person who built it
One failure is choosing the wrong process. It is building the wrong thing: automating a process nobody properly understood, at a step that was not the bottleneck, with a tool chosen before the problem was diagnosed. That is why the diagnosis always comes first.
Where to start
Do the calculation
before you spend anything.
Which tasks repeat most often? How long do they actually take, measured rather than remembered? What does that cost in a year at your effective rate? Which of them are stable enough to be worth fixing safely?
That is what the Business Process Review produces: a clear picture of where the time goes, the cost of each category, and a ranked list in order of impact. Under two hours of your time, from £650. If the numbers do not support building anything, the report says so.
In practice
A complete payback calculation
| Input | Conservative case | Stronger case |
|---|---|---|
| Time actually released | 4 hours a week | 6 hours a week |
| Illustrative avoidable cost per hour | £30 | £30 |
| Working weeks used in the model | 46 | 46 |
| Gross monthly benefit: hours × rate × 46 ÷ 12 | £460 | £690 |
| Monthly software, support and remaining checks | £120 | £120 |
| Net monthly benefit | £340 | £570 |
| Illustrative full upfront budget | £4,080 | £4,080 |
| Payback: upfront cost ÷ net monthly benefit | 12 months | About 7.2 months |
This is a worked model using example inputs, not a client result or a 10PM quotation. The hourly value only counts as cash benefit if that cost can actually be avoided. If the time becomes extra client work, use achievable contribution with enough demand. If net monthly benefit is zero or negative, the model has no positive financial payback. Capacity and personal time can still matter, described separately.
Before we talk
What people ask
about payback.
Three questions that decide whether this is worth your money.
What payback period should I be looking for?
Use the full upfront cost divided by positive net monthly benefit. Include the agreed process review, design, implementation and relevant migration or training, then subtract ongoing software, support and checking from the monthly benefit. The useful period depends on how long the process will remain relevant and whether the benefit is achievable.
Can you tell me the cost before the Review?
The Focused Process Review is £350 and the broader Review is from £650. We agree the appropriate starting point during the free introduction. A fixed implementation price follows sufficient mapping and design of the agreed process.
What if only one of the three conditions holds?
It needs a closer look. Frequency is one consideration; avoiding a costly error or using an inexpensive built-in rule can change the decision. The Review examines the benefit, stability and full cost rather than applying one universal threshold.
Keep reading
Related
Agree the starting point
Measure the change that matters to your business.
| The issue | What we establish first | What we check afterwards |
|---|---|---|
| Work behind the fee | Agreed scope, actual effort and how extras are handled. | Delivery effort and additional requests recorded for a fee decision. |
| Work waiting to be billed | Time from completed work to an invoice ready for approval. | That interval, missing approvals and unresolved billing exceptions. |
| Repeated preparation | Time spent retyping information, chasing documents or assembling reports. | Time still needed, checking effort and the quality of the output. |
| Decisions without a clear picture | The questions you need answered and the records available. | Whether the agreed view is current, useful and used by the team. |
Released time creates capacity. Earlier payment improves cash flow. Include design, implementation, software, support and ongoing checking in the financial case.
Your business
Run the numbers
for your business.
Tell me what your week looks like and I will tell you whether removing the work makes financial sense, and what would have to be true for it to pay.
15 minutes · No charge
Prefer to write? anne@10pm.works