article · cross business
What an AI workflow costs to run
Estimate workflow operating cost with explicit variables, hypothetical USD inputs, setup separated from monthly costs, and sensitivity to review time.
The direct answer
Count subscriptions, usage, human review, corrections, maintenance, and setup. Compare the full task with its current manual version. Minutes released are capacity you may use elsewhere; they are not automatically money removed from payroll or cash saved.
A hypothetical monthly example
Synthetic assumptions in USD, not vendor prices or measured results: monthly volume V = 120 items; baseline B = 8 minutes; review R = 3 minutes; rework W = 1 minute per item; hourly value H = $30. Subscriptions S = $20/month; usage U = $10/month; maintenance M = 2 hours/month. Setup takes T = 5 hours and external setup expenses E = $50.
| Quantity | Formula | Example |
|---|---|---|
| Monthly capacity value | V × (B − R − W) ÷ 60 × H | 120 × 4 ÷ 60 × $30 = $240 |
| Monthly net benefit | Capacity value − S − U − M × H | $240 − $20 − $10 − $60 = $150 |
| One-time setup | T × H + E | 5 × $30 + $50 = $200 |
| Estimated payback | Setup ÷ positive monthly net benefit | $200 ÷ $150 ≈ 1.33 months |
The arithmetic illustrates assumptions. It does not predict what your business will save. Include all remaining per-item handling in review time, or explicitly expand the model to include it; omitted manual steps inflate the apparent benefit.
What belongs in each cost
Subscriptions are recurring charges allocated to this workflow. State whether you are counting a new subscription or an existing shared tool and how you allocate shared cost. Usage includes model requests and other metered operations, including failed calls and retries when charged. Verify actual requirements and charges in the relevant accounts; this guide quotes no current prices.
Rework is correction time averaged across all eligible items, including zero-correction cases. Maintenance includes checking logs, updating sources, rerunning tests, repairing connections, and handling incidents. Setup includes process design, data preparation, integration, testing, and training. Keep setup separate from monthly operating cost to avoid counting it twice.
Test the sensitivity
Keep the example’s other assumptions but increase review time to 6 minutes. Capacity value becomes $60; monthly net benefit becomes −$30. Preserve that negative result. The correct payback statement is “No positive payback under these assumptions.” Do not divide setup by zero or a negative benefit.
If monthly volume falls to 60 while review stays at 3 minutes, capacity value becomes $120 and net benefit becomes $30. Estimated payback becomes about 6.67 months. A result that depends on high volume deserves a measured volume baseline.
Limits and non-example
A blank usage estimate is unknown, not free. Zero is appropriate only when you deliberately mean zero and can explain why. Cost inputs are nonnegative, but the resulting benefit can be negative. Review quality, data permissions, and consequences remain separate acceptance conditions even when the arithmetic is favorable.
This is workflow planning, not an investment recommendation. It omits taxes, financing, and any effects you have not explicitly modeled.
Gather your inputs
Choose one measurement period. Count eligible items and record baseline, review, and correction minutes using consistent definitions. Record actual operating charges and maintenance hours separately. Mark unknown values and assign a person to measure each one before treating an estimate as a decision input.
Sources and scope
The formulas are the site’s original planning model. All numbers above are hypothetical and can be checked by hand; none represents a vendor quote or business outcome.
Next step
Add the assumptions and unknowns to your workflow brief. Revisit the decision after observing comparable work. Suggest a correction.
Change notes
Foundation draft prepared October 20, 2026. No public publication or successful live-tool test is claimed.
Next learning step: One-page workflow brief