The black fox jumps quickly over the lazy dog Fastly
Idea type: Minimal Signal
There’s barely any market activity - either because the problem is very niche or not important enough. You’ll need to prove real demand exists before investing significant time.
Should You Build It?
Not yet, validate more.
Your are here
Based on the limited data, your idea falls into the "Minimal Signal" category. This means that similar products haven't generated much market activity, indicating a potentially niche or unimportant problem. With only two similar products found and low engagement (an average of 1 comment per product), it's hard to gauge real demand. The absence of positive or negative signals regarding use or purchase further emphasizes the uncertainty. Before investing significant time and resources, it's crucial to validate whether a genuine need exists for your idea. Consider this phase as an opportunity to test the waters without diving in headfirst.
Recommendations
- Given the minimal signal, begin by directly engaging with potential customers in online communities. Share your idea in relevant forums, groups, or subreddits and carefully observe the responses. Instead of immediately pitching a product, frame your posts as questions or discussions around the problem you're aiming to solve, gauging whether others experience the same pain points. Be prepared for potentially lukewarm reception and use that as a data point.
- Before building anything, offer to solve the core problem manually for 2-3 potential customers. This could involve providing a service, creating a temporary workaround, or even just offering personalized advice. This hands-on approach helps you deeply understand their needs, identify hidden complexities, and gather invaluable feedback to inform your product development.
- Create a short, simple explainer video that clearly articulates the problem you're addressing and your proposed solution. Host it on a platform like YouTube or Vimeo and track how many people watch it fully. This helps determine whether people are interested enough to invest their time in understanding your concept. Make sure to include a clear call to action in the video, such as signing up for an email list or requesting more information.
- Gauge commitment by asking for a small, non-refundable deposit to join a waiting list for your product. This serves as a tangible indication of genuine interest, separating curious onlookers from potential customers who are willing to invest financially. Clearly communicate what they'll receive in exchange for their deposit, such as early access, exclusive features, or a discounted price.
- Set a clear deadline: If you can’t find 5 genuinely interested people willing to take one of the previous actions within 3 weeks, honestly reconsider your idea. This isn't a failure, but rather a valuable learning experience that saves you from investing in a product that the market doesn't want. Be open to pivoting to a related problem or exploring alternative solutions based on what you've learned.
Questions
- Given the lack of existing use/buy signals, what assumptions am I making about the user's pain points that might be incorrect? How can I directly validate these assumptions through user interviews or surveys?
- If similar products haven't gained traction, is it due to a lack of awareness, poor execution, or a fundamental flaw in the problem being addressed? How can I differentiate my approach to overcome these challenges?
- What are the minimal set of features needed to solve the core problem effectively for my initial users? How can I iterate quickly based on their feedback to avoid over-engineering a solution that doesn't resonate with the market?
Your are here
Based on the limited data, your idea falls into the "Minimal Signal" category. This means that similar products haven't generated much market activity, indicating a potentially niche or unimportant problem. With only two similar products found and low engagement (an average of 1 comment per product), it's hard to gauge real demand. The absence of positive or negative signals regarding use or purchase further emphasizes the uncertainty. Before investing significant time and resources, it's crucial to validate whether a genuine need exists for your idea. Consider this phase as an opportunity to test the waters without diving in headfirst.
Recommendations
- Given the minimal signal, begin by directly engaging with potential customers in online communities. Share your idea in relevant forums, groups, or subreddits and carefully observe the responses. Instead of immediately pitching a product, frame your posts as questions or discussions around the problem you're aiming to solve, gauging whether others experience the same pain points. Be prepared for potentially lukewarm reception and use that as a data point.
- Before building anything, offer to solve the core problem manually for 2-3 potential customers. This could involve providing a service, creating a temporary workaround, or even just offering personalized advice. This hands-on approach helps you deeply understand their needs, identify hidden complexities, and gather invaluable feedback to inform your product development.
- Create a short, simple explainer video that clearly articulates the problem you're addressing and your proposed solution. Host it on a platform like YouTube or Vimeo and track how many people watch it fully. This helps determine whether people are interested enough to invest their time in understanding your concept. Make sure to include a clear call to action in the video, such as signing up for an email list or requesting more information.
- Gauge commitment by asking for a small, non-refundable deposit to join a waiting list for your product. This serves as a tangible indication of genuine interest, separating curious onlookers from potential customers who are willing to invest financially. Clearly communicate what they'll receive in exchange for their deposit, such as early access, exclusive features, or a discounted price.
- Set a clear deadline: If you can’t find 5 genuinely interested people willing to take one of the previous actions within 3 weeks, honestly reconsider your idea. This isn't a failure, but rather a valuable learning experience that saves you from investing in a product that the market doesn't want. Be open to pivoting to a related problem or exploring alternative solutions based on what you've learned.
Questions
- Given the lack of existing use/buy signals, what assumptions am I making about the user's pain points that might be incorrect? How can I directly validate these assumptions through user interviews or surveys?
- If similar products haven't gained traction, is it due to a lack of awareness, poor execution, or a fundamental flaw in the problem being addressed? How can I differentiate my approach to overcome these challenges?
- What are the minimal set of features needed to solve the core problem effectively for my initial users? How can I iterate quickly based on their feedback to avoid over-engineering a solution that doesn't resonate with the market?
- Confidence: Low
- Number of similar products: 2
- Engagement: Low
- Average number of comments: 1
- Net use signal: 0.0%
- Positive use signal: 0.0%
- Negative use signal: 0.0%
- Net buy signal: 0.0%
- Positive buy signal: 0.0%
- Negative buy signal: 0.0%
The x-axis represents the overall feedback each product received. This is calculated from the net use and buy signals that were expressed in the comments. The maximum is +1, which means all comments (across all similar products) were positive, expressed a willingness to use & buy said product. The minimum is -1 and it means the exact opposite.
The y-axis captures the strength of the signal, i.e. how many people commented and how does this rank against other products in this category. The maximum is +1, which means these products were the most liked, upvoted and talked about launches recently. The minimum is 0, meaning zero engagement or feedback was received.
The sizes of the product dots are determined by the relevance to your idea, where 10 is the maximum.
Your idea is the big blueish dot, which should lie somewhere in the polygon defined by these products. It can be off-center because we use custom weighting to summarize these metrics.