How to Build a Sustainable Newsletter Practice
Content creation usually comes down to one of two problems: you have too many ideas, or you can't find a single one.
For a while I took the traditional route of pouring my weekly thoughts straight into the newsletter. It was incredibly unstructured, and while it produced evergreen content, I've come to believe newsletters are better suited to real-time, "this is what's happening" content.
Then I started my blog, where I park everything I think might be useful later. With that in place, the way I'd been treating my newsletter no longer made sense — especially since these would be buried in everyone’s emails at one point.
Here's how I see my content channels now, each with its own job:
Blog: evergreen content that stays useful forever
Short-form social: quick, repeatable posts that explore different angles of one core message
YouTube: long-form business assets (working on this)
Newsletter: a direct line from creator to audience, the most human channel of them all
Coming from a marketing career, I've noticed creator brands tilting away from a business-y approach toward a more human one. Fascinatingly, the rise of AI has only made what's human matter more than ever.
With that in mind, here's my game plan:
A journal, not a “funnel”
This newsletter is episodic. Think "this is what I built this week." Each issue is numbered, like episodes of a show, so readers follow along to watch the systems get made.
I chose this format for one reason: it removes the blank page. Most newsletters die because every issue starts from zero, and willpower runs out long before the ideas do. When the newsletter is a journal of what I actually did, the content already exists by the time I sit down to write. I'm reporting, not inventing.
It also plays to where attention is going. People are tired of polished, faceless "expert" content. They want to watch a real person make real decisions. Narrating the week-by-week process of running a creator business inside Notion is more honest, more repeatable, and frankly more interesting than another listicle of tips. People follow because they get to watch the sausage get made.
To keep it sustainable, every issue follows the same shape: a fixed spine I never rethink, plus a small rotating menu I pick from in about 30 seconds based on what my week actually looked like.
The Spine
These three run in every single edition. The spine exists so the newsletter is recognizable as a series and so I can guarantee a complete issue even on a quiet week. Consistency is what turns a newsletter into a habit, for me and for the reader.
System of the Week — the one system I touched most, what it does, and how it's wired.
Why: it gives every issue a concrete centerpiece. A specific system is more memorable and more useful than a vague theme, and it naturally shows my work instead of just describing it.
How I Used Notion AI — one place AI did "employee work" for me this week, while I kept the creative direction.
Why: my audience is curious and slightly anxious about AI. Showing exactly where I hand off grunt work (and where I don't) demystifies it and reinforces that the creator stays in the driver's seat.
Insight from the Business — one lesson from operating the creator business.
Why: this is the trust-builder. Real numbers and real lessons prove there's an actual business behind the advice, which is what separates a build journal from generic productivity content.
The rotating menus
On top of the spine, I pick one segment from any of three menus. This is where the week's specifics come in. The menus exist so I'm never staring at infinite choices; I'm choosing from a short, pre-decided list that matches what actually happened.
Menu A: Build & Systems
Use when I built or changed something.
This menu covers the "what I made" angle. I rotate through it because not every week is a big build week, and pretending otherwise leads to fluff.
Behind the Build: a screenshot teardown of a database or relation I wired up
What I Killed: what I deleted or archived this week, and why
What I Repurposed: one thing turned into another (a hook becomes a thread becomes a newsletter)
Experiment Log: something I'm testing, verdict still pending
Friction Point: what slowed me down, plus the fix
Menu B: Business & Creator
Use when I have a number or a business move to share.
This is the operator's-eye view. I include it because creators rarely get to see the actual business mechanics behind someone's content, and that transparency is what keeps people subscribed.
The Numbers: one honest metric and what it told me
Offer Update: progress on a product, freebie, or launch
What's Converting: which content or hook is landing right now
From the Audience: a DM or comment that shaped my thinking
Honest Moment: a flop or a slow week, told honestly
Menu C: Process & Steal-This
My value-add closer.
Every issue should leave the reader with something they can use today. This menu guarantees a takeaway so the newsletter gives more than it asks for.
Hook of the Week: my best hook, plus the formula behind it
Prompt I Used: one copy-paste Notion AI prompt
Reader Steal: a template, view, or mini-system to copy
One Lean Principle: a short reflection tying back to calm systems
The weekly formula
Spine (3) + one from A,B, or C (or none at all)
Busy build week? Post something from A, B, or C.
Quiet week? Lean on the spine.
Launch week? Make Offer Update (B) the hero and shrink the rest.
The whole point is that I never have to invent content. At the end of each week, I glance at what I edited in Notion, run it through the spine and menus, and the issue is basically pre-written.
Lean by design: a fixed spine I never rethink, plus a small menu I choose from in seconds. The newsletter reflects the work instead of competing with it, so it never becomes the kind of overbuilt system I'd want to kill.
My weekly workflow
This is the 15-minute routine that turns my week into an issue:
Open my recent Notion activity and skim what I actually built, changed, or killed.
Pick the System of the Week, usually whatever I touched most.
Choose one segment from each rotating menu that matches the week.
Draft the spine, then let Notion AI help with the grunt work (transcribing, tightening copy).
Write the Building Next Week teaser and hit send.
Build, reflect, send, and do it again next week.
How to build this into your own system
Of course, I want this to be as uesful as possible so if you want to run your own build journal, here's how to set it up in an afternoon. You don't need my exact segments, just the same skeleton.
Define your channels first. Write one sentence on the job of each channel you run (blog, social, video, newsletter). This tells you what the newsletter is not responsible for, which keeps it focused.
Write your spine (3–5 segments). These appear in every issue. Pick the few things you always want readers to get, then commit to them. The constraint is the point.
Build 2–3 rotating menus. Group your "sometimes" segments into themed menus (build, business, takeaway). Aim for 4–5 options each so you always have something that fits the week.
Lock a formula. Decide how many segments make a full issue (mine is spine + one from each menu). Write it down so you never re-decide it.
Track it in Notion. Create a simple Issues database with properties for issue number, send date, status, and a relation to the system you featured. Add a template that pre-loads your spine and menu checklist so a new issue starts half-built.
Source from your own activity. Before writing, review what you actually did that week (your recent edits, your task list, your published content). Let the work choose the content.
Ship before it's perfect. The first few issues will feel rough. Keep the spine, cut what doesn't earn its place, and let the system tighten over time.
Start lean. A 3-segment spine you actually send beats a 10-segment masterpiece you never finish.
Want weekly insights on building creator systems with Notion?
Join 1,700+ creators that receive a weekly behind-the-scenes look at what I made, optimized, and killed each week on Notion.