Tool · Automation
See whether automating a task actually pays, and when. Enter the time it eats now, what that time is worth, and what the automation costs to build and run. The tool shows the net time value per period and how long the build takes to pay back.
Your numbers stay in your browser. This calculator doesn't save or transmit them. The fields start with an example. Replace them with yours.
The read
Example data—
Hours saved
/ period
Now minus what's left.
Net time value
/ period
Time value, after running cost.
Build
pays back in
Periods to recoup the build.
The math, per period
Where the net saving comes from, and the one-time build it has to pay back.
Hours saved = time now − time you'll still spend. Net time value = hours saved × hourly value − incremental running cost. One-time investment = build hours × value of build time + other one-time cost; payback = investment ÷ net time value. Saved time is only money if you actually reinvest it — into billable work, more customers, or something you'd otherwise pay for. An hour you'd have spent scrolling isn't $50 back. Automations rarely remove all the time, which is why "time you'll still spend" is a required input, not an afterthought — monitoring, exceptions, and the occasional 2 a.m. fix are real. The simple time-saved figure assumes the time you'll still spend is worth about the same per hour as the manual work; if the person minding the automation is worth much more or less, adjust the hours accordingly. The value of build time is separate from the task rate on purpose — a task a $25/hr assistant does but that you build at your own higher rate should price the build at your rate, not theirs. The 12-period line is one fixed comparison point, not a year — it's only a year if your period happens to be a month. This sizes the money case only; it doesn't price the things that often matter more: fewer errors, work that scales past your own hours, and not having to do the tedious thing. If the payback is long, weigh those before you decide.
An MMS Vegas Imprint · Las Vegas, NV
The Operator’s Library
Field manuals, guides, and tools for the people who have to make the system actually work — written from production, not theory.
Verified Current
Every manual and guide is checked against the current release and carries the month it was last verified.
Corrected Openly
When a tool changes or we get something wrong, the fix is dated and noted on the affected guide.
Built by an Operator
Written by one person running the same automations, checkouts, and campaigns these books document. By Brian Kasday →