What does another attempt cost?

Retries, evaluator calls and repairs can each look inexpensive while their combined cost grows. Trace one task from first request to accepted result.

How to use the review

Record the usual token and tool costs, the cost of a repair cycle and how many cycles can occur. Set one budget for the whole task. Decide what happens when the next attempt would exceed it.

Your numbers stay in your browser. They are not sent or stored, and the check needs no sign-up. The workbook download asks for your name, role and email address first.

Typical cost per task — tokens — Unit economics: what one task costs on a normal day, counting the rounds that get sent back.
Worst case at peak — of your quota — Availability: the share of your tokens-per-minute quota this workflow would ask for if every loop ran to its cap during your busiest minute.
A The workflow

Four numbers about a normal task

B Paths that send work back

Cost one round of each

Whatever sent the work back, a round costs the same three things: the steps that run again, the check that re-reads the new attempt, and the extra context the redo carries. Add only the paths your workflow actually has. Zero is a real answer; blank is not.

Add a path only if it makes the model do work a second time. That is what this tool counts. A send-back that spends no further tokens — a person editing the output themselves, say — belongs in your process notes, not here.

C Budget

One budget for the whole task

No price entered yet, so this stays in tokens. The scheduling example leaves the price blank on purpose: it is the one figure nobody else can supply, because it depends on your provider, your tier and your own mix of input and output tokens. Put your number in Your price per million tokens above and the cost per task appears here. At that rate, a typical task costs —, and a thousand of them cost —. That is the everyday figure, not the worst case.

For scale: the same task at frontier rates

Your typical cost per task, priced at what three frontier models charge. It is a range because input and output are priced differently: the low figure is all input, the high figure is all output, and real work sits between them, usually nearer the low end. Checked 28 September 2026.

Model Input
per 1M
Output
per 1M
Your typical task Worth knowing
Claude Opus 5.5 Anthropic 4.00 20.00 — US-only inference costs 1.1×. Fast mode costs 2×.
GPT-6 Astra OpenAI 10.00 50.00 — Long context costs $20 in and $75 out, so a growing redo can double this.
Gemini 3.1 Pro Google 2.00 12.00 — Prompts over 200k cost $4 in and $18 out.

Figures are US dollars, which is how all three publish. Rates change, and two of these carry a condition that doubles them, so check the provider before you quote one: Anthropic · OpenAI · Google .

Pass, attention or fail

Each check reads your figures and says where you stand, then what to do about it. Work down the list; the one to fix first is called out at the bottom.

Pass
Nothing to do here.
Attention
It works today, and something about it will surprise you. Worth fixing.
Fail
This is the one that stops you scaling. Fix it first.
Not answered
The check needs a figure you have not entered yet.
  1. Not answered

    1. Every path that sends work back is listed

    A path you have not listed is spend you cannot see. Most teams count their retries and miss the judge entirely, because a judge rejection looks like normal operation rather than a failure.

    No path is marked as present yet.

  2. Not answered

    2. Each round is costed as repeated, review and growth

    A round is three things and teams usually count only the first. The review call and the growing context are what make a judge loop expensive, and neither appears in a retry counter.

    No path is marked as present yet.

  3. Not answered

    3. Every loop has a limit, a decided outcome, and an owner

    A loop with no cap has no worst case. This is the check that turns "it depends" into a number, and an uncapped path is the single most common finding here.

    No path is marked as present yet.

  4. Not answered

    4. Both numbers fit: what you pay daily, and your busiest minute

    One number is not enough, because the two ways this hurts you are different. The typical cost is what you pay every day, and it decides whether the product makes money. The worst case at peak decides whether one bad minute takes the whole system down. A workflow can be fine on one and fatal on the other.

    Peak tasks per minute and the quota are needed for this one.

  5. Not answered

    5. One token budget for the whole task, not one per call

    A task that goes round three times spends three times. A budget checked on each call sees the attempts one at a time and never sees the total, so it cannot stop a task that is running away. To do that, every round has to count against one limit that belongs to the task.

    Choose how your budget is enforced.

Worked example

A scheduling agent drafts a reply three times while a judge requests more detail. Count all three drafts and all three checks before comparing this path with a human handover.

What to take away

Use the estimate to choose a stopping rule. Confirm the inputs against a trace before treating the result as an operating budget.

Explore a pilot readiness assessment

Published 28 September 2026 · Content CC BY 4.0 · Code MIT · © The Living Craft

File Download

Get the file

The Excel workbook is the same check, with the worked example on its own sheet and every figure explained. It is built against a name, a role and an email address.

This file is the same for everyone. Nothing you typed goes into it.

Privacy · Change my email preferences