How to find customers on Reddit when you are building solo

You finish shipping a feature, open a new tab, and try to find customers on Reddit. An hour later, you have read three arguments about pricing, bookmarked a marketing thread, and answered nobody. The work feels close to selling. It has mostly been scrolling.

A better starting point is one specific person with a problem you understand. Find the question they are trying to answer, decide whether you can help, and make the next step easy if they want it. This guide gives you a small routine you can run between building sessions, without pretending every mention is a lead.

The examples below use a fictional product that helps freelance designers collect client feedback. They are invented to show the decisions involved, not testimonials or reports of customers we acquired. You can run the whole process with Reddit search and a plain spreadsheet.

Before you find customers on Reddit, define one customer

Start with a sentence that describes the person, the task, and the moment that makes the task painful. For our example: a freelance designer is collecting approval on several client projects and keeps losing feedback across email and chat. That is narrow enough to search for and concrete enough to recognize.

Compare that with 'creatives who want to be more productive.' Almost any discussion could fit. You will collect attractive-looking threads without learning which people actually need the product. A specific starting customer gives you a reason to ignore most results.

Write down who the product does not help yet. Perhaps it cannot handle video review, enterprise procurement, or a client who refuses to open a link. Those limits belong in your research notes. They stop you from turning every objection into an unsupported promise.

You do not need to settle your audience forever. Choose a starting group for a short research pass, then change it if the evidence points elsewhere. If you are still unsure whether the problem matters at all, start with our guide to validating a startup idea on Reddit. Finding interested people and proving a business are different jobs.

Choose subreddits by the work people do

Founder communities are useful when founders are your customers. They are less useful when you sell to tutors, photographers, or independent shop owners. Look for communities where the buyer discusses their actual work, including the awkward bits that happen before they consider buying software.

For the designer example, search for discussions about revisions, client approval, project handoff, and freelance operations. Follow those discussions to the communities where they happen. Do not choose a subreddit just because it is large or has a promising name.

Read several recent threads before adding a community to your shortlist. Are people describing firsthand problems? Do replies contain useful detail? Are product recommendations welcomed, restricted to certain threads, or prohibited? A smaller community with relevant discussions can be a better use of your attention than a broad feed of founder announcements.

Keep the shortlist small enough to understand. Three communities is a reasonable starting constraint for one person, not a magic number. Record the rule page, what people ask about, and where product mentions are allowed. If you cannot explain why a community belongs on the list, remove it until you can.

Find customers on Reddit by searching for their problems

People rarely describe their problem using the category name you put on your homepage. They say 'the client sent changes in five emails' or 'I never know which version they approved.' Search for those situations before searching for 'client collaboration platform.'

Build a short set of searches around the task, the frustration, and the decision. The examples below are query ideas for the fictional designer tool, not claims that these exact searches contain customers today. Change the wording after reading how people actually describe the problem.

• Task: client feedback, design revisions, project approval.
• Frustration: feedback scattered, conflicting revisions, approved wrong version.
• Decision: feedback tool recommendation, alternative to email, client approval software.
• Constraint: clients without accounts, small budget, freelance workflow.

Reddit documents community-scoped search and manual filters such as subreddit: and title:. For example, subreddit:freelance client feedback narrows a search to that community. You can also search inside a post's comments when a useful detail is buried in a long discussion. See Reddit's search feature documentation for supported syntax.

Read older threads to learn the vocabulary and newer ones to assess current conversations. An old thread can explain a recurring problem even when it is no longer a sensible place to reply. Avoid treating the newest result as automatically the best opportunity; the actual question still has to fit.

Decide whether a thread deserves a reply

A keyword match only tells you that words overlap. Before replying, look for three things: a person doing the relevant work, a problem your knowledge addresses, and a conversation where your contribution would add something. If one is missing, you may have useful research rather than an opportunity to sell.

'What software do designers use?' is broad discovery. 'My client approved an old PDF and now wants the latest changes reversed' reveals a specific failure. 'I need a review tool that does not make clients create accounts' includes a buying constraint. Each needs a different answer.

For broad discovery, explain the choices. For a failure, help troubleshoot the process. For a constrained request, compare options against the constraint, including yours only if it fits. Do not send all three people the same product paragraph.

Read the comments before deciding. The author may already have chosen a tool, explained that they cannot pay, or corrected the original question. A reply that ignores this looks careless. Sometimes the best decision is to save the thread as research and leave the conversation alone.

Use plain labels in your notes: reply, research, follow up if invited, or skip. A precise-looking lead score is not necessary when you can explain the decision in a sentence. 'Needs video support we do not offer' is more useful than a mysterious score of 62.

Check Reddit self-promotion rules before mentioning your product

Read the community's current rules and any instructions attached to the thread. If the rules are unclear, ask the moderators before posting promotional material. A recommendation request is not automatically permission to advertise, and adding a disclosure does not override a no-promotion rule.

Reddit's moderator guidance on spam says some communities prohibit promotion, while others use a 10% rule. That is not a universal allowance to make every tenth contribution an advertisement. The community's own rules still decide what belongs there.

Reddit's spam policy also covers unwanted repeated activity, including mass unsolicited messages. Keep outreach specific and welcome. If a contribution is removed, review the reason instead of reposting it through another account or changing a few words to get it through.

Make affiliation easy to understand whenever you mention your own product. 'I built this' is clearer than posing as a happy customer. Be equally direct about limitations and availability. If your product is a prototype, say so before asking someone to spend time evaluating it.

Write a reply that helps before anyone clicks

Begin with the problem the person described. Offer a practical step, explain the relevant tradeoff, and ask a focused question only if you need more information. The reply should remain useful if the person never opens your profile or visits your site.

Here is an invented reply to the designer who keeps losing approvals. It assumes the community allows a relevant product mention. Notice that the operational advice comes first and the product limitation is explicit.

I would separate feedback from approval. Give each revision one review link, ask the client to keep comments there, and get a clear yes on the version you will deliver. That can work with your existing tools. I am building a small review tool for this, but it only handles static designs right now. Are the conflicting comments coming from one person or several reviewers?

The final question changes the recommendation. Several reviewers may need one decision-maker more than another tool. One reviewer using different channels may need a clearer agreement about where feedback goes. You cannot know which until you listen.

Avoid the little claims that creep into a sales reply: 'everyone struggles with this,' 'this will save hours,' or 'it is the best option.' Unless you have evidence, describe what the product does and who it currently fits. A useful answer with honest limits is easier to trust than a perfect-sounding promise.

Offer a next step that matches the person's interest

A thoughtful answer is the beginning of a conversation, not permission to start a sales sequence. If someone asks for a link and the community permits it, share the relevant page. If they ask about a constraint, answer that constraint before suggesting a demo.

Keep the next step proportionate. A person comparing two features may need a screenshot or a short explanation. Someone trying to solve an immediate problem might want a brief walkthrough using a sample project. Do not demand a calendar booking just to reveal basic pricing or a missing feature.

If moving to private messages would help, ask first and wait for agreement. Explain what you want to send and why. 'Would you like a link to the prototype?' is specific. An unsolicited pitch followed by repeated check-ins spends the goodwill your public reply earned.

For a prelaunch product, distinguish feedback from access. You might invite someone to describe their current process or review a mockup. That does not make them a customer. Record what they agreed to do, fulfill that request, and let them choose whether to continue.

Make the page after the click answer the same question

Suppose your reply discusses collecting feedback without client accounts. A visitor clicks through and sees 'Transform your creative workflow' with no explanation of the account requirement. You have made them restart their research. Put the relevant answer where they can find it.

A small, honest product page should explain who it helps, the task it handles, its meaningful limitations, and the next available action. If it is live, show a real path to trying it. If it is coming soon, label the preview and explain what contact means. Do not disguise a concept as a finished app. A public record of your product decisions can give interested visitors more context about what you are building.

You can use the same page for several conversations if the underlying problem is the same. You do not need a separate landing page for every comment. Update the explanation when the same confusion appears repeatedly, rather than adding sections based on guesses about what visitors might want.

This is also where you check your promise. If a Reddit reply says a feature exists and the product page says it is planned, fix the reply. Being a solo founder does not make every detail obvious to the person arriving for the first time.

Track progress beyond upvotes and profile visits

Keep one small record per relevant conversation. You need enough information to decide what to do next, not a database of everything a person has ever posted. Save the thread link, the problem, why it fits, what you contributed, and the outcome you actually observed.

• Conversation: someone answered your question or asked a substantive follow-up.
• Interest: they requested more information or agreed to see the product.
• Trial: they tried the product or completed a clearly defined pilot step.
• Customer: they paid for the offer you are tracking.
• Learning: they exposed a mismatch, a missing requirement, or a better way to describe the problem.

Do not combine these into a single conversion total. Ten people thanking you and one person paying you are different results. Both can teach you something, but only one tells you a sale happened. If somebody says they heard about you on Reddit without naming a thread, record that uncertainty.

A tagged link can help connect a visit to a post, but it does not explain every step a person took before buying. Pair whatever analytics you already use with a simple question about how they found you. Treat attribution as a useful clue, not a reason to claim every later sale.

A worked example: one thread, three different decisions

Imagine finding a post from a freelance designer who says a client keeps sending contradictory revisions. It has a handful of comments, and the author posted a follow-up that morning. Your tool collects feedback in one place. It is tempting to reply immediately, because the keywords fit almost perfectly.

Read the follow-up and the situation changes. The client's marketing lead approves the design, but the owner reverses the decision later. The thread is about authority and sign-off. A shared review page might make the disagreement visible, but it cannot decide who has final approval. Your best contribution is a process suggestion about naming the approver before work starts.

Now imagine the follow-up says there is only one reviewer, but feedback arrives as screenshots in three different channels. That fits the coordination problem more closely. You can explain how one review location helps, mention the limits of your tool if promotion is permitted, and ask whether the client is willing to change where they leave comments.

A third version says the designer already solved it with a shared document and is asking how to charge for extra revisions. Your product is no longer the subject. Answer the billing-process question only if you have relevant experience, or save the thread as an example of an acceptable workaround. There is no requirement to contribute to every relevant-looking post.

All three versions could trigger the same keyword alert. Only one suggests a plausible conversation about the product. That is why reading and judgment remain part of the work. A search result can bring you to the door; it cannot tell you what the person inside needs.

Your notes should preserve that distinction. Record 'approval authority,' 'feedback scattered,' or 'problem already solved,' along with the next action. After several sessions, those distinctions will tell you whether your positioning is attracting the right situations. You may discover that the product needs a narrower promise, or that the best buyer describes the problem using a phrase you had never considered.

A small routine to find customers on Reddit without losing the day

Give the work a boundary before opening the feed. For example, reserve half an hour for checking saved conversations, scanning a few searches, and answering the strongest match. That is an illustrative time budget, not a promise that customers appear in thirty minutes.

Start with people already talking to you. If someone answered yesterday's question, continuing that conversation is usually more meaningful than collecting another hundred keyword matches. Then look for new discussions in your shortlist. Save only the ones you can explain a reason for keeping.

End the session by writing the next action beside each active conversation. It might be 'answer their import question,' 'send the example they requested,' or 'nothing further.' Close the tabs after that. A founder needs a way to stop researching as much as a way to start.

Once a week, review the record. Which searches produced actual questions from your intended buyer? Which replies opened useful exchanges? Which requirements kept excluding your product? Keep the searches that taught you something and remove the ones that created busywork.

What if Reddit is not bringing customers?

Separate the possible failures. No relevant threads may mean the search vocabulary or community is wrong. Plenty of relevant threads but no welcome opening may mean the channel is better for research than direct outreach. Useful exchanges without trials may point to product fit, timing, or the next step you are offering.

Do not respond to every weak result by posting more. Read the last few conversations closely. Perhaps people solve the problem with an existing tool, cannot approve a purchase, or only encounter the issue once a year. That is evidence about your offer, not a challenge to write a more persuasive comment.

There is no dependable universal answer to how long getting a customer from Reddit takes. Price, urgency, audience, product readiness, and the conversations you find all matter. Pick a review date and a manageable effort budget. Decide in advance what would justify continuing, changing the approach, or trying another channel.

If people agree that the problem exists but nobody takes a concrete next step, use the research-to-validation process to test your assumptions. More enthusiastic comments will not resolve whether someone can and will use the thing you are building.

Start with one question you can answer well

For your next session, choose one buyer, three problem phrases, and a community where those problems are discussed. Read a complete thread. Write down whether you can help and why. If the answer is no, move on without forcing your product into it.

If the answer is yes, contribute something specific, respect the community's rules, and follow through on whatever you offer. The first useful outcome may be a better understanding of the buyer rather than a sale. Keep the distinction visible so you can improve the next conversation.

This is the work we are planning BeSeen around: helping solo founders keep relevant conversations and their context together. BeSeen is coming soon, the workspace is a concept preview, and pricing is TBD. You do not need to wait for us to try this routine. If a part of it keeps getting in your way, tell us what you are building and where finding customers gets difficult.