How to find customers on X (Twitter) by replying, not posting

If you have a few hundred followers, posting about your product on X mostly reaches people who already know about it. The common advice is to post more, grow an audience, and wait. That takes months, and many indie makers give up before it pays off.

There is a faster route that does not depend on followers: find the people who are already describing your problem, and reply to them. This guide covers why replies work, how to use X search to find the right posts, how to write replies that start conversations, and how many to send.

Replies are read even with zero followers

When you post, your audience is your followers. When you reply, your audience is the person you replied to, plus everyone reading that conversation. The original poster usually sees your reply in their notifications, whether or not they follow you. If they asked a question, they are actively waiting for answers.

That is why a single good reply to someone with the exact problem you solve is often worth more than a week of posts. It reaches the one person who needs you, at the moment they need you, and it shows them how you think. If they reply back, you have a conversation, which is where customers come from.

Use search like a filter, not a feed

X search is noisy by default. The Top tab favors popular posts, which are rarely the ones you want. Switch to the Latest tab and add operators to cut the noise. A few that matter most, as of writing:

• Quotes for exact phrases: "how do you track" finds that phrase, not posts that merely contain those words.
• -filter:links removes posts with links. Most promotional posts, news and articles include a link; people describing their own problem usually do not.
• -filter:replies keeps only original posts, which is useful when you want people starting a conversation rather than people inside one.
• lang:en restricts results to one language, so you only see posts you can reply to well.
• A minus sign excludes words, such as -hiring or -giveaway, to remove recurring noise in your niche.

Combine them with problem phrases rather than product categories. A search for "any recommendations for" invoicing -filter:links lang:en will find people asking for help. A search for invoicing software will find vendors. As on Reddit, the phrases that work are the ones your customers use when they are stuck: "is there a tool that", "how do you all handle", "I'm so tired of", "why is it so hard to".

What about min_faves, which filters to posts with at least a certain number of likes? It is useful for research, to see which complaints resonate with many people. For finding customers it usually hurts: the person who needs you most often posts something with zero likes, and a popular post already has dozens of replies competing with yours. Use it to learn, not to find people to reply to.

Bookmark the search URLs that work, and keep them in one note so you can open them in a minute each morning.

How to write a reply that starts a conversation

Posts on X are short, and replies should be too. A good reply does one of three things: answers the question, shares a specific experience, or asks a sharp follow-up question.

1. Answer in the first line. If they asked "how do you track X", tell them how, concretely.
2. Add one detail that shows you have dealt with this: a number, a mistake, a setting.
3. If it helps, ask one short question back about their situation. Questions invite replies; statements end threads.
4. Mention your product only if it is clearly the answer, and say you built it. Often it is better to leave it out and let them find it on your profile.

Make sure your profile does the work your reply does not. A clear one-line bio saying what you build and for whom means anyone curious after your reply can find your product without you linking it.

When they reply back

A reply back is the moment that matters, so answer it the same day if you can. Keep the exchange about their problem. Ask what they have tried, what broke, what a good outcome would look like for them. These answers are useful to you whether or not they become a customer: they tell you how people describe the problem, which gives you better search phrases tomorrow.

If the conversation naturally reaches the point where your product would help, say so in one sentence and offer to share it. If they say yes, share it in the thread or in a direct message, whichever they prefer. If they say no thanks, thank them and leave it there. People remember founders who helped without pushing, and some of them come back weeks later when the problem gets worse.

What to avoid

• Links in every reply. Replies that are mostly a link look like spam to the reader, and they are easy to mute or report.
• Templates. If you paste the same reply into ten threads, people notice, and you will be ignored at best.
• Replying to posts that only loosely relate to your product. If you have to stretch the connection, skip it.
• Arguing with people who criticize your category or your product. Thank them, take the point if it is fair, and move on.
• Burst activity. Many replies in a few minutes can look like a spam account. Spread them out.

One more habit helps: before replying, open the person's profile for a few seconds. If they are a vendor, a recruiter or an account that only posts threads for engagement, skip them. If they are building or running something and the post is about their own day, they are the person you want to talk to.

How many replies per day

Quality beats volume here, but some volume is needed for anything to happen. A sustainable target for most indie makers is three to ten thoughtful replies a day, to posts from the last day, spread across the day rather than in one burst. At that pace you can write each one properly, and over a month you will have started dozens of conversations.

Keep a simple log: the post, your reply, and whether they responded. After two weeks you will see which search phrases lead to conversations and which lead to silence. Keep the first kind, replace the second.

A short note on X's search limits

X has changed its rules on access several times in recent years. Its API, which third-party search and monitoring tools depend on, is a paid product, and some features of the site require being logged in. Plan to run your searches from your own logged-in account, and check X's current terms rather than relying on older guides.

X is also only one place your customers talk. Longer questions tend to show up on Reddit, and Bluesky and Hacker News have their own audiences. If you are building in public and wondering why your own posts get little response, building in public when nobody replies explains how to shift from posting to replying, and social listening for indie hackers covers searching across platforms.

If running the same searches every morning is the part you skip, Ownfeed can do it for you. You paste your product URL, it searches public posts on Reddit, X, Bluesky and Hacker News every day, and AI keeps only the posts where your product would help. You write every reply yourself; it never posts for you and never connects to your X account.