Newsletter App Starter · Industry version
A paid publication platform — tiers, gated issues, referrals, churn metrics — generated into code you own, with no platform cut.
A paid newsletter is a media business: free readers funneling to paid tiers, premium issues behind a gate, and a churn number that decides whether this is a living. This starter builds that machine into the schema and hands you the code — with no percentage of your subscription revenue going anywhere.
01 · The problem
Free-list tools bolt payments on; a paid publication needs the money model in the schema. Tiers, comped subscriptions, annual-versus-monthly, grace periods on failed cards — when those are afterthoughts, every edge case becomes support email with a spreadsheet on the side. The gate deciding who reads the premium Friday issue has to be a join, not a judgment call.
The free-to-paid funnel is the actual business, and most platforms show you only its endpoints. Which posts convert free readers? How long does the average reader lurk before upgrading? Does the podcast audience convert better than the one from short-form video? Those answers live across signups, opens, clicks, and upgrades — queryable only when all four are tables you own.
And platform economics compound against you. A percentage of revenue plus per-subscriber pricing means your best months are your most expensive, and the audience relationship — including the paying one — sits on infrastructure you rent. For a creator, the list and the paywall are the whole company; renting them is a strange default.
02 · Data model
Everything in the base Newsletter starter —
subscriberssegmentscampaignsissuessendslink_clicks— plus the entities this industry actually runs on:
| table | what it holds |
|---|---|
paid_tiers | Subscription levels with price, billing interval, and what each unlocks — the money model as structure, comps and trials included. |
referrals | Who brought whom — subscriber-to-subscriber referral credits and milestone rewards, the growth loop paid publications live on. |
03 · Screens
Each issue declares its audience — free, paid, or a specific tier — and the send fans out accordingly, with the web archive gating to match. Free readers see the teaser and the upgrade path, not an error page.
The dashboard tracks the path that matters: signup source to engaged free reader to paid conversion, with time-to-upgrade and the issues that most often precede it. Publish more of what converts, on evidence.
Cancellations, failed payments in dunning, and cohort retention by signup month — the recurring-revenue vitals, computed from your own tables. MRR isn't a screenshot from a payments dashboard; it's a query you can decompose.
04 · In practice
Define monthly and annual tiers, mark the Friday deep-dive as paid, and announce to the free list with an upgrade link. The first paid cohort's conversion source data starts accruing immediately.
A subscriber shares their referral link; at three referrals they unlock a month of paid access, applied automatically as a comp with an expiry. The leaderboard runs from the referrals table — no third-party referral tool taking a cut.
A card fails; the subscriber enters dunning with retry logic and a grace window on gated content, then a win-back sequence if it lapses. Every step is your code, so the tone of those emails is yours too.
No — the platform is code you own, and payments go through your own payment processor account. There's no revenue share and no per-subscriber fee; infrastructure cost is your hosting bill.
Yes — comps and trials are part of the tier model, with expiry dates and automatic downgrade to free. Press comps, gift subscriptions, and referral rewards all use the same mechanism, visible in each subscriber's history.
Free readers get the open section and a clear upgrade prompt where the gate begins — in email and on the web archive. The cutoff point is per-issue, so a mostly-open edition with a paid postscript works fine.
Upgrades are timestamped rows next to your sends and clicks, so 'which issue preceded each conversion' is a join, and the funnel view ships as a dashboard. That's the editorial feedback loop paid publications need and platforms rarely expose.
Dual7 App Starters
A paid publication platform — tiers, gated issues, referrals, churn metrics — generated into code you own, with no platform cut. Describe your version to start — the output is a project you own.