Deep-dive guide
Project Delay Opportunity Cost Simulator: What Every Month of Waiting Really Costs
Executive industry analysis
When a project slips, the usual report counts the extra weeks and perhaps the extra salary. Neither number captures the real loss, which is the value the project would have earned in those weeks and never will. A product that creates forty thousand a month does not simply start later; the months before launch are gone for good. That is an opportunity cost, and because it never appears in a ledger it is easy to underestimate. Teams then trade a month of delay against a small improvement in polish, without noticing that the month is worth far more than the polish.
The structure of the problem is a window of fixed length. If the project is judged over a fixed period from the original launch date, every month of delay removes one month of live operation from the end of that window. Meanwhile the team keeps costing money, and the market does not wait. Competitors who launch first take customers, and the value of what you finally release shrinks by the share they have taken. Delay therefore acts three times: it removes live months, it adds holding cost and it shrinks the value of the months that remain.
The domino cascade shows how they connect. A longer delay raises the share of on-time value that is never earned. That loss comes with a growing holding cost for the team and for rework. The combined cost of waiting then takes longer to recover once the product is live, which pushes the payback period out. A long payback leaves the project exposed to any further slip, and the average monthly result turns negative. Each stage feeds the next, so a delay that looks tolerable in the first box can turn the last box red.
The iceberg separates the costs that appear in a project plan from those that do not. Above the waterline are the team paid while waiting and the running cost after launch, which finance can see. Below it are three costs that rarely get a line: the value of months with nothing live, the market share taken by competitors and the rework needed to restart. In many delayed projects the missed months and the erosion exceed the visible team cost several times over. Use the simulator to find the delay at which the project stops paying, then decide how much scope to give up to avoid it.
Formula and methodology blueprint
The model looks at the 24 months starting at the originally planned launch date and reports the average month. After a delay of d months the product is live for 24 minus d months. Value starts at your monthly figure but declines by the erosion rate every month from the original date, so late launches earn less per month. Running cost applies only while live. The team is paid for every month of delay, and rework scales up to its full size at three months of delay.
- Live months
- L = 24 − delay
- Months inside the window in which the product is actually earning.
- Value earned
- V = value × (1 − e)^delay × [1 − (1 − e)^L] / e
- Monthly value summed over the live months, with competitor erosion e applied from the original launch date.
- Cost of waiting
- W = team cost × delay + rework × min(1, delay / 3)
- Team paid while waiting plus rework needed to restart.
- Project result
- Net = (V − run cost × L − W) / 24
- Average monthly result across the window. The break-even delay is where this reaches zero.
- Payback
- months = W / (value × (1 − e)^delay − run cost)
- How many live months it takes to recover the cost of waiting.
Cascading elasticity
Delay and monthly value are the most elastic inputs: each month of delay removes a full month of value and adds a month of team cost at the same time. Erosion compounds with delay, so the same competitor pressure hurts more when the launch is late. Running cost and rework are linear and act as thresholds.
Three real-world case studies
Bootstrapped starter
A small product two months late
A small team has a product worth nine thousand a month and slips two months. The team is small, rework is modest and competitors are slow. The project still pays easily. Load it to see that a short slip costs a visible amount but does not break a healthy project.
Scaling mid-market
A large programme four months late
A major programme worth a hundred and sixty thousand a month slips four months with a large team waiting. Absolute losses are big, yet the value is large enough that the project stays strongly positive. Load it to see how large value hides large delay costs.
Black-swan crisis
A project a year late with rivals ahead
A project worth twenty thousand a month slips twelve months while forty-five thousand a month of team cost keeps running and rivals take five percent of the market every month. Load it to see how delay, erosion and holding cost together turn a good idea into a loss.
Industry benchmark matrix
| Metric | Danger zone | Industry average | Top 10% elite |
|---|---|---|---|
| Delay against original plan | Above 6 months | 1–3 months | Within 1 month |
| Value lost against on-time plan | Above 25% | 8–15% | Below 8% |
| Payback of the cost of waiting after launch | Above 8 months | 2–4 months | Below 2 months |
| Market erosion per month from rivals | Above 4% | 1–2% | Below 1% |
| Running cost as share of monthly value | Above 60% | 25–35% | Below 20% |
Variables and levers
Monthly value once live
Revenue, savings or avoided loss the project creates each month at launch, before running costs.
Lever: Launch a smaller first version that earns part of this value sooner, rather than waiting for the full scope.
Running cost per month
Hosting, support, licences and staff needed to operate the project after launch.
Lever: Plan operating costs before launch; a project whose running cost eats the monthly value gains little from being on time.
Delay in months
How far the launch slips beyond the original date. The model looks at 24 months from that original date.
Lever: Cut scope, not quality, to recover months, since every month removed is worth the full monthly value plus the cost of waiting.
Team cost per month of waiting
Monthly cost of the people and tools kept on the project while it is not yet live.
Lever: Move people to other work during a long wait instead of paying them to idle on a stalled project.
Competitor erosion per month
Share of the market value you lose each month because rivals launch first or customers move elsewhere.
Lever: Ship a visible first release early to hold customers, because market share lost to rivals is much harder to win back than to keep.
Rework and relaunch cost
One-off cost of refreshing scope, retesting and re-planning the launch. It reaches its full size at three months of delay.
Lever: Keep the scope document alive and testable during the delay so the relaunch does not start from scratch.
How to use this simulator
- 1Enter the monthly value the project creates once live and its running cost.
- 2Set the expected delay and the monthly cost of the team while it waits.
- 3Add an honest competitor erosion rate and the rework needed to relaunch.
- 4Read the five dominoes and note the delay at which value lost or payback turns amber.
- 5Compare with the minimum launch plan in the Parallel universe tab and share the link.
Mistakes to avoid
- Counting only the extra salary. The value the project never earned is usually several times larger than the cost of the idle team.
- Assuming the market waits. Customers and rivals keep moving, so the same product is worth less when it finally appears.
- Treating each month of polish as free. A month of delay costs the full monthly value, so weigh it against a measurable gain.
- Ignoring running cost. A project that is late and expensive to operate may never pay back the cost of waiting.
Frequently asked questions
Why does the model use a 24-month window?
A fixed window makes the cost of delay visible: each month of delay removes one live month from the end. The longer the window, the lower the average impact of the same delay.
What is competitor erosion?
A monthly percentage by which the value of your market shrinks because rivals launch first. It is an assumption, so test several values and watch the effect compound with delay.
Should the team be cut during a delay?
Not always. Moving people to useful work reduces holding cost, but rebuilding momentum later is also costly. The model shows the saving so you can weigh it.
What does the minimum launch plan change?
It halves the delay and trims rework, at the price of more team cost for contractors and a lower value per month. The 24-month tab shows when it pays back.
Can a delay ever be worth it?
Yes, if the extra time raises quality enough to protect value or avoid a costly failure. The simulator shows the price of each month so the choice is deliberate.
How accurate is this?
It is an educational planning model with the assumptions shown, not financial advice. Replace the inputs with your own estimates and test low and high cases.
This is an educational planning model with stated assumptions. It is not financial, tax or legal advice. Replace the inputs with your own figures and verify important decisions with a qualified professional.