Skip to content
Sundayship

Methodology

Every build card starts as a real request found on a public developer forum or an open-source issue tracker. Nothing here is invented.

Where signals come from

  • Hacker News, via its public Algolia search API: story and comment hits for phrases like “is there a tool” or “Ask HN: AI tool”.
  • GitHub issue trackers on popular open-source AI projects: feature requests and enhancement issues, ranked by community reactions.
  • Product launch sites, when a launch itself is the demand signal (for example, a well-received Show HN or Launch HN post).

What every card links to

Every demand quote and every proof signal on a card links directly to the original post, issue, or comment. If you can't verify it by clicking through, it doesn't belong on Sundayship.

What we don't do

We never estimate or imply revenue numbers for any build idea. Proof signals are real, observed numbers (upvotes, reactions, comment counts), not projections. Difficulty ratings are our own opinionated estimate, clearly labeled as such, not a guarantee.

How we keep ideas recent

Ingest only looks at signals created in roughly the last 12 months, or older GitHub issues that still saw activity in the last 6 months. Every card also carries a freshness label based on when its source was last active: Fresh (within 90 days), Active (within 12 months), or Aging (within 24 months and still open). A source with no activity in over 24 months, or a GitHub issue closed as completed or a duplicate with no recent comments, is Stale and gets archived rather than published. A weekly recheck rescoring published cards flags any that turn Stale for a human to review instead of removing them automatically.

How cards get added

A scheduled ingest job pulls fresh raw signals from the sources above. A human (or an AI-assisted drafting pass) then reviews the raw signals and hand-writes each new build card (including its build prompt and hook pack) before it's published.