TestingBudget

Run

Run cost per year

Run effort per year at the effective hourly rate, plus any tokens consumed during execution.

Unit
money per year
Where you enter it
Computed; shown on the Run and Total Cost tabs.

What it means

Effort per year converted to money at the effective hourly rate, plus the yearly token cost of AI-driven execution and triage where the tool uses a model. It recurs every year of the analysis horizon.

It is one of the four recurring lines that make up the annual ongoing cost.

Why it matters to the cost

Across a five-year horizon the run line is usually the largest single cost for manual testing and a major one for automation; it is the line that release cadence multiplies. Doubling runs per year doubles it exactly.

Typical values

For a 300-case suite on a monthly cadence: roughly $5,000–$10,000 a year for a tool; $80,000 or more for manual execution.

Typical values describe a category of tool — AI-native, codeless, script-based, homegrown, manual — never a named product. Why we do not price named products.

Where it appears in the model

Run — every release

tests broken per run
Total test cases × Test breakage rate ÷ Runs per year — found here, repaired under Maintain
Failures per run
Defects found per run + tests broken per run + flaky per run — derived, never asked
Machine time per run
Total test cases × Execution time per case — automation only; duration, not labour
Run cost per year
Run effort per run × Runs per year × Effective hourly rate + Token cost

Totals, per application

Analysis horizon
Build cost + Annual ongoing cost × years in the horizon — the total over the horizon

Every name is a link to its definition. See the whole model.

Try it with your numbers

Run cost per year is a row in the calculator. Change it and every total on the page moves with it — free, in your browser, nothing to install.

See how run cost per year impacts the calculation of test automation costs

Last reviewed 2026-09-15. All terms.