Cost Of Delay Calculator
Every slipped launch has a price, but in most planning meetings it is quoted in adjectives: urgent, critical, soon. Adjectives do not settle arguments about what to build first. A daily cost figure does.
Enter what one day of delay costs (lost revenue, churn, penalties, idle spend) and how many days the work slips. The calculator multiplies them into the total cost of delay, the number SAFe and lean product teams use to sequence a backlog.
A linear estimate: it assumes the daily cost stays flat across the delay. Real delay costs often step up at deadlines, contract dates and competitor launches, so treat the result as the floor of the argument, not the ceiling.
Quick Answer
Key takeaways
- The formula is one multiplication: daily cost x days delayed. All the skill is in estimating the daily cost honestly.
- Cost of delay is the numerator of WSJF: divide it by job size and the backlog sorts itself by economic urgency, not by who shouted loudest.
- Compare items with the same day convention. Mixing business days for one feature and calendar days for another quietly rigs the ranking.
- The estimate is linear and therefore conservative: step costs at deadlines and launch windows sit on top of it.
- Quick Answer
- How to estimate the daily cost (the part that actually matters)
- The formula and the WSJF step after it
- Worked example: three backlog items, one honest ranking
- When the linear number understates the damage
- What competing calculators miss
- Frequently Asked Questions
- Add This Calculator to Your Website
- References
How to estimate the daily cost (the part that actually matters)
The multiplication is trivial; the daily figure is the work. Build it from parts you can defend in the room, using the three components SAFe uses for cost of delay thinking: user and business value, time criticality, and risk reduction or opportunity value.
Forgone revenue or savings per day. Take the monthly value the finished work is expected to create or save and divide by 30. A feature projected at $37,500 a month carries a $1,250 daily rate before anything else is added, which is exactly the worked example below.
Time criticality. Add anything with a date attached: contract penalties per late day, a seasonal window closing, a compliance deadline, a marketing launch already booked. If the date has passed, this component is not a rate any more, it is a lump sum: add it separately and say so.
Risk and opportunity cost. Add the daily value of what the delay exposes: churn while a fix is missing, support load the automation would have removed, the competitor window left open. Keep it modest and documented; inflated risk lines destroy the credibility of the whole estimate.
Run the tool, then rank. Price every candidate item the same way, then divide each total rate by its job size for a WSJF order. The worked comparison under the example shows the ranking flipping once size is counted.
Don Reinertsen, whose product development flow work SAFe built on, put the principle bluntly: if you only quantify one thing, quantify the cost of delay. The SAFe WSJF guidance turns that into the sequencing rule used below.
The formula and the WSJF step after it
Keep the two numbers separate in your notes. Cost of delay alone favors big valuable items; WSJF corrects for size, which is why a small item with a modest daily rate can rightly jump a flagship project. The mistake to avoid is using the TOTAL cost of delay for a long delay as the WSJF numerator against a short item’s daily rate: same units, same horizon, or the comparison is rigged.
Worked example: three backlog items, one honest ranking
The calculator is pre-filled with the first row: $1,250 a day for 20 days returns $25,000.00. Priced the same way, its two rivals look like this:
| Item | Daily cost | Delay priced | Cost of delay | Job size (days) | WSJF (per day / size) |
|---|---|---|---|---|---|
| Checkout fix (example) | $1,250 | 20 days | $25,000 | 10 | 125.0 |
| Billing migration | $600 | 20 days | $12,000 | 30 | 20.0 |
| Onboarding email flow | $300 | 20 days | $6,000 | 4 | 75.0 |
Ranked by cost of delay alone, the order is checkout, billing, onboarding. Ranked by WSJF, the four-day email flow jumps the thirty-day migration, because it buys back its delay cost six times faster per day of work. That flip is the entire point of pricing delay: it moves the argument from seniority to arithmetic. Closely related, but not the same, is unplanned stoppage: when work halts mid-flight rather than starting late, the cost of interruption calculator prices the standstill, and when output is simply lost, the cost of lost production calculator covers that ledger.
When the linear number understates the damage
This tool multiplies a flat daily rate, and three real patterns break flatness. Deadline steps: a regulatory or contractual date converts delay into a penalty event, not a slope. Market windows: a launch that misses a season or a competitor’s release date loses a step of value overnight, not a day of it. And compounding churn: customers lost in month one do not return when the feature ships, so the revenue line keeps paying for the delay long after delivery. Name these in the meeting, quantify the ones you can as separate lump sums, and keep the calculator’s output as the defensible core. The opposite failure also exists: teams that price delay for everything end up pricing it for nothing, because a backlog where every item is a five-figure emergency has no sequence at all. Reserve real estimates for the contested items. Doing nothing about a delay is itself a priced option, as the cost of doing nothing calculator shows from the inaction side.
What competing calculators miss
Most pages ranking for this keyword are essays about WSJF with, at best, a relative scoring worksheet in Fibonacci numbers. The dollar tool is usually missing.
Miss 1: scores instead of money. Relative 1-to-10 value and time-criticality scores cannot be compared across teams, quarters or budget lines. A daily dollar rate can: it survives contact with finance, procurement and the steering meeting.
Miss 2: no method for the daily rate. Tools and templates that do accept dollars rarely explain where the number should come from, so users type a guess and distrust the output. The three-part build above (value, criticality, risk) is the method, and it is what makes the result arguable in the good sense.
Miss 3: no honesty about linearity. Delay cost is presented as exact when every practitioner knows about deadline steps and windows. This page states the assumption at the calculator itself and names the three patterns that break it, so the $25,000 reads as a floor with a method behind it, not a prophecy.
Frequently Asked Questions
Cost of delay is the money lost for each unit of time a piece of work is late: forgone revenue, added cost, churn and risk, expressed as a rate such as dollars per day. Multiply the rate by the length of the delay and you get the total economic damage of delivering at the later date instead of now.
Opportunity cost is the general value of the best alternative you gave up. Cost of delay is narrower and time-shaped: it prices what waiting itself destroys. A delayed feature’s cost of delay grows with every day of slippage, while its opportunity cost is about the other work the same team could have done instead.
Weighted Shortest Job First is the SAFe sequencing rule: WSJF equals cost of delay divided by job size or duration. Work the highest score first. In the example on this page, the onboarding flow (daily cost $300, size 4 days, WSJF 75) outranks the billing migration (daily cost $600, size 30 days, WSJF 20) despite costing less per day.
Either, consistently. Market-facing losses (revenue, churn, competitor moves) accrue on calendar days; internal carrying costs often accrue on business days. Pick the convention that matches your daily cost estimate and use it for every item you compare, because mixing conventions rigs the ranking.
Estimate it from parts: expected monthly value of the work divided by 30, plus any dated penalties averaged per day, plus a modest risk allowance for churn or support load. A documented rough figure beats a precise-sounding guess, and the estimate only has to be good enough to rank items against each other.
No. It is deliberately linear: daily rate times days. Deadline penalties, seasonal windows and compounding churn are step costs that sit on top of the linear estimate. Add any you can quantify as separate lump sums when you present the result.
Yes. The same arithmetic prices a delayed hire (vacancy cost per day times days unfilled), a delayed marketing launch, a late equipment installation, or a supplier delivery slip with a per-day penalty clause. Anywhere waiting has a daily price, the formula applies.
It converts a deadline from a preference into a priced fact. Showing that each week of slippage costs $8,750 at a $1,250 daily rate changes a resourcing conversation: stakeholders can still choose the delay, but they choose it knowing its price, which is usually all the tool is asked to do.
Add This Calculator to Your Website
References
- Scaled Agile, Inc., “Weighted Shortest Job First”: the SAFe definition of WSJF as relative cost of delay divided by relative job duration, and the source of the “quantify the cost of delay” principle. Scaled Agile Framework: WSJF. Accessed October 2026.
- Reinertsen, D.G., The Principles of Product Development Flow: Second Generation Lean Product Development, Celeritas Publishing, 2009: the origin of cost of delay as the central economic variable in product development queues. Celeritas Publishing: Principles of Product Development Flow. Accessed October 2026.
- Product School, “Cost of Delay: Why Time is Money in Product”: a practitioner walkthrough of the daily value times delay period formula used by this calculator. Product School: Cost of Delay. Accessed October 2026.
- Project Management Institute, “A Guide to the Project Management Body of Knowledge (PMBOK Guide)”: schedule management and cost baseline concepts behind delay and schedule variance analysis. PMI: PMBOK Guide. Accessed October 2026.
- Leffingwell, D., SAFe Distilled and the SAFe body of knowledge on economic decision-making: background on sequencing work for maximum economic benefit rather than by stakeholder seniority. Scaled Agile Framework. Accessed October 2026.