How HackerBooks reached 1,861 points on Show HN with a five-word pitch

What drove it

1. 1

   Borrow a format the audience just met

   Identity hook

   What they did: The tagline names an existing, widely discussed product and changes one word: "HackerTube, but for books."

   Why it worked: Readers understood the product before clicking and could repeat it in one line. The comparison also carried the credibility of the original.

   Try this: Write your pitch as "<known product>, but for <your domain>" and test whether three people can explain it back to you without a demo.

2. 2

   Launch where the data comes from

   Community seeding

   What they did: A catalog built from Hacker News comments was posted on Hacker News, where every commenter could look for their own recommendations.

   Why it worked: The audience was both the source and the reader. Finding your own comment in the product gives a personal reason to open the page, reply and share.

   Try this: If your product is built on a community's output, launch in that community and make each contributor findable (a name, a quote, a link back to their post).

3. 3

   Ride a live moment

   Borrowed audience

   What they did: It shipped right after HackerTube dominated the conversation, and its tagline pointed at it.

   Why it worked: The topic was already on readers' minds, so the launch landed as the next entry in a running story rather than a cold start.

   Try this: Watch the top of Show HN and Product Hunt for a pattern people are discussing. If you have a credible variant, ship within days, and say plainly what you borrowed.

4. 4

   A ranking people want to argue with

   Participation loop

   What they did: Books are ranked by how many different people named them, which makes the list checkable and open to dispute.

   Why it worked: Search summaries describe commenters questioning the ranking method. A visible method gives people something to correct, and correcting is participation.

   Try this: Publish the rule behind your ranking or score, invite corrections, and credit the people who send them.

Try this for your launch

• Write the pitch as "<known thing>, but <one change>" and test it on three people.
• Launch in the community that produced your data, and let contributors find themselves in the product.
• Check what pattern is trending on Show HN this week and whether you have an honest variant.
• Show the method behind any ranking on the page, and say where it can be wrong.
• Stay in the thread on launch day and answer method questions with numbers.
• Keep a way to follow up: new entries daily or weekly, so launch-week visitors have a reason to return.

Caveats

• We could not open the Hacker News thread, hackerbooks.org or the press articles from our environment. Points and comments are Launch Index data; we did not independently count them.
• Book counts differ across sources (15,362, 15,766 and 16,543), probably because of different snapshot dates. We have not confirmed which is current.
• A search summary reports that the maker said an AI model wrote almost all of the pipeline and site. This is the maker's claim and we did not check it.
• We did not verify the maker's audience size or any promotion outside Hacker News, so we cannot say how much of the result came from the HackerTube attention versus the product itself.
• Several Hacker News-derived launches appeared in the same week. Part of the lift may be topic interest rather than anything specific to this launch.

Sources

• Launch Index page for HackerBooks ↗
• Show HN thread (item 50326821) ↗
• Runtime Wire coverage (seen as a search summary) ↗
• Korben coverage (seen as a search summary) ↗
• HackerTube coverage (dsebastien.net, search summary) ↗
• Launch Index page for Wikihack ↗
• Launch Index page for HackerTV ↗

Checked on Nov 9. Spotted something wrong? Email [email protected] and we'll correct it.