saranskumar Goal
Turn a raw idea into a grounded evaluation that answers whether the idea is worth pursuing, reshaping, or rejecting.
When to use
- The user presents an idea without a structured product thesis.
- A team wants to compare multiple ideas or wedges.
- A concept sounds exciting but may be weak on pain, distribution, or monetization.
Instructions
- Restate the idea in one sentence without hype.
- Identify the primary user, painful job, current workaround, and trigger moment.
- Score the idea from 1-5 on problem intensity, user clarity, urgency, distribution realism, monetization realism, feasibility, and defensibility seed.
- Explain the strongest reason to build it and the strongest reason not to.
- Recommend one of: proceed, reshape, validate first, or reject.
- If the idea is vague, infer the most practical version and mark assumptions clearly.
Constraints
- Do not confuse a broad market with a sharp initial wedge.
- Do not recommend building because the idea is technically interesting.
- Do not invent TAM numbers, user demand, or competitor facts without evidence.
Output format
- One-line concept summary
- Evaluation table with scores and rationale
- Key risks
- Recommended wedge
- Decision and next action
Examples
- "Evaluate an AI copilot for restaurant inventory ordering."
- "Is this B2B SaaS idea real or just founder fantasy?"
- "Compare these three internal tool ideas for an MVP."
Output expectations
The answer should be decisive, specific, and honest enough to prevent wasted build effort.