How to Answer Questions in Public Without Selling
The helpful-answer channel: how answering strangers' questions builds an audience for an AI product, what a good answer contains, and where the line is.
Published 2026-08-13 · 4 min read
Answering questions in public is the most reliable growth channel available to a founder with no audience, and it is the one most founders abandon because it produces nothing measurable for the first month. It works by a mechanism that has nothing to do with the product: people act on recommendations from handles they recognise.
This is how to do it properly, including where the line between helpful and promotional actually falls.
Why it works
- The audience already exists. You are not building one; you are becoming visible inside one. That is far faster.
- Competence is demonstrated rather than claimed. A good answer proves something about you that no amount of marketing copy can.
- It compounds. Answers stay indexed and keep being read. A useful reply from eight months ago still brings people to your profile.
- It teaches you the market. The questions people ask are the raw material for your landing page, your descriptions and your content.
- It costs nothing but time. Which makes it the only channel available to a founder with no budget and no audience.
Finding the questions
- 1
Search the problem, not your category
Use the phrases your users use — you collected these during onboarding. "How do I turn a recording into clips" finds buyers; "AI video tools" finds competitors.
- 2
Follow the recurring questions
Every community has five questions that come up weekly. Answering them each time is repetitive to you and invisible to everyone else, because most of the audience is new.
- 3
Watch for the complaint-shaped question
"Is there anything that does X without Y" is the highest-intent post that exists. Answer it properly and the person becomes a user.
- 4
Set up saved searches
For the three or four phrases that matter. Checking manually means missing most of them.
What a good answer contains
| Element | Why |
|---|---|
| A direct answer in the first line | The person asked a question. Answering it in the fourth paragraph is not answering it |
| The reasoning or the mechanism | This is what makes it useful to everyone else reading, not just the asker |
| The limitation or the case where it does not apply | What separates an answer from an advertisement |
| A specific detail only someone with experience would know | The credibility signal. Vague advice could come from anyone |
| Nothing about your product, usually | Mentioned only when it is genuinely the answer, and then described factually with its limits |
The line, precisely
The question everyone gets wrong. The rule is not "never mention your product" — it is whether the answer would still be useful if you had never built anything.
- Mention it when it is the answer. "You can do this with X, or with our tool if you want it automated" is helpful and reads as helpful.
- Do not mention it when it is an approximation of the answer. If your product is adjacent but not the solution, answer the actual question and stop.
- Never lead with it. An answer that opens with your product is an advertisement with a preamble.
- Disclose plainly. "I build this" takes two seconds and removes the deception. Undisclosed interest, once noticed, costs the standing you spent months building.
- Answer the question you were asked, not the one you want. This is the whole discipline.
The rhythm
- Twenty minutes daily beats three hours weekly. Recognition comes from frequency, and the good questions appear continuously rather than in batches.
- Two or three answers a day is enough. Quality is the mechanism; volume is not, and thin answers damage the handle that took months to build.
- Reply to replies. A conversation under your answer is read by more people than the answer itself.
- Keep going through the month with no results. The results arrive as a step change, usually when someone with a larger audience notices, and there is no way to schedule it.
What it produces besides an audience
| Output | Use |
|---|---|
| The vocabulary your buyers use | Your headline, your description, your tags, your landing page copy |
| The questions that recur | Your FAQ page and your first blog posts |
| The objections that appear | Your comparison page and your pricing page |
| The workarounds people describe | Your real competition, which is rarely another product |
| A list of people with the problem | Your first ten users, recruited individually |
Where it fails
- In communities that prohibit any commercial interest. Some spaces remove answers from vendors regardless of quality. Read the rules first.
- When the answer is genuinely "use our product" every time. Repetition is visible, and the handle becomes known for one thing.
- When you stop. Recognition decays within weeks. This is a practice, not a campaign.
- On platforms where answers are not durable. A disappearing feed produces no compounding; an indexed forum or a persistent thread does.
Answering questions in public is not a marketing tactic. It is being competent in a room where people can see you, consistently, for long enough that they know who you are before you ever ask anything.
More in Community playbooks
- How to Find and Join AI Newsletter CommunitiesNewsletter authors and their reader communities are a reachable audience for a new AI product. How to find them, get on their radar, and get mentioned.
- Product Hunt Community: How to Engage Before You LaunchA launch-day platform rewards the people who were already there. How to build standing in a launch community in the months before you need it.
- AI Founder Communities Compared: Where to Spend Your First MonthFounder, buyer and technical communities compared by audience, tolerance for promotion, time to pay off and what each is actually good for.