Calculator

Cost of Delay Calculator

Puts a monthly price on a decision that has been pushed to next quarter, so the cost of the queue can be argued about alongside the cost of acting.

Enter the monthly value at stake and the number of months the decision has been, or will be, parked. The formula is fixed and runs entirely in your browser: identical inputs always return identical results, and nothing you type is stored anywhere.

Last reviewed 3 July 2026 · Free and ungated

Pressure-test this decision

Selected senior operators from the Global Board can tell you whether the deferral is buying evidence or just time, before another quarter of run-rate is spent.

Pressure-test this decision

How a client brief works · What you receive

Fixed formula · no AI · nothing stored

Run the numbers

Cost of delay = monthly value at stake × months delayed. How our tools work

What the formula does

Every month a decision sits in the queue, the organisation either forfeits a benefit it could be earning or keeps paying a cost it could have removed. The monthly value at stake is that run-rate: the saving not banked, the revenue not captured, the process still bleeding money. The calculator multiplies it by the months of deferral. The point is not precision. The point is that "let us pick this up next quarter" gets said in every steering committee, and it is almost never accompanied by its price.

Running the numbers

A distribution business knows its manual dispatch process is costing roughly €45,000 a month in overtime, errors and missed delivery windows. The decision to replace it slips past two quarterly meetings, six months in total. The price of that slippage is €45,000 × 6 = €270,000, more than the €220,000 the replacement system was quoted at. The project was never rejected; it simply queued, and the queue cost more than the decision.

What the total leaves out

The output looks solid because it is a multiplication, but its quality is set entirely by the weaker of its two inputs.

  • The monthly value is almost always the softest number in the room, and it is usually produced by whoever wants the decision made. Interrogate how it was built before quoting the total.
  • Delay is linear in the formula but rarely linear in life. Some costs accelerate when a competitor signs your target customer or the engineer who understands the legacy system resigns, and the calculator cannot bend the line.
  • Waiting sometimes buys information worth more than the waiting costs. A three-month pilot that materially changes which option you would choose is a purchase, not a delay. The test is whether the pause is producing evidence that alters the decision, or merely postponing it.
  • A decision that keeps slipping is often a symptom of unresolved disagreement. The multiplication prices the symptom, not the cause.

Where the calculator stops

This is one multiplication with no discounting, no ramp and no probability weighting. It cannot distinguish productive waiting from drift, and it will faithfully amplify an inflated monthly estimate into an inflated total. Use it to force the deferral onto the agenda as a cost, then argue about the inputs in the open.

Frequently asked questions

How should I estimate the monthly value at stake?

Build it from observable run-rate items rather than from a share of a business-case total: current overtime, error rework, spend that the decision would remove, revenue the capability would capture. If the figure only exists inside the business case for the project, treat it as an advocate's number and stress it downwards before relying on it.

When is delaying the decision actually the better move?

When the pause has a defined output that changes the choice: a pilot result, a customer commitment, a regulatory ruling. Compare the delay cost from this calculator with what that information is worth. If waiting has no defined output and no end date, it is drift with a price attached.

How does this differ from the opportunity cost calculator?

The opportunity cost calculator weights an annual opportunity value by a success probability and scales by the fraction of a year lost. This one is blunter: it takes a known monthly run-rate and multiplies by months. Use this version when the monthly cost of the status quo is observable, and the probability-weighted version when the value is still speculative.

The queue has a price. Decide whether to keep paying it.

Pressure-test this decision