Total attempts
requested runs x (1 + retry rate)
Counts the extra model and tool calls created by retry loops.
Go beyond model-call cost. Include platform fees, tool usage, retry loops, acceptance rate, human review, and maintenance to see what a useful outcome actually costs.
This tool runs in your browser. Your workflow data is not uploaded or sent to an AI model.
Replace the examples with real workflow data before using the result.
Your fully loaded cost report will appear here
Include quality and retries so a cheap run does not hide an expensive result.
Open methodology
A low model bill does not mean an agent is inexpensive. Failed outputs, retries, review time, platform fees, and recurring maintenance can become the larger cost. This model makes each assumption visible so you can replace estimates with operating data.
requested runs x (1 + retry rate)
Counts the extra model and tool calls created by retry loops.
total attempts x (model cost + tool cost)
Combines per-attempt model and connected-tool spend.
runs x review share x review time x hourly cost
Converts review minutes into a monthly labor estimate.
variable + platform + review + maintenance
Keeps direct usage and human operating costs in one total.
fully loaded monthly cost / accepted outcomes
Divides cost by useful results, not attempted runs.
Pull model and tool cost from billing exports. Measure acceptance, review time, retries, and maintenance from run logs over a representative period.
Cost per accepted outcome is an operating metric, not a promise of ROI. Compare it with the value and risk of the completed task before deciding to scale.
The estimate excludes taxes, implementation cost, revenue lift, incident impact, and workflow-specific risk. Add those separately when they affect the decision.
Frequently asked questions
A run can finish and still be unusable. The acceptance rate forces rejected outputs and quality failures into the unit cost instead of hiding them behind activity.
That depends on consequence, reversibility, and process maturity. Enter the share of runs you actually review, then use the workflow readiness checker to set an appropriate approval level.
No. The calculation runs in your browser and does not send these inputs to an AI model.