Academy · 2026-11-16 · 7 min read
Get free Indie Hackers comments: ask for feedback
By Feedlark Team
Key takeaways
- • You cannot guarantee free comments; ask for genuine critique with one narrow, answerable question.
- • Disclose that you built the product and follow the community's current rules.
- • Treat comments as clues, then group recurring problems before changing the product.
- • Feedlark's indie-hacker workflow connects a free board to a changelog and voter notifications when a request ships.
If you searched for get free Indie Hackers comments, the useful answer is not a list of places to buy replies. Paid or coordinated comments do not tell you whether a real person understands your product. They can also make a community post look like promotion instead of a genuine request. The better goal is to earn a small number of specific, candid responses by making it easy for the right people to react to one real question.
Indie Hackers describes itself as a community where builders share their experiences, give and receive feedback, and support one another. That makes it a reasonable place to ask for critique when your post gives people something concrete to respond to. It is not a promise that anyone will comment. Your odds depend on whether the question is relevant, clear, and respectful of the people reading it. See the Indie Hackers overview for how the community describes its purpose.
Ask for a useful reply, not a comment count
A request such as “please comment on my startup” asks a stranger to do the work of deciding what to review. It also gives you little to learn from a short reply. Narrow the request to a decision you can still change: whether the landing page explains the product, which of two onboarding steps is confusing, or what a person expected to happen after clicking a button. Tell readers who the product is for and what you have already tried. Then ask one question that can be answered from the information in the post.
Do not hide that you made the product. A short disclosure builds trust and gives readers context. If you are looking for product feedback rather than customers, say so plainly. Link directly to the page or flow you want reviewed, explain whether it is a prototype or a live product, and make it easy to say that the idea is not for them. A useful reply can be a criticism, a question, or a reason someone would not use the product. Praise alone is a weak signal for what to build next.
A practical post format for Indie Hackers
Keep the post short enough that someone can understand the situation before deciding whether to help. Start with the audience and the problem, add the smallest useful description of what you built, and state the one thing you want reviewed. If there is a constraint, such as a mobile-only flow or an early prototype, mention it. Finish with the link and a thank-you. Do not ask for votes, comments, sign-ups, and shares all at once; each extra request makes it harder to know which response matters.
- Context: who has this problem and when it occurs.
- What exists: one sentence about the current product or prototype.
- The ask: one question that invites a specific observation.
- The link: a working page or short recording, with sensitive information removed.
- The follow-up: say what you changed or learned after people reply.
There is a useful distinction between asking for help and manufacturing engagement. An older Indie Hackers feedback thread is an example of a builder asking the community for product feedback. Treat it as an example of a focused request, not as a current posting rule. Read the community's current guidance before posting, and follow any moderator instructions that apply to your account or post.
Where free comments can come from
Start with people who have a reason to understand the problem: other builders in a relevant discussion, a small group of existing users, or people you already know in the target audience. A public post can widen that circle, but it should not replace direct conversations with likely users. If a community is not the right fit, move on rather than reposting the same pitch. Indie Hackers' terms of service prohibit spam and automated activity that interferes with the service, so avoid schemes that promise a fixed number of comments or ask people to post scripted replies.
| Step | What to do | What to learn |
|---|---|---|
| Ask | Share one product question with context | Whether the problem is clear |
| Listen | Reply to questions and record the exact concern | What readers misunderstood or need |
| Sort | Group feedback by problem, not by who said it | Which issue is repeated and actionable |
| Close the loop | Share what changed or why it did not | Whether the response earned trust |
Turn comments into feedback you can act on
A comment thread is a conversation, not a product backlog. Thank people, ask a follow-up if a point is unclear, and do not treat one person's preference as a vote from your whole market. Keep the original wording where you have permission, remove identifying details that are not needed, and note the context around the comment. Then look for a pattern: did several people misunderstand the same sentence, hit the same obstacle, or ask for the same outcome? That pattern is a better starting point than a tally of comments.
A public feedback board gives recurring requests a place to live after a social thread has moved on. A person can add an idea or support one that already exists, and you can show whether it is being considered. If your audience is wary of creating an account just to leave a thought, see our guide to no-login feedback. Keep the original community conversation where it happened; use the board as a durable home for product requests, not as a way to scrape or republish somebody else's comments without consent.
A worked example using Feedlark's own workflow
Feedlark's indie-hacker use case describes a free feedback board that can be set up in two minutes, with unlimited users and an automatic changelog when a requested feature ships. That gives a solo builder a concrete loop to test: post one narrow question on Indie Hackers, invite people who want to help to add or support the request on the board, then review the responses together before choosing what to build. The two-minute setup and unlimited-user terms come from Feedlark's current product copy, not an estimate of how many comments a post will receive.
For example, a builder testing an onboarding flow could ask, “Which step made you pause, and what did you expect to happen?” If a respondent also wants a particular change, record that request on the public board with enough context to understand it. Do not turn a single comment into a promise. Once you decide to build the request, update its status. Feedlark's documented ship loop creates a changelog entry and notifies the people who voted, so the person who took time to respond can see what happened. The Indie Hackers feedback board use case shows how that workflow is positioned for independent builders.
This is the part a comment thread alone cannot do: preserve a request, show its status, and close the loop after release. The board is free for unlimited users according to Feedlark's product description, so a builder can ask for feedback without putting a per-voter cost between a curious visitor and a response. If your immediate problem is how to explain a shipped change, the guide to writing a changelog covers the announcement itself.
What not to do
- Do not buy comments or promise a comment exchange. Those replies measure a transaction, not interest in your product.
- Do not disguise an advert as a question. Disclose your connection and explain why the question is relevant to the community.
- Do not post the same request repeatedly when the first post is quiet. Improve the question or find a more relevant audience.
- Do not copy usernames, private messages, or personal details into a public board without permission.
- Do not claim that a handful of comments proves product-market fit. Treat them as clues to validate with real users.
A better definition of free feedback
Free feedback is not guaranteed attention. It is a way to learn without paying for a panel or a promotion, while respecting the time of people who choose to reply. A clear question, a relevant audience, and a visible follow-up give you more value than a target number of comments. Keep notes on what people said, what you changed, and what still needs testing. If nobody responds, that is not proof that the product is bad; the audience, timing, or question may simply be wrong. Refine the ask and try a more suitable group instead of manufacturing engagement.
For indie hackers, the practical sequence is straightforward: earn the conversation, capture the product problem, decide what deserves action, and tell contributors what changed. A community post helps you start the conversation. A board and changelog help you carry it forward. That is a more honest answer to “how do I get free comments?” than any service selling replies, and it leaves you with feedback you can use after the thread is no longer at the top of the feed.
Frequently asked questions
- Can I get guaranteed free comments on Indie Hackers?
- No. You can invite people to give feedback, but nobody can guarantee that community members will reply. Be wary of services promising a fixed number of comments because scripted or coordinated engagement does not show genuine interest.
- How should I ask Indie Hackers for product feedback?
- Explain who the product is for, disclose that you built it, and ask one specific question about a page, workflow, or decision. Give enough context to answer and follow the current community rules.
- Is it okay to share my product in an Indie Hackers post?
- Share it when the post is relevant and your purpose is clear. Do not disguise an advert as a question, repeat the same promotion, or use automated comments. Check the current community guidance and terms before posting.
- What should I do with comments after I receive them?
- Thank people, ask follow-up questions when needed, and group comments by the problem they describe. Record useful requests in a durable place, decide what to test, and tell contributors what changed when you ship.