Build Cleverly is not a black box. Here's a complete explanation of how we derive scores from community discussion data.
We crawl publicly accessible community discussions from the following platforms. All sources are linked in reports:
Posts and comments from r/SaaS, r/indiehackers, r/webdev, and related subreddits
Primary data source, widest coverage
Comments from Ask HN, Show HN, and related discussion threads
Excellent technical user coverage
Product discussions, milestone sharing, community Q&A
Valuable indie dev WTP insights
Other relevant forums, product review sites, and public discussions
Supplementary source, broadens signal diversity
Measures overall demand for this type of product in the target market. Calculated through post volume, discussion trends, keyword frequency, and other metrics.
Key Signals
Measures the intensity of target users' current pain points. Uses sentiment analysis to identify high-emotion vocabulary (frustrated, waste, hate, need desperately, etc.).
Key Signals
The most critical dimension and the hardest signal to fake. We only count original evidence where users explicitly mention willingness to pay, not inferred 'felt need' signals.
Key Signals
WTP Hard Threshold: When fewer than 5 explicit payment intent discussions are found, the overall score is capped at 60.
Analyzes existing solution coverage and user satisfaction in the market to identify differentiation opportunities. More competition means less space, but zero competition may mean no market exists.
Key Signals
Measures how identifiable and reachable the target user group is. Vague targets ('everyone') lower the score; precise user profiles raise it.
Key Signals
The only dimension based on internal assessment rather than external evidence β estimated from tech stack maturity and competitor implementation cycles. Lowest weight, doesn't determine the overall verdict.
Key Signals