How to Never Run Out of Content Ideas (Founders)

"I do not know what to post" is almost never true. What is true is that you forgot the six things worth posting that happened this week, because you did not write them down when they happened. Idea drought is a memory and capture problem wearing a creativity costume. Fix the capture habit and the drought disappears.

Why do founders run out of content ideas?#

Because they try to invent ideas on the spot instead of capturing the ones that appear all week. Good post ideas show up constantly, in a customer question, a thing you fixed, an opinion you blurted out, and then they evaporate by the time you sit down to write.

I lived this for a long time. I would open the composer cold on a Monday, stare, and conclude I had nothing to say, when in reality I had answered three sharp questions in DMs that same week. The ideas were there. I just never wrote them down. Nobody is creative on demand at 9am. Everyone is creative in the moment.

Where do the best content ideas actually come from?#

From sources already around you, not from a brainstorm. The strongest ones are questions and moments where someone already showed they care. A real question makes a real post, because you know at least one person wanted the answer.

Here are the sources I lean on and the kind of post each one becomes:

Source	What to look for	Example post
DMs	A question someone asked you directly	"Someone asked how I price as a solo founder. Here is my honest answer."
Support tickets	The same problem reported twice	"Three people hit this same setup snag this week. Here is the fix."
Your week	Something you shipped, learned, or broke	"I shipped a feature nobody used. Here is what I got wrong."
Your opinions	A take you actually hold	"I think most founders post too often. Here is why."
FAQs	The questions you answer constantly	"The five things people ask before they sign up, answered."

Every row is a post you can write without inventing anything, because the idea came from a real moment.

The DM and support sources are the ones founders sleep on most. If someone took the time to ask you a question, that question is validated demand for an answer. Other people have it too and just did not ask. The same goes for a support ticket that lands twice: the second time you see it, it is a post, not just a fix. Your FAQs are the strongest of all, because by definition they are the questions asked most often. Answering one in public can save you the same conversation fifty times and double as content. I have written single posts that quietly cut my inbox in half, just by answering the thing everyone kept asking.

How do you build a capture system that actually works?#

Keep one place, and drop the raw idea into it the second it appears. Not the finished post, just the seed: a question, a sentence, a link. The whole point is to remove the gap between having the idea and recording it, because that gap is where ideas die.

Mine is embarrassingly simple. One note on my phone, and a habit of pasting good DM questions straight into it. When something annoys me or surprises me, one line goes in the note. That is it. The system only works if capturing is faster than forgetting, so do not make it fancy. A messy list you actually use beats a tidy database you do not.

The one rule I hold to is to capture the raw thing, not a cleaned-up version. If a customer asks "how do you handle pricing when you are tiny," I save that exact sentence, not "write a post about pricing." The exact wording carries the energy and the angle. When you sit down to write later, a real question is half a post already, while a vague topic line is still a blank page in disguise. The closer your captured note is to the real moment, the easier the writing gets.

How do you turn raw ideas into actual posts?#

Write in batches, not one at a time. Once a week, open your capture note and turn the strongest seeds into posts in a single sitting. Separating capture from writing is the trick. You collect all week with no pressure, then write when you are in the mood to write.

This is also where one idea multiplies. A single DM answer can become an X post, a longer LinkedIn version, and a thread, which means one seed covers several days. I broke that down in how to repurpose one idea into ten posts. And if you are early and feel you have nothing to show yet, your process and your small wins are still content, which I cover in build in public when you have nothing to show.

What if you serve a specific platform like LinkedIn?#

Tailor the source to the platform. The same capture habit works everywhere, but the framing shifts. On LinkedIn, founder lessons and behind-the-decision posts tend to land harder than quick tips, so favor seeds from your week and your opinions there. The capture stays the same. The selection changes.

The point is that you are never picking ideas from nothing. You are picking from a backlog you have been quietly filling. If you want platform-specific angles, I wrote what to post on LinkedIn as a founder. And once you have the ideas, the bottleneck becomes publishing them consistently, which is what the scheduling guide for solo founders is built to solve.

Where to start#

Open one note right now and title it "post ideas." For the next three days, drop in every question someone asks you and every small thing you ship or learn. Do not write any posts yet. By day three you will have more ideas than you can use, and the drought will be over.