Velocity Calculator

Tests designed per month * ? Experiments entering the design stage each month. This can be higher or lower than approved demand.

Experiments entering the design stage.

Tests approved per month * ? Approved experiments ready to be considered for implementation in the same monthly measurement period.

Approved demand ready for implementation.

Tests implemented per month * ? Approved experiments that actually reach implementation. This drives the observed implementation gap.

Tests actually reaching implementation.

Current monthly build & QA capacity (hours) * ? Total project-level build and QA hours available each month. Do not enter individual role capacity or billing hours.

Total project-level capacity available each month.

Average hours required per test * ? Estimated combined build and QA effort for one implemented test. Use a realistic average rather than the easiest test.

Combined build and QA effort for one test.

Additional monthly capacity (hours) ? The extra project-level capacity being considered. The model limits its benefit to approved tests not already implemented.

The extra capacity being considered.

Experiment win rate (%) ? Expected percentage of implemented experiments that produce a positive result. This is an assumption, not a guaranteed outcome.

Expected proportion of tests producing a positive result.

Revenue per winning test per year ? Estimated incremental annual revenue attributed to one successful test. The result is a modeled opportunity, not guaranteed revenue.

Incremental annual revenue attributed to a winning test.

Currency ? Currency used to display the modeled annual revenue opportunity. GBP (£) USD ($) EUR (€)

Used only when both revenue assumptions are supplied.