A paid newsletter with card subscriptions, built by Claude Code on Elements

A paid newsletter with card subscriptions, built by Claude Code on Elements

Free or $8 a month subscriptions by card, a teaser on paid posts, and markdown posts the writer schedules and emails.

How it's built

Letterhearth needed free and paid subscriptions billed monthly by card, scheduled posts that go out by email, a teaser for readers who are not paying, one-click unsubscribe, and live counts for the writer. Each of those is a part of Elements, so the agent spent its 22 minutes on the newsletter itself.

  • Live counts and revenue. Subscribers are a LiveTable, so the writer's free and paid counts and monthly revenue move the moment a reader subscribes or upgrades.
  • Monthly subscriptions. Subscribing, upgrading and cancelling are @rpc calls, and paid plans go through Stripe at $8 a month. The return page and Stripe's webhook record a new subscription once. Until a Stripe key is added, a built-in test checkout takes the payment through the same code, and in production the app registers its own webhook.
  • Posts on a schedule. A cron schedule checks every minute for posts whose time has come and queues one email job per reader, so a failed send retries alone. Paid posts go in full to paid readers and as a teaser to everyone else.
  • One-click unsubscribe. Every email carries the headers mail clients turn into an unsubscribe button, and the app answers that button directly.
  • Data from SQL files. Migrations define the newsletter and seed the writer, six posts (three paid), five free readers and three on complimentary paid plans.
  • Sessions for readers and the writer. Readers are signed in when they subscribe and later by an emailed link, and every writer page shares one guard on the writer's role.

Why Elements

Elements is an integrated full-stack app framework and a project server. The project server checks the agent's work as it builds: it type-checks the server and browser code, analyzes the program, applies migrations and runs the tests, then reports the results to the agent. A security mistake, such as calling a server-only function from the browser, is a compile error. The agent reads the report and fixes its own mistakes before it tells you a feature is done. The same checks run on every feature you ask for next.

Run it yourself

  1. 1 Sign up

    Already have an account? Sign in

  2. 2 Install and run the demo One prompt to paste into your agent.

View the code on GitHub →

The prompt

What Claude was given to build this app.

Agent Prompt
Build a paid newsletter site named letterhearth for an independent writer.

READER
- Subscribe with an email address, free or paid ($8/month by credit card).
- Upgrade, or cancel a paid subscription.
- Read the archive. Paid posts show the first paragraphs and a subscribe prompt
  to readers who are not paying.

WRITER (one admin account)
- Write posts in markdown with a live preview. Mark each post free or paid.
- Publish now or schedule for later.
- Publishing emails the post: free posts to every subscriber, paid posts in full
  to paid subscribers and as a teaser with a link to free subscribers.
- Subscriber list with free and paid counts and monthly revenue.

Every email has a one-click unsubscribe link.

Public home page: the newsletter's name, a subscribe form and the post archive.

Payments by Stripe.

Seed the writer, five free and three paid subscribers, and six posts, some paid.
Show the writer's login on the sign-in page.

Subscriber counts and revenue update in real time.