sales-venturevault

name	sales-venturevault
description	VentureVault (venturevault.space) platform help — a free IdeaBrowser alternative: a browsable vault of AI-scored, pre-researched startup ideas (market analysis, opportunity scores, revenue/execution/go-to-market signals) for indie hackers, makers, and first-time founders hunting for something to build. 100% free forever, no credit card; a web app plus iOS/Android apps, open-source on GitHub. Use when browsing VentureVault's idea vault to find a niche worth building, interpreting its opportunity scores and market analysis, comparing it to the paid IdeaBrowser, asking whether it has an API to export the ideas, or judging whether a browsable idea equals validated demand. UI-only, NO public API/webhooks/Zapier/MCP; the GitHub repo is the app source, not a data API. Do NOT use for the tool-agnostic validate-before-building method or comparing idea validators across the market (use /sales-idea-validation), or building the smoke-test landing page (use /sales-funnel).
argument-hint	[describe what you need help with in VentureVault]
license	MIT
version	1.0.0
tags	["sales","validation","pre-launch","platform"]
github	https://github.com/Stevekaplanai/venturevault

VentureVault Platform Help

VentureVault (venturevault.space — the canonical domain; venturevault.co is a dead skeleton and there are unrelated "Venture Vault" namesakes) is a free IdeaBrowser alternative: a browsable vault of AI-scored, pre-researched startup ideas. Each idea entry comes with AI-powered market analysis and opportunity scores (revenue potential, execution difficulty, go-to-market signals, community interest) so you can discover → analyze → launch something worth building. It's 100% free forever, no credit card — a web app plus native iOS/Android apps, open-source on GitHub. It's an idea-discovery / research tool, not proof of demand, and it has no public API (a UI app; the GitHub repo is the app's own source, not a data API).

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

Ask only what you can't infer:

1. What do you want from VentureVault?
   • A) Browse the vault to find a niche / idea worth building
   • B) Interpret an idea's opportunity score and market analysis
   • C) Compare it to the paid IdeaBrowser (or other free alternatives)
   • D) Get the ideas out / automate them (export / API reality)
   • E) Judge whether a browsable idea = validated demand
2. What's the real question — "what should I build / is this idea worth building?" or "how do I use this tool?" If it's the go/no-go decision, that's /sales-idea-validation (browsing a curated idea list and reading an AI score are not demand) — route in Step 2.

Skip-ahead: if the user wants the validate-before-building method or to compare validators across the market, that's a /sales-idea-validation question — route immediately.

Step 2 — Route or answer directly

If the user's question is about…	Route to
The validate-before-building method, or the go/no-go decision itself	/sales-idea-validation {question}
Comparing VentureVault against other validators/discovery tools (BuildOrNot, IdeaBrowser, Validator AI…)	/sales-idea-validation {question}