Before you build
Check whether people already describe the problem, and in what words, before you commit months to a solution.
The costliest mistake early on is building something nobody was asking for. This use case is about finding out first, while changing course still costs almost nothing.
The decision
Do enough people already talk about this problem to justify building a solution?
Why it is worth checking first
Founders usually test an idea by asking people if they like it. People are polite, and a "yes, interesting" costs them nothing. What they say unprompted, in reviews, threads and questions to strangers, is a different kind of evidence. If the problem shows up on its own, in plain words, it is more likely to be real.
How Wisentry helps
Wisentry reads public conversation about your idea's space and groups it into the problems people raise, the words they use, and the places they gather. You see whether the problem shows up on its own, or only when you bring it up.
A walk-through (illustrative)
Say a founder is thinking about a reusable bottle for people who climb. Reading the conversation, three things could happen:
- People complain about the problem in their own words, again and again, in several places. That is a point in favour.
- People mention it once in passing, and the loud thread turns out to be one person. That is noise. Our guide on telling a real demand signal from noise shows how to tell the two apart.
- People talk about a nearby problem instead. That is worth knowing before the build, not after it.
Then test with something small
Conversation is a signal, not proof of demand. The cheapest next step is a stand-in for the product: a simple page that describes it with a button to join a waitlist, or a "coming soon" option that records interest. Pre-orders are a stronger signal than a waitlist, because paying is harder than clicking. Decide in advance what counts as enough interest, and be honest on the page about what happens after the click. Our guide on validating B2C demand before you build goes through the steps.
What you take away
- The problems people describe, in their own phrasing
- Where those conversations happen
- Objections that would slow a first customer down
- A short list of what you would still need to confirm with real people
Watch out for
- Treating volume as demand. A lot of talk can come from a few voices.
- Searching only for the answer you hope to find.
- Skipping the small real-world test because the reading looked good.
Treat this as evidence to weigh, not a verdict. Public conversation is only one input, and it can mislead. Once the problem looks real, choosing a first market is the next decision.
Example only, not a customer story.
