A month of founder social content fits inside one three-hour session, but only if the session is built as five separate passes: collect sources, choose angles, draft, review, schedule. The version that fails is the blank-calendar version, where you open the scheduler and try to invent, write, judge, and place twenty posts in a single motion. That approach produces three good posts, four weak ones, and a closed laptop.
Batching works because it groups work by mental mode instead of by post. You do all the remembering at once, all the deciding at once, all the writing at once. Each pass is easy in isolation. Only the combination is exhausting.
Why context-switching kills founder content
Every post asks for four different kinds of thinking: recall (what happened), judgment (what matters and to whom), craft (how to say it), and criticism (is it true and would I sign it). Handling one post end to end means switching modes four times. Handling twenty posts one at a time means paying that switching cost eighty times, which is why ad hoc posting collapses in any week the product demands attention.
For a founder the cost is worse than lost time. Content decisions made in the gaps between real work default to the safest possible post, and safe posts are the ones nobody replies to. A batching session moves all the deciding into one block where you can hold the month in your head and cut the weak ideas before they cost writing time.
The three-hour session, pass by pass
Times below assume 16 to 20 posts for the month. The rule that makes the structure work: finish each pass for every post before starting the next. Drafting stops the moment you begin polishing a sentence, because polishing is review, and review has its own pass.
If three hours in one block is unrealistic, halve everything and batch two weeks at a time. The pass structure matters more than the horizon; a fortnightly ninety-minute session with clean passes beats a monthly marathon that dissolves into per-post tinkering.
| Pass | Time | The job | Output |
|---|---|---|---|
| 1. Source collection | 30 min | Empty the notes file: releases, customer questions, decisions, numbers, opinions that survived the month | 8 to 12 dated source notes |
| 2. Angle selection | 25 min | Give each surviving source a job and a primary platform; kill anything without evidence or a reader | 16 to 20 one-line briefs |
| 3. Drafting | 60 min | Write or generate a platform version for every brief, in order, without editing | A rough draft for every brief |
| 4. Review | 35 min | Fact-check, voice-check, cut; read as an editor, not as the author | Approved drafts, and a few honest rejections |
| 5. Scheduling | 30 min | Place approved posts across the month, leave open slots, set holds on date-sensitive drafts | A scheduled month with deliberate gaps |
The session agenda, ready to copy
Preparation is what makes the three hours enough. The agenda assumes one thing exists before you sit down: a running notes file you have been feeding all month with anything that might become a post. Two lines per item is plenty. The session consumes the file; it does not stare at a blank page.
- Capture all month, in two lines each: shipped changes, customer phrasing worth quoting, numbers that moved, opinions you defended on a call.
- Book the same afternoon every month and treat it like a customer call.
- Bring the notes file, last month's results, and the roadmap for the coming month.
- Work the five passes in order; no skipping ahead to a post you are excited about.
- During drafting, a bad sentence gets a bracket and a note, not a rewrite.
- During review, reject drafts with a reason so next month's briefs improve.
- End by scheduling, then close the tool. Mid-month edits happen in the open slots, not in the batch.
0:00 Sources
Empty the notes file and the changelog into a list. Date each item. No judging yet.
0:30 Angles
Assign each keeper a job (teach, argue, show, ask) and a primary platform. Kill the rest out loud.
0:55 Drafts
Write every draft in one run. Momentum over polish. Brackets for anything uncertain.
1:55 Review
Break first, then read everything as a skeptical editor. Check facts, cut filler, reject freely.
2:30 Schedule
Place the month, spread the heavy posts, hold anything tied to an unshipped date.
What breaks batching
Batching fails in two predictable ways. The first is stale news: a 'we just shipped' post drafted three weeks before the ship date, which then slips. The second is fake spontaneity: a 'thinking about this today' post written a month ago, which reads false the moment a real event contradicts it. Both are lies of timestamp, and readers are better at spotting them than founders expect.
A quieter failure is batch monotony. Twenty posts written in one afternoon can carry one afternoon's mood, and a month of them reads like a single long thread. The fix lives in pass two, where you deliberately vary the jobs across the month, and in pass five, where you reread the scheduled month top to bottom before closing the tool.
- Anything tied to an unshipped date gets scheduled as a hold and confirmed the week it publishes.
- Write batched posts in a timeless register; save 'today' language for posts you actually write today.
- When a launch moves, search the batch for every post that references it before the first one fires.
- If a scheduled post has been overtaken by events, pull it. An empty slot costs nothing; a tone-deaf post does.
Leave room to be alive
Schedule 60 to 70 percent of your posting slots and leave the rest empty on purpose. The open slots are for launches, replies that deserve a full post, and reactions to things that actually happened that week. A calendar batched to 100 percent reads like a broadcaster; the batch should be the reliable floor under a live presence, not a replacement for one. As a starting ratio, a sixteen-slot month gets eleven scheduled posts and five holes.
Review is also where an approval habit pays off. Batched drafts are approved in one sitting with fresh eyes, which is exactly the setup a lightweight approval workflow formalizes, and it is the reason AI drafts belong in a batch: generation is cheap in pass three when every draft waits for your judgment in pass four.