I subscribe to about 25 newsletters. For a long time my relationship with them worked like this: subscribe with genuine excitement, read the first two issues, then watch the rest pile up in Gmail until the unread count made me feel bad enough to archive everything and start over.
The problem was never the newsletters. Most of them are good. The problem is that "good" and "worth my time this week" are different bars, and an inbox can't tell them apart. Every issue lands with identical urgency, mixed in with actual mail that needs answers. So the inbox becomes a guilt pile, and the genuinely great issue from a writer who posts once a quarter drowns under three "this week in JS" roundups covering the same three links.
Unsubscribing doesn't fix it either, because almost every newsletter earns its slot maybe once a month. You don't want zero issues. You want the right three.
Here's the workflow that finally worked for me, in two layers. The first layer you can build yourself in ten minutes. The second is harder, and it's where I'll disclose that I ended up building a product.
Layer 1: get newsletters out of the inbox entirely
The single biggest improvement is mechanical, not smart: newsletters should never land where your real mail lands. Route them to a read-later app instead.
Two ways to do it:
Option A: your read-later app's native newsletter address. Readwise Reader gives every account its own email address (Reader settings, under "Add email subscriptions"). Anything sent to that address shows up in your Reader feed instead of your inbox. When you subscribe to a new newsletter, use that address directly. Matter does the same thing.
Option B: a Gmail filter for the ones already coming in. For existing subscriptions you don't want to re-subscribe one by one, add a forwarding address in Gmail (Settings, Forwarding and POP/IMAP, then verify it), and create a filter like:
Matches: list:(*) OR from:(substack.com OR beehiiv.com OR buttondown.email)
Do this: Skip Inbox, Forward to <your-reader-address>
The list:(*) trick catches most legitimate mailing lists because they set the List-Id header. You'll need to hand-tune a couple of senders, but 20 minutes of filter fiddling covers 90% of a typical subscription list.
If you want to script it instead, Reader also has a proper API: POST https://readwise.io/api/v3/save/ with your token in the Authorization header accepts raw HTML, so you can pipe anything into your queue programmatically. I used this for a while with a small script that pulled from a dedicated Gmail label.
After layer 1, your inbox is clean and your newsletters live in an app designed for reading. This is already a big win. Enjoy it for two weeks.
Layer 2: the firehose is still a firehose
Then notice the catch: you moved the pile to a nicer screen. Reader now shows 25 unread newsletters instead of Gmail showing 25 unread newsletters. The queue grows faster than you read. Same guilt, better typography.
The missing piece is ranking. Not summarizing — summaries answer "what does each issue say?", which still leaves you 25 things to process. The useful question is "which 3 should I actually open this week?"
You can hand-roll a crude version of this. Score each issue on three signals:
- Interest match. Keep a short list of topics you currently care about (mine: local-first software, LLM evals, indie SaaS). +2 if the issue's subject or first paragraph clearly hits one.
- Sender hit rate. Track which senders you actually finish reading. A newsletter you've opened 4 of the last 5 times outranks one you've skipped 5 straight. +1 or -1.
- Duplication. If three roundups this week all link the same launch post, they're one unit of information. Keep the earliest or best one, demote the rest. -2 for a mostly-duplicate issue.
Sort descending, read the top 3, archive everything below without opening it. Even doing this manually with a notes file every Sunday beats reading in arrival order, because arrival order is the worst possible order: it rewards frequency, and frequency and quality are barely correlated.
The hand-rolled version's weakness is discipline. Scoring 25 issues by hand is exactly the kind of chore you skip on busy weeks, which are the weeks you need it most.
Disclosure: I built the thing
That's the part I automated, and it turned into a small product. Weekly Brief does the ranking layer for you: point your newsletters at it (directly or via forwarding), tell it what you care about, and once a week it delivers one brief — must-reads on top with a one-line reason each, everything else triaged below — straight to Readwise Reader, Matter, or Kindle. It ranks, it doesn't summarize; you still read the originals. Free tier covers up to 10 newsletters with one weekly brief, and there's a $5/mo plan for unlimited. It's young and I run it, so read this section with that bias in mind.
Whether you use it or hand-roll the scoring, the two-layer shape is the thing I'd push anyone drowning in subscriptions toward: first move newsletters out of the inbox, then add a ranking pass so the queue tells you where to spend your attention. Subscribing generously stops being a problem when arrival stops implying obligation.
Top comments (0)