Writing and content decision

Amazing Newsletters

A small, public newsletter directory is realistic for one technical user to build and run; the site lacks durable moats and no public pricing was found, so self-hosting a scoped replacement is practical.

Visit website

Built by Rishit Patel, who ships 3 products in this index

You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off40 h to build

$50/mo3 h/mo upkeep

No published price to break even against.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Users browse and search curated newsletter listings; owners submit newsletters; site shows metadata and links; maintainers moderate submissions.

What it still won’t have

  • Built-in audience and SEO/traffic the public site has
  • Existing publisher relationships, sponsorship/ad sales channels
  • Brand recognition and curated dataset/ratings
  • Any proprietary analytics or aggregated open rates shown on the site

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Amazing Newsletters does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a searchable newsletter directory as a single-developer project using PostgreSQL, Node.js (Express) backend, and React frontend. Core features in scope: CRUD for newsletter records, category/tag filtering, full-text search (Postgres trigram or Elastic if chosen), public newsletter detail pages with metadata (frequency, platform, open rate fields), a submission form with CAPTCHA and admin moderation UI, and CI/CD deployment (Dockerized app, managed Postgres on a cloud provider). Out of scope: revenue/sponsorship platform, ad sales dashboard, and large-scale sending infrastructure. Include input validation, error handling, automated tests for API endpoints and key UI flows, and deployment scripts. Provide basic observability (error logging and uptime alerts) and a README with setup and maintenance instructions.
How we checked3 sources · 2/3 runs agreed · evidence score 81

How the score was reached

  • Build verdict base78
  • 3 cited sources+3
  • Evidence score81

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded