What is that manual processactually costing you?
Three inputs. You get the annual cost of one manual process, and an honest answer on whether it is worth automating — including when it is not.
How many people touch this one process in a normal week.
Only the manual part — the copying, checking, chasing, and re-entering. Not the whole job.
Salary plus employer costs, divided by hours worked — not the headline salary. A $60k role usually lands near $40–45/hr fully loaded.
Borderline — but probably worth a look.
This is the range where partial automation usually wins: automate the repetitive 80% and keep a human on the exceptions. Full automation is often over-engineering at this volume. Worth a scoping call to find out which.
No call required · written breakdown in 48h · nothing to sign
Or book a 30-min callRead the number as a floor
Hours only
The figure counts salary time and nothing else. Rework from bad data, missed SLAs, and the risk of one person being the only one who knows the process are all real costs sitting on top of it.
46 weeks, not 52
We deduct holidays and leave before multiplying. Most vendor calculators use 52 weeks because it makes their pitch look better. This one does not.
No uplift multipliers
No "productivity gain" or "efficiency factor" is applied anywhere. The output is arithmetic on the three numbers you entered, so you can check it on paper.
Common Questions
People × hours each per week × 46 working weeks × loaded hourly cost. We use 46 weeks rather than 52 to allow for holidays and leave, so the figure under-states rather than over-states the real cost. No hidden multipliers, no "efficiency uplift" — just the hours you already told us about.
Salary plus employer taxes, benefits, software, and overhead, divided by hours actually worked. It is typically 25–40% above the headline salary. A $60k role usually lands near $40–45/hour fully loaded. Using the raw salary rate will under-count what the process really costs you.
Because under roughly 10 team-hours a week, a custom build costs more than the problem does. We would rather tell you that here, for free, than take a project that cannot pay back. At that volume a template, a shared inbox rule, or a cheaper off-the-shelf tool is usually the honest answer.
No — deliberately. Rework, bad data downstream, missed SLAs, and the cost of one person being the only one who knows the process are all real and often larger than the hours. This calculator counts only the hours, so treat the number as a floor.
A 30-minute scoping call, then a written breakdown of the specific process within 48 hours — what to automate, what not to, and a fixed price if it is worth building. Nothing to sign, and no obligation to proceed.
If the number is big enough
Workflow automation
Connect the tools that should already talk to each other, so nobody re-enters data by hand.
Internal tools
Replace the spreadsheet running a core process with a real tool that has validation and permissions.
n8n automation
Production-grade n8n builds with error handling, logging, and alerting — on your own infrastructure.