All terms

CRO Glossary

Experiment Cost of Delay

The estimated value lost each day a validated or promising experiment isn't shipped or started.

Experiment cost of delay is a way of quantifying the opportunity cost of inaction — either the revenue or conversions forfeited by not shipping a winning variant sooner, or the learning forfeited by not launching a queued test sooner. It reframes experimentation backlogs and approval bottlenecks in economic terms rather than just prioritization scores, making it easier to argue for engineering resources or faster sign-off.

Teams use this concept when a test has already shown a statistically significant lift but implementation is stuck behind a sprint queue, legal review, or competing priorities. By estimating daily lift in revenue or conversions and multiplying by the delay in days, stakeholders get a tangible number — "this delay is costing us $8,000 a week" — that cuts through debate about relative priorities.

For instance, a checkout page test shows a 5% lift in completed purchases worth roughly $3,000/day in incremental revenue. If the fix sits in an engineering backlog for three weeks before full rollout, the team can point to roughly $63,000 in foregone revenue, which often reshuffles priorities instantly.

Cost of delay is also applied prospectively to the test backlog itself: tests that address high-traffic, high-friction pages are estimated to have a higher potential cost of delay if left untested, which helps teams decide what to test next, not just what to ship next.

Related terms

See this in the wild

ABWatcher watches how top teams apply experiment cost of delay.

Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.