Validate your idea with the community before coding

Writing code is cheap until it's expensive. Before investing 200 hours in an MVP, the highest-return validation you can do is putting the idea in front of people who think like your users, know product, and will answer without sugarcoating. Those people are already in the community — you just need to know how to ask.

What validation is NOT

• Telling a friend the idea and hearing "that's awesome."
• Posting on LinkedIn and counting likes.
• Asking "would you use this?" — everyone says yes and nobody uses it.

The internal pitch, in 5 blocks

When you share your idea with the community, structure the message like this:

1. Problem in one sentence, with the person who has it.
2. How that person solves it today (even if badly).
3. What you're proposing, in another sentence.
4. Why you think it deserves to exist, with a verifiable hypothesis.
5. What kind of feedback would be useful to you today.

Point 5 is the most important and the most ignored. If you don't ask for specific feedback, you'll get generic opinions. "What do you think?" gives you air; "do you see any obvious problem in this flow?" gives you a useful answer.

Three questions that change the conversation

• "Do you know anyone with this problem today?" — if nobody says yes, it's not widespread enough.
• "What would you do differently if you were in this project?" — separates product thinkers from information consumers.
• "What would make you use it, and what would make you not use it?" — ask for both sides; the full answer hides in the negative half.

Signs of real validation

• Someone tells you "I'd use that" without you asking.
• Someone sends you the name of a connection who has the problem.
• Someone proposes an improvement you hadn't thought of — a sign they're thinking about the product, not being polite.

Signs of fake validation

• Likes and "good idea" without commitment.
• Comments on the landing aesthetics, not on the problem.
• Enthusiastic people who never follow up.

What to do with what you learn

Write 3 sentences: what changed in your idea, what got confirmed, and what's still unresolved. Share them back with the community — closing the feedback loop makes you someone worth talking to, and next time you ask you'll get much more back.

Validation done well inside the community is the difference between shipping something nobody asked for and shipping something at least three people were already waiting for.