There’s a moment every founder hits where the excitement has worn off, the results aren’t clear, and you’re left staring at a question that has no easy answer: Do I keep going, or do I walk away?
I’ve been on both sides. With Vulpine Creations, Adam Wilber and I committed — and we built twelve premium magic products, earned a 4.9-star rating, and eventually exited in 2024 by selling the product rights and inventory to respected magic companies. With other ventures I won’t name, I killed the idea and moved on. Both decisions were correct. The hard part was knowing which one to make when I was in the middle of it.
After working with 40+ startups through the Startup Burgenland accelerator, I’ve watched founders agonize over this decision for months, sometimes years. That agonizing is itself destructive. So I built a framework to make the decision faster and more honest.
Why This Decision Is So Hard
The kill-or-commit decision sits at the intersection of three powerful forces: sunk cost, identity, and uncertainty.
Sunk cost whispers: “You’ve already invested so much. Don’t waste it.” This is a lie. Money and time already spent are gone regardless of what you do next. But it feels true, and feelings drive decisions more than logic does.
Identity whispers: “If you quit, what does that say about you?” This is especially dangerous for first-time founders who’ve told everyone about their idea. Walking away feels like public failure. So they keep going, not because the business warrants it, but because their ego demands it.
Uncertainty whispers: “What if success is just around the corner?” This is the cruelest one because it’s occasionally true. Sometimes persistence pays off. But more often, “just around the corner” turns into a slow bleed of resources and energy.
The framework I use cuts through all three by focusing on observable evidence rather than feelings. It won’t make the decision painless, but it will make it honest.
The Five-Question Kill-or-Commit Test
Answer each question with evidence, not hope. Write your answers down. Vague thinking produces vague decisions.
Question 1: Is There Evidence of Demand?
Not “do people say it’s a good idea?” but “has anyone taken a costly action indicating they want this?” Costly actions include: paying you money, giving you their email and following up, spending significant time testing your product, referring others without being asked.
If after a meaningful effort period (I typically say 90 days of active selling), you have zero costly actions from potential customers, that’s a strong kill signal. Not absolute — but strong.
If you have some demand signals but they’re inconsistent, that might be a pivot signal rather than a kill signal. The problem might be real, but your solution might need rethinking.
Question 2: Do You Know Why It’s Not Working?
This is the most important diagnostic question. There are two kinds of “not working”:
Not working and I don’t know why. This is dangerous. If you can’t identify the bottleneck, you can’t fix it, and more effort will just be more of the same.
Not working but I have a specific hypothesis about the cause. This is fixable. Maybe your pricing is wrong. Maybe you’re talking to the wrong audience. Maybe your message is unclear. If you can name the specific problem and describe a specific experiment to test it, that’s a commit-and-adjust signal.
The founders I’ve seen waste the most time are the ones who keep grinding without a clear diagnosis. They work harder instead of working differently. Validated learning means each failed attempt teaches you something specific. If your failures are teaching you nothing, that’s a kill signal.
Question 3: Do You Still Care About the Problem?
Not the solution. Not the business model. The underlying problem.
Sometimes founders lose interest in the problem itself but keep going because of momentum. They started caring about, say, helping freelancers get paid faster. But now they realize they don’t actually care that much about freelancer payment cycles — they just thought it was a good market opportunity.
If you don’t care about the problem, commit is the wrong call even if the numbers look okay. You’ll eventually cut corners, ignore customer feedback, and build something mediocre. Businesses require too much energy to sustain on market opportunity alone. The problem needs to matter to you.
If you still genuinely care about the problem but your current approach isn’t working, that’s often a pivot-and-commit scenario rather than a kill.
Question 4: What Would You Need to See in 30 Days to Commit?
This forces you to define a clear threshold. Not “things getting better” but specific, measurable criteria.
Examples of good thresholds: “5 paying customers at EUR 50/month,” “20 email subscribers from organic search,” “3 repeat purchases,” “one partnership signed.”
If you can’t define what success looks like in the next 30 days, you don’t have a plan — you have a hope. And hope is not a strategy.
Write the threshold down. Share it with someone who will hold you to it. Then run the 30-day experiment with full effort. At the end, the data makes the decision for you.
This approach aligns with the Start Now Statement — giving yourself a defined window to test rather than an open-ended commitment that stretches into years.
Question 5: What’s the Opportunity Cost?
This is the question people forget. Every month you spend on a failing idea is a month you’re not spending on something that might work.
I’m not talking about shiny-object syndrome. Jumping from idea to idea without giving any of them a real chance is its own problem. But if you’ve done honest work, collected real data, and the evidence points to “this isn’t it,” then continuing isn’t persistence. It’s avoidance.
Ask yourself: If I killed this today and started fresh next Monday, what would I build? If the answer comes easily and excites you, that’s telling you something. If the answer is “I have no idea,” maybe commit a bit longer while you find a problem worth solving.
Scoring the Framework
For each question, assign a score:
- Strong kill signal: -2
- Mild kill signal: -1
- Neutral: 0
- Mild commit signal: +1
- Strong commit signal: +2
Score of -5 to -3: Kill it. The evidence is clear. Thank the idea for what it taught you and move on.
Score of -2 to +2: You’re in the gray zone. Set a 30-day sprint with clear criteria (Question 4) and reassess. Don’t linger in the gray zone for more than one sprint.
Score of +3 to +5: Commit. You have signals, you understand the problem, you care about it, and you know what success looks like. Go all in.
The Emotional Part Nobody Talks About
I want to be honest about something. Even with a framework, killing an idea feels terrible. You’ll second-guess yourself. You’ll see someone else succeed in a similar space and wonder if you quit too early. That’s normal.
What I’ve learned from my own experience — from the ideas I killed and the ones I committed to — is that the pain of killing is acute but short. The pain of grinding on something that isn’t working is dull but endless. Given the choice, take the sharp pain.
And here’s what people don’t tell you about walking away: it releases an enormous amount of energy. The mental load of carrying a struggling venture is heavier than most people realize. When you put it down, you suddenly have capacity for things you’d forgotten about.
Walking away from an idea isn’t failure. It’s editing. And editing is how you get to the good stuff.
When to Revisit a Killed Idea
Just because you kill an idea now doesn’t mean it’s dead forever. Markets change. Technology changes. Your skills and network grow.
I keep a “killed ideas” file with a brief note on why each one didn’t work at the time. Every six months, I scan it. Occasionally, an idea that was wrong for 2024 is right for 2026 because the conditions have shifted.
The difference between smart revisiting and commitment escalation is this: smart revisiting is triggered by new external evidence. Commitment escalation is triggered by ego and sunk cost. Know the difference.
Takeaways
- Use evidence, not feelings. Score the five questions honestly. If the numbers say kill, trust the numbers.
- Define a 30-day threshold. If you’re in the gray zone, set specific criteria and run a sprint. Don’t stay in limbo.
- Separate the problem from the solution. If you still care about the problem, maybe you need a different approach, not a different direction.
- Acknowledge the opportunity cost. Every month on a dead idea is a month not spent on a live one.
- Keep a killed ideas file. What doesn’t work now might work later. Let time and new evidence, not ego, decide when to revisit.
