Cost per Completed Workflow Template
Replace token-price comparisons with a transparent unit that includes quality, retries, review, exceptions, infrastructure, and operating work.
Start with the actual decision
Cost per token is an input. The business unit is an acceptable completed workflow: one outcome that meets the quality threshold and includes the work needed to handle failures and exceptions.
Build a range, not a single magic number. Separate observed measurements from estimates, retain the source date, and show which assumption changes the result most.
Intended user
Finance, product, platform, operations, and AI leaders comparing models, providers, hosting patterns, or workflow designs.
Collect before comparing
- 01Definition of completion and measurable acceptance threshold
- 02Requests per workflow, input and output units, context repetition, cache behavior, retries, and routing
- 03Success, exception, escalation, and human-review rates measured on the intended workload
- 04Dated model, provider, compute, storage, network, and supporting-service prices
- 05Integration, evaluation, monitoring, support, incident, and change-management effort
- 06Demand range, concurrency, utilization, capacity headroom, and relevant latency or cycle-time cost
Test every material criterion against the workload
Comparable completion
Do all options meet the same quality threshold and finish the same business task?
A cheaper output is not cheaper if it creates more rework or fails the required outcome.
Full workflow path
Are retries, fallbacks, tool calls, human review, and exception handling included?
Ignoring the failure path understates both cost and operating effort.
Demand and utilization
Does the model show low, expected, and peak demand plus idle or reserved capacity?
Owned and consumption-priced systems respond differently to utilization and variability.
Repeated context
How much input repeats, and is any assumed cache saving actually supported for this pattern?
Caching can change economics, but only when the workload and provider behavior support it.
Operating cost
Who maintains integrations, evaluations, models, infrastructure, and incidents?
Internal labor and lifecycle work belong in the comparison even when they are not invoiced per request.
Compare options only after normalizing to the same acceptable completion. Prefer the option with the strongest economics across a plausible demand range, not merely at the expected point, and validate the assumptions that dominate the result before committing.
Do not use this template to promise savings, ROI, or payback. It is unreliable when quality is unmatched, demand is unknown, exception work is omitted, prices are stale, or internal operating cost is treated as free. Token cost can still be useful for diagnostics; it is simply not the final business unit.
Editorial version 1.0
Initial public template reviewed August 2026. Recalculate whenever prices, workload shape, quality thresholds, routing, cache behavior, or operating assumptions change.
StandardsExplore the economics assessment
See how a bounded assessment turns supplied workload and dated price inputs into a sensitivity model.
Continue