Science of Apps - Launchpad · Playbook

How to get feedback
on your startup idea

The best feedback on a startup idea comes from people who have the problem, so start with 10–20 customer conversations about their past behaviour, not your idea. Then get outside views from r/roastmystartup, Indie Hackers and founder friends, and, once something exists to try, from Peerlist, Microlaunch, Show HN and an evidence-based product test.

By , FounderUpdated 6 min read

Share

Quick answer: Where can I get honest feedback on my startup idea?

  1. Before building: 10–20 conversations with people who have the problem, about what they did last time.
  2. Blunt outside views: r/roastmystartup, Indie Hackers and founders you trust.
  3. Once it's tryable: Peerlist Launchpad, Microlaunch (feedback and roasts), Show HN for developer products.
  4. Evidence, not opinions: a product test of your live first version.
  5. Ask about the past: 'When did this last happen? What did you do?', not 'Would you use this?'.

Key takeaways

  • The most useful feedback comes from people who have the problem, not from people who like startups.
  • Ask about past behaviour; people are poor predictors of what they'd use or pay for.
  • Public roasts catch unclear pitches and obvious competitors; they can't validate demand.
  • Once a first version exists, feedback from people trying it beats any opinion about the idea.
  • Look for patterns across many conversations; one enthusiastic person is noise.

Ask friends about your startup idea and they'll say it's great. Ask strangers on the internet and they'll say it's doomed. Neither tells you much. Useful feedback comes from the right people, asked the right way, at the right stage: people with the problem before you build, blunt outsiders on your pitch, and real users once something exists. This guide lists ten places that work, grouped by stage, and the questions that get honest answers. Jump to before you build, outside views, once it's tryable or the questions to ask.

Ten places to get feedback, by stage

StageWhereWhat it's good for
Before you build1. People with the problemWhether the problem is real and painful
2. Your past colleagues and customersContext and introductions
Outside views3. r/roastmystartupBlunt reactions to your pitch
4. Indie HackersFounders' views on the business model
5. Founders you trustPattern-matching from experience
6. Niche communitiesWhether the audience recognises the problem
Once it's tryable7. Peerlist LaunchpadA week of builder feedback
8. Microlaunch30 days of feedback and roasts
9. Show HNCandid technical feedback, for things people can try
10. A product testEvidence of where users get stuck

Table: Where to get feedback on a startup idea, by stage

Before you build: talk to people with the problem

Diagram of 5 steps for before you build: talk to people with the problem: 1. List 30 people who have the problem; 2. Ask for 20 minutes to learn, not to pitch; 3. Ask about the past; 4. Pitch only at the end, if at all; 5. Write down exact words.
Before you build: talk to people with the problem
  1. List 30 people who have the problem. Not people who'd "find it interesting".
  2. Ask for 20 minutes to learn, not to pitch. "I'm researching how teams handle X."
  3. Ask about the past. "When did this last happen? What did you do? What did it cost? What have you tried?"
  4. Pitch only at the end, if at all. Watch for follow-up questions and requests to try it; those are signals.
  5. Write down exact words. The way people describe the problem becomes your headline later.

Outside views: blunt and fast

r/roastmystartup is a subreddit built for blunt feedback. In the month to 17 November 2026, its top posts scored under 10 points but drew up to 48 comments, so the value is in the comments. Ask specific questions and reply to everyone; see Roast my startup.

Indie Hackers homepage with founder posts about revenue, customers and marketing
Indie Hackers: founders who share numbers and give business-model feedback.Image: Indie Hackers · Screenshot shown for commentary, 17 Nov 2026 · source

Indie Hackers is a free community of founders sharing strategies and revenue numbers: the best place to have your business model questioned. Post your reasoning and numbers, and ask what you're missing.

Founders you trust and niche communities where your users already talk round it out. In communities, help first and read the rules; most remove promotion.

Once it's tryable: real users

Peerlist Launchpad showing this week's projects with upvotes and comments
Peerlist Launchpad: a week of builder feedback, every Monday.Image: Peerlist · Screenshot shown for commentary, 16 Nov 2026 · source
  • Peerlist Launchpad: launches open every Monday and run a week, for verified individuals with a complete project; no fee is mentioned. Builders try projects and comment.
  • Microlaunch: a paid 30-day launch (from $49) designed to collect "honest feedback, roasts, and testimonials".
  • Show HN: free, for "something you've made that other people can play with"; not for landing pages or sign-up pages.
Microlaunch homepage with the monthly leaderboard and products scored on idea and product
Microlaunch: products scored on idea and product, with roasts.Image: Microlaunch · Screenshot shown for commentary, 17 Nov 2026 · source

Evidence instead of opinions

Science of Apps product investigation page with the headline Product intelligence that shows its work
The product investigation: findings backed by evidence, signed off by an analyst.Image: Science of Apps · © Science of Apps · source

Comments tell you what people think. A product test shows what happens. List your first version free on Science of Apps Launchpad, and once it's live it's tested end to end: loaded in a real browser on desktop and mobile, measured automatically and reviewed by experts, with each finding rated and approved by an analyst.

The questions that get honest answers

Instead of…Ask…
"Would you use this?""When did this problem last happen? What did you do?"
"Do you like the idea?""What have you already tried? What was wrong with it?"
"How much would you pay?""What do you spend on this today, in money or time?"
"Any feedback?""Where did you get confused? What did you expect to happen?"
"Is this a good idea?""Who else have you seen try to solve this?"

Table: Questions that get honest feedback on a startup idea

Mistakes that waste feedback

Checklist: Mistakes that waste feedback — Asking people who don't have the problem; Pitching before listening; Treating compliments as validation; Arguing with critics; Acting on one voice.
Mistakes that waste feedback
  • Asking people who don't have the problem — their opinions are guesses
  • Pitching before listening — people become polite
  • Treating compliments as validation — look for behaviour, not praise
  • Arguing with critics — ask what they'd expect instead
  • Acting on one voice — wait for patterns

Ready for real feedback?

How we know

Platform details come from Peerlist's help centre, Microlaunch's premium page and Show HN's guidelines (16–17 November 2026); the r/roastmystartup pattern from its top posts of the month to 17 November 2026. The interview approach is our editorial guidance, consistent with widely used customer-discovery practice. Science of Apps runs the Launchpad and the product investigation.

Key terms, defined

  • Customer interview: a conversation with someone who has the problem, focused on their past behaviour.
  • Feedback: opinions and reactions to an idea or product.
  • Validation: evidence that people will use or pay, such as repeat use or pre-orders.
  • Leading question: a question that suggests the answer you want.
  • Roast: blunt, public feedback on a startup or pitch.

Frequently asked questions

Where can I get honest feedback on my startup idea?

From people who have the problem, in one-to-one conversations. For outside opinions: r/roastmystartup, Indie Hackers and experienced founders. Once something exists to try: Peerlist Launchpad, Microlaunch (which collects feedback and roasts), Show HN for developer products, and an evidence-based product test.

How do I ask for feedback without leading people?

Don't pitch first. Ask about the last time the problem happened, what they did, what it cost them and what they've tried. Only describe your idea at the end, and watch for specific follow-up questions, which signal real interest.

How many people should I talk to?

Enough to see patterns: often 10–20 conversations with people in one target group. If you hear the same problem described the same way repeatedly, you've learned something; if every conversation is different, narrow your audience.

Is feedback from Reddit useful?

For specific questions, yes: whether your pitch is clear, what competitors exist and what confuses people. It isn't validation, because most commenters aren't your customers. Read each subreddit's rules before posting.

What's the difference between feedback and validation?

Feedback is opinions and reactions. Validation is evidence that people will use or pay: repeat usage, pre-orders, a signed letter of intent, or people doing the workaround you'd replace. Collect feedback to improve; look for validation before you invest heavily.

How do I get feedback on a product, not just an idea?

Watch people use it, launch it where builders try new things (Peerlist, Microlaunch), post a Show HN if developers can try it, and get the live product tested end to end so you see where people get stuck, not just what they say.

Sources

  1. Reddit — r/roastmystartup, top posts of the month (via ScrapeCreators, retrieved 17 Nov 2026)
  2. Indie Hackers — Homepage
  3. Peerlist Help Center — Launchpad rules and guidelines
  4. Microlaunch — Premium: feedback and roasts over 30 days (checked 17 Nov 2026)
  5. Hacker News — Show HN guidelines
  6. Science of Apps — Product investigation: what we investigate and how
  7. Checked November 17, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free, forever

Launch day ends. Your listing shouldn't.

Once you have a live product, list it free and get evidence-based feedback: your product tested end to end, with every finding backed by a measurement or pinned to the screen it came from.

Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free PDF · 188 pages · 2 editions

Unmistakable: the logo book

How the world’s greatest logos are made, chosen and kept — and how to make yours. 98 short lessons and 19 true stories for founders, designers and the curious. By Sushant Singh, founder of Science of Apps.

  • 98 lessons
  • 19 true stories
  • 60+ real logos

Why did a $35 sketch become the Swoosh, and why did Gap lose its nerve in six days? It’s all inside.

Pick your edition