What We Look For
Signals strong enough to justify deeper validation work.
- A narrow buyer and one repeated workflow problem worth paying to improve.
- Public evidence that the category already has demand, vendors, budgets, or stubborn workarounds.
- A product wedge that can be explained clearly without enterprise-level sprawl on day one.
- Enough market and pricing context to judge whether the idea can support a paid product.
What Makes An Idea Survive
Ideas stay in the database when the commercial logic still holds up.
- The buyer and trigger event are clear enough that discovery work can start immediately.
- The MVP can be scoped without solving several products at once.
- The category already supports believable pricing or willingness-to-pay signals.
- The product can be positioned against real alternatives instead of fantasy whitespace.
What We Exclude
Interesting does not automatically mean investable.
Vague buyer painIf the buyer cannot describe the pain clearly, the idea does not earn top priority.
Unscoped product sprawlIf the first version needs too many users, workflows, or integrations, the idea weakens fast.
Zero proof of spendIf there is no sign of existing demand, budget, or painful workaround, caution goes up sharply.
What The Purchase Includes
Rows designed to reduce research time after checkout.
The paid database packages this methodology into a working system: idea core, buyer signals, market context, product framing, pricing logic, proof planning, and launch copy. The product is meant to shorten evaluation time, not to replace the interviews and execution work that still decide outcomes.
Next Step
Check the standard, then decide whether the full catalog is worth buying
Read a few public dossiers after this page. If the research structure feels like the kind of judgment support you want across a larger catalog, that is the moment to move to pricing.