You have thirty minutes, a free afternoon, a fresh cup of coffee, and X (formerly Twitter) open in a tab. You also have nothing to say. So you close the tab, tell yourself you'll post tomorrow, and tomorrow goes the same way.

Most founders diagnose that as a discipline problem. They buy a posting calendar, block time in the morning, set a reminder to be consistent. Two weeks later the calendar is empty and the reminder is muted, because the diagnosis was wrong. You were not short on discipline. You were short on raw material.

Topics are not invented at the moment you sit down to write. They are harvested from work you already did this week: the objection a prospect raised three times, the support thread that took an hour, the feature debate that split the team. That material is already sitting in your week, and almost none of it ever reaches a post.

This guide is a sourcing sequence for founders with a product to run and no content team. Four steps, roughly thirty minutes a week, plus one step that turns out to be the whole game and gets skipped by nearly everyone.

The Blank Box Problem Is Not a Discipline Problem

A founder who blocks thirty minutes to post and writes nothing concludes they need to try harder. What actually happened is simpler: they opened a writing tool with no input.

Think about what a blank box asks of you. It asks you to generate an idea from nothing, then judge it, then write it, all inside one sitting. That is three jobs stacked in one slot, and the first one is the hardest.

The founders who post consistently are not more inspired. They keep a raw pile of material and empty it into posts. Their sitting is the second half of a process that started days earlier, when they noticed something.

Here's the pattern worth stealing. A founder in the middle of a sales week stops posting entirely, gets on three calls, hears the same objection each time (in this case, "we already have a tool that does that, it just doesn't tell us who to talk to"), then writes one post about that specific objection. It does more for their pipeline than the previous month of scheduled posts combined. Nothing about their effort level changed. They just stopped starting from an empty page.

That is the practical difference between a discipline problem and a sourcing problem. You cannot out-discipline an empty page. You can feed it.

Where Topics Actually Come From

There are three sources of topics, and most sole operators use only one of them.

Your own work. Objections from calls, support tickets, feature trade-offs, the mistake you made last quarter. The speeches you give to prospects inside a call, minus the pitch. This is the highest-trust source and the lowest-volume one, and it is the reason your posts can sound like a person instead of a brochure.

Search demand. What people type into Google or the X search bar about your problem. It tells you the words buyers use, and it is the fastest way to find the shape of the demand. It is also the reason so many feeds feel interchangeable: answer only from search demand and your post could have been written by anyone in your category.

Live conversation. What people are saying in public right now: asking for a tool that does a specific job, weighing two options, complaining about what they bought. This is the highest-relevance source and the one that takes the most effort, because it does not come to you.

Here's the tell for which source you are working from. If a post could have been published by any other founder in your category without changing a word, it came from search demand alone. That is not a failure. It is a signal that you are writing something generically useful instead of something specifically yours.

The reframe this guide asks for: sourcing is research, not creativity. Writers do not wait for topics. They collect them, and they treat collection as an ordinary part of the work week.

A founder I'd point to as an example keeps a note with every question a customer has asked twice. Three recurring questions becomes three posts minimum, and each one arrives with proof attached that someone cares about the answer.

The Sequence, Step by Step

Step 1: Write your niche sentence

One line: who you help, and with what. "I help bootstrapped SaaS founders find out-of-network leads on X" beats "I help people grow."

Every candidate topic gets tested against this sentence. Without it, every topic looks vaguely plausible, which means none of them is sharp. With it, you can kill a mediocre topic in five seconds, which is the actual time savings of the whole system.

Step 2: Harvest your own week

Ten minutes. Scan your calls, your DMs, your support threads, and your own notes, looking for tension: anything someone pushed back on, misunderstood, or asked twice.

You are not looking for your best story. You are looking for the friction. The part of the conversation where the person leaned in. Write those down as fragments, not full sentences. This layer is free, and it is the layer no competitor can copy because it is made of your week.

Step 3: Filter with the buyer test

Ask: would someone who has the problem you solve stop scrolling for this?

If the honest answer is "other founders would enjoy this," it is a peer post, not a buyer post. Both are legitimate, and they do different jobs. Peer posts earn you a reputation. Buyer posts earn you conversations. What matters is knowing which one you wrote, because the metrics that make you feel good (likes from peers) are not the metrics that move your pipeline.

Step 4: Go where the demand is already stated out loud

This is the step almost everyone skips, and it is the one that keeps the machine from running dry.

Instead of guessing what people want to hear about, read what they are already asking. You are not brainstorming a topic list. You are reading a list that the market has already written. The next section covers how, because it is the difference between a topic list that works for a month and one that works for years.

The sequencing matters: steps 1 through 3 are desk work you can do alone. Step 4 is the one that takes you out of your own head, which is exactly why it gets dropped the first busy week.

The Step Almost Everyone Skips

Step 4 gets skipped for three predictable reasons. It feels like scrolling, so it does not register as work. It has no obvious output. And it does not work if you do it once, which makes it easy to dismiss after a single attempt.

Here is where the demand is already sitting, in order of usefulness.

Questions aimed at nobody in particular. Someone posts "anyone know a tool that does this?" with no shortlist and no strong opinion about where to find one. The asker has a problem and an empty shopping list. That is the highest-intent topic source available to you, because the answer you write is also the answer a hundred quiet readers were looking for.

Comparison posts. Someone weighing two options and naming what frustrates them about both. This tells you which axis buyers actually care about. If everyone complains about the same limitation in the same category, you have just found your differentiation, written by your buyers instead of your marketing.

Complaints about the last purchase. A churned customer describing exactly what the tool failed to do. Read enough of these and your positioning writes itself, because you are quoting the gap in the market rather than guessing at it.

Repeated phrasing. When ten people describe the same problem in the same words, that phrasing belongs in your title. It is the closest thing to free keyword research you will ever get.

The mapping rule is simple: one conversation you can answer from experience is one post. Not a thread, not a hot take. One useful answer, published where the audience already gathers.

The frequency constraint, stated honestly: fifteen to twenty minutes a day beats a three-hour session once a month, because the value is in catching a live conversation while it still has an audience. A week-old thread is a document. A live thread is a conversation you can join.

If you want that discovery step done for you, a layer like X Growth Engine exists to surface conversations from people you do not already follow. It handles the finding. The rest, which is being genuinely useful in the reply and turning it into something worth reading, stays with you.

Install Free →

One failure mode to name before you move on: collecting screenshots of great conversations and never turning them into posts. Collection is not sourcing until it becomes a draft. A folder of screenshots is a hobby with extra steps.

Turning Topics Into a Queue You Can Actually Work

A weekly routine, thirty minutes, once:

Fifteen minutes in the conversation layer, collecting candidates. Fifteen minutes drafting the strongest three into rough outlines. Three real drafts a week beats seven sessions of staring at a blank box, and it takes a third of the calendar time.

The "worth writing" test, applied after collection rather than before:

Can you add something the existing answers do not? If not, skip it. Being the fourth reply that says the same thing adds nothing for the reader and nothing for you.
Is there tension worth stating? Agreement is fine. Disagreement gets read.
Will it still be useful in six months, or is it a news cycle? Both have a place. Label them so you do not judge an evergreen post by trend-post numbers.

The "not worth writing" list, so the queue stays small enough to work:

Trend reactions with no product relevance
Follower-count commentary
Engagement-bait questions with no substance
Anything you would have to invent data to support

Batch the peer posts, because they only need your thinking. Keep the buyer-facing topics for when the conversation is live, because they need the audience that has already gathered. The operating rhythm this queue plugs into is covered in the Social Media X operating system, and the reply craft it feeds is covered in how to turn Twitter replies into customers.

How to Tell Whether It Is Working

Diagnose by stage, not by feel. Each symptom below points at a different broken link in the chain.

No topics collected: step 4 is not happening. You are still brainstorming, and no amount of scheduling fixes that.
Topics collected, nothing published: the collection loop is not connected to a drafting slot. Give it a fixed thirty minutes a week and it will fill.
Published, no replies: the topic passed the peer test and failed the buyer test, or your first line buried the tension. Tighten the opening before you change the topic.
Replies, no profile visits or DMs: the post worked and the profile did not carry the next step. That is a profile problem, and the fallback that converts visitors into followers walks through it.
Replies and DMs, no real conversations: you are being read by peers rather than buyers. Rebalance toward the question-and-complaint sources.

The metric that matters early is simple: how many of your posts started from a conversation someone else had. A rising number means sourcing is working, regardless of how any single post performed.

Set your expectations for the shape of the results. This is an audience-building layer, not a spike generator. It compounds in weeks, not days. If you want the measurement side, how to measure whether your Twitter strategy is actually working covers which numbers deserve attention and which are decoration.

The Short Version

Topics are collected, not invented. If you are staring at a blank box, you are skipping the collecting.
The sequence: write your niche sentence, harvest your own week, run the buyer test, then go where the demand is already stated out loud.
The skipped step is the one that matters. Read the questions, comparisons, and complaints already sitting in your niche, then answer one of them properly.
Three real drafts a week beats seven sessions of trying to think of something.
One post per conversation you can answer from experience. The queue builds itself once you stop starting from a blank page.

FAQ

Why do I run out of things to post even when I post consistently? Because consistency addresses the publishing half of the problem and not the sourcing half. A calendar can hold a slot open, but it cannot fill it. The founders who keep posting are the ones who keep collecting, which is why fifteen minutes a day beats a blocked-out hour.

How long does this take per week? About thirty minutes in total: fifteen collecting candidates, fifteen turning the strongest three into rough outlines. If it is taking longer, you are probably drafting instead of collecting, which means you are writing posts before you know whether they are worth writing.

Where should I look for topics if my niche is small? Smaller niches need the question-and-complaint sources more, not less, because fewer people are writing about the category and each conversation stands out more. Search demand will look thin (this is normal at small volume), so treat the live conversations as your primary source and search data as vocabulary support.

Should I write for peers or for buyers? Both, deliberately. Peer posts build your reputation and get shared; buyer posts start conversations. Label each one as you draft it so you can judge it against the right standard instead of wondering why a peer post did not generate a single demo.

What do I do with topics I collected but never used? Keep them, and re-run the buyer test on them monthly. A topic that failed the test in June often passes it in September, once you have shipped the feature or heard the objection a fourth time. What you should not keep is the illusion of progress: a screenshot folder with nothing published from it.

How many of my posts should come from live conversations? Early on, most of them. It is the source with the shortest feedback loop and the clearest proof of demand. Once you have five or six pieces published, you can start repurposing your own material, which is how one good post becomes a month of content.