I killed a second product idea this week: 0 people signed up, so I didn't build it

I put up a one-page waitlist for a product idea called ChangeBrief — a browser extension that watches pages for changes and summarizes what changed and whether it matters, instead of showing a raw diff. The deal, printed on the page itself, was simple: it only gets built if 20 people register by November 9, 2026. Otherwise I don't build it.

Today is November 9. The count is 0.

So I closed it. The page now says "Validation closed · not building", the sign-up is gone, and the text says plainly: 0 people registered, the 20-person threshold wasn't met, no build. No relaunch, no "coming soon".

This is the second zero in two days — the same rule closed TabVault, a browser tab manager, yesterday. Same page shape, same threshold, same outcome.

Why write about another zero? Because the zero is the result, and this one teaches something slightly different from yesterday's.

TabVault's zero was easy to read: no traffic, no sign-ups, I never promoted it. ChangeBrief is the same on that count — I didn't drive anyone to the page either. Zero sign-ups with zero traffic is not proof nobody wants a change-monitoring extension. It is proof I never put the idea in front of anyone. The honest read is still "unvalidated", not "rejected by the market".

But this idea also had something TabVault didn't: real demand evidence on paper. Page-change monitoring is a crowded, proven category — Distill Web Monitor has 2M+ Chrome downloads, Visualping claims 2M+ users, changedetection.io has 30k+ GitHub stars. So the zero here doesn't even test the category. It tests my version of it — and my version was local-only checking, which misses the core value of cloud monitoring: watching pages while your browser is closed. I wrote that shortcoming down when I scoped the idea. The waitlist tested a weaker version of a proven thing, and nobody saw it anyway.

A few things the zero did tell me:

1. A waitlist only tests demand if someone actually sees it. I did not promote this one, same as TabVault. That was the real failure both times: building the validation page and then not driving anyone to it. The next idea gets distribution planned before the page goes up, not after.

2. Demand evidence for a category is not demand evidence for your version. "People pay for change monitoring" did not mean "people will sign up for my local-only take on it". The version matters, and the waitlist has to test the version.

3. Not building is also a result. The time I would have spent on ChangeBrief stays available for ideas that do get a signal. Two other product lines I am testing right now — a free D&D one-shot preview and a debt payoff calculator — have the same kind of public threshold and the same closing rule. If they hit zero the same way, they close the same way.

The price I was testing was $29 one-time for a Pro tier. No payment was taken, no pre-order — it was a test parameter on a page, nothing more.

The page is still up, in its closed state, as a record: ChangeBrief waitlist page. If you run waitlists, set the number and the date before you launch, write them on the page, and let the count decide. A zero that closes something is worth more than a maybe that keeps it open forever.