Weekly Newsletter in an Hour: Research to Sent Issue

Key takeaways

Research is the real bottleneck, not writing. Most of a curated issue is reading, scanning and discarding, which a machine does well. Judgment and voice are the thin slice at the end, and that slice stays yours.
Write from what people actually said, not what publishers wrote. The free, open-source last30days skill pulls real posts and engagement from Reddit, X, YouTube, Hacker News, GitHub, and the web from the last 30 days.
Use the same four-part structure every week: a hook, three to five curated items with YOUR take, one thing you built, and one single call to action.
Always include one thing you built. It is the forcing function that makes you a practitioner instead of an aggregator, and it is the slot people skip first.
Feed the model 3 to 5 samples of your real writing before asking for a draft, and tell it to leave brackets where it does not know your opinion instead of inventing one.
Write the subject line first, and lead with what the reader gets. When opens drop, check the subject line and your send gap before you blame spam filters.
A human reads every issue before it sends. AI is your researcher and first-draft writer, never your editor. Editorial selection and angle are the product.

The Solo Creators AI Studio

Get this skill, and every one I build.

The whole vaultA new drop monthlyBuild live with meYours to keep, forever

See inside the Studio

30-day money-back guarantee. Cancel anytime.

Questions people ask

Won't an AI-drafted newsletter sound like AI?

It will if you let the model invent the voice. It won't if you feed it yours. Paste 3 to 5 of your past issues, emails, or LinkedIn posts into the voice prompt and tell it to copy your rhythm, your sentence length, and your favorite phrases. Then do a read-aloud pass and fix every line that isn't how you'd say it. The bigger protection is that the take is yours. AI can summarize a Reddit thread. It can't tell your clients what that thread means for their business next Tuesday. That part never comes from the model.

What if I have nothing to write about?

You have a capture problem. Keep a running idea file: one document, one line per idea, no editing. Every client question, every objection, every thing that annoyed you goes in it. Then run research on last month's real conversation in your niche and you'll find you have five things to say. The hard part is remembering the ones you already had.

How long does this really take?

Be honest with yourself about issue one. It'll take about 90 minutes because you're building the assets: the running idea file, the voice sample, the structure. Issue two is faster. By issue four you're at an hour or under, because research is a 10-minute step, structure is a template you don't rethink, and the draft arrives already sounding like you. The hour is real, but it's earned around issue four, not issue one.

What if I built nothing this week?

Then ship something small before you send. A one-page checklist. A three-minute video. A template. A rewritten section of your site. The "one thing I built" slot is a forcing function, and that's the point of it. A newsletter where you always have something to show is a newsletter that's quietly making you produce every single week. If the slot is empty, the week was empty. Fix the week.

Is last30days really free, and what needs setup?

Yes, it's free and open source on GitHub (mvanhorn/last30days-skill). Reddit, Hacker News, GitHub, and Polymarket work with zero configuration. X, YouTube, and TikTok need a one-time 30-second setup wizard the first time you ask for them. That's the honest caveat. Anyone claiming every source works with zero setup is skipping that step. You install it inside the Claude desktop app by typing two slash commands into the chat box. No terminal, no code.

Why not just use Feedly or Inoreader?

Use them if what you want is publisher coverage. RSS readers are excellent at telling you what got published. They're built on feeds, so they surface articles, not people. If your newsletter's value is "here's what the industry press wrote," a free Feedly tier covering 100 sources is genuinely enough and you should stop reading here. If your value is "here's what your peers are actually struggling with right now," you need forum and social signal, and RSS won't give you that.

My open rate is falling. What do I check first?

Check the subject line before you check the spam filter. If your last six subject lines led with a feature or a scold instead of what the reader gets, that's usually it. Next, check your send gap: go quiet for three-plus weeks and people forget they subscribed. Then check weight, because image-heavy, multi-CTA emails get folded into Promotions. Only then look at your bounce log, and read the actual diagnostic text rather than guessing. And if the "one thing you built" slot has been empty for three issues, that's your answer.

Should I let AI send the issue automatically?

No. Auto-generated newsletters are widely and correctly criticized for being low quality, because editorial selection and angle are what make a newsletter worth opening, not aggregation. AI is your researcher and your first-draft writer. You're the editor, and the editor never gets automated. A human reads every issue before it sends. That rule costs you five minutes and saves you your reputation.

Found this useful? Share itPost Share

Written by Ronnie Nijmeh

Ronnie spent 18 years building a SaaS with a team of 20 that served over 650,000 customers, generated over $14M in sales, and sent over 550M emails. Now he's solo, solving real business bottlenecks and turning them into working AI skills, workflows, and automations. He teaches all of it, with direct access to him, inside the Solo Creators AI Studio Skool community. See what he's built →