Lesson 4 of 87 min read

Plan a month in one sitting

Turn your pillars and source list into a month of scheduled posts in one afternoon, with a cadence per network and room for launches.

In this lesson you will

  • Choose a cadence per network you can actually keep
  • Fill a four-week grid from your pillars and source list in one sitting
  • Leave room for launches, replies and the things you can't plan

Posting "when we have something to say" is how most SaaS accounts end up posting twice in a week and then nothing for a month. The problem is not discipline. It is that deciding what to post, writing it and publishing it are three different kinds of work, and doing all three every day costs far more than doing each once.

Batching fixes this. Once a month, in one sitting of about three hours, you decide the whole month: which pillar goes on which day, which source feeds which post, which slots are held for launches. Then you write in batches and schedule everything. The rest of the month, your daily social work shrinks to replies and the occasional timely post. This lesson walks through that sitting step by step.

Before the sitting: pick a cadence you can keep

Cadence is how often each account posts on each network. The most common mistake is picking the cadence of a company ten times your size. A cadence you keep for six months beats an ambitious one you abandon in three weeks.

Starting cadences for a small SaaS team:

NetworkCompany accountFounder accountNotes
LinkedIn3 a week3 a weekThe main B2B network for most SaaS buyers
X4 to 5 a week3 to 5 a weekShorter posts; threads for how-tos
Bluesky3 a weekOptionalOften the same idea as X, reworded
Your community (Discord or Slack)1 to 2 a weekReplies onlyUpdates and questions, not marketing
YouTube or TikTok1 a week or noneNoneOnly if you can make a short demo every week

Decision rules:

  • If you can't keep a network weekly, drop it for now. A quiet account looks worse than no account.
  • If two networks get the same post, reword it. Same idea, different first line and length. Readers who follow you on both will notice copy-paste.
  • If you only have time for one network, pick the one where your buyers ask questions in public. For most B2B SaaS that is LinkedIn; for developer tools, often X or Bluesky.

Add up the slots. A team running the cadence above for the company account on LinkedIn, X and Bluesky has around 40 to 45 slots a month. That number is your target for the sitting.

The sitting, step by step

Block three hours. Close the inbox. Have your positioning, message bank, pillars, source list and parked drafts open.

Step 1: mark the fixed dates (15 minutes). Put in everything you already know: planned releases, a launch, events, webinars, holidays when your buyers are offline. Launches get their own block of slots; lesson 5 covers how to fill it.

Step 2: assign pillars to slots (20 minutes). Use the mix from lesson 3 as a starting point. Spread each pillar across the week so no day is all product updates. A simple pattern for a three-a-week network: Monday how-to, Wednesday customer problem, Friday product update or behind the scenes.

Step 3: assign sources to slots (30 minutes). For each slot, name the source it will come from: a docs page, a changelog entry, a support question, a blog post. Start with your parked drafts; they are free. If a slot has no source, mark it "open" rather than inventing a topic.

Step 4: write in batches (90 minutes). Write all the how-to posts together, then all the customer-problem posts, then the rest. Writing the same kind of post in a row is faster than switching. Write the longest version first (usually LinkedIn), then shorten for X and reword for Bluesky.

Step 5: schedule and review (25 minutes). Put everything on a calendar. Then read the month top to bottom as a follower would: does any week repeat itself, is any network silent for a week, does every week have at least one post that is not about your product?

What to leave unplanned

A fully planned month is brittle. Leave room for things you cannot predict:

  • Hold one open slot a week per main network. Fill it with whatever happened: a customer win, a sharp question, a market event.
  • Do not schedule replies. Replies are daily work and the subject of lesson 7.
  • Keep a short pause rule. If something serious happens (an outage, bad news in your market, a public tragedy), pause the whole schedule first and decide later. A cheerful scheduled post during an outage costs more trust than a month of good posts earns.

The review checklist for step 5

Before you close the sitting, run through this list once:

  • Every week has at least one post that is not about your product.
  • No two networks carry the same first line on the same day.
  • Every link is the right one, and every link to your own site is tagged (lesson 8 explains why).
  • Every post that names a customer, a price or a security topic has been through approval (lesson 2).
  • The open slots are spread out, not bunched at the end of the month.
  • Nothing is scheduled for a day you already know your buyers are offline.

If you fix only one thing, fix the first: a month of nothing but your own product is the most common reason a planned calendar still feels like an ad.

Worked example: how we plan a month for our accounts

Here is how we lay out a month across our primary accounts: X, LinkedIn, Bluesky and our Discord community. This is our process, not a report of results.

Our grid has one row per day and one column per network. We fill it in this order: releases from our changelog, then blog posts from our blog, then how-tos built from our free tools, then open slots.

One week from that grid looks like this:

DayXLinkedInBlueskyDiscord
MonHow-to thread from a free toolHow-to post, same tool, longerShort how-to, reworded—
TueChangelog post: one shipped feature—Changelog post, rewordedRelease note with a question
WedCustomer problem from a support themeCustomer problem, longer——
ThuOpen slotBehind the scenes: a decision and whyOpen slot—
FriWeekly recap with links—Weekly recap—

And here is how one source, the hook library we shipped, fills three slots in that week.

The how-to thread on X, first two posts:

The first line of a post decides whether anyone reads the second.

Here's how we pick one, using the hook library we just shipped. 1/5
Start from the goal of the post, not the network. Teaching something needs
a different opener than promoting something. Pick the goal (education,
engagement, authority, promotion, connection), then browse the openers
written for it. 2/5

The LinkedIn how-to, same idea, longer:

Most posts lose the reader at the first line.

When we write a post, we name its goal first: teach, start a conversation,
show expertise, promote, or connect. The hook library in our templates is
grouped the same way, with patterns like "Myth vs Fact", "How We Did It"
and "Before and After", and you can send one straight to the composer.

Our own rule: write the post first, choose the hook last. A hook written
first tends to promise more than the post delivers.

The Discord note, Tuesday:

New: a hook library for first lines, grouped by what the post is for. If you
try it, tell us which goal you wish had more patterns.

Notice that the LinkedIn version adds an opinion ("choose the hook last"), so it is not just a longer copy of the X post.

Two ways to fill the calendar faster

Once you have run the sitting by hand a couple of times, you can speed up step 4 and step 5:

  • A spreadsheet import. Keep the grid in a spreadsheet with one row per post (date, time, network, text, link) and import it into a scheduler in one go. Our bulk scheduling page describes how that works in FoPost: every row is checked and previewed before anything is queued.
  • Queue slots. Instead of picking a time for every post, set fixed weekly times per account and drop posts into the next free slot. This keeps cadence steady even when your writing is not.

Recap

  • Pick a cadence per network you can keep for six months; drop any network you can't post to weekly.
  • Plan the whole month in one three-hour sitting: fixed dates, pillars, sources, batch writing, schedule and review.
  • Write the same kind of post in a row, longest version first, and reword rather than copy across networks.
  • Leave an open slot a week per main network, never schedule replies, and keep a pause rule.
  • Once the routine works by hand, use a spreadsheet import or queue slots to make it faster.

Exercise

Fill a four-week grid

  1. Open any free spreadsheet and make a grid: one row per day for the next four weeks, one column per network you will post to.
  2. Mark fixed dates first: releases, launches, events, holidays.
  3. Fill each slot with a pillar and a source from your lesson 3 list. Mark slots with no source as "open".
  4. Write one week of posts in batches, longest version first. Use the LinkedIn caption generator for a first draft if you are stuck, then rewrite it with your message bank.
  5. Check every X post with the X character counter and split any that run over.
  6. Read the week as a follower would and fix any day where every network says the same thing.

Done looks like: a four-week grid with every slot assigned a pillar and a source (or marked open), and one full week of posts written and checked.

Go further

The agent

In FoPost, you can describe the month in one sentence to the agent, for example "plan four weeks of LinkedIn and X posts from our last three blog posts and this month's changelog", and it drafts every post into a plan you approve before anything is scheduled. Review and drag posts around on the calendar afterwards. See the agent for how campaigns are planned and approved.

Check yourself

  1. 1Why should you drop a network you cannot post to weekly?

    A quiet account looks worse to a buyer than no account. Keep only the networks your cadence can actually cover.

  2. 2Why write the same kind of post in a row during the sitting?

    Switching between kinds of work is slow. Writing all the how-tos together, then all the customer-problem posts, is faster than alternating.

  3. 3What should you do with your schedule if something serious happens, like an outage?

    Pause the whole schedule first and decide later. A cheerful scheduled post during a crisis costs more trust than the plan is worth.

Academy

Keep reading, free

Tell us a little about you and the rest of this lesson, and every lesson in every course, opens on this device. No account and no card.

What describes you best?
Where do you post today? Pick any that apply.
What do you want most right now?

We use your answers to suggest lessons and to improve the Academy. They are never shown publicly. Read our Privacy Policy.