Is it worth automating?

Compare the time a recurring task takes with the time automation might recover. Test three scenarios and, if you know the costs, estimate capacity-based payback.

No signup. Your inputs and calculations stay in this tab. Export anything you want to keep before leaving or reloading.

How to make useful automation estimates
The work today

Use ungrouped numbers, e.g. 1200 or 6.5. Separators that could mean thousands, such as 1.200, are rejected; write 1.2 for a decimal.

Use a representative monthly total, as a whole number.

Include the hands-on work that happens today.

Your three scenarios

25%, 50% and 75% are illustrative starting assumptions, not benchmarks. Include remaining review, corrections and exceptions when estimating the percentage saved.

0 hours is a starting assumption. Include additional monitoring and maintenance, not review already counted in your savings estimate.

Costs, if you know them

All costs are optional. Blank means unknown; enter 0 only when the cost is zero. Use one currency and a consistent cost basis. Changing currency changes the label, not the amounts.

Use a consistent cost per working hour, including relevant employer costs.

Include implementation, preparation, testing and training.

Include subscriptions, usage charges and other recurring costs. Do not count upkeep labour twice.

Start a new calculation?

This clears your inputs and results and restores the illustrative starting assumptions. Export anything you want to keep first.

With your permission, Matomo helps us understand which pages and resources are useful. Your tool answers and documents are never included. All tools work without analytics.

Read our privacy information