Two Products in 10 Days, Zero Users — My First Loop as a Solo Founder

At the end of February, I ran my homegrown demand mining system against HackerNews and Reddit. It clustered 91 pain points, pushed them through a 5-stage funnel, and surfaced a Top 5. I picked #1, shipped an MVP in 3 days, launched it — zero traction. I ran a postmortem, upgraded the system, picked the new #1, built a second MVP in 4 days — then paused before hitting “promote.”

This was the first full loop of my one-person company. Both products failed, but what they taught me is worth more than either product ever could have been.

BuyOnce: 1,625 Interactions Does Not Equal a Market

My demand mining system’s top recommendation was “a curated directory of buy-once software.” The data looked compelling: HackerNews posts about subscription fatigue had 1,625 interactions, and subreddits like r/buyitforlife and r/degoogle were full of people complaining about SaaS subscription costs.

I went for it. The reasoning checked out:

• Highest demand signal in the dataset (top interaction volume)
• Technically trivial (curated directory — one week to MVP)
• Clear monetization path (affiliate -> paid listings -> subscription)
• Lowest risk — even if nobody paid, the SEO content would retain value

Three days later, BuyOnce was live. 39 buy-once apps, 8 categories, search and user submission features all working.

Then I posted to Show HN.

Zero engagement. Reddit post: 1 karma. Not a single software submission, not a single affiliate click.

Four-Layer Postmortem: Where Did the Judgment Go Wrong?

I ran a postmortem that peeled back four layers:

Market layer — The information gap wasn’t big enough. Free software lists are everywhere: Product Hunt, AlternativeTo, countless awesome-lists. Buy-once software is a low-frequency decision; nobody’s browsing a directory every week.

Competitor layer — Someone had built almost the same thing on HackerNews 11 months earlier and gotten 222 upvotes. This wasn’t a fresh opportunity — it was a validated market where first movers already had the advantage.

Monetization layer — Affiliate coverage was only 20%. Buy-once products have no recurring purchases, which means no recurring commissions. I did the math on the ceiling: $50/month. That doesn’t even cover domain costs.

Distribution layer — Zero followers, zero SEO authority, zero community relationships. Every cold-start channel failed.

The core lesson: high interaction volume on HN was people venting (“I hate subscriptions”), not searching for a solution. The gap between emotional resonance and actual demand is far wider than I assumed.

Traction: The Confirmation Bias Trap

BuyOnce died on distribution. So my next instinct was: help other people solve their distribution problem.

The demand mining system surfaced a new high-scorer — “AI makes building products easy, but founders still can’t do GTM.” It felt like it was describing me. Score: 8.6/10, competitive whitespace: 9/10 (no direct competitors), tech-channel fit: 10/10.

Four days later, Traction’s MVP was wired up: user inputs a product description and target market, AI generates a 30-day GTM playbook with daily checklists and channel templates. Stripe integration done, pricing set at $19/month or $49 one-time.

But this time, before I hit “promote,” I stopped and looked at the data.

That 8.6-scoring demand came from a single HN post — “Could you create a competitor to your company at 10% of the cost?” — with 7 upvotes and 10 comments. The discussion was actually about AI lowering competitive costs, not about “founders need a GTM tool.”

My system had flagged it: evidence_type: inferred, confidence: 2/5.

And I had selectively ignored both fields. Because BuyOnce died on GTM, I wanted to believe GTM was a good direction. That’s confirmation bias, textbook.

I paused Traction. The MVP works, but there was no data proving anyone needed it.

3 Rules Extracted from Two Failures

These 10 days of tuition fees bought me 3 rules that are now hardcoded into the system:

Rule 1: Weak Singleton Filter

If a demand is mentioned by only 1 post, the evidence is inferred, and the LLM confidence is <= 3 — auto-kill. Don’t waste time evaluating it.

After this rule went live, the next run through 91 clusters immediately eliminated 6 candidates that would have previously passed. Traction itself was a weak singleton.

Rule 2: Validate Search Demand Before Building

I added a Google Search verification step: for each Top 20 demand, search for commercial keywords (“best X tool,” “X pricing”). If Google shows no commercial discussion around the topic, the demand is still in the complaining phase — it hasn’t converted into buying behavior.

BuyOnce’s demand had plenty of Google results — but they were all free lists. The market existed, but the monetization model was wrong. Traction’s demand had almost no Google results. The market might not exist at all.

Rule 3: Gate Promotion Behind Data Thresholds

Deploying an MVP is not the same as being ready to promote. Before spending time and API costs on cold-start outreach, you need at minimum: email collection gating, basic analytics, and payment integration complete. Traction’s MVP used a “graceful degradation” design that let anyone use the full product for free without leaving a trace. Promoting a product like that = burning API credits for zero return.

The System Is Worth More Than the Products

10 days, 2 MVPs, 0 users. Sounds brutal.

But I now have something worth more than either product: a more reliable judgment system. It can take 91 pain points down to 5 (95% elimination rate), each with evidence quality scores, search demand validation, and competitive survival analysis.

BuyOnce and Traction are still alive. One sits quietly at buyonce.yuyuqueen.com, the other waits at traction.yuyuqueen.com to be woken up once demand is validated. Their code isn’t sunk cost — it’s scaffolding for the next product and material for the next blog post.

The loop of a one-person company isn’t “pick right -> succeed.” It’s “pick wrong -> postmortem -> upgrade the system -> pick again.” Speed matters more than accuracy, because you can rapidly improve accuracy, but you can’t rapidly improve speed.

The next loop has already started.