HackerBooks

What is it

HackerBooks is a discovery and browsing layer that takes the books discussed on Hacker News and turns them into a HackerTube-style, scrollable reading experience. In technical terms, it's a scraper plus ranking engine: it ingests HN threads (comments, submissions, and the recurring "What books are you reading?" posts), extracts book mentions, deduplicates against a book metadata source (Open Library or Google Books API), scores each title by mention frequency and comment sentiment, and renders the result as a fast, visual feed — covers, one-line blurbs, and links to the original HN discussion.

The business significance is bigger than the product itself. HN is one of the highest-signal technical communities on the internet, and its reading recommendations carry outsized credibility for engineers and founders. That makes HackerBooks a curation engine for a high-intent, high-spend audience. The underlying asset isn't the feed — it's the ranked dataset of "what smart technical people actually read." That dataset can power a newsletter, an affiliate storefront, a recommendation API, or a paid membership. The 920-point discussion proves the concept resonates; the question is whether the novelty converts into a business.

Why now

Three forces converge to make this viable in late 2026 rather than a year earlier or later.

First, LLM summarization got cheap and good. Two years ago, turning 50,000 HN comments into per-book sentiment scores and one-line summaries meant either manual work or garbage output. Today a small model pass over the corpus costs a few dollars and produces usable blurbs. This collapses the hardest part of the build.

Second, the "HackerTube" pattern is proven. The original HackerTube (browsing HN videos) and similar "HN, but for X" projects have repeatedly hit the front page. The format — fast, visual, zero-login browsing of a curated HN slice — is a validated UX template. HackerBooks is that template applied to a new vertical.

Third, affiliate and creator economics have matured. Bookshop.org, Amazon Associates, and niche book clubs now pay reliably, and indie devs routinely monetize curation feeds at $500–$5,000/month. The infrastructure to turn a ranked book list into revenue exists off the shelf.

The timing risk is the opposite: this is easy enough that someone else builds it in a weekend. That argues for speed over polish.

Market Evidence

The evidence base is thin but pointed: 1 independent source, 1 mention, 100% growth rate, stage: nascent. That single source is a Show HN post that drew 920 points of discussion. Read that number carefully — 920 points on HN puts a post in roughly the top 1–2% of all submissions that day. The comment volume signals genuine engagement, not a polite upvote.

But one data point is not a trend. A 100% growth rate off a base of one is mathematically meaningless — it just means "it appeared." The honest read: this is real but unproven demand. The 920 points prove people want to look at the product. They do not prove people want to pay for it, return to it weekly, or that the audience is large enough to sustain a business.

Compare to validated categories: a genuine consumer SaaS trend shows 5–10 independent sources and sustained mention growth over 4–8 weeks. HackerBooks has neither yet. Treat the 920 points as a green light for a 3-day validation build, not a green light for a 3-month investment. The signal is loud enough to test and too thin to bet on.

Who's Behind It

There are no "whales" here yet — and that's the point. HackerBooks is a classic solo indie project born on Show HN. The community driving it is the Hacker News core audience: engineers, indie founders, and technical readers who trust HN curation over algorithmic feeds. That's a small but high-value tribe — the same people who subscribe to Stratechery, buy books on Bookshop.org, and pay for tools like Obsidian and Readwise.

The competitive dynamics are shaped by adjacent whales rather than direct ones. Readwise (and its Reader product) already owns the "save and revisit what you read" space and has a large, loyal paid base. Goodreads owns social reading but is stagnant and Amazon-owned. Bookshop.org owns ethical book commerce. None of them do HN-specific curation — that's the gap.

The real risk isn't a whale entering; it's that the HN community itself builds three clones in a week. The moat, if any, is speed, brand, and the quality of the ranked dataset — not the code.

TAM & Market Size

Be honest about the ceiling. The core audience is the HN readership that actively reads books: realistically 50,000–150,000 people globally. That's the top of the funnel. Of those, a fraction will pay.

Addressable buyers break into three tiers:

• Consumers (readers): 50k–150k reachable, price tolerance $3–$8/month or $30–$60/year. Conversion realistically 1–3% → $15k–$70k/year at scale.
• B2B / teams (engineering book clubs, L&D budgets): smaller count, higher ACV. Companies spend $200–$2,000/year on team reading lists. Maybe 500–2,000 viable accounts → $100k–$400k/year potential.
• API / data licensing: media companies, newsletters, and AI training-data buyers wanting a curated "what engineers read" dataset. Unproven but high-margin.

The provided scores — Opportunity 0/100, Demand 0/100 — are essentially "insufficient data," not "bad opportunity." The market is real but niche. This is a $50k–$300k/year lifestyle business or a $1M+ acquisition target, not a venture-scale market. Price accordingly and don't over-invest.

Competitive Landscape

Direct competitors are effectively zero mature players — this is greenfield, which is both the opportunity and the warning sign. The competitive set is adjacent:

• Readwise / Readwise Reader — strong, paid, loyal. Weakness: it's a personal library tool, not a discovery feed. Doesn't surface what others are reading.
• Goodreads — massive but stagnant, poor UX, Amazon-owned, no HN angle.
• HackerTube and "HN but for X" clones — prove the format, but none own books.
• Newsletters (e.g., niche reading-list Substacks) — fragmented, no product layer.

The gap: nobody owns "curated technical reading discovery." The differentiation is the HN signal — credibility that Goodreads and Readwise can't manufacture.

If Big Tech enters — say, Amazon folds HN-style curation into Goodreads, or Readwise adds a discovery feed — you have roughly 6–12 months before the niche gets crowded. But Big Tech rarely bothers with a $100k niche; the real threat is a faster indie. Competition score of 0/100 means "no competition yet," which is a 12-month head start, not a permanent moat. Move fast, build brand, own the keyword.

Business Model

Recommended: freemium subscription with an affiliate layer. Here's why it fits.

The core feed should be free — that's the growth engine and the reason HN upvoted it. Gate the depth: personalized reading lists, "books like this," saved shelves, weekly curated digests, and export/API access. That's a classic freemium split that Readwise has proven works for the same audience.

Pricing:

• Free: browse feed, search, top-100 list.
• Pro — $5/month or $40/year: saved shelves, personalized recommendations, weekly email digest, "why this book" AI summaries, no ads.
• Team — $15/seat/month (min 3 seats): shared reading lists, L&D export, discussion threads.
• API — $29–$99/month: ranked dataset access for newsletters and media.

$5/month is the sweet spot for this audience — low enough to be an impulse buy, high enough to filter. $40/year gives a 33% discount and improves retention.

12-month forecast:

• Conservative: 400 Pro subs + affiliate → ~$2.5k MRR ($30k ARR).
• Base: 1,200 Pro + 30 team accounts + affiliate → ~$9k MRR ($108k ARR).
• Optimistic: 3,000 Pro + 100 teams + API deals → ~$28k MRR ($336k ARR).

CAC: near-zero via HN/Reddit/SEO; paid CAC ~$15–$25. Payback under 2 months on annual plans. The math works only if organic acquisition holds.

MVP Blueprint

Target: 3–5 days. Cut everything that isn't the core loop.

Core features (only these):

1. HN ingestion — pull submissions and comments via the HN Firebase/Algolia API, filtered to book-related threads (keywords: "book", "reading", "recommend", plus known recurring threads).
2. Book extraction & dedup — regex + LLM pass to pull titles, match against Open Library API for covers and metadata.
3. Ranking — score by mention count × thread recency × comment upvotes. Simple, transparent formula.
4. Feed UI — HackerTube-style: cover grid, one-line AI blurb, "discussed in N threads," link to source HN thread.
5. Search + top-100 page — the SEO and shareability hook.

Tech stack: Next.js + Tailwind on Vercel; Supabase (Postgres) for the book/mention tables; a nightly cron (Vercel Cron or GitHub Actions) for ingestion; OpenAI or a cheap model (gpt-4o-mini / Claude Haiku) for blurbs and sentiment. Total infra cost under $30/month at MVP scale.

Fastest path: skip auth entirely for v1 — the feed is public. Add email capture ("weekly digest") on day one to build the list. Ship, post to Show HN, measure. Don't build accounts, payments, or personalization until the free feed proves retention.

Estimated dev days: the provided field reads 0, which is clearly a placeholder — realistically 3–5 focused days for a solo dev.

Commercial Opportunities

1. The curated reading newsletter + affiliate storefront. Turn the ranked dataset into a weekly "What HN is reading" email. Monetize via Bookshop.org/Amazon affiliate (3–8% commission) and sponsored slots. Target user: technical readers who trust HN. Expected: $1k–$5k/month at 5k–20k subscribers. Beats a pure SaaS because it monetizes the free audience directly and builds a list you own.

2. Team reading-list SaaS for engineering orgs. Sell shared shelves, L&D exports, and book-club tooling to engineering managers. Target user: eng managers and DevRel leads with L&D budgets. Expected: $5k–$20k MRR at 30–100 accounts. Beats consumer subs because B2B ACV is 10–20x and churn is lower.

3. "What engineers read" data API. License the ranked dataset to newsletters, media, and AI companies wanting curated training/recommendation data. Target user: media and AI-data buyers. Expected: $500–$5k/month per deal, high margin. Beats product work because it's pure data with no UI maintenance — but it's unproven and slow to close.

Product Ideas

🥇 HackerBooks Digest — the weekly HN reading email. Value prop: "The books HN is talking about this week, ranked and summarized, in 5 minutes." Target user: technical readers and indie founders. Why now: email is the highest-retention channel for this audience, affiliate economics are mature, and the HN signal gives instant credibility. Lowest build cost, fastest path to revenue.

🥈 HackerBooks Pro — the personalized discovery feed. Value prop: "Your reading list, curated by what 100,000 engineers actually recommend." Target user: power readers willing to pay $5/month. Why now: the free feed proves demand; gating depth is the proven Readwise playbook. Needs auth + payments, so it's a month-2 build, not week-1.

🥉 HackerBooks for Teams — shared engineering reading lists. Value prop: "Curate, assign, and track technical reading across your engineering org." Target user: engineering managers and L&D leads. Why now: B2B budgets exist and nobody serves this niche; the HN dataset is the differentiator. Highest revenue ceiling, longest sales cycle — build after consumer traction.

SEO Opportunity

Search demand for "best books for engineers," "books Hacker News recommends," and "technical reading list" is steady and evergreen. SEO difficulty is scored 0/100 — effectively uncontested for the exact-match niche.

Long-tail targets:

• "books hacker news recommends"
• "best programming books 2026"
• "what books do engineers read"
• "HN book recommendations list"
• "best software engineering reading list"

Content strategy: publish an auto-updating "Top 100 Books Hacker News Recommends" page (regenerated weekly from the dataset) and let it rank. Add per-topic pages ("best distributed systems books per HN"). The freshness signal plus zero competition should rank within 8–12 weeks.

Risk Assessment

When the thesis is wrong: if the 920 points were pure novelty — people clicked, laughed, and never returned. Novelty traffic is the #1 killer of "HN but for X" projects.

Top 3 risks:

1. Market/retention risk (highest). One-time curiosity, no repeat visits. Validate with 4-week retention, not launch-day traffic.
2. Commoditization risk. Anyone clones it in a weekend. Mitigate with brand, SEO, and the owned email list — not code.
3. Monetization risk. This audience is famously cheap and ad-blocking. Affiliate commissions on $20 books are pennies; subscriptions may convert under 1%.

Cheap validation before building: post a "Top 100 books HN recommends" listicle to HN/Reddit before building the app. If it gets traction and email signups, build. If it flops, you saved a month.

Walk away if: after 4 weeks the free feed shows under 15% week-2 return rate and the email list grows slower than 50/week. Those numbers mean novelty, not demand.

Action Plan

Today: pull the top 200 book-mentioning HN threads via the Algolia API and generate a ranked "Top 100" markdown list. This is a few hours of work and is your validation artifact.

Low-cost validation (this week): publish that list as a free page and a Reddit/HN post. Add an email capture ("get the weekly digest"). Track signups and return visits. Spend $0.

If signal confirms (week 1): build the 3-day MVP feed, ship to Show HN, and start the weekly digest immediately to build the list.

Month 1 goals: 1,000 email subscribers, 5,000 monthly visitors, first affiliate revenue, 50+ Pro waitlist signups.

Month 3 goals: 300+ paying Pro subs or a validated B2B pipeline, $2k+ MRR, top-3 ranking for "books hacker news recommends." If those miss, reassess before investing further.

Related Terms

HackerTube — the original "browse HN as video" project that validated the format HackerBooks adapts. Readwise/Reader — the adjacent paid incumbent proving this audience pays for reading tools. Show HN launch dynamics — the 920-point signal is a launch phenomenon; understanding HN's novelty-vs-retention pattern is essential to reading the demand correctly. Together they frame HackerBooks as a format-proven, audience-validated, monetization-unproven niche play.