Lesson 3 of 87 min read
Content pillars from material you already have
Build four content pillars for your SaaS and a source list from your docs, blog, changelog and support questions, so you never start from a blank page.
In this lesson you will
- Choose four content pillars that map to your positioning
- Build a source list from material your team already wrote
- Turn one source into several posts without repeating yourself
The blank page is the most expensive part of social media for a small SaaS team. Writing a post takes ten minutes. Deciding what to write about takes forty, and most of that time ends in a vague post about "productivity" that nobody needed.
Here is the good news: a SaaS company produces raw material every week without trying. Docs pages, release notes, blog posts, support answers, sales call notes, onboarding emails, the bug that took three days to find. Each of those already contains a problem, an answer and proof. This lesson shows you how to sort that material into four content pillars and a source list, so every week starts with a shelf of material instead of a blank page.
What a content pillar is
A content pillar is a recurring topic you post about on purpose. It is not a format (threads, carousels) and it is not a network. It is a category of "why someone would care".
For most B2B SaaS companies, four pillars cover nearly everything:
- Product updates. What shipped, what changed, how to use it. Proves the product is alive and getting better.
- Customer problems. The pain your positioning names, described in detail, with or without your product in the post. Proves you understand the buyer.
- How-to. Teach the job your product helps with, including the parts you do not automate. Proves you are useful even before someone signs up.
- Behind the scenes. Decisions, tradeoffs, mistakes, numbers you are comfortable sharing. Proves there are thoughtful people behind the logo.
Each pillar should map back to the message bank you wrote in lesson 1. If a pillar cannot carry at least two of your messages, swap it for one that can. A developer tool might replace "behind the scenes" with "the stack" (how things work under the hood). A compliance product might add "regulation explained". Keep it to four. More pillars means each one shows up too rarely to become recognizable.
A rough mix to start with
You will adjust this after lesson 8, but start with something like:
| Pillar | Share of posts | Main source | Typical CTA |
|---|---|---|---|
| Product updates | 25% | Changelog, release notes | Link to the changelog entry or docs |
| Customer problems | 25% | Support tickets, sales notes, public questions | A question back to the reader |
| How-to | 35% | Docs, blog, onboarding emails | Link to the guide |
| Behind the scenes | 15% | Team notes, decisions, retros | None, or "reply with your take" |
How-to gets the largest share because it is the pillar that most often reaches people who do not know you yet. Product updates matter, but a feed of nothing but releases reads like an ad.
Where the material already is
Make a source list: every place your team already writes something a buyer might find useful. Here is a checklist to work through.
- Changelog or release notes. One entry is often three posts: what changed, why, and how to use it.
- Docs. Every page answers a question someone had. The "getting started" and "troubleshooting" pages are the richest.
- Blog. Each post can feed a week: the main point, two supporting points, a quote, a question.
- Support inbox. The questions you answer more than twice a month are posts. Strip the customer details; keep the question.
- Sales and demo notes. The objections you hear on calls are the comparison and "not for you if" posts.
- Onboarding emails. These are already short, tested how-tos.
- Comparison pages. If you have them, each row in a comparison table is a post about one difference.
- Internal decisions. Pricing changes, why you dropped a feature, what you learned from an outage (only what is safe to share).
For each source, note three things: where it lives, how often it changes, and which pillar it feeds. That list is your shelf.
Worked example: our own source list
Here is our own source list, sorted by pillar. Every item is public, so you can look at them.
| Source | Where | Pillar |
|---|---|---|
| Our changelog | /changelog | Product updates |
| Our blog | /blog | How-to, customer problems |
| Our compare pages | /compare | Customer problems (the "why switch" questions) |
| Our free tools | /tools | How-to |
| Our post templates | /templates | How-to, behind the scenes |
| Our public roadmap | /roadmap | Behind the scenes |
And here is how one source becomes several posts. Take one free tool, our UTM generator. It is a how-to source. One tool page gives us:
A how-to post for LinkedIn:
If you post a link to your site on social and never tag it, your analytics
file the visit under "referral" or "direct" and you can't tell which post
sent it.
Three fields fix that:
- source: the network (linkedin)
- medium: social
- campaign: what the post was about (launch-week)
We made a free generator so you don't have to remember the format: [link]
A customer-problem post for X:
"Social doesn't bring us signups."
Maybe. Or maybe it does, and the visits are landing in "direct" because
the links weren't tagged.
Check before you cut the budget.
A behind-the-scenes post for Bluesky:
Why we build free tools that don't need an account: most people need the
answer to one small question today, not a new subscription. The tool answers
it. If they need more later, they know where we are.
Three posts, three pillars, one source, and none of them repeats another's wording. That is the pattern: one source, several angles, each in its own pillar.
Turning one source into posts: a repeatable method
For any source, ask five questions and write one post per good answer:
- What problem does this solve? That is a customer-problems post.
- What are the steps? That is a how-to post, or a thread.
- What did we decide, and why? That is a behind-the-scenes post.
- What changed? If it is new, that is a product-update post.
- What would someone get wrong? That is a myth-busting or mistake post, which tends to draw replies.
Not every source answers all five. Most answer two or three. A source that answers none is not worth posting about.
Time budget: about 15 minutes per source for three drafts once you have done it a few times. If a source takes longer, you are probably rewriting it from scratch instead of pulling from it.
Support questions: the richest source, handled with care
Support questions are the best raw material most SaaS teams ignore. They are written in the buyer's words, they name a real problem, and if one person asked, many more wondered. They also carry the most risk, because they come from customers who did not agree to be content.
Rules we follow before a support question becomes a post:
- Strip everything that identifies the customer. No name, company, screenshot of their account, or detail specific enough to recognize them.
- Keep the question, rewrite the wording. Paraphrase so that the customer would not find their own sentence quoted back at them.
- Never post a bug that is still open as if it were fixed. If it is open, the post is about the workaround, or it waits.
- Answer the general version. "How do I schedule the same post to two time zones?" is a how-to. "Why did my post fail on Tuesday?" is a ticket, not a post.
A before and after. The raw ticket:
Hi, our marketing lead set up the LinkedIn page last week but the posts
keep going to her personal profile instead. We're on a deadline, help!
The post it becomes:
A common setup mix-up on LinkedIn: connecting your personal profile when
you meant to connect your company page.
They are two different connections. If your company posts keep landing on
a person's profile, reconnect and pick the page, not the profile.
No customer, no deadline, no blame, and the next person with the same problem finds the answer before they need to write in.
Keep the drafts you don't use
You will write more drafts than you post. Keep them. A draft that did not fit this week is often exactly what you need in six weeks when a customer asks the same question again or a related feature ships. Keep a "parked" list next to your source list: the draft, its pillar, and the source it came from.
When you plan a month (lesson 4), you start from the parked list and the source list, not from a blank page.
Recap
- Four pillars cover most SaaS content: product updates, customer problems, how-to and behind the scenes.
- Map each pillar to your message bank from lesson 1; drop any pillar that cannot carry two messages.
- Your source list is material you already wrote: changelog, docs, blog, support answers, sales notes, comparison pages.
- Ask five questions of every source and write one post per good answer, each in a different pillar.
- Keep the drafts you do not use; they are next month's plan.
Exercise
Build your source list and first drafts
- List every place your team already writes for customers: changelog, docs, blog, support answers, onboarding emails, sales notes. Aim for at least eight sources.
- Next to each source, write which of your four pillars it feeds and how often it changes.
- Pick one source and answer the five questions above in a sentence each.
- Turn the two best answers into posts. Paste the source text into the LinkedIn caption generator to get a first draft, then rewrite it in your own words using your message bank.
- Park any draft you will not use this week in a "parked" list with its pillar and source.
Done looks like: a source list of eight or more items tagged by pillar, two finished drafts from one source, and a parked list started.
Go further
Sources and collections
In FoPost, paste a link to a blog post or changelog entry into the agent or the composer and ask it to write from it.
Check yourself
1Why does how-to get the largest share of posts in the starting mix?Show answer
It is the pillar most likely to reach people who do not know you yet, and it is useful even before they sign up. A feed of only releases reads like an ad.
2What should you do with a pillar that cannot carry at least two messages from your message bank?Show answer
Replace it with one that can. Pillars should all point back to your positioning.
3Why keep drafts you did not post?Show answer
They often fit a later week, when a related feature ships or a customer asks the same question again, so the next month starts from material instead of a blank page.
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.