What could one manual task be costing you?
Pick a task, set how often it really happens, and see the hours it gives back. Illustrative — the real numbers come from the 20-minute check.
Any business that prices work before doing it
Each one takes about 40 minutes — pricing it, writing the mail, attaching the documents, two follow-ups, finding the thread again
Illustrative — your real numbers come from the 20-minute check.
How the number is worked out
Minutes per occurrence times how often it happens, divided by sixty. A year assumes 46 working weeks and an eight-hour day, and the displayed figure rounds down rather than up. The arithmetic is deliberately simple so you can check it rather than trust it.
What this does not tell you
- Whether it is worth building. A task can cost ten hours a week and still be the wrong thing to automate.
- What the integration costs. The same automation is two weeks or two months depending on whether your systems can be reached from outside.
- How many cases are exceptions. If a third need a person, you are building assisted work, not automation — a different price and a different promise.
- Whether the process is about to change. Automating something that is being replaced sets the old way in concrete.
These are the questions the 20-minute check exists to answer. They are also why a number on its own is a starting point, not a decision.
The 20-Minute Check
Let's find out what's worth building.
A free 20-minute call, then a short written list of the manual work in your week that software could be doing instead — what's worth automating, what isn't, and what it would take.
- The three tasks costing you the most hours
- What each one would take to automate — plainly, and roughly how long
- What to leave alone, and why
No sales pressure, no obligation. If nothing's worth doing, we'll say so.