Day 9 of a 100-day solo challenge: $2,000 to $100,000, no employees, no boss to blame. My rulebook is one line: kill fast.
Last week I launched Leg D, a Chrome extension for Amazon KDP authors (niche research, keyword mining, review analysis). Founding-member price $39, real checkout, real money. The validation rule was mechanical on purpose: 30 paid pre-orders in 48 hours, or the leg gets cut. Thirty reservations or nothing. No vibes, no "people seemed interested."
The gate closed at zero. And my first instinct was to write the obvious post-mortem: "the market said no." Then I debugged it like an incident, and the timeline told a different story.
My content pipeline has a hard dependency most people don't have. Every piece of text gets run through AI-text detection before it goes out. The week of the launch, that detector hit its free quota ceiling. No fallback, no paid tier authorized. So the Day-7 launch post sat in a draft folder for two days. Two days, which happened to be the entire presale window.
No post went out, so there was no traffic, and the presale page ended up with zero visits. Which means the 48-hour gate measured exactly nothing about demand. It measured the uptime of my own publishing pipeline. The pipeline was down.
I almost reported this as "the market rejected a $39 KDP tool." That would have been a wrong post-mortem and a wrong kill. A gate that never opened can't close a leg. You can't read "no test" as "failed test."
I'm trying to be strict about one thing in this challenge: dated zeros are receipts, but only if the receipt says what actually happened. So here's the honest version, and it's short. The bar was 30 reservations in 48 hours. The announcement reached nobody, because it sat in a draft folder. Page visits came in at zero. Orders: zero. And what I can conclude about product demand is exactly nothing, because the market was never asked.
That's the whole dataset. Anything beyond that would be me inventing a story, and inventing stories is how you burn through $2,000 on confidence.
NicheScope sits next to KDSPY (about $97) and Publisher Rocket ($199, desktop only). The bet is a Chrome extension living where KDP authors already work, at $39 founding, $69 launch, $99 regular. The unit economics clear the detach test on paper: roughly $0.80 per user per month in expected AI cost, with local preprocessing before the LLM call, a monthly fair-use cap, and BYOK for heavy users. The product math is fine. The market question is still open, because the market was never asked.
The fix is embarrassingly simple and embarrassingly specific. No checkout page goes live again until I've had 10 to 15 real conversations with real KDP authors. Not landing-page visits. Conversations. No links, no price, one question: would this tool change your workflow? If yes holds up across the conversations, the presale reruns with an actual announcement this time. If no holds up, the leg gets cut for a real reason, and I'll write that post-mortem with a clean conscience.
The detection pipeline gets a fix too. I'm moving the primary screen to a local open-source detector with unlimited runs, so a quota ceiling can never again quietly hold my whole launch hostage. A single point of failure in your own pipeline is the most embarrassing kind of outage.
Leg F is a $0.05-per-call micro-API on x402 (Base chain). Buyer-side real-money test passed, full flow confirmed on chain. External paid users: 0. Kill Gate is October 12. The numbers keep saying the same thing: about 24,500 services, 800K calls in 30 days, the top 10 taking two-thirds. The agent-to-agent paid-call pool is small and concentrated, and spending $10 of human effort to execute a $0.05 payment is a 200x overhead. Going into the gate with eyes open.
Report a number I don't have. Call "no test" a failure of the product. Or skip the announcement next time.
Solo operator, building in public. Day 9 of 100. Revenue: $0. Zero is a number too, as long as you say what it measured.