Is It Worth Automating? ROI Calculator
Find out if automating a task is worth the build time. Enter your frequency, savings, and build hours for a break-even point and a clear verdict.
Doing this 5 times a week and saving 10 minutes each run saves 43h 18m over your horizon, against a 3h build. That nets 40h 18m saved ($2,015), breaking even in 3.6 weeks. Verdict: a clear win.
Overview
Automating a task is worth it when the hours it saves clearly exceed the hours spent building it, not just barely edge past it. This calculator applies the xkcd 1205 logic to your own frequency, minutes saved, build hours, and horizon, then returns a break-even point in weeks and a verdict: clear win, close call, or not worth it.
How it works
- 1Enter how often you do this task, in times per week.
- 2Enter how many minutes it takes manually today, and how many of those minutes automating it would save, per run.
- 3Enter how many hours it will take you to build the automation.
- 4Enter how many months you expect to keep using it once it exists.
- 5Enter your hourly value, whether that is your wage, your contract rate, or a rough estimate of what your time is worth.
- 6Read the live verdict (clear win, close call, or not worth it) plus the break-even point in weeks and the net hours and dollars saved.
- 7Copy the plain-text summary to share with whoever needs convincing that the automation is, or is not, worth building.
Worked example
A 10-minute-a-run task, done 5 times a week, automated in 3 hours
At 5 runs a week, 10 minutes saved each time, a 3 hour build, and a 12 month horizon at $50 an hour, the calculator shows 43h 18m saved over the year against a 3 hour build, a net of 40h 18m and $2,015. It breaks even in 3.6 weeks. Verdict: clear win.
The same task, but the automation takes 100 hours to build
Same frequency, savings, and horizon, but the build balloons to 100 hours: the calculator still shows 43h 18m saved, but against a 100 hour build that is a net of -56h 42m and -$2,835, breaking even only after 120 weeks. Verdict: not worth it. The net is shown honestly as a loss, not hidden or floored at zero.
Methodology & privacy
Hours saved per week is how often you do the task times minutes saved per run, divided by 60. Saved hours over your horizon multiplies that by your horizon in weeks, where a month is treated as 4.33 weeks (52 weeks divided by 12 months). Net hours is saved hours minus build hours, and net dollars values that net time at your hourly rate; when build cost outweighs savings, net hours and net dollars go negative and are shown as a loss, not clamped to zero. Break-even weeks is build hours divided by hours saved per week, or no break-even at all (null) when nothing is saved. The verdict compares net hours to a margin of 20% of your build cost: net hours above that margin is a clear win, within plus or minus that margin is a close call, below it is not worth it. Your xkcd 1205 budget mirrors the logic of the original webcomic chart, which lists the maximum time worth spending automating a task at a given frequency and time saved: that maximum is exactly the total time you would save over the period, so it equals your saved-hours-over-horizon figure, just framed as a budget instead of a savings total. Unlike the original chart, which looks up a fixed frequency and time-saved combination over a fixed multi-year horizon, this calculator uses your own numbers and your own horizon directly, plus adds the break-even point and dollar value the chart does not show.
- Source: xkcd 1205, "Is It Worth the Time?"
- Source: "What are your favorite Mac shortcuts..." (r/shortcuts), evidence people build automations without knowing which ones pay off
- Source: "What's the best/easiest way to automate things on the mac?" (r/MacOS)
Every number you type into this calculator (frequency, minutes, build hours, hourly value) stays in your browser. There is no upload, no account, and no server call; the results exist only on your screen, and nothing is saved unless you copy the summary yourself.
FAQ
Is it worth automating this task?
+
It is worth automating when the hours it saves you over your horizon clearly exceed the hours it takes to build, not just barely edge past it. This calculator flags anything within 20% of the build cost as a close call rather than a clear win, and shows you the exact break-even point in weeks so you can judge for yourself.
What should I automate first?
+
Frequency matters more than duration: a task you do 10 times a week that saves 5 minutes each time often pays off faster than one you do monthly and saves an hour. Run your most repetitive tasks through this calculator and compare break-even weeks; the ones that break even fastest are almost always the right place to start.
Is automation worth the time it takes to build?
+
That depends entirely on how often you do the task and how long you will keep using the automation, which is exactly what break-even weeks measures. A task that breaks even in a few weeks is a safer bet than one that takes months, even if both look similar at a glance before you run the numbers.
How is this different from the xkcd 1205 chart?
+
The original xkcd chart is a static table: you look up your frequency and time saved and read off a fixed number for a fixed multi-year horizon. This calculator uses the same underlying logic but runs it on your actual numbers and your actual horizon, and adds two things the chart does not show: a break-even point in weeks and the net dollar value at your hourly rate.
How do I automate repetitive tasks on a Mac?
+
Shortcuts and Automator are the built-in starting points, though Automator in particular has a reputation for never gaining widespread adoption because it is unclear where to begin. This calculator does not build the automation for you; it only tells you whether building one is worth your time before you invest in Shortcuts, Automator, or a third-party tool.
Can this calculator build the automation for me, or spot what I should automate automatically?
+
No, this calculator only computes the ROI from the numbers you type in; it does not watch your screen or build anything. Automatically spotting repeated patterns and proposing the automation is what recal, a local-first Mac assistant, does on device, carrying the build cost itself so you only need to approve it.
Related tools
Context-Switching Cost Calculator
Calculate how many hours and how much money context switching costs you per day, week, and year, from your interruption count and refocus time.
True Meeting Cost Calculator (with refocus tax)
Calculate what a meeting really costs: attendees times rate times duration, plus the refocus tax everyone pays after, annualized by recurrence.
Realistic Day Planner (Planning-Fallacy Check)
Enter today's tasks and see if your plan actually fits. Applies your overrun percent, subtracts meetings and breaks, then names what to cut.
Downloads Folder Analyzer: Clean Up Downloads on Mac
See what is actually clogging your Downloads folder: type breakdown, biggest files, screenshot piles, old files, and duplicates. Runs entirely in your browser.
This tool fixes one moment. recal handles the whole day.
recal is a private brain for your Mac. It watches how you work, on device, and starts doing your busywork itself. You approve every action.
Get early access