The Sunk Cost of Falling in Love With Your Own Idea

After months of development, investor conversations and team discussions, the founder has invested not only money and time, but also reputation and identity. Questioning the product can begin to feel like questioning the person who created it.

This is where business decisions become psychological ones. Instead of evaluating whether a product still deserves investment, founders may find themselves trying to justify the resources already committed.

The result is a familiar trap: continuing with an idea because abandoning it feels more painful than admitting it may not work.

When Your Idea Becomes Your Identity

Passion is essential to entrepreneurship. Building a company requires persistence through uncertainty, limited resources and periods when progress is difficult to see.

But conviction can become a liability when founders stop evaluating evidence objectively.

A customer who loves the product becomes proof of its potential, while a customer who rejects it is dismissed as an exception. A disappointing experiment is blamed on the testing method, and a competitor entering the market is interpreted as validation, even when it may reveal how difficult the opportunity is.

Each explanation might be reasonable on its own. The problem emerges when every result is interpreted to protect the original belief.

Founders need to distinguish between the mission they want to accomplish and the solution they have chosen to pursue. A meaningful problem may remain worth solving even when the current product, target customer or business model proves unsuitable.

Changing the approach does not necessarily mean abandoning the ambition.

The Sunk-Cost Trap Starts Before Development

Sunk cost is commonly understood as the tendency to continue an investment because resources have already been spent. For founders, however, the emotional commitment often begins before significant money changes hands.

It starts when they spend weeks refining an idea and imagining its future. It grows through hiring, product development, investor presentations, public announcements and promises to customers.

By the time meaningful feedback arrives, the decision is no longer simply whether the idea deserves more resources. It is also whether the founder can accept changing a plan they have worked hard to establish.

Past investment, however, cannot guarantee future returns. Money already spent cannot be recovered by spending more, and a roadmap does not become strategically sound simply because a team has worked hard to deliver it.

The relevant question is not how to make the original investment worthwhile. It is whether continuing offers a better use of resources than the available alternatives.

This does not mean every setback should trigger a pivot. Early customer feedback can be incomplete, and promising products may need improvements before their value becomes clear. The distinction lies in whether founders are responding to evidence or searching for reasons to disregard it.

Persistence Needs Room for Change

Persistent and stubborn founders can look similar from the outside. Both work through difficulties, tolerate criticism and remain committed when progress slows.

The difference is whether new information can change their decisions.

Persistence means staying committed to an important objective despite obstacles. Stubbornness means remaining attached to a particular approach even when the reasons for choosing it have weakened.

A founder can continue addressing the same customer problem while redesigning the product. They can pursue the same market while changing the pricing model or distribution strategy. The objective remains, but the method evolves.

This requires separating two questions: Do I still believe in what I am trying to accomplish? And Is this still the right way to accomplish it?

They do not always have the same answer.

Set the Criteria Before You See the Results

One practical way to reduce the influence of ego is to define success criteria before an experiment begins.

Before building a feature, decide what outcome would justify further investment. Before testing a product with customers, identify which behaviours would indicate genuine demand. Before launching, determine which assumptions the launch is intended to test.

Consider a founder developing a workflow tool for a specific customer segment. Positive feedback during a demonstration may suggest interest, but stronger evidence could include qualified customers agreeing to a structured pilot, providing the necessary operational data and committing to a paid implementation if agreed outcomes are achieved.

If customers express enthusiasm but repeatedly avoid taking the next step, that gap deserves investigation. The problem may not be urgent enough, the offer may not fit the buyer’s needs, or the timing may be wrong.

These results do not automatically mean the product should be abandoned. They do, however, provide a reason to reassess the assumptions behind it.

Predefined criteria help founders avoid quietly changing their definition of success whenever the evidence becomes uncomfortable.

Give Yourself Permission to Stop Before You Start

Before committing significant resources, founders should ask a difficult question: What evidence would make this idea not worth building?

Answering it early helps identify the assumptions that matter most, the customer behaviours that would support them and the alternatives available if the results are disappointing.

This is not pessimism. It is capital allocation. Every engineering hour spent on one idea is an hour unavailable for another opportunity, while every additional feature creates development and maintenance costs.

A deliberate validation period can help founders test critical assumptions while changing direction is still relatively inexpensive. The 72-hour build bet is one practical expression of this approach: clarify the demand question before turning an idea into a major engineering commitment.

Not every uncertainty can be resolved in three days. The purpose is to discover what can be tested early and avoid treating a promising concept as proof of a viable business.

Ultimately, founders do not need to eliminate their attachment to their ideas. They need to recognise when that attachment begins to distort their judgment.

The mission deserves commitment. The plan deserves scrutiny.

A founder’s responsibility is not to prove that the first idea was right, but to make the best decision possible with the information available—and revise it when that information changes.

Sometimes the most important question is not whether you know how to keep going, but whether you are willing to let go of an approach that no longer serves the opportunity.

Before investing further, ask yourself: If I were starting from zero today, knowing what I know now, would I make the same decision?