· 5 min read
How to Get Honest Feedback on Your Startup or App Idea
Most idea feedback is polite and useless. How to ask the right people the right questions, test demand before you build, and turn the answers into decisions.
You've got an idea for an app or a startup and you want to know if it's any good. So you ask friends, family and classmates. They say it's great. Six months and a lot of code later, nobody uses it.
The feedback wasn't wrong because people lied. It was wrong because of how it was asked. "Would you use this?" invites kindness, not truth. This guide shows how to get feedback you can actually build on: who to ask, what to ask, and how to tell real interest from politeness.
Why most idea feedback misleads you
- People are polite. Especially in India, friends and seniors don't want to discourage you.
- Hypothetical questions get hypothetical answers. "Would you pay for this?" costs nothing to answer with yes.
- You ask the wrong people. Your friends may not have the problem you're solving.
- You pitch instead of listen. Once you've explained your idea with excitement, people respond to your excitement, not the idea.
Rule 1: Ask about their past, not your idea
The most reliable signal is what people already do. Instead of describing your app, ask about the problem:
| Instead of | Ask |
|---|---|
| "Would you use an app that tracks shared expenses?" | "The last time you split a trip's costs with friends, how did you do it?" |
| "Do you think this is a good idea?" | "What's the hardest part of doing this today?" |
| "Would you pay ₹99 a month for this?" | "Have you paid for anything to solve this? What, and how much?" |
| "Would this feature be useful?" | "When did this problem last cost you time or money?" |
If people can't remember the last time they had the problem, or have never tried to solve it, that tells you more than any compliment.
Rule 2: Show something concrete
Ideas in your head are easy to like. Something people can see or click gets sharper reactions:
- A one-page landing page that explains what it does and asks for an email.
- A clickable prototype made in a design tool.
- A two-minute screen recording of a rough version.
- A manual version of the service, run by you, before any code exists.
Watch what people do with it. Where do they get confused? What do they try to click that doesn't exist yet?
Rule 3: Ask two kinds of people
You need two different kinds of feedback, from two different groups:
- People with the problem tell you whether it's worth solving: demand, urgency, what they use today and what they'd pay.
- Builders tell you whether your approach makes sense: the technical approach, the user experience, pricing and what to build first.
Mixing them up causes trouble. A developer may love your architecture for a problem nobody has; a potential user can't tell you whether your tech stack will scale.
Rule 4: Look for commitment, not compliments
Compliments are free. Commitments cost something, which makes them real signals:
- They give you their email or phone number to try it first.
- They agree to a follow-up call or a test next week.
- They introduce you to someone else with the same problem.
- They pre-order, pay a deposit or sign a letter of intent.
- They use your rough version more than once without being asked.
If you get lots of "great idea!" and none of these, treat it as a "no."
A one-week feedback plan
| Day | Do this |
|---|---|
| 1 | Write the problem in one sentence and list three assumptions that must be true. |
| 2 | List 15 people who have the problem and 5 builders whose opinion you trust. |
| 3–4 | Run short conversations with the people who have the problem. Ask about their past, take notes, don't pitch. |
| 5 | Show builders your landing page or prototype and ask specific questions. |
| 6 | Group what you heard: repeated pains, repeated objections, real commitments. |
| 7 | Decide: build, change direction, or test a different assumption next week. |
Where to get honest feedback in India
- Your college E-cell or incubator. Mentors there see many ideas and are used to being direct.
- Hackathons and demo days. Judges and other teams give fast, technical feedback.
- Communities for your audience. Groups where your future users already spend time, approached respectfully.
- Early users. The first ten people who try your rough version are worth more than a hundred opinions.
- Builders on AILexityTedo. Post your product or feature idea on IdeaHub and developers, designers and founders tell you what to add or fix. TedoAI sums up the strongest ideas, so you're not reading every reply. Posting on IdeaHub is free.
Turn feedback into decisions
Feedback only helps if it changes what you do next:
- Count patterns, not opinions. One loud comment is a data point; the same pain from six people is a finding.
- Separate the problem from the solution. People are usually right about their problems and often wrong about the fix.
- Pick the riskiest assumption that's still untested and design your next small test around it.
- Write down what you decided and why, so you don't relitigate it every week.
FAQ
Will someone steal my idea if I share it?
Very rarely. Most people are busy with their own work, and ideas are worth little without execution. The risk of building in secret for months is far bigger than the risk of sharing.
How many people should I talk to?
Ten to fifteen conversations with people who have the problem usually show clear patterns. Keep going until you stop hearing anything new.
What if all the feedback is negative?
Then it worked: you learned something before spending months building. Check whether the problem is real but your solution is wrong, or whether the problem itself isn't painful enough.
Should I ask for feedback before writing any code?
Yes. The cheapest version of your idea, a page, a prototype or a manual service, is the best thing to test first.
The bottom line
Good feedback comes from asking about real behaviour, showing something concrete, talking to both users and builders, and trusting commitments over compliments. Then turn what you hear into one clear decision a week.
Ready to put your idea in front of builders? Post it on IdeaHub. When you've built something, show how you did it as a Blueprint, and if you need people to build with, read how to find a technical co-founder in India and how to split equity with a co-founder.