Submissions are open — put your project in front of the r/startupaccelerator community →
Growth3 min read

Build a distribution radar: the agent that finds conversations

Answering the right thread is the highest-quality distribution a new product has. Finding it every morning is a chore, and chores get dropped — so hand the finding to an agent and keep the answering.

The StartupAccelerator team

The short version

  • Showing up where your problem gets discussed works, but almost nobody sustains the searching by hand past week three.
  • Automate the finding and keep the answering human: a community forgives a founder who shows up often, never one who shows up automatically.
  • Score threads against your product rather than against keywords, because the useful question is whether an honest answer from you would relieve someone.
  • A month of ranked queues tells you which communities deserve your mornings, which is evidence no launch day will ever hand you.

This desk has argued that early users arrive through conversations rather than broadcasts. That still holds. What nobody mentions is the shelf life. Reading six communities every morning is a real job, and it is the first job a founder quietly drops. Week three is usually when it stops.

The searching is the part that rots

Notice what actually decays. Not your ability to write a good reply, which only improves. What decays is the scanning: the tabs, the repeated queries, the scroll past threads where nobody has your problem. Repetitive and unrewarding is exactly the shape of work a machine does well.

From the open web down to a morning queue, in four narrowing passes. Only the last one should ever be human.

What the agent may and may not do

Draw the line at the keyboard. The agent searches, reads, scores and ranks. It never posts, never drafts a reply for you to paste, never touches an account. A community will forgive a founder who shows up often. It will not forgive one who shows up automatically.

  • Search wide, read narrow. Breadth is for finding candidates; your attention belongs to the few that survive.
  • Score against the problem, not against keywords. Ask whether this person would be relieved to hear your answer.
  • Keep the queue short. Five threads you will actually open beats forty you will not.

The build, in order

  1. Write the brief: who you help, their problem in their own words, and three phrasings they would use that never name your product.
  2. Give a model web search — Sonnet 5 carries this well — and let it run those phrasings overnight, keeping links, titles and enough surrounding text to judge by.
  3. Score every candidate on three axes — is the problem real, is it recent, would an honest answer help — and keep only the high ones.
  4. Remember what you have already seen, so tonight cannot hand you yesterday's threads. A small table will do, once it exists and the job can actually reach it.
  5. Deliver the survivors as one ranked email: the link, two lines of context, and why it scored.
  6. Read it with your coffee. Open three. Answer them as yourself.

After a month the queue is worth more than any reply you sent. You will know which communities produce real conversations and which only produce noise, and you will know it from evidence.

Accelerator AI

Put this article to work

Ask it a question, or turn it into a to-do list for your own project. Both answer strictly from this article — nothing invented.

Answers are generated from this article only and are a working draft, not advice.

Questions this answers

Can you automate finding customers in online communities?

You can automate the finding, and you should not automate the replying. An agent can search the public web overnight, read the threads it turns up, score them against the problem your product solves, and leave you a short ranked list by morning. Writing the answer stays yours, because the credibility you are building is personal and does not survive being generated.

How do you stop an outreach agent from becoming spam?

Give it no ability to post anywhere. If the agent only reads and ranks, its worst failure is a wasted morning; if it can write, its worst failure is a reputation you cannot repair. Communities tolerate a founder who turns up often with useful answers, and they remove the one who turns up automatically.

What makes a discussion thread worth replying to?

Three conditions at once. The person describes a real problem rather than asking for tool recommendations, the thread is recent enough that a reply will still be read, and you can answer usefully whether or not they ever try your product. A thread that fails any one of the three is better skipped than answered.

distributiongrowthaiautomation
Found this useful? Send it to a founder who needs it.

Building something?

Put it in front of founders who read this — free listing, community-voted, reviewed before it goes live.

Submit your project →
Growth3 min read Your first hundred users will not come from a launch Launch days produce a spike and a lesson. The founders who get to a hundred real users almost always get there through channels that look too small to bother with. Read the article → Growth3 min read Launch day mechanics: the week that decides the day A launch is a logistics exercise dressed as a marketing event. Almost everything that decides the outcome is done in the week before you post — which is good news, because that part is controllable. Read the article → Engineering3 min read Vibe coding reached production. Here is what breaks first. AI writes most of the code in a lot of new startups now. The failure modes are consistent, they are boring, and they are entirely avoidable if you know where to look. Read the article →