Run your numbers
your arithmetic, not our claims
Count what repetitive work costs your team and what recovering it is worth. Every number below is yours: we supply the arithmetic and decline to invent the rest.
The calculator
count the whole team
Team-wide hours, not per person. If three people each lose two hours to status reports, that row reads six. The defaults are a starting point, yours to change.
Where the hours hide
Someone reads every email or form that comes in and passes it along.
Copying numbers out of your systems into a report or update, again and again.
A record gets entered in one tool, then typed again into billing, tracking, or a spreadsheet.
Proposals, quotes, and letters that start as a save-as of the previous one.
Reminders about unsigned documents, unpaid invoices, and unanswered emails.
Your numbers
The full cost: wage plus benefits plus overhead. Not sure? Round up from the hourly wage.
A quote you’re considering, from us or anyone else. No number yet? Leave it blank; payback and ROI appear once you have one.
These five patterns come straight from our field notes on where the hours hide. The defaults are guesses; walk your own floor before you trust them.
The readout
Yearly figures use 46 working weeks. Holidays, PTO, and the slow weeks are already out. And we count only 60% of the hours you enter, so the estimate stays conservative.
6
Hours back, weekly
280
Hours back, yearly
$13,800
What those hours are worth, yearly
Waiting on your number.
Payback
Waiting on your number.
First-year ROI
Counting 60% of those 10 hours, that’s 6 hours a week, worth about $13,800 a year.
What clients measured
different paper entirely
Everything above is your estimate, built from your numbers. These are different: results clients measured after real builds. We do not mix the two.
$2.5M
Revenue recovered
Telecom
A telecom company had years of past projects sitting dormant: real revenue nobody had time to chase. We built a backlog-builder agent to work the list and reopen the right conversations. It recovered $2.5 million in dormant revenue.
4 days → 5 min
Per client onboarding
Professional services
A services company was losing four days of manual stitch work to every new client onboarding: the same forms, folders, and handoffs, rekeyed by hand. One automation build turned that into a five-minute job that runs itself.
FAQ
asked before the math
It is arithmetic on your estimates, not a prediction. The page multiplies the hours you entered by the cost you entered, then trims the total by the share of time you said you would really get back. Better inputs make better output. Bring the result to a call and we will pressure-test it against the actual workflow.
The full cost of an hour of someone’s time: wage plus benefits, payroll taxes, and the overhead that keeps the seat filled. Your finance team has the number, and it sits comfortably above the wage alone. Using bare wages makes every automation look worse than it is.
Because saved hours never all come back as working time. Some of what an automation saves gets absorbed by edge cases, ramp-up, and the meeting that replaces the task. We keep the count low on purpose and would rather you undercount. If you believe your number is different, bring it to the call and we will run the math with yours.
Because we have not seen your workflow yet. Builds are scoped per project, and you hear real numbers on the first call. The cost field starts blank on purpose: put in our quote once you have it, or any number you are weighing.
Usually the one your team touches most often. Frequent, rule-bound work that crosses tools tends to pay back fastest, because the gaps between systems are where the hours collect. The article this calculator is built on walks all five patterns and the tell for each.