Why Every MVP Needs a Kill Switch: Lessons From Projects That Didn't Make It
We build MVPs for a living. And some of the best ones we've built are dead.
That's not a failure. That's the entire point.
An MVP exists to answer a question: does this idea have a market? Sometimes the answer is no. The faster you get to that answer, the less money you burn and the sooner you can move on to something that works.
But killing a project is hard. Founders are emotionally invested. Sunk cost fallacy kicks in. The temptation to "just add one more feature" is always there. That's why every MVP needs a kill switch — a predefined set of conditions under which you stop, evaluate honestly, and decide whether to continue.
The Kill Signals
After building dozens of MVPs across different markets, we've identified five reliable kill signals. If you're seeing two or more of these, it's time for an honest conversation.
1. Nobody Uses It After the First Visit
You launched. You got traffic. People signed up. But nobody comes back.
This is the most common and most painful signal. The product works — technically. But it doesn't solve a problem that people care about enough to return.
Week 1: 142 sign-ups → 38 active users (27% retention)
Week 2: 89 sign-ups → 11 active users (12% retention)
Week 3: 34 sign-ups → 4 active users (11% retention)
Week 4: 12 sign-ups → 1 active user (8% retention)
If your retention curve looks like this, more features won't save it. The problem is at the idea level, not the execution level.
"Users would come back if we just had feature X" is almost always wrong. If the core value proposition doesn't retain users, adding more features just makes a more complex product that still doesn't retain users.
2. Users Want Something Different
You built a tool for managing inventory. Users keep asking if it can do invoicing. You built a marketplace for freelancers. Users want it to be a project management tool.
When user feedback consistently points away from your core offering, the market is telling you something. Not that your product is bad — that a different product is more needed.
This is actually the most valuable kill signal because it often points directly at what you should build next.
3. The Unit Economics Don't Work
You're acquiring users for €30 each. They pay €10/month. Average lifetime is 2 months. That's -€10 per user.
"We'll fix it with scale" rarely works. If the fundamental cost-to-value ratio is broken, scaling just means losing money faster.
We've seen founders pour €50K into marketing an MVP whose unit economics were negative from day one. A €2K analysis would have revealed the problem before launch.
4. You Can't Explain the Value in One Sentence
If your elevator pitch takes a full elevator ride, the product is too complex or the value proposition is too weak.
Every successful MVP we've built can be explained in one sentence:
- "Order food from your phone and skip the queue."
- "Find and book automotive experiences across Europe."
- "Manage and track reusable containers across gastronomy locations."
If yours requires a paragraph, a diagram, or "let me show you," that's a signal.
5. The Founder Isn't Excited Anymore
This one is subjective but remarkably accurate. Founders who believe in their product talk about it constantly. They share it with everyone. They're in the analytics dashboard at midnight.
When the founder stops checking metrics, stops sharing updates, stops having opinions about the roadmap — the project is already dead. The code just hasn't been turned off yet.
How We Build Kill Switches In
We don't wait for these signals to appear organically. We define them before writing a single line of code.
The Pre-Mortem
In our discovery phase, we ask the founder: "What would prove this idea wrong?"
Most founders have never been asked this. They've spent months thinking about why their idea will work. Forcing them to articulate failure conditions is uncomfortable but essential.
We document three measurable kill criteria before development starts:
## Kill Criteria for [Project Name]
1. **Retention**: If fewer than 15% of users return within 7 days
after first use, the core value proposition is insufficient.
2. **Activation**: If fewer than 30% of sign-ups complete the
primary action (e.g., place an order, create a listing),
the onboarding or UX has a fundamental problem.
3. **Willingness to pay**: If fewer than 5% of active users
indicate willingness to pay (survey, waitlist, or actual
conversion), the business model is not viable.
Review date: 4 weeks after launch.
Decision: continue, pivot, or kill.These numbers aren't arbitrary — they're calibrated based on the specific market and business model.
The Review Meeting
Four weeks after launch, we have a structured review. Not a "how's it going?" chat — a data-driven decision meeting.
We look at:
- The kill criteria metrics
- Qualitative user feedback
- Support requests and complaints (what's missing?)
- Competitive landscape changes
- Founder's gut feeling (seriously — it matters)
The outcome is one of three decisions:
- Continue — metrics are healthy, double down with a v1.1 sprint
- Pivot — the market signal points to a different product or audience
- Kill — the idea doesn't have legs, shut it down gracefully
Shutting down an MVP doesn't mean disappearing overnight. We help founders communicate with early users, export data, and document what was learned. The relationships and insights from a failed MVP often seed the next successful one.
The Projects That Died
We can't name names, but here are real patterns from projects we helped kill:
The Social Feature Nobody Wanted. A B2B tool added social/community features because "engagement." Users wanted better reporting, not a feed. The social features were the most expensive part of the build and had zero adoption. Kill signal: #2 (users want something different).
The Marketplace With No Supply. A two-sided marketplace launched with a beautiful buyer experience and no sellers. No supply = no demand = no marketplace. The team spent 3 months on the buyer side and 0 on seller acquisition. Kill signal: #3 (unit economics — infinite acquisition cost on the supply side).
The Solution Looking for a Problem. A technically impressive product with no clear buyer. The founder could explain what it did, but not why anyone would pay for it. Kill signal: #4 (can't explain the value) and #5 (founder lost enthusiasm after the market showed indifference).
Why This Matters
Building an MVP that proves an idea wrong is not a waste of money. It's the cheapest way to learn.
The alternative is worse: building for 12 months, raising funding on projections, hiring a team, and then discovering that the market doesn't want what you've built. We've seen this happen. The financial and emotional cost is 10–50x higher than a 4-week MVP with a built-in kill switch.
The Bottom Line
An MVP without a kill switch is just a project. A project without a deadline is a hobby. A hobby burning €10K/month is a problem.
Define your failure conditions before you start. Measure them honestly. And have the courage to act on what the data tells you.
The best founders we work with aren't the ones whose every idea succeeds. They're the ones who kill fast, learn faster, and build the next thing with everything they learned from the last one.
Olio on LinkedIn
