Skip to content

Build1 publisher3 min readPublished

A launch that failed six weeks early: 2 upvotes, 27 page views and a karma gate

LeadAce's Product Hunt day returned 2 upvotes and no signups. The four weeks before it returned 6 users and 2 link clicks, which is where the launch actually went wrong.

The Engineer · Build desk

Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction

Illustration accompanying A launch that failed six weeks early: 2 upvotes, 27 page views and a karma gate
Generated illustration

What happened

  • LeadAce's first 24 hours on Product Hunt produced 2 upvotes, one comment written by the founder, day rank #160 and 3 product page followers.
  • The site logged 6 active users and 27 page views in the four weeks up to launch day, with a single referral from producthunt.com.
  • The company's X account made 48 posts in that same window for 576 impressions, 2 link clicks and 2 new followers.
  • Hacker News blocked the Show HN outright, because the founder's account, made years earlier and never used, carried karma 1.
  • The two subreddits that did accept the post, r/SideProject and r/SaaS, produced questions from readers, one of which changed the roadmap the same day.

Compiled by The EngineerSomething wrong?How this is made

Why it matters

  • constraint Karma and account age cannot be bought or accelerated, so the earliest honest launch date is set by when the accounts qualify, not by when the demo video renders.
  • cost The spend landed on assets that were ready on schedule while the distribution prerequisite was not, which effectively warehoused finished product work until the channels could accept it.
  • decision Eligibility on one channel arrived nine days after the launch, which turns launch timing into a calendar decision about gate dates rather than a judgement about product readiness.
  • capability Roadmap-grade answers on pricing and injection came out of a handful of votes, so a founder with no reach can still extract the one thing a launch is meant to produce.

The gates that stopped this are denominated in time, which is why nothing done in the final week could have moved them. r/ClaudeAI removed the first attempt because the account was too new; a moderator then locked the retry from a five-year-old account, because Showcase posts on that feed require 50 total karma and the account had 1 [10], a shortfall of 49 [26]. r/selfhosted keeps projects under three months old in a New Project Megathread. The public repo was created on May 28, so eligibility arrived on August 28 [13], nine days after the launch date the founder had already committed to [25].

Everything on the other side of those rules was finished: the product, the demo video, the gallery images and the copy [8]. What was missing was account history, and account history accrues through months of ordinary participation rather than preparation [14].

The arithmetic on the owned channel is worth doing, because it explains the emptiness of the site logs. Four weeks of X posting comes to about 12 impressions per post and a link click rate of 0.35 percent [20][21]. The site analytics land in the same place: roughly 4.5 page views per active user, and referrer counts that sum to exactly the active user count, so almost every visitor was one session and no return [22][23].

Now the comparison the write-up does not make. The consolation megathread comment on r/ClaudeAI drew 67 views and one upvote in 19 hours [11], about 3.5 views an hour. The X account over four weeks ran at roughly 0.86 impressions an hour, so a comment in a thread the founder was demoted into out-delivered the entire owned channel by about four to one on a per-hour basis [24].

One sentence in the post is carrying more than the data allows. The founder concludes that the launch did not fail at the landing page [7]. The four-week traffic figures make the distribution case convincingly, but the post reports ranks, votes and a four-week window without ever giving launch-day sessions [27], so the conversion result being defended has no denominator [4]. The page was not cleared. It was never put under load.

What did work needed no audience at all. r/SaaS accepted the post only after every link came out of the body and the ending became a real question [12], and that version became the most discussed thing the company published. A pricing question about the hard monthly cap, where sending simply stops, put metered overage on the roadmap the same evening [16]. A prompt injection question got a specific answer: the send step uses only the stored record, and the server enforces quotas, do-not-contact, the country allowlist, email verification and the compliance footer, so a hostile page can poison one prospect's record but cannot trigger mass sends [28]. Six upvotes and a dozen comments were enough for both conversations [17].

The founder's remedy is to stop launching and start commenting on three chosen channels six weeks out, treating karma as something built in advance like a mailing list [18], with daily useful replies on X in place of a second launch [19]. Measured in hours, that is cheaper than the demo video. It is also the only input on the list that a deadline cannot compress.

What to watch

  • Whether the r/selfhosted New Project Megathread post after August 28 outperforms the Product Hunt day, which would price the nine-day wait retrospectively.
Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories