Time Saved Calculator: Is That Automation Actually Worth Building?

There's a famous XKCD chart showing how long you can work on automating a task before the time savings justify the investment. The math is straightforward and worth running before any automation project.

The Break-Even Calculation

Break-even (weeks) = Time to automate ÷ Time saved per week

If automating a 15-minute daily task takes 4 hours:

Break-even = 4 hours ÷ (15 min × 5 days/week) = 4 hours ÷ 1.25 hours/week = 3.2 weeks

After 3.2 weeks, every week is a net gain of 1.25 hours. Over a year that's 65 hours saved — from a 4-hour investment. Clear win.

When Automation Doesn't Pay Off

Infrequent tasks. A 2-hour task done once per quarter: automation saves 8 hours/year. If building the automation takes 10 hours, break-even is 15 months. For most automations that require maintenance, this is marginal.

Evolving tasks. If the process you're automating changes frequently, the automation breaks frequently. Maintenance cost often exceeds savings.

One-time tasks. Never automate something you'll only do once. This seems obvious but catches people in "this would be a good project" thinking.

Low accuracy automations. An automation that handles 90% of cases and requires manual review for 10% may save less time than it appears — especially if the error cases require significantly more effort to fix.

The Hidden Cost: Brittleness

Automated systems have a failure mode that manual processes don't: they fail silently. A person doing a task manually notices when something is wrong. A script running at 2 AM may fail for weeks before anyone notices. Factor in monitoring and alerting as part of the automation cost.

[Calculate time saved →](https://doesitaddup.com)

This article is for informational purposes only. See our disclaimer.