How it works
For each task you describe, we ask two things: how long one run takes, and how often it happens. Multiply those and you get weekly hours. Multiply weekly hours by the hourly rate you gave us, then by 48 working weeks a year (not 52; nobody works every week), and you get what that task costs you annually. No single task is credited with more than 40 hours a week; a number that big stops being credible and starts being noise.
Cost isn’t the whole story, so every task also gets three scores: Impact (how much time it eats, and whether it’s a bottleneck when it’s late), Confidence (whether the process is actually written down, or lives in one person’s head), and Ease (how many tools and people it touches, and whether it needs access you don’t have). Those combine into a ranking, and every task lands in one of five verdicts: Easy win, Strategic initiative, Worth revisiting, Deprioritise, or Document first. That last one means the process needs to exist on paper before anyone can safely automate it. You can’t automate a process nobody’s written down.
What you get
A dollar figure for what your busiest process costs you a year, and up to three tasks ranked against each other, not just against themselves. You’ll see which one to attack first, which ones aren’t worth touching yet, and which ones need a written process before they’re worth automating at all. We ask for your email at the end of the six minutes, not the start. You see your own numbers before we ask you for anything.
Before you start
No. The hours and dollar figure are calculated live from what you enter, using the same rubric described above. Nothing is pre-filled or templated to look impressive regardless of your answers.
They go to Minchin, used to build your report and, if a task looks worth automating, to follow up about it. See our privacy policy for the detail.
It’s only as accurate as the hourly rate and frequency you give it: a real calculation off your own numbers, not a canned estimate. It’s built to point you at what’s worth investigating, not to be an invoice.
Teams where at least one task eats real hours every week. The assessment asks about business size and up to three specific repetitive tasks: how long each takes, how often it happens, and how it’s handled today. If you’re a team of one with no repeat process yet, there won’t be much here for you.