Every slot carries a pillar and a job, at a cadence you can actually sustain.
Build a 6-week LinkedIn calendar. We can realistically do 3 posts a week.
Eighteen slots across six weeks, with three held back for reactive posts. Two pillars had no coverage in the last quarter and now get a third of the slots. Nine existing posts supply eleven of the eighteen topics, so only seven need original research.
A social media content calendar template that hands you an empty grid has moved the hard problem, not solved it. This one starts from your content pillars, assigns every slot a pillar and a job — demand, proof, or point of view — and sizes the cadence to the output you can genuinely sustain.
A schedule where each slot already has a pillar, a job, and a format assigned before anyone writes. That constraint is what stops a calendar from filling up with whatever was easiest to produce that morning.
The highest frequency you can hold for three months without dropping quality — for most B2B teams two to four posts a week. Five-a-week calendars that collapse in month two perform worse than three-a-week calendars that survive.
A ratio across pillars and jobs so the feed does not become all product or all commentary. The template flags weeks where one job dominates, because that imbalance is invisible in a grid view and obvious to a reader.
By scheduling it deliberately. Each long-form asset gets slots for the specific angles worth extracting, which is different from posting the same summary three times and calling it distribution.
The agent takes your pillars and voice from workspace Knowledge, and can read published blog posts or campaign plans to schedule repurposing against real assets. Calendars export to Notion, Google Sheets, or Airtable with pillar, job, format, and owner per slot, and pair with the content pillar map when the pillars themselves need defining first.
Or run the content pillar map first if the pillars are not defined.
Posts per week you can hold for three months, not your best week.
Each slot shows pillar, job, and format; job balance is flagged per week.
Push to Notion, Sheets, or Airtable with owners and draft dates.
Every slot has a pillar and a job before it has a topic
Cadence sized to sustainable capacity, not ambition
Flags weeks where one job dominates the feed
Repurposing is scheduled against real assets
Define pillars, decide a cadence you can sustain, then assign each slot a pillar and a job before filling in topics. Starting from topics produces a calendar that drifts toward whatever is easiest to write.
Two to four times a week for most B2B accounts. Consistency beats frequency — an account that posts three times weekly for a year outperforms one that posts daily for six weeks and stops.
Four to six weeks of assigned slots, with reactive capacity held back. Planning a quarter in detail guarantees rework, because the interesting posts respond to things that have not happened yet.
Balanced across your pillars with no single job dominating a week. The specific ratio matters less than avoiding the failure mode where every post is product news.