Building a weekly publishing rhythm when you are also running the company

Most founders who say they will "blog weekly" stop after three posts. Not because the writing is hard, but because writing competes with everything else on the calendar, and everything else usually wins. The fix that actually holds up over months is not more discipline. It is changing which part of the job is yours.

Split the work by what only you can do#

A founder is the only person who knows what actually happened this week: the customer conversation that changed a decision, the bug that taught something, the feature that shipped and why. An AI assistant cannot know any of that until you tell it. But once you have told it, the assistant is perfectly capable of turning a rough account into a structured first draft, and that is the part that eats most of the time.

So the rhythm that works looks like this:

You supply the raw material. A voice note, a few bullet points, or a messy paragraph typed straight after the moment happens. Three minutes, not thirty.
The assistant drafts. Structure, headings, a reasonable opening, a first pass at the argument. This is where most of the clock time would otherwise go.
You edit. Cut what is wrong, add the detail only you have, fix anything that sounds like nobody in particular wrote it. Fifteen to twenty minutes, done once, not redone from scratch each week.
The assistant publishes. To your own blog first, then cross-posted to wherever your audience actually reads.

The founder's job shrinks from "write a post" to "say what happened and then tidy someone else's draft of it." That is a much smaller ask of a Tuesday evening.

Pick one day and protect it, not a word count#

A weekly target measured in hours is easier to keep than one measured in words. Twenty minutes on a Thursday, same time each week, is a habit. "Write 800 words sometime this week" is a chore that gets pushed to Friday and then to never. Put the slot in the calendar as if it were a client meeting, because in a sense it is: it is the meeting with your future audience.

Keep a running list of raw material#

The biggest single reason founders stop is not lacking time to write, it is sitting down with nothing to write about. Keep a single running note, titled something plain like "blog ideas", and drop a line into it the moment something worth writing about happens: a support ticket that revealed a real problem, a decision you reversed and why, a number that surprised you. By the time your weekly slot arrives, you are choosing from three or four options instead of staring at a blank page.

What "good enough to publish" actually means#

A weekly post does not need to be definitive. It needs to be honest, specific, and short enough that you actually finish it. A 700-word account of one real decision beats a 2,000-word attempt at a comprehensive guide that stalls in draft for three weeks. Readers of a founder's blog are mostly there for the specific, not the exhaustive; save the exhaustive guide for the rare week you have the hours for it.

A simple weekly loop#

Day	Task	Time
Any day	Drop a one-line idea into the running note	1 minute
Thursday	Turn that note into a rough account, voice note or bullets	5 minutes
Thursday	Assistant drafts the post	a few minutes, unattended
Thursday	Edit and approve	15 to 20 minutes
Thursday	Publish to your own site, cross-post the rest	automatic

Where scatterpost fits#

The drafting and publishing steps above are exactly the loop scatterpost is built for: your AI assistant, whether that is Claude, Claude Code or Cursor, drafts and schedules the post through a set of tools, scatterpost publishes it to your own blog first and cross-posts it to Dev.to, Hashnode, LinkedIn, Bluesky and Mastodon with the canonical link intact, then reports back what happened. The thinking and the editing stay yours. The retyping, the formatting for five different platforms and the remembering to actually hit publish do not have to be.

A rhythm that survives a busy quarter is one where the founder's part of the job gets smaller every week, not bigger. Start there, and the weekly post stops being a resolution and starts being a habit.