Validate Guide
Demand is real almost everywhere; coverage is what kills most ideas. Before you invest research or build time, the gapquery-validate skill pressure-tests an opportunity against the real world.
Why Validate #
GapQuery's signals are strong candidate-generators, but a high score is not proof of an opening. A workflow can look wide open because no app describes itself in the same words, while a broad incumbent already covers it. Validate catches that before you commit.
Demand Check #
Validate web-searches forums, Reddit, and communities for evidence that people actually do this workflow and feel the pain — not just that an app-store category exists.
- Confirmed: Clear, repeated demand in real user discussions.
- Weak: The pain shows up only as a sub-need of something else.
- None: No real-world signal beyond the raw score.
Coverage Check #
Then it checks whether the gap is already solved — including by tools outside the app marketplace (standalone SaaS, broad platforms) that the in-marketplace signals can miss.
- Open: No credible solution exists yet.
- Partial: Solved in part, with room for a sharper wedge.
- Covered outside marketplace: Already handled by established tools elsewhere.
Market-Reality Verdicts #
Validate saves a market-reality verdict (demand plus coverage) onto the opportunity. It shows on the opportunity page and is carried into discovery, so an idea you have already disproven does not resurface as fresh.
Running Validation #
- Surface or save an opportunity with discover
- Ask Claude to validate it: "Validate the supplier reliability monitoring idea"
- Validate runs the demand and coverage web checks and reports a verdict
- The verdict is saved through the save-market-reality MCP tool
