3 Newsletters You Should Launch (Research Report)

Date: 2026-04-11 Prepared for: Alexis Bouchez Scope: What I read, what exists in the market, and 3 concrete ideas with form, substance (fond), tone, and format.

1. What I read before writing this

Before pitching anything I pulled from your own material:

All 6 blog posts (Go/Docker/Postgres/HTTP, Voxtral, Python YouTube downloader).
About 20 journal entries across Feb, March, April 2026. The recent ones where you are pivoting Palmframe, getting tired of free reviews, archiving Hyperbulletin, job-hunting for half a day and rage quitting it.
The reviews you already published (pyannote, Scrape Creators, nanocorp, etc.). I looked at the format and the frontmatter.
/now, /projects, /interests, /like, /dislike, /offer, /palmframe, /internet-history, plus a sample of the 260 AI analyses in content/ai.
CLAUDE.md, including your LinkedIn post rules and your "no fake oppositions" feedback memory.
The existing Crunchbase report at research/crunchbase-complaints-better-version-report-2026-04-07.md so I could match the report format.

What stood out:

You already have one strong asset nobody in your niche has: real, hands-on, written + video reviews of tools most people only read about on Product Hunt. 11+ of them. Your review format is locked in (what it does, what worked, what did not, verdict, best for).
You are burnt out on doing free reviews on a treadmill cadence ("I am tired of recording free reviews", March 31). So whatever we design has to monetize the existing archive and let you batch, not grind.
You are deeply intellectual in a way your current writing only half expresses. Girard, Schmitt, Dantec, Packy's "read a lot of sci-fi", Gnosticism, Million Dollar Homepage, perennial philosophy, Maggie Appleton, gwern. This is a layer that does not show up in the reviews at all and it is your clearest differentiation.
You are unusually candid about failure. Valyent shut down after a year. Palmframe positioning is not landing. Resend account got suspended for mass outreach and you laughed. There is a huge content gap for honest indie hacking content that is not "I made $1M in 6 months" bait.
Your voice rules are already documented: short sentences, no dashes, casual, no corporate filler, no false dichotomies, journalistic over guru. We just stay inside that.

2. What exists in the market (short version)

Full breakdown in the Appendix. The short version:

Platform: stay on beehiiv. Substack takes 10% of paid revenue forever. Ghost needs self-hosting work and has no growth marketplace. Kit is tuned for creators selling courses. beehiiv Scale at $49/mo unlocks Ad Network + Boosts + 0% paid-sub fee in one move. You are already on pub pub_ccead006-8cac-4f29-b160-305f55bcb997, so the switching cost is zero to none.
Cadence that wins in 2026: weekly long-form essay for depth newsletters; daily for pure curation plays. Monthly only works if each issue is a "report" that feels like a product.
Format that wins in 2026: hybrid. One long-form piece on top, short curated or build-in-public section below. AI is killing pure link-digest newsletters; personality and hands-on testing are the moat.
Monetization reality: paid sub growth is stagnating industry-wide; free list + sponsorships is where indies under ~50k subs actually make money. Your niche (dev tools, founders picking their SaaS stack) sits at $40 to $100 CPM. Paid tiers only make sense after ~10k subs, usually gated by community or archive, rarely by the newsletter alone.
Distribution: email ownership on beehiiv, mirror on LinkedIn (it rewards newsletter content hard in 2026), X threads for every issue, link always in first comment per your own rules.
Benchmark trio to study: Lenny's Newsletter (depth + community + product bundles), Bytes by Cassidoo (one engineer, weekly, warm voice, sponsor-funded), Not Boring (narrative essays, $20k+ per deep dive sponsorship). None of them own the niche I am about to hand you.

3. The 3 newsletters you should launch

I picked these three because each one leverages something you already have, each one is defensible against AI slop, and together they form a portfolio where the three audiences overlap enough to cross-pollinate but stay different enough to not cannibalize.

Ranked by "ship first".

1. The Stack Report (ship first)

Also viable names: "SaaS for Builders", "Stack Diary", "Shipped & Tested", "Under Review".

The concept in one line. Every week, one SaaS or dev tool gets opened, built on top of, and reviewed by someone who actually shipped something with it.

Why this one and not another review newsletter. There are curation newsletters (TLDR, Refind, Console). There are review sites (G2, Capterra, Product Hunt). There is nothing in between run by a person who actually writes code with the tool before judging it. Your pyannote review is the proof: you built two apps live, you noticed the fuzzy segment boundaries, you flagged that Claude Code could build both apps just from the docs (which is the real tell on doc quality nobody else measures). That is not a tier a curation bot can fake in 2026.

Fond (substance / pillars). Each issue has the same spine:

What it does (one paragraph, no marketing copy).
What I actually built with it this week (screenshots or GIF).
What worked, what did not.
Verdict + best for.
"In your stack instead of…" : a one-line comparison to the thing it would replace.
"Would I put my money on it?" : a buy / wait / skip call.

Then a short "builder notebook" at the bottom: 3 to 5 links to tools you are watching but have not tested yet, with one sentence each. That is where the curation lives, safely contained.

Forme (format). 800 to 1,500 words. One hero product, one embedded YouTube clip from your channel (reuses your video work instead of doubling it), screenshots, no stock photos. Table at the bottom with the buy/wait/skip verdict so skimmers get the answer in 3 seconds. Issue number in the subject line, not the title (e.g. subject: "Stack Report #07: pyannote", H1: "pyannote is the piece Whisper is missing").

Ton (voice). The one you already use in reviews. Warm, specific, zero marketing, willing to say "it did not work". Short sentences. Never end with a lesson. No "here is what this means for you". The verdict sentence is enough.

Cadence. Weekly, Thursday morning European time. Thursday lands the best for B2B opens and it gives you the weekend to batch two at a time.

Audience. Solo engineers and indie founders picking their next SaaS / tool / API. Secondary: buyers at small startups (10 to 50 people) who do their own tool selection. You have already been talking to them on YouTube.

Launch plan.

Seed with your existing 11+ reviews as "back catalog" (one per week for the first 11 weeks, rewritten with the new spine so you are not starting from zero).
Port the frontmatter you already write in content/reviews/ into the newsletter almost verbatim. The work is half done.
Import your YouTube subscribers and any email list you have. Put a signup form on the top of every content/reviews/*.md page. You have app/reviews already.
Cross-post every issue as a LinkedIn article (the /offer redirect to /review suggests LinkedIn is already a channel). Follow your own LinkedIn post rules, put the sub link in the first comment.
Apply to beehiiv Boosts once you hit 1k subs.

Monetization. Two revenue streams stack naturally:

Paid reviews as the upsell. You already sell them. The newsletter becomes the distribution layer. Founders pay because they land in front of 5k+ buyers, not because they want a 15-minute video on an empty channel. Price tier: free product mention in "builder notebook" + sponsored deep-dive review as a separate premium slot, clearly marked.
Sponsorships to the niche. Turso, Neon, Supabase, Flightcontrol, Sentry, Posthog, Clerk, Resend (yes, even after the ban, ha). $40 to $60 CPM is a realistic target. At 5k engaged subs that is $200 to $300 per issue.

Risk and how to kill it. Review fatigue is the enemy. Solve it by (a) counting the 11 existing reviews as 11 weeks of runway, (b) batching 2 products per filming session, (c) keeping the cadence at weekly not daily, (d) letting "builder notebook" carry half the curation weight with near-zero effort.

Why this one first. Lowest cost to ship. The asset already exists. Every other newsletter you launch later benefits from "writer of The Stack Report" as the credential line in the bio.

2. Hyperstition Weekly

The concept in one line. Every week, one sci-fi idea that has just become real, written by someone who actually ships software with the tech underneath it.

Why this one. You already have Hyperstition as a project. The intellectual engine is already running in your journal: you quote Packy's "the only way to not be totally flummoxed is to have read a lot of sci-fi", you read Dantec, you study Girard and Schmitt as applied to strategy, you saved the Million Dollar Homepage piece, you care about perennial philosophy. This audience exists and nobody is serving them in a disciplined, weekly, technically credible way. Not Boring is the closest comp and it is a $20k per sponsor brand that does not touch engineering. You can own the engineering-literate corner of it.

Fond (substance / pillars). Each issue is a short essay built on a strict template:

The sci-fi source. One paragraph. Book, film, story, year, author, the exact idea.
The present-day hook. One paragraph. The paper, product, or launch from the last 7 days that is quietly making that idea real.
How it actually works under the hood. 3 to 5 paragraphs. This is where you earn the reader. No hand-waving. You are a backend engineer, explain it like one.
What breaks when this ships. The business model, job, or institution the idea dissolves.
The question it leaves open.

No "takeaway". No bullet list of "what this means for founders". Just the essay, the way Packy writes, but technical enough that the person shipping AI agents next week actually learns something.

Forme (format). 1,500 to 2,500 words. One hero image from the source (sci-fi cover, still, diagram), one embedded diagram of the architecture you are describing. Always a source footer with the exact citations. The discipline is the product.

Ton (voice). Less casual than Stack Report. Still short sentences and no dashes. More literary. Think: gwern crossed with Packy McCormick, minus the MBA-speak. You drop quotes from the source text. You are not afraid of a Schmitt reference or a Plato gloss if it actually earns its place. You never do the "this is so Black Mirror" joke.

Cadence. Weekly, Sunday morning European time. Sunday is the essay slot for literate readers. Stratechery, The Generalist, Not Boring all hit their highest open rates on Sunday / Monday.

Audience. CTOs, senior engineers, AI researchers, tech-literate VCs, the "very online but read actual books" crowd. This is the group you respect and it is bigger than it looks.

Launch plan.

Archive your current Hyperstition under the new brand immediately so you do not start from zero.
First 4 issues should be pre-written before you announce. That is the hardest constraint; without it Sunday becomes a panic.
Pick 12 permanent "source texts" you can mine: Neuromancer, Snow Crash, Solaris, Diamond Age, Accelerando, Blindsight, Permutation City, Ghost in the Shell, Ted Chiang shorts, Dantec, Lem, PKD. Each issue picks a source + a present-day hook. That gives you a quarter of issues planned in advance, basically forever.
Launch post: a single essay titled something like "Why I am writing about sci-fi as if it were API documentation". Pin it.

Monetization. Slower on purpose. Free for the first ~3,000 subs. Then paid tier at $8/mo or $80/yr that unlocks: (a) the monthly "Field Report" (a longer piece applying one sci-fi frame to a current startup, named directly, deep enough that founders share it), (b) a Discord or small forum, (c) archive access after 6 months. Target 3% to 5% conversion which is realistic for a niche + literary newsletter. Sponsorships are a secondary lever and should be picky; never run a crypto or AI-slop sponsor here, it breaks the brand.

Risk and how to kill it. The risk is thinking it has to be perfect. Kill it by pre-committing to 52 issues a year and letting the worst ones be short. The discipline is the product. Readers forgive a 900-word issue; they do not forgive a week off.

Why this one second. It takes more effort per issue than Stack Report but it is the newsletter that best matches the person you actually are in your journal. It is also the one that will age best. Tool reviews are evergreen for 18 months; sci-fi-and-philosophy essays are evergreen for 10 years.

3. Shutdown Notes

Also viable names: "The Postmortem", "Kill File", "Ship Diary: Failures Edition".

The concept in one line. Every other week, one honest autopsy of an indie product that stopped: what it was, why it ended, what it leaves behind.

Why this one. You lived it. Valyent shut down after a year of engineering without traction. Palmframe is mid-repositioning. You are explicit about review fatigue. You screenshot hyperbulletin.com the week it dies, because you want to keep it around forever. That impulse, "save the thing before it disappears", is the exact instinct this newsletter is built on. Indie Hackers has a community post format for this. Starter Story has the opposite ("how I made $10k/mo"). Nobody is running a disciplined, respectful, technically literate postmortem newsletter about projects that ended. You are the right person to own it precisely because you are candid without being bitter, and technical enough to actually explain the why when someone says "we ran out of money".

Fond (substance / pillars). Two types of issue, alternating:

Field postmortem. You interview (or just read + write up) another indie who shut down a project in the last 90 days. Structured: origin story, thesis, what shipped, what broke, the month the founder knew, what the sunset looked like, what they took away, what still works if you pay the domain. No schadenfreude. No fake empathy.
Archive entry. You pick a dead project from the wider internet, often one that mattered, and you write the "obituary". Hyperbulletin is issue 1. Valyent (yours) is issue 2. Then projects from the last 5 to 10 years that taught something when they died. The archive work is already in your blood: you literally archived hyperbulletin on April 10.

Forme (format). 1,000 to 1,800 words. One screenshot (always the home page on the last living day, preferably archived by you). One metrics table if you have it (MRR, users, churn, burn). One "what I would do differently" sentence from the founder, pulled out as a callout.

Ton (voice). Warm, quiet, respectful. Short sentences. Never mocking. Never moral. You are not here to teach; you are here to record. Think obituary in a good newspaper, not LinkedIn guru post. This is where your "no fake oppositions" rule matters most: the temptation to say "it was not a failure, it was a lesson" is the cliché that would kill this newsletter in one issue. Do not do it. Just say what happened.

Cadence. Biweekly, Tuesday. Half the volume of the other two because the work is heavier (interviews, archival, sensitivity).

Audience. Founders who are either (a) in the middle of ending something, (b) deciding whether to end something, or (c) trying to learn from the ones who did. Secondary: operators and investors who find this kind of signal more useful than yet another win post.

Launch plan.

Issue 0: a manifesto post on why shutdowns deserve better coverage. Honest, not click-baity. Publish it on your existing blog first, cross-post to LinkedIn with your own post rules, end with "I am starting a newsletter about this. Link in comments."
Issue 1: Hyperbulletin. You already did the archival work; write it up with what you know about what they were trying to do and why it did not land.
Issue 2: Valyent. Your own postmortem. This is the credibility issue; it proves the newsletter is not punching down.
Issue 3 onward: outreach to 3 to 5 founders a week via your existing cold email playbook (you know how to do this already), offering a 30-minute call and a respectful writeup. Most will say yes because they have wanted someone to tell their story and nobody asks.

Monetization. Slowest of the three. Stay free for a year. When it works, the revenue comes from: (a) a paid tier for the interview archive with transcripts and metrics sheets, (b) one job board slot per issue aimed at founders who just shut down and are hiring or looking, (c) eventually a small annual conference or dinner for operators who went through a shutdown. This one is a community play, not an ad-sales play. Never run a "startup accelerator" sponsor.

Risk and how to kill it. The risk is people not wanting to go on record. Kill it by offering anonymous cuts with verifiable details for the ones who refuse attribution, and by having your own Valyent post in issue 2 as the trust signal.

Why this one third. Highest emotional labor. Slowest monetization. Most defensible long term. Launch it after Stack Report is generating revenue and Hyperstition has a small cult, so you can afford to be patient with this one.

4. The portfolio view (why these three and not four)

These three live in three different emotional registers (practical, visionary, elegiac) and three different cadences (weekly batch, weekly essay, biweekly interview). They share an audience overlap of ~30% (indie founders / engineers / builders), which is enough for cross-promotion but not so much that one cannibalizes another. They each cover one side of who you actually are in your journal:

Stack Report = the builder shipping things with real tools.
Hyperstition Weekly = the reader of Dantec, Girard, and Packy's sci-fi advice.
Shutdown Notes = the guy who archives hyperbulletin the day it dies.

Any fourth idea I tried to add either doubled up on one of those registers, or required a pivot you should not be doing right now (a Go-only tutorial newsletter would be good tech, but it would pull you into exactly the treadmill you are burned out on).

5. What I would actually do next week

If it were me, I would ship Stack Report first, using 8 of your existing reviews as 8 weeks of runway, and use those 8 weeks to pre-write the first 4 issues of Hyperstition Weekly. Announce Stack Report now. Announce Hyperstition in 6 weeks when you have ammunition. Leave Shutdown Notes for Q3, when the first two are generating revenue and you can afford to take the slower, heavier one seriously.

Concrete first actions:

Create content/newsletter/stack-report/ and drop the spine template in a _template.md file.
Rewrite your pyannote review into the new spine as Stack Report #01 and mark it as the public sample.
Add a beehiiv subscribe form to the top of every page under app/reviews/.
Pick the 12 permanent sci-fi source texts for Hyperstition so you can stop picking them every week.
Write the Valyent postmortem draft and keep it in a drawer. That is Shutdown Notes issue 2 whenever you are ready.

6. Appendix A: Platform comparison (picked the numbers that matter)

Platform	Base cost	Take rate on paid	Growth tooling	Verdict for you
beehiiv	free up to 2.5k; Scale $49/mo; Max $109/mo	0% (Stripe only, 2.9% + $0.30)	Ad Network, Boosts, referral program, recommendations	Stay here. You already have a pub ID and the monetization is the best in class.
Substack	free	10% + Stripe	Notes, Network recommendations	Discovery is real but 10% forever is a tax. Costs you $6k on $60k of paid revenue.
Ghost	$9/mo starter, $29/mo publisher	0% (Stripe only)	None native	Engineer-friendly but you would have to rebuild growth from scratch.
Kit	free up to 10k on Newsletter plan; $39/mo+ on Creator	0%	Creator Network recommendations	Designed around course/product selling, not your pattern.
Buttondown	$9/mo to 1k, $29/mo to 5k	0%	Minimal	Good if you were a markdown purist; you are not.

Do: upgrade beehiiv to Scale ($49/mo) the week you cross 1,000 subs on any one of the three newsletters. That unlocks the Ad Network + Boosts + paid sub infrastructure simultaneously. Before 1k subs, free tier is fine.

Do not: migrate off beehiiv. The cost of losing the pub history and the integration work already done is real and the replacement platforms do not offer a differentiator big enough to justify it for your niche.

7. Appendix B: Benchmark table

Newsletter	Niche	Subs	Format	Model	Revenue estimate
Lenny's Newsletter	Product management	1M+ / 18k paid	Weekly long-form + interviews	Paid + community + bundles	$4M+/yr
Not Boring	Tech/strategy essays	256k	Weekly deep dives	Sponsorships ($20k+) + VC syndicate	$3M+/yr
Stratechery	Tech strategy	~40k paid	Daily + weekly	Pure paid, $12/mo	$5M+/yr
The Generalist	Startups/VC	130k / ~2.3% paid	Long-form analysis	Paid subs	$300k+/yr (probably more)
TLDR	Tech curation	1.25M+	Daily bullet links	Sponsorships ($5k to $18k/slot, 3 slots)	$5M to $10M/yr
Bytes by Cassidoo	JS devs	200k+	Weekly, voice-driven	Sponsorships	Solo engineer scale
JavaScript Weekly	JS ecosystem	~260k	Weekly curation	Sponsorships	Cooper Press portfolio ~$2M+/yr
Refind	Cross-newsletter	491k	Daily	Conversion Ads	Growth channel more than target

Closest voice match: Bytes by Cassidoo (warm, solo, sponsor-funded). Closest depth target: The Generalist (longform, disciplined, niche). Closest discipline target: Stratechery (show up every single time, no misses).

8. Appendix C: Monetization benchmarks

CPM for your niche (dev tools / founders): $40 to $60, with upside to $75 to $100 if positioned toward founders picking their SaaS stack, not devs picking libraries.
Paid-sub conversion: niche newsletters hit 4% to 10% (vs 1% to 3% for general). Realistic target for Hyperstition: 3% to 5%.
Viability thresholds: ~1k subs = beehiiv Ad Network eligible; 5k = first sponsors in $300 to $800/slot; 10k = a real business at $3k to $10k/mo across 2 to 3 streams; 25k to 50k = full-time range $100k to $500k/yr; 100k+ = $1M+/yr plausible in dev/B2B.
Industry trend to respect: paid subscription growth is stagnating in 2025 to 2026; free + sponsorship is winning for indies under ~50k subs. Design for that reality, not the 2021 Substack dream.

9. Appendix D: Voice rules to hard-enforce across all three

Pulled from your own CLAUDE.md and feedback memory, because the editor you will need is you:

No dashes, no emdashes. Use ":", ";", or short sentences instead.
Short sentences. Under 20 words most of the time. Under 12 words on LinkedIn.
No false oppositions. Never "it is not X, it is Y". Just say the thing.
No "I'd be delighted", no "excited to announce", no "looking forward to connecting".
No forced lessons. Never end an issue with "here is what I learned" or "the takeaway is". The verdict is the ending.
No humble brag. No fake vulnerability. No "I almost gave up" arc.
Cross-posting: single emoji in first position of LinkedIn post, link in first comment, never in the post.
Reddit test: if r/LinkedInLunatics would dunk on it, rewrite it.

10. Appendix E: Sources

beehiiv pricing + ad network docs (beehiiv.com/pricing, beehiiv.com/blog/the-state-of-newsletters-2026, beehiiv.com/blog/newsletter-sponsorship-cost)
Substack platform data (popup.fm/blog/substack-pricing, sacra.com/c/substack)
Ghost pricing (ghost.org/pricing, forum.ghost.org July 2025 pricing update)
Kit pricing (emailtooltester.com convertkit pricing review 2026)
Buttondown (newsletter.co/buttondown-review)
Growth in Reverse profiles: Lenny's paid newsletter, Packy/Not Boring, TLDR, The Generalist
Newsletter Operator: "10 newsletters doing $1M+ with 1-person teams"
Simon Owens on paid-sub conversion rates (simonowens.substack.com)
Wellput: State of Newsletters 2025 / market maturing piece
InboxBanner: newsletter ad pricing guide
TLDR advertise page (advertise.tldr.tech)
Refind Ads (refind.com/ads)
influenceflow.io: LinkedIn newsletter strategy 2026
HubSpot: future of newsletters
Stratechery about page + Blockbuster "How Ben Thompson got 40k paid subs"
Bytes by Cassidoo sponsor page
draft.dev: ultimate list of developer newsletters 2025
Your own content: content/blog/*, content/journal/2026/**, content/reviews/2026/**, content/ai/*, app/now, app/projects, app/interests, CLAUDE.md, research/crunchbase-complaints-better-version-report-2026-04-07.md