Validating an idea isn't about proving you're right — it's about finding out, as cheaply and honestly as possible, whether you're wrong before that mistake becomes expensive.
Start with the problem, not the product
The first question isn't "would people use this?" — it's "is this a real, specific problem that people already try to solve today, even badly?" If the answer is no, the product idea usually isn't ready yet, no matter how well it's designed.
Good signs the problem is real:
- People are already paying for imperfect solutions (spreadsheets, manual work, a competitor they complain about)
- The problem costs real time or money on a recurring basis
- You can describe exactly who has this problem, not just "everyone"
Talk to potential users before you design anything
Conversations with 10–15 people who genuinely have the problem you're targeting will tell you more than a landing page with a signup form. Ask about how they solve the problem today — not whether they'd use your future product. What people say they'd use and what they actually use are often different things.
Test willingness to pay, not just interest
Interest is easy to get; a genuine commitment is a much stronger signal. That can look like:
- A small number of people agreeing to pay for early access before it exists
- A pilot customer willing to commit real time to testing a rough version
- An existing business agreeing to change a real workflow to try it
Build the smallest thing that tests the real risk
Once the problem is validated, the next step isn't the full product — it's the smallest version that tests your riskiest assumption. See our article on MVP vs. full product for how to scope that.
Where AfroSaaS fits in
Validation is part of our Discover stage — we help you get clear on the real problem and the riskiest assumption before we define what the first build should include. Tell us about your idea and we'll help you think it through.