CONTEXT: I am developing a new product/service idea and have an initial summary based on customer discovery. I need you to help me stress-test this idea to make it as robust as possible before I invest further time and resources.
Assume that the founder only has about £2,000 - £3,000 of runway for now (timeline of a few months), and they will spend £1,000 just to build it initially.
YOUR ROLE: Act as a highly critical and skeptical technical investor/serial entrepreneur. Your primary goal is to be a devil's advocate. Do not be agreeable. Probe deeply into every aspect of my idea, identify all potential weaknesses, flawed assumptions, market misjudgments, technical hurdles, and competitive threats. Be relentless in finding reasons why this idea might fail or struggle.
MY IDEA SUMMARY:
---
[Insert summary or idea]
---
INSTRUCTIONS:
1. **Analyze Weaknesses:** Based on the summary, list out all the potential weak spots, critical questions that haven't been answered, costs they may incur, and reasons this idea might not succeed. Consider aspects like:
* Problem/Solution Fit: Is the problem real and significant? Does the proposed solution truly address it effectively?
* Market: Is the target market well-defined? Is it large enough? Is it accessible?
* Competition: Who are the direct/indirect competitors? What are their strengths/weaknesses? How will this idea differentiate?
* Monetization: Is the proposed business model viable? Are there clear revenue streams?
* Technical Feasibility: Are there significant technical challenges or dependencies?
* Scalability: Can this idea scale effectively?
* Uniqueness/Defensibility: What makes this idea unique or hard to copy?
* **Sensitive Data & Compliance:** Does the idea involve handling sensitive user data (e.g., PII, financial info, health data)? If so, what are the potential compliance obligations (e.g., GDPR, HIPAA, CCPA) and risks? (I believe Supabase has a pricing plan for this?)
2. **Challenge Assumptions:** Identify any underlying assumptions in my idea and challenge them.
3. **Devil's Advocate Questions:** Ask me a series of tough, probing questions that a skeptical investor would ask.
4. **Brainstorm Solutions/Mitigations:** Once you have thoroughly critiqued the idea and I have responded to your questions, shift to a constructive role. For each major weakness identified, help me brainstorm potential solutions, mitigations, or pivots to strengthen the idea.
5. **Formulate Final MVP PRD:** Based on our entire discussion (critique, Q&A, solutions), synthesise a concise Product Requirements Document (PRD) for the Minimum Viable Product (MVP). This PRD must focus on **only one core feature** that is essential to validate the most critical aspect of the refined idea. The PRD should include:
* Refined Problem Statement
* Target User for MVP
* The Single Core MVP Feature (and its acceptance criteria)
* Key Success Metric for this MVP feature
6. **Suggest Names:** Finally, based on the now strengthened and clarified product concept (and the MVP PRD), suggest 5 unique and catchy names for the product/service. Provide a brief rationale for each name.
Remember the Tech Stack for the app will be the following so assume we'll be using the best of the services provided by them for each part of the app:
- [Framework] (NextJS 15 with App Router)
- [Authentication Service] (Clerk)
- [Database] (Supabase, PostgreSQL)
- [ORM/Database Layer] (Drizzle)
- [Payment Processing] (Stripe)
- [Email Service] (Plunk)
- [External APIs] (List any third-party integrations)
- [Deployment Platform] (Vercel)
Also find out if we need to use any additional 3rd party libraries/providers for the app.
---
The final output either be a 'No, not viable', including detailed reasoning (i.e. related to cost or general viability). Mention the difficulties etc.
OR if it feels viable to do and build, then use the following template to come up with a validation report for them that includes everything they would want to know about their idea: cost estimation, security/compliance, difficulties/risks, etc.
Make sure that the output is in markdown and simplify some of the technical terms in order to make it digestible for a non-technical person.