“We’re a few weeks behind schedule.”

That sentence has been said in every software project that ever failed. It sounds manageable. It sounds like something that will self-correct. It almost never does.

The problem with delay is that its cost is invisible. You can see the team’s salaries leaving the bank account every month. You cannot see the revenue that isn’t arriving, the market window that’s closing, or the competing product that’s gaining ground while you’re stuck.

The three costs of delay

Direct burn. Your team costs money whether they’re shipping or spinning. If a team costs €80,000 per month and the project is three months late, that’s €240,000 spent on a project that hasn’t delivered value yet. This is the number most people track — and it’s the smallest of the three.

Lost revenue. If the project would generate €50,000 per month once shipped, every month of delay is €50,000 you’re not earning. Over twelve weeks, that’s €150,000 in revenue that simply didn’t happen. Unlike team costs, this number doesn’t appear on any budget report. It’s the gap between where you are and where you’d be.

Opportunity cost. While your team is stuck on this project, they’re not building the next thing. The feature that would retain customers. The integration that would open a new market. The technical debt cleanup that would make everything else faster. Opportunity cost is the hardest to quantify and often the largest.

Why delay compounds

A project that’s two weeks late is an inconvenience. A project that’s three months late is a strategic problem. The difference isn’t just arithmetic.

Late projects get more late. When a team misses a deadline, morale drops. When morale drops, productivity drops. When productivity drops, the next deadline is missed. This is the delay spiral.

Scope creeps into the gap. While the team is delayed, stakeholders keep adding requirements. “Since we’re already late, can we also add…?” Every addition makes the delay longer, which creates more time for more additions.

Context evaporates. The decisions made at the start of the project made sense in that context. Three months later, the market has shifted, the strategy may have changed, and the team has forgotten why certain decisions were made. The longer the delay, the more rework is needed.

What to do about it

Put a number on it. Use our delay cost calculator to convert weeks of delay into euros. Share that number with leadership. “We’re late” is ignorable. “This delay has cost us €380,000 so far and costs €30,000 per additional week” is not.

Separate sunk cost from future cost. The money already spent is gone regardless. The only question that matters: is the future cost to finish less than the future value delivered? If yes, finish. If no, stop.

Cut scope, not corners. The fastest way to ship is to ship less. Identify the minimum version that delivers real value and cut everything else. The features you cut can come back later — once you have something live.

Set a decision deadline. If you’ve been “a few weeks late” for more than a month, the delay is not going to self-correct. Set a date. On that date, either the project ships as-is, the scope gets cut to what’s ready, or the project gets stopped. No more drift.