Calculate the real ROI of an automation before you build it
Prices an automation honestly before you commit: manual cost including error and delay drag, build plus run plus maintenance cost, payback period with visible arithmetic, sensitivity analysis, and a one-sentence verdict. It kills both vanity automations and false 'too busy to automate' economics with the same math.
You are an operations economist who has evaluated hundreds of automation proposals, and you know both failure modes intimately: teams that automate everything and drown in maintenance, and teams that automate nothing because 'we're too busy' — doing the same task 400 times a year. You count everything: build time, run cost, maintenance tax, error risk, and the option nobody prices — just not doing the task at all. Calculate the ROI of the automation I describe. Output: 1. CURRENT COST — hours per run, runs per month, loaded hourly cost of whoever does it, plus the error and delay costs of the manual version (missed leads, stale data), stated as monthly dollars with assumptions shown. 2. AUTOMATION COST — build hours (or agency/freelancer cost), tool and API costs per month, plus a maintenance tax of 10-20% of build cost per year, justified for my case. 3. THE MATH — monthly savings, payback period in months, and 12-month net, all with the arithmetic visible so I can challenge any line. 4. SENSITIVITY — the two assumptions the result is most sensitive to, and where the break-even sits on each. 5. THE THIRD OPTION — whether this task should exist at all, or shrink; sometimes the best automation is deletion. 6. VERDICT — build now, build later at a stated trigger volume, or don't build, in one sentence. Rules: never let enthusiasm inflate hours saved — use the interview numbers, not optimistic rounding. If payback exceeds 6 months, the default verdict is 'build later' unless strategic value is explicit and named. Before calculating, interview me. Ask ONE AT A TIME, waiting for my answer each time: 1. Describe the task and how often it runs. 2. Who does it today, how long does each run really take, and what do they cost per hour, roughly? 3. What goes wrong when it's done late or wrong, and how often? 4. Who would build the automation, and what would their time or fee cost? 5. What tools or API costs would running it add monthly? Then show the math and give the verdict.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Time the manual task for real before answering question 2 — self-reported task times run low by half.
- 3
Challenge any line of the math that feels off; the assumptions are stated precisely so you can attack them.
- 4
Run it across your automation wishlist and build in payback order — it turns a debate into a queue.
Best practices
Include the error costs (question 3) — for revenue tasks, a missed handoff often outweighs all the labor savings.
Respect the maintenance tax; automations aren't fire-and-forget, and pretending otherwise flatters every proposal.
Take 'build later at trigger volume' verdicts seriously by writing the trigger down where you'll see it.
Rerun the math after shipping with actual numbers — calibrating your estimates makes every future verdict sharper.
Example: what this looks like in practice
A sales leader at a 45-person manufacturer wants to automate weekly quote-follow-up reminders that an admin currently assembles by hand. The interview establishes 3 hours a week at $35 loaded hourly cost, roughly two forgotten follow-ups a month with an estimated $400 in lost-quote impact each, a freelancer build quote of $1,800, and $60 a month in tool costs. The math shows $455 monthly labor savings plus $800 of recovered follow-up value against $60 run cost and a $270-a-year maintenance tax, for a 1.6-month payback and a $12,400 twelve-month net. Sensitivity flags the $400-per-miss estimate as the swing variable. Verdict: build now. The same leader runs the prompt on a dashboard automation next and gets 'don't build — delete the report', which saves more than the first project did.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Monthly manual cost (hours times loaded rate, plus error and delay costs) minus monthly automation cost (tools, APIs, amortized build, maintenance), then divide build cost by monthly savings for payback. The commonly skipped lines are error costs on the manual side and maintenance on the automated side — skipping either flips wrong decisions to 'yes'.
More automation & workflow design prompts
Build a system prompt for an AI cold email reply agent
Interviews you about your offer, booking flow, and voice, then generates a complete production system prompt for an AI reply agent — classification taxonomy, response rules, escalation conditions, and a strict JSON output contract an n8n or Zapier workflow can parse. You get the artifact teams pay thousands to have written, tuned to how you actually talk.
Turn a manual sales process into an automation blueprint
Converts a fuzzy 'we do this by hand every week' description into a structured blueprint with a detectable trigger, labeled steps, edge cases, human checkpoints, and failure alerts. It forces the design decisions people usually discover mid-build, so what you hand to n8n, Zapier, or an ops hire is assembly work, not archaeology.
Architect a Clay table before you burn the credits
Designs the Clay table before you build it: sources, column order, run conditions, waterfalls, outputs, and a credit estimate. Column ordering and gating are where most teams silently overspend, so the prompt enforces filter-first architecture and makes every paid column defend its run condition — typically cutting credit burn 40-70% versus enrich-everything builds.