Sunk Cost Fallacy in Business Decisions: How to Escape It

The sunk cost fallacy happens when you keep investing in something because of what you have already spent, rather than because continuing makes sense going forward. In business, this means pouring more money, time, or people into a failing product, campaign, or vendor relationship simply because walking away feels like admitting defeat. The fix is a mental reframe: treat past spending as gone and evaluate your options purely on future costs and future returns.

What the sunk cost fallacy actually is

A sunk cost is any investment you have already made that you cannot recover. Cash spent, hours logged, prototypes built. Once that money or time is gone, it is gone regardless of what you decide next.

The fallacy is treating those past costs as a reason to continue. "We have already spent $80,000 on this platform, we cannot just stop now." That sentence sounds reasonable, but it is not. The $80,000 leaves your account whether you continue or not. It has no bearing on whether continuing is the right move.

Humans are roughly twice as sensitive to losses as to equivalent gains, according to foundational behavioral economics research. Abandoning a project feels like confirming a loss. So you keep going to avoid that feeling.

The sunk cost fallacy is one of several cognitive biases that warp business decisions. What makes it particularly expensive is that it compounds. You do not just lose what you already spent. You also burn future resources defending that original decision.

Why smart people fall for it

Here is the uncomfortable part: the fallacy hits hardest when you are experienced, visible, and accountable.

If you publicly championed a new CRM system, signed the contract, and told your team it would transform operations, every dollar you consider cutting feels personal. Stopping is not just a financial decision. It is a public acknowledgment that you were wrong. That is a much higher psychological hurdle than any spreadsheet captures.

Three patterns drive the fallacy in business settings:

• Identity lock-in. You have told clients, employees, or investors about this initiative. The project has become part of how you describe your strategy.
• Completion bias. Humans have a strong pull toward finishing things. A project that is "70% done" feels like it deserves to cross the finish line, even if the finish line leads somewhere you no longer want to go.
• Escalation of commitment. Each new investment makes the previous one feel more justified. You spend $20,000, then another $15,000 to "protect" the first $20,000, then $30,000 more. Each decision seems locally rational while the total becomes absurd.

A worked example: the custom software trap

Let's make this concrete with a scenario that plays out constantly in small and mid-size businesses.

A marketing agency with 18 staff commissions a custom project management tool from a freelance developer. Budget: $45,000. Timeline: four months.

At month five, the tool is functional but riddled with bugs. The developer asks for an additional $22,000 to stabilize it and add the remaining features. The founder is frustrated but agrees. "We have put $45,000 in, we cannot just abandon it."

At month eight, the tool still crashes weekly. Client-facing workflows are breaking. The team has spent roughly 200 hours working around bugs and training new staff, which translates to around $18,000 in lost productivity at average billing rates. A third request comes in: another $18,000 to finish the remaining 20% of features.

Total spent: $85,000. Additional amount requested: $18,000, with no firm guarantee of stability.

A competitor SaaS product does 90% of what the custom tool was supposed to do. Annual cost: $12,000. Migration time: estimated two weeks.

Here is the forward-looking comparison:

The only number that matters for this decision is what happens from today forward. The $85,000 is gone. Every conversation that starts with "but we have already spent..." is the fallacy doing its work.

The right decision is obvious once you strip out the past spending. The agency switched, recovered within a month, and saved roughly $50,000 over the following two years compared to the custom build path.

The reframing technique: the "new CEO" test

The most practical way to escape the sunk cost fallacy is to separate the decision from the decision-maker's history with the project.

Ask yourself: "If a new CEO joined today with no knowledge of what we have already spent, what would she decide?"

This removes identity lock-in. It turns a personal question ("should I abandon something I championed?") into a structural one ("given our options from here, what makes the most sense?"). It also helps when presenting the choice to stakeholders who are emotionally attached.

A variation that works well in team settings: before reviewing any proposals, ask everyone to write down what they would do if they were starting from scratch with the same resources available today. Compare those independent answers before the group discussion starts. This reduces anchoring to past decisions and surfaces genuine disagreement early. It pairs well with keeping a decision log so you can track what conditions drove the original commitment and see whether those conditions still hold.

How to escape the sunk cost fallacy: a 5-step process

When past spending is pulling you forward on a decision, work through these steps.

1. List only forward-looking costs and returns. Write down every dollar and hour required to continue, and every realistic return. Do not include anything already spent. If you find yourself writing "we have already invested..." stop and delete that line.

2. Run the same analysis for your best alternative. What does stopping or pivoting actually cost from today? Include transition time, retraining, and lost momentum. A cost-benefit analysis structured around future cash flows, not total historical spend, is the right tool here.

3. Apply the new CEO test. Write one paragraph describing the situation as if explaining it to someone who joined the organization today with no knowledge of past decisions. If that framing changes how compelling "continue" looks, that is the fallacy at work.

4. Set explicit kill criteria before you commit more resources. Define in writing what has to be true in 60 or 90 days for you to continue further. Make these criteria specific: "monthly active users above 150," "error rate below 2%," "gross margin positive." Vague criteria like "meaningful progress" always get reinterpreted to justify continuation.

5. Separate the review from the people who made the original call. If possible, have someone not involved in the original investment evaluate whether continuing makes sense. They have no ego in the outcome. If that is not practical, at minimum read your analysis aloud and ask a trusted colleague to challenge it.

The common mistake: confusing sunk cost with strategic commitment

Not every decision to continue is irrational. This is where people overcorrect.

If you are two years into building a brand in a new market, switching direction every time results disappoint will destroy the effort. Markets take time. Distribution relationships take time. The discipline to stay the course despite early losses is sometimes exactly right.

The difference is whether you have identified a specific, time-bound condition that will tell you your theory is wrong, or whether you are simply committed to defending past spending because stopping is uncomfortable.

A useful rule of thumb: strategic commitment has a testable hypothesis attached. Sunk cost thinking does not.

"We are going to invest in this channel for 18 months because organic search compounds and needs that runway to prove itself, and we will know by month 18 whether our traffic-to-trial conversion rate justifies the spend" is strategic commitment.

"We cannot cut this now because we have spent so much building it" is the fallacy.

Reversible vs irreversible decisions are worth thinking about here too. If walking away closes a door permanently, a lease, a key hire, a regulatory window, that genuinely changes the calculation. But most business decisions are more reversible than they feel in the moment.

Key takeaways

• A sunk cost is unrecoverable regardless of your next decision. It is not a reason to continue.
• The fallacy is strongest when you have publicly committed to a course of action and stopping feels like admitting personal failure.
• Use the "new CEO" test: reframe the decision as if someone with no knowledge of past spending was making it from scratch today.
• Before committing more resources to a struggling initiative, write down only future costs and future returns. Strip out all history.
• Distinguish sunk cost thinking from genuine strategic patience: the difference is whether you have a specific, testable hypothesis for why more time or money will change the outcome.
• Set explicit kill criteria in writing before you continue. If you cannot define what failure looks like, you have already lost the ability to make a clean call.