Community listening: finding the thread where your buyer is asking

Community listening is the unglamorous half of community marketing. Not posting — reading. Somewhere, right now, a person is typing out the problem your product solves, in a subreddit, a forum, a Discord channel or a GitHub issue, and asking strangers what to do about it. Finding that thread and answering it well is worth more than most ad spend at a small budget. It is also easy to do badly, and the communities in question have spent twenty years learning to spot the bad version. This is the procedure we use, what it costs in hours, what it returns, and when to stop.

What a listening post is, and what it is not

The indie playbooks doing the rounds this month put community listening next to build in public, SEO and intent outreach as one of the four channels a small founder should consider, and the advice in buildinpublic.so's marketing guide is the same advice you would have got in 2016: be useful in the places your buyers already are.

What is different now is the volume. There are more places, they are more fragmented, and the search engine that used to send a person to the one good thread now often answers them itself. So the thread matters more, and it is harder to find. The person asking is the buyer you cannot target with an ad, because they have not searched for your category yet. They have described a symptom.

A listening post is not a social media presence. It does not need followers. It does not need a content calendar. It needs a saved search, a spreadsheet, and the discipline to answer a question without steering it.

Finding the thread: the procedure

Write down the sentence a buyer says before they know your product exists. Not your category name. The complaint. If you sell an invoicing tool, the sentence is "client hasn't paid and I don't know how to chase without being rude", not "invoicing software". If you sell an ad slot, it is "I have $50 and no idea where to spend it".

Search those words, sorted by new, in the places that have search. Reddit's own search is passable and gets better with quoted phrases. Hacker News is searchable through Algolia and the comments are indexed, not only the titles. GitHub issues on competitor repositories are a goldmine for developer tools. Indie Hackers, Product Hunt discussions and the bigger Discord servers each have their own search, some of it terrible. Do it anyway.

Keep a list. URL, date, whether the thread is still active, what the person literally asked, and what you did. This is the part everyone skips and it is the part that turns an afternoon of browsing into a channel. Without the list you cannot tell whether last month's answers sent anyone anywhere.

Answer the question first. Fully, as if your product did not exist. If the honest answer is a competitor, say the competitor. If your product is part of the answer, say so, say it is yours, and put it after the answer, not before.

Tag the link if the community allows links at all. Many do not, and a link in a first-time poster's comment is the fastest way to be removed. Where links are allowed, a UTM parameter is what lets you count the visit later. Where they are not, a distinctive phrase you can spot in your referrer logs is the fallback.

The rules the communities enforce

Every community has a version of the same rule and enforces it with different levels of ferocity. Reddit's content policy prohibits spam and manipulation platform-wide, and individual subreddits layer their own rules on top: no self-promotion, self-promotion only on a given weekday, self-promotion only if you have participated elsewhere first. Moderators read post histories. An account whose entire contribution is the same product link in twelve threads is banned before the thirteenth.

The usable rule of thumb: for every comment that mentions your product, leave several that do not. Not as a ratio to game, as a description of what a person who genuinely belongs in the community looks like. If you cannot bring yourself to be useful in a community without mentioning your product, it is not your community and you should not be there.

What it costs and what it returns

Cost is time, and it is more time than people expect. Half an hour a day is the minimum at which the list stays current; below that, the threads have gone cold by the time you find them, and a reply to a three-week-old question is mostly read by nobody.

Returns are small and countable. A good answer in an active thread sends a handful of visitors over a few days, sometimes more if the thread ranks, occasionally none. The variance is enormous and you will not know which kind you wrote until a week later. This is why the list matters: over a couple of months, the visits column tells you which communities and which questions are worth the half hour, and which were a habit.

Be honest with yourself about what "worked" means. Upvotes are not visits and visits are not sign-ups. A comment that gets forty upvotes and sends three people is a good comment and a poor channel. Count the thing that matters to you, and count it with your own logs rather than the platform's karma.

When to buy the thread instead

At some point you will find a community where your buyer clearly is, where the rules forbid you from saying so, and where the one thing you could do is pay. That is the case for Reddit's own ads, and the honest summary of that post is that they work for some products, cost more than the forum post would have, and are measured by a platform with an interest in the measurement.

There is another option, which is ours, so weigh it accordingly. BidSurvivor sells two twelve-hour slots a day on a single board, by open auction, and the first brand into an empty slot pays nothing. It does not find your buyer — there is no targeting, and it reaches whoever is looking at the board, not whoever asked your question. What it does have is the property a forum comment lacks: the opens and click-throughs are counted and published on the front page and on each brand's page, so a test costs an afternoon and produces a number. The numbers are small, and they are visible, which is the deal.

Neither replaces the thread. The thread is where the buyer said what they wanted in their own words, and nothing you buy tells you that.

When to stop

Stop answering a thread when the question has been answered, including by someone else. Stop watching a community when a month of the list shows zero visits from it. Stop the whole channel when you notice your answers have become a template — the moment you are pasting, you have become the thing the moderators are looking for, and the community will notice before you do.

And stop before you start writing to people directly. The step after listening is intent outreach, which is a different discipline with its own rules, the first of which is that a person who asked a question in public did not thereby hand you their inbox.

If you are choosing between listening and a launch-day platform, the alternatives to Product Hunt are the same choice at a different scale: one loud day against many quiet ones. Most small products need the quiet ones, and the quiet ones start with reading.