Build a B2B content calendar

A pillar topic is a theme broad enough to anchor 20-50 pieces of content and narrow enough that your ICP cares about it on a Monday morning. Pick 3-5 pillars by intersecting three lists: the problems your ICP tells sales they are trying to solve, the themes your product has a credible point of view on, and the search universes where you have a realistic shot at ranking in the next 12 months. Avoid picking pillars that are only interesting to your product team; the test is whether a buyer would type the pillar name into a search bar. Document each pillar in one sentence with the buyer, the job-to-be-done, and the business outcome it drives, so writers and editors do not drift.

• List every recurring buyer problem from the last 50 sales calls or discovery notes.
• Cross-reference against product differentiators you can defend with evidence.
• Score candidate pillars on search demand, ranking difficulty, and sales relevance.
• Pick 3-5 pillars and write a one-sentence definition for each one.

Under each pillar, map the cluster: the supporting articles, how-to guides, comparison pages, and answer pages that link up to the pillar and to each other. A healthy cluster has one pillar page targeting the broad head term, 8-15 cluster pages targeting mid-tail queries, and a long tail of answer and how-to pages targeting specific buyer questions. Pull cluster candidates from keyword tools, Reddit and community threads, sales objection libraries, and the questions your support team answers every week. Draw the map in a mind-mapping tool or a simple sheet with pillar, cluster, and child columns, so the internal linking plan is visible before anyone writes a word.

• For each pillar, list the single head-term pillar page you will build or rewrite.
• List 8-15 cluster pages per pillar at the mid-tail difficulty level.
• List the answer, how-to, and comparison pages that will link up to each cluster.
• Document the internal linking plan from child to parent to pillar.

Not every cluster page should ship first. Prioritize by two axes: search intent (informational, commercial, transactional) and funnel stage (top, middle, bottom). Bottom-of-funnel commercial pages like comparisons, pricing explainers, and category pages usually drive pipeline fastest and should get the first slots. Top-of-funnel informational pages drive volume and backlinks but take longer to pay off. Score every candidate on monthly search volume, keyword difficulty, business value (how close to a sales conversation), and content effort. Sort by business value divided by effort and start shipping from the top. Keep a visible backlog so demand gen and SEO can see what is coming next quarter.

• Tag every candidate with intent (informational, commercial, transactional).
• Tag every candidate with funnel stage (TOFU, MOFU, BOFU).
• Score volume, difficulty, business value, and effort on a 1-5 scale.
• Rank by business-value-per-effort and freeze the top 20 as the quarter's queue.

A calendar without a named owner on every row is a wishlist. For each piece in the quarter queue, assign a writer (in-house, freelance, or SME-paired), an editor, a reviewer (usually product marketing or a subject-matter expert), and a target publish date. Match writers to clusters where they have real context, not just availability. Build in realistic time per piece: a 1,500-word SEO article takes 6-10 hours of writer time plus 2-3 hours of editing; a 4,000-word pillar page takes 20-30 hours end to end. If capacity does not match the queue, cut the queue, do not inflate deadlines you cannot hit. Make capacity math visible to leadership so the publishing commitment survives the first unexpected product launch.

• Name a single writer, editor, and reviewer for every row in the queue.
• Set draft, edit, and publish dates with buffer for SME review.
• Match writer specialization to cluster so research time stays bounded.
• Model total writer hours against capacity and cut the queue if it overflows.

Content without a workflow produces inconsistent quality and endless rewrites. Define four stages every piece moves through: brief, draft, edit, publish. The brief locks the target query, intent, outline, internal links, and the one argument the piece has to prove. The draft is written against the brief, not against a blank page. Edit is a structural pass (does the argument hold, do the examples earn their place, are the internal links in) followed by a line edit. Publish includes meta title, meta description, schema markup, hero image, internal linking QA, and a social and newsletter plan. Enforce the workflow in whatever tool your team already uses, so no piece skips a stage.

• Write a one-page brief template covering query, intent, outline, and internal links.
• Require every draft to be written against an approved brief, not from scratch.
• Separate structural edit from line edit so writers get the right feedback at the right stage.
• Checklist publishing steps (meta, schema, images, internal links, social, newsletter).

A content calendar lives or dies by visibility. Pick one tool (Notion, Airtable, Asana, ClickUp, or a dedicated editorial platform) and schedule every piece with status, writer, editor, publish date, target query, pillar, and cluster. Give demand gen, SEO, product marketing, and sales read access so the calendar becomes the source of truth across the GTM org. Color-code by pillar so pattern drift is visible at a glance. Build at least four weeks of forward schedule so one surprise does not collapse the whole plan. Link each row to the brief, the draft doc, and the final published URL so anyone can trace a piece end to end without asking in Slack.

• Pick one calendar tool and migrate every active and planned piece into it.
• Add status, pillar, cluster, writer, editor, target query, and publish date columns.
• Grant read access to demand gen, SEO, PMM, and sales leadership.
• Keep four weeks of forward schedule visible at all times.

The calendar is a plan; the standup is where it survives contact with reality. Run a 20-minute weekly editorial meeting with the writers, editors, SEO lead, and demand gen partner. Walk the next two weeks of the calendar row by row: what is on track, what is slipping, what needs an SME introduction, what is blocked. Review last week's publishes for traffic, rankings, and pipeline attribution so the team sees the outcome of their work. Close the standup with explicit owners and dates for any slipped item. Keep the meeting short and ruthless; the point is to unblock, not to brainstorm. Brainstorming belongs in the quarterly review.

• Walk the next two weeks of the calendar line by line.
• Review last week's publishes for traffic, rankings, and pipeline influence.
• Name an owner and a new date for every slipped row.
• End the meeting on time; brainstorming belongs in the quarterly review.

Every quarter, rebuild the queue against what actually worked. Pull traffic, rankings, backlinks, newsletter subscribers, and pipeline influenced for every piece shipped in the last 90 days. Which pillars drove the most pipeline per hour of writer time? Which clusters are ranking and which are stuck on page three? Which pages drove backlinks or newsletter signups? Retire pillars that are not earning their slot, double down on the ones that are, and refresh underperforming cluster pages with new data, new internal links, or stronger intent matching. Publish a short quarterly recap so leadership and GTM partners see the system working. Treat the calendar like a product backlog: versioned, measured, and reprioritized every 90 days.

• Pull traffic, rankings, backlinks, and pipeline influence for every piece shipped.
• Rank pillars by pipeline per writer hour and funnel-stage mix.
• Refresh underperforming cluster pages before commissioning new ones.
• Publish a short quarterly recap to leadership, demand gen, and sales.