How do you find people looking for SaaS tools?

What buying language looks like

People rarely announce that they are ready to buy. They ask for help. A post such as does anyone know a good tool for scheduling client calls is a request, and a request is the earliest public sign of a buying decision. The skill is in finding those posts quickly and telling the serious ones from the casual.

This matters most for sales teams, agencies, and founders who sell software. The people in these posts have already admitted a need. You are not interrupting them with a cold message. You are answering a question they asked.

The phrases that signal intent

Search for the wording people use when they are evaluating tools.

• looking for a tool
• can anyone recommend
• best software for
• alternative to
• switching from
• what do you use for
• need something that
• anyone using

Where people ask

Requests appear in Reddit threads, Twitter or X posts and replies, Indie Hackers discussions, Hacker News Ask HN threads, LinkedIn posts, and community groups. Reddit and Hacker News tend to produce detailed requests with context. Twitter or X produces quick asks that often get answered within minutes, so timing matters more there.

A simple process

The workflow has five steps.

• Define the job your product does in plain words, not in your own marketing terms.
• Search for intent phrases combined with that job and the names of tools you compete with.
• Read each result in full, including replies, to confirm the need is real.
• Qualify the post using the checklist below.
• Respond helpfully or add the person to a research list, then record the outcome.

How to qualify a post

Not every request is worth a reply. A short checklist keeps effort focused.

• Recency: posted in the last few days, since fast answers win.
• Specificity: the person describes a clear job, not a vague wish.
• Fit: your product solves that job, not something nearby.
• Authority: the author appears to run or influence the purchase.
• Engagement: replies show the problem is shared or that the question is still open.

How to respond without being spammy

Lead with help. Answer the question, mention what you have seen work, and only then, if it fits, say that you make a tool for it. Disclose that you are affiliated with it. Keep replies short, specific to the post, and free of copy and paste pitches.

Follow each platform's rules on promotion and on direct messages. Several communities remove self promotion or ban accounts that repeat it. Do not scrape private data or contact people who have not publicly asked for help.

Sample reply structures

These shapes work because they put the person's question first. The examples are illustrations to adapt, not scripts to copy.

• Answer first: give a direct recommendation, explain why it fits their situation, and mention one limitation honestly.
• Compare options: name two or three tools that fit, say what each is best at, and include your own only if it truly fits.
• Ask a clarifying question: if the need is unclear, ask what they have tried and what matters most before suggesting anything.

Signs a post is not worth a reply

Skipping the wrong posts saves more time than writing better replies.

• The need is satisfied in the replies already.
• The author is looking for a free hack, not a tool.
• The request is for something your product does not do.
• The post is old and the thread has gone quiet.
• The platform or community forbids promotion in that thread.

Build a repeatable list

Over time the posts you collect become a research asset. Keep a list with the same columns each time so you can sort by recency and fit.

• Date, platform, and link to the original post.
• The job the person wants done, in their words.
• Tools they already mention or reject.
• Your qualification notes and the action you took.
• Outcome: replied, answered by someone else, or skipped.

Timing and follow up

Requests go stale quickly. A reply within hours is far more useful than one a week later, so build the habit of checking at a fixed time each day. If someone replies, answer fast and offer something concrete, such as a short comparison or a trial. If they do not reply, leave it. One useful message is enough.

Example searches by product type

Searches work best when they combine intent language with the job. These illustrations show the pattern for different kinds of products.

• An email tool: looking for a tool to send newsletters, alternative to a named email platform, best way to email my customers.
• A scheduling tool: how do you handle booking calls with clients, any app for scheduling interviews.
• An analytics tool: need simple analytics for a side project, switching away from a heavy analytics platform.
• A design agency: looking for a designer for a landing page, can anyone recommend a brand studio.

Legal and ethical basics

Stay on public posts and public profiles. Follow each platform's terms, including limits on automation and on unsolicited messages. Respect privacy law when you store names or contact details, honor requests to stop, and delete data you no longer need. If someone says they are not interested, close the conversation politely.

Measure what works

Track every post you act on: the source, the date, what you sent, and what happened. After a few weeks you will see which platforms, phrases, and reply styles produce conversations. Drop the ones that do not, and refine the ones that do.

How Posts Finder helps

Posts Finder surfaces public posts where people ask for tools, recommendations, contractors, agencies, and software. You can filter by intent and opportunity type, check recency and source, and open the original post to qualify it before you reply. Saved searches send daily or weekly email alerts so you see new requests quickly, and results export as CSV or JSON for prospect research and account planning.