TestingBudget

Build

Build effort

The total person-hours to stand the suite up: set-up, training, scoping, authoring every case, and validating it.

Unit
hours, one-time
Where you enter it
Computed; shown on the Build tab.

What it means

The sum of every one-time human activity in the Build phase: set-up and configuration, training multiplied by people, scoping, the case counts multiplied by their tier build times, and validation of each built case. It is an output — you never type it — and it is per vendor.

Divided by the FTE capacity in Settings it also gives the build duration in weeks, which is checked against the release cadence to flag a plan that cannot land in time.

Why it matters to the cost

Build effort is the year-one spike on every chart and the reason a tool with higher licence fees can still win over five years: a lower build effort is paid back every year by not having been spent. It is also the figure to sanity-check against your team: 1,200 hours is seven months of one person.

Typical values

For a 300-case suite: roughly 100–150 hours for AI-native tools, 300–700 for codeless enterprise and script-based tools, over 1,200 for a homegrown framework.

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

Build — one-off

Total test cases
basic + average + complex Test case complexity tiers
Build effort
Set up, install and configure + Scoping the suite + Training time per person × People trained
+ Σ Test case complexity tiers × Build time per test case for each tier, as Scratch vs migration
+ Total test cases × Validate a built case
Build cost
Build effort × Effective hourly rate + Build tokens priced as Token cost

Build duration is a workspace-level question

FTE capacity
FTEs in budget × productive hours per FTE per year ÷ 52
Build duration
Σ Build effort across all applications ÷ FTE capacity

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

Try it with your numbers

Build effort 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 build effort impacts the calculation of test automation costs

Related terms

  • Build cost Build effort at the effective hourly rate, plus build tokens — the one-time cost of standing the suite up, landing in year one.
  • Build duration How many weeks the build takes with the budgeted team: build effort across every application divided by weekly FTE capacity.
  • Build time per test case How long it takes one person to author, debug and get one test case passing in a given tool — the single biggest lever on build cost.
  • FTE capacity The hours a week the budgeted team can give: FTEs in budget times productive hours, divided by 52.

Last reviewed 2026-09-15. All terms.