Start a reply guy strategy by choosing the conversation: who is there, what remains unanswered, and what you can add from your own work or reading. Keep the source URL and a one-sentence reason before drafting.
The walkthrough below holds the intended writer constant: a SaaS builder discussing customer learning. Three dated public posts lead to three different decisions. The result is a shortlist and a proposed question.
Contents
Choose for one writer, not for every large account
These posts were selected to show a relevant topic, a point already stated, and a corrected figure. Their published dates matter. The notes use the available post text; they do not represent a complete reading of every reply in those conversations.
- Rob Walling · September 9, 2026
- His post about an interview with Steve Blank describes fast AI development masking untested assumptions. It fits customer learning. Keep it as a research candidate, then read the interview and the current exchange before asking about the missing decision.
- Dickie Bush · January 15, 2022
- The writing post already advises choosing one reader and using specific problems and examples. A reply that merely recommends specificity would repeat the source. Save the writing advice; skip that draft.
- Pieter Levels · October 9, 2026
- The opening of a correction post says the author misread a headline $11K amount that was a total. A congratulatory reply treating it as a new payout would miss the correction. It also falls outside this writer's chosen customer-learning topic.
The shortlist keeps Walling's topic for further reading, stores Bush's post as a writing reference, and leaves the payout discussion out. No replies were published for this walkthrough.
Turn the relevant topic into a precise opening
Walling's source post says founders should check assumptions while building. It does not specify which assumption a founder should test first. That gives this writer a possible question.
What would you test with a buyer before polishing the demo: whether the problem recurs, or whether they would pay to solve it?
This is an editorial draft, not an actual reply under the post. It asks about a decision in the source without inventing a client result or claiming the writer ran a test.
The source also announced an interview expected in the following weeks. For someone reading later, the interview may now contain the answer. Follow that context first. If the answer is there, save it or ask a question that builds on it.
Next read the replies you can access. An existing answer can turn a proposed question into a follow-up to that answer. If the relevant part is unavailable, keep that gap in your note rather than writing as though you saw the full discussion.
Keep five conditions in the candidate note
The three source checks happen before a reply is ready. Use these conditions on the particular conversation you are considering.
- Audience
- Can you identify people doing the work you want to discuss? A large account can attract several audiences. Read who is actually talking about the problem.
- Your contribution
- Write the question, source, counterexample, or observation you can add. If it requires an experience you have not had, choose another contribution.
- Conversation activity
- Look for people still answering one another or a current development that reopens the topic. The original view count alone does not tell you this.
- An unanswered point
- Check the post, quoted material, corrections, and the relevant replies. Record which piece your draft adds.
- Profile continuity
- If someone opens your profile, will the bio and recent work continue the subject? A useful original post gives the visitor more than one borrowed exchange.
For shaping a draft after the choice, use the reply editing case.
Build a small observation list
Use a stable mix: people a little ahead of you, peers who continue discussions, and customers or operators who describe the problem from inside the work. That last group helps prevent the list becoming only creators talking about creator tactics.
Search the problem in public X search or X itself. A query such as from:robwalling assumptions restricts the search to that account and word. For discovery, use the customer's wording, such as “customer interviews” or “first customer”.
If the search reports that it is unavailable, use X or a direct source link. Keep “search unavailable” separate from “searched and found no relevant conversation”. The two results should lead to different next actions.
CarryFeed's founder described keeping a private observation list while building an account, alongside original posts, profile changes, and replies. The useful habit to borrow is returning to a stable group long enough to notice recurring questions.
Use timing to plan a session
X's conversation recommendation explanation describes recent and top-reply sources, relationships, and predicted actions. An early reply can enter a developing exchange, but a universal five-minute deadline is not a useful substitute for reading that exchange.
A posting-time view can help you reserve an observation window. It does not tell you when a particular question will appear. Keep the session practical and repeatable.
Record the candidates you did not reply to
The three-post walkthrough produces a usable record. In each row, distinguish the source observation from the editorial choice.
- Walling
- Observed: a relevant assumption-checking topic and an interview announced for later. Decision: research first. Next action: read that material and check the exchange before using the proposed question.
- Bush
- Observed: the post already states the specificity advice. Decision: save as a reference; skip a restatement. Next action: use it when editing an original post.
- Levels
- Observed: a correction to the meaning of a payment figure. Decision: skip the payout angle for this topic. Next action: retain the correction if that claim is ever cited.
Session topic and time window: Candidate URL and publication date: Relevant source/reply/correction: Who this helps: What I could add: Decision: reply / research / save / skip Reason: Published reply URL, if any: Later response or idea:
Keeping the skipped rows prevents a busy session from looking successful merely because it produced more text.
Change one part of the selection next time
Try a small series of comparable sessions. Keep the topic and session length stable at first. Record how many useful candidates you found, how many had an unanswered point, and which exchanges continued when you did reply.
If most posts are outside your subject, change the account list. If the questions are relevant but already answered, change the search or observation window. If your replies receive attention but visitors see unrelated work on your profile, improve that continuity.
Change one of those things at a time. A daily profile-visit or follower total is context for the account, not a count of people brought by a particular reply. Use direct follow-up and repeated topic fit to decide where to spend the next session.
The output you want is a better selection habit: a clear reason to reply, a clear reason to skip, and a useful next step when more reading is needed.