Planet RoadmapCost of Delay Calculator
What is it costing you to not ship that feature? Quantify the dollar cost of every delay and rank features by CD3 — Cost of Delay divided by Job Size.
The formula
(value normalized to monthly)
CD3 = Cost of Delay per month ÷ Job Size
The total Cost of Delay is the value you forgo over the delay window. CD3 is the rate-adjusted ranking score — use it to decide which feature to ship next when capacity is fixed.
How to estimate value
- Revenue impactNew revenue, retained revenue, or upsell that this feature unlocks per period.
- Churn reductionCustomers retained × ARPU. Even small churn improvements compound to large numbers fast.
- Time savedUser hours × hourly rate. Works for internal tools and B2B features that automate manual work.
- OptionalityStrategic value: features that unlock new markets, integrations, or platforms. Estimate as the expected value of the future opportunity.
Frequently asked questions
What is cost of delay?
Cost of delay is the value you forgo by not having a feature in production. If a feature would generate $20,000 a month in revenue and you delay it three months, the cost of delay is $60,000 — money you simply do not collect. Treating delay as a cost rather than a free option changes which features rise to the top of the queue.
Why does cost of delay change prioritization?
Most teams prioritize on value and effort but ignore time. Cost of delay forces time into the model. Two features with the same value can have wildly different cost of delay if one becomes obsolete in 60 days while the other generates value forever. The urgent one should obviously go first, and cost of delay shows that explicitly in dollars.
How do I estimate value when I do not have hard numbers?
Use ranges and confidence multipliers rather than refusing to estimate. A rough number with 70% confidence beats no number every time. Common signals: revenue impact, churn reduction, support cost saved, hours of user time recovered. For internal tools, convert time saved to dollars at a fully-loaded hourly rate. For strategic features, estimate the value of the optionality they unlock.
What is the difference between Cost of Delay, CD3, and WSJF?
Cost of Delay is the raw dollar amount of value lost per unit time. CD3 — Cost of Delay Divided by Duration — is the rate-adjusted ranking score: Cost of Delay per month ÷ Job Size in months. WSJF is a Fibonacci-scaled relative version of CD3 used in SAFe. CD3 keeps absolute dollars; WSJF abstracts to story-point-style numbers. Pick CD3 when stakeholders want money on the table; WSJF when teams want fast relative scoring.
How do probability and time horizon interact?
Probability discounts the value to account for uncertainty — a $100,000 outcome with 50% confidence is treated as $50,000 expected value. Time horizon (months delayed) multiplies that monthly value by how long the delay actually is. Both matter: a high-confidence short-window feature can outscore a low-confidence long-window feature even if the headline value is similar.
When should I use cost of delay versus RICE?
Use cost of delay when stakeholders speak in dollars and you need to defend prioritization to finance, executives, or a board. Use RICE when you are scoring smaller features against each other and Reach is easier to estimate than dollar value. Many teams use cost of delay for the top of the funnel — large bets — and RICE for the team-level backlog underneath.
Defend every roadmap decision in dollars
Planet Roadmap lets every initiative carry its own cost-of-delay estimate alongside customer evidence and team capacity — so prioritization conversations stay grounded in numbers stakeholders trust.
Try Planet Roadmap Free