Home/Templates/Feedback
Template

Product Feedback Request Templates for Reddit

Reddit gives you access to opinionated strangers who will tell you exactly what's wrong with your product. These templates help you ask in a way that invites honest, useful critique instead of polite non-answers.

When to use

Use feedback request posts when you have something real to show and a specific question you need answered — not as a backdoor launch tactic. The best feedback posts are focused on one problem area: pricing, onboarding, a specific feature, or positioning. Vague 'please give me feedback' posts get vague responses.

The Specific Question Ask

Template #1

When you want feedback on one specific aspect — pricing, landing page clarity, a particular feature. Works in r/SaaS, r/startups, niche communities.

I built [PRODUCT NAME] — [ONE-SENTENCE DESCRIPTION]. I have a specific question I'm hoping this community can help with.

[SPECIFIC QUESTION — e.g., 'Is $[PRICE]/month reasonable for [VALUE PROP]?' or 'Does the landing page clearly explain what this does in under 10 seconds?']

Here's the context: [2-3 sentences of relevant background]. I've already [WHAT YOU'VE TRIED OR TESTED]. Brutal honesty is genuinely appreciated here — I'd rather know now than after I've built more in the wrong direction.

Tips

One specific question gets 10x more useful responses than 'any feedback welcome'
Showing what you've already tried signals you're past the 'validate my idea' stage — people respect that
Say 'brutal honesty appreciated' and mean it — it sets a norm that unlocks real criticism

The Roast Request

Template #2

When you want critical feedback on your landing page or positioning. The 'roast' framing works exceptionally well in r/SaaS and r/startups.

Roast my landing page — [PRODUCT NAME]

I've been staring at this thing for too long and I can't see it clearly anymore. Here's the URL: [LINK]

[PRODUCT] does [ONE-SENTENCE DESCRIPTION] for [TARGET USER].

Things I'm specifically unsure about: [2-3 specific concerns — e.g., 'Is the headline clear?', 'Is the pricing section confusing?', 'Does the value prop land?']. But rip into anything you notice. I can take it.

Tips

The word 'roast' signals you want real feedback, not validation — it changes the entire tone of responses
Admitting you've lost perspective is relatable and invites empathy alongside the criticism
List your specific concerns so feedback is focused, but frame them as examples rather than the only acceptable topics

The ICP Interview Ask

Template #3

When you need to talk to potential customers before or during early development. Works in any community where your target user hangs out.

I'm building something for [TARGET USER TYPE] and would love to talk to a few people who deal with [SPECIFIC PROBLEM].

Not trying to sell anything — I genuinely want to understand the problem better before I build more. I have about [TIME — e.g., '15 specific questions'] and I can do async (DMs, email) or a short call, whatever works for you.

Context: [2-3 sentences on what you're building and why]. The main thing I'm trying to understand is [SPECIFIC RESEARCH QUESTION].

If you've dealt with [PROBLEM] before, I'd really appreciate 10 minutes of your time.

Tips

Leading with 'not trying to sell anything' disarms the reflex to ignore you — people actually respond to this at a higher rate
Offering async as an option (not just calls) roughly doubles response rate
Be specific about your research question — 'I want to understand how you currently handle X' beats 'I want to learn about your workflow'

The Beta Tester Ask

Template #4

For recruiting early beta users from a specific community. Works when you have a functional product but need power users to stress-test it.

Looking for 5-10 people to break [PRODUCT NAME] before I launch publicly.

What it does: [ONE-SENTENCE DESCRIPTION]. Who it's for: [SPECIFIC USER TYPE — e.g., 'solo founders managing 3+ clients', 'developers who do code reviews daily'].

What you'd get: free access for [TIMEFRAME], direct line to me to report issues, and your feedback actually shapes the product. What I'd ask for: honest notes on what's confusing, broken, or missing — ideally in writing so I have a record.

If this sounds like something you'd use, comment or DM me.

Tips

A specific number ('5-10 people') creates scarcity and urgency without false marketing pressure
Defining exactly who you want filters out low-quality testers before they sign up
Spelling out the exchange (what they get, what you want) respects the reader's time and signals professionalism

Common mistakes to avoid

Asking for 'any feedback' with no specific focus
Pick one thing: the headline, the pricing page, the onboarding flow. Focused questions get focused answers
Responding defensively to critical feedback in the comments
Say 'thank you, that's really useful' and mean it. You can ask a follow-up question, but arguing with the feedback sender kills the thread and your reputation
Posting in a community where your target user isn't present
Feedback from r/SideProject on a medical device tool is less valuable than feedback from r/medicine. Post where your actual users are, even if those communities are less friendly to self-promotion
Using the feedback post as a stealth launch with no genuine intent to iterate
If you're going to ask for feedback, commit to posting an update after you've acted on it. Redditors remember, and follow-up posts drive significantly more engagement than the original

Skip the templates — let AI write for you

RedditGrow generates context-aware responses that match each subreddit's tone and rules. You review and edit before posting.

FAQ

Ready to get started?

7-day free trial. No card required. 30-day money-back guarantee.