Killing a product after 30 days: why we don't mourn dead experiments
We killed a product this month. Nobody cried. That's the system working.
I run Inithouse, a portfolio of about 14 MVPs. Each one gets 30 days to prove it deserves to exist. Not "prove product-market fit" or "hit revenue targets." Just show me one real signal that somebody out there gives a damn.
The signal can be anything. Organic search clicks trickling in without paid ads. A user coming back twice without being reminded. Someone sharing it with a friend. A stranger emailing to ask when feature X is coming.
If none of that happens in 30 days, the product is dead. We don't debate it. We don't run one more experiment. We don't pivot.
The kill is not a failure. The kill is the whole point.
Most solo founders I know treat every product like it's their only shot. They pour months into something, then months more trying to save it, then months more convincing themselves the next tweak will change everything. By the time they admit it's not working, they've burned a year.
I can't afford that. Not when there are 13 other products waiting for attention.
What the kill actually looks like
There's no ceremony. I check the numbers, I check my gut, and if both say the same thing, I'm out. The domain stays registered. The code stays in the repo. Sometimes I recycle a component or a whole page layout into something else. Nothing gets thrown away, it just gets reassigned.
The hardest part isn't the decision. It's the five minutes after. You built this thing. You had an idea at 2am, you sketched it out, you shipped it. And now you're looking at a dashboard with single-digit visitors and deciding it doesn't matter anymore.
But here's what I've learned: that feeling fades fast when you have something else to work on. Portfolio approach is an emotional cheat code. You're never mourning because you're always building.
The signals I watch
I keep it simple. Three things:
Organic traction without paid push. If Google isn't sending anyone after the initial indexing window, the topic either doesn't have search demand or my angle is wrong. Either way, 30 days of zero organic means a dead signal.
Return visits. One-time visitors are noise. If people come back even once on their own, something clicked. If nobody does, I'm solving a problem that doesn't hurt enough to revisit.
Unsolicited feedback. This is the rarest and the strongest. Someone reaching out to say "hey, I tried this and..." That email changes everything. No email after 30 days? Message received.
What happens to the body
The code doesn't disappear. I've pulled auth flows, UI components, even entire database schemas from killed products and dropped them into live ones. Without Human has pieces of two dead experiments in its codebase right now.
The domain usually stays parked. Domains are cheap. Sometimes a killed product gets resurrected six months later with a completely different angle. Rare, but it happens.
The biggest thing: learnings get logged. What worked in the marketing. What didn't. Which landing page copy converted vs which one bounced everyone. That knowledge compounds across the portfolio, even when individual products don't survive.
Why this works (and why it might not work for you)
This system only makes sense if you're running multiple bets. If you have one product, killing it after 30 days is just giving up. The portfolio model is what makes the kill constructive instead of destructive.
It also requires you to ship fast enough that 30 days is actually enough time to test something real. If your MVP takes 3 months to build, this framework falls apart. I use vibe coding tools and move quick. Most of our MVPs go from idea to live product in a week or two.
The point isn't that killing is good. The point is that killing quickly frees up the scarcest resource you have: your attention. Attention, not money, not code, not ideas, is what actually determines which products survive.
We killed a product this month. We'll probably kill another one next month. And somewhere in the portfolio, something is quietly picking up traction, getting that second visit, generating that first unsolicited email.
That's the one that gets to live.
I get the portfolio logic, but 30 days feels brutally short unless the product is solving something with obvious immediate demand.
Some things get no signal because the idea is bad. Some get no signal because distribution was weak or the timing was wrong.
With one product, this would be panic. With fourteen, I can see how it becomes discipline instead.
Interesting approach—and I’d say the real strength here isn’t the 30-day rule itself, but the removal of negotiation after exposure to data. That’s where most founders lose time: not in building, but in continuously re-litigating decisions that should already be closed.
I often see the opposite problem: not enough structured “killing,” which leads to emotional attachment outweighing weak or ambiguous signals.
What stands out in your system is that you predefine what “life” means before launch, which effectively protects attention—the scarcest resource in early-stage portfolios