Describe the repetition.
0001Assumes 48 working weeks per year. Calculator inputs stay here unless you ask to email the estimate.
Time back. Costs accounted for.
- Hours / year spent now
- 480
- Cost / year now
- $21,600
- Hours saved / year
- 336 hours
- Dollars saved / year
- $15,120
Value of time recovered, before tool costs. Not guaranteed cash savings.
- Tool cost / year
- $600
- Annual savings after tools
- $14,520
- Payback period
- 2.9 months
- 3-year net return
- $40,060
Three years of time value saved, minus tools and the one-time build cost.
This scope has a modeled payback within 3 years. Confirm the achievable share and real costs before treating it as a business case.
Email me this estimate
Simple arithmetic, with the costs left in. Use conservative inputs and test them against a real week of work.
Read the ROI guide- 0001Annual hours now = minutes ÷ 60 × weekly occurrences per person × people × 48 working weeks. Do not count the same team occurrence twice.
- 0010Hours saved = annual hours × automatable share. Dollar savings = hours saved × loaded hourly cost. This is capacity value, not a promise of lower payroll or new revenue.
- 0011Annual net savings = time value saved − (monthly tool cost × 12). Payback in months = build cost ÷ (annual net savings ÷ 12). Zero or negative net savings has no payback.
- 01003-year net return = (annual net savings × 3) − one-time build cost. The calculator uses unrounded values; displayed dollars have no cents and hours/months show up to one decimal.
- 0101Assumes steady task volume, fixed costs, and full adoption from the start. Build time, maintenance, additional review work, the $1,900 audit, taxes, inflation, discounting, and revenue effects are not modeled. Add known setup/training costs to build cost and recurring support to tool cost.
Not necessarily. Hours saved multiplied by loaded hourly cost is the value of capacity recovered. It becomes cash savings only if spending actually decreases; otherwise your team can use that time on other work. This tool does not assume layoffs, new revenue, or fewer errors.
Use the hourly cost of the person's time, including wages, benefits, payroll costs, and any overhead your organization normally allocates. The $45 default is an editable assumption, not an industry benchmark. If people have different costs, use a weighted average or calculate each group separately.
Low volume, a small automatable share, or expensive tools can outweigh the value of the time saved. If annual savings after tool costs are zero or negative, there is no modeled payback. An Automation Audit is $1,900 fixed and can help test feasibility before committing to a build, but it is a separate cost, not included here.
No. They load published service prices as a starting assumption. Reporting & Notification Automation is fixed-priced for its defined service scope; Workflow & Tool Integration and Business Process Automation have starting prices. Your actual build cost depends on systems, exceptions, security, testing, and handover.
Bring one repetitive process and your estimate. We will discuss the exceptions, the systems involved, and whether a smaller first step makes more sense.