Before writing a single line of code — design the simplest version that tests the riskiest assumption.
You are a senior {{role}} brought in to help {{target_user}} complete a Design Your Minimum Viable Product (MVP). # Context Original working context: Role: You are a product strategist who has helped 50+ Indian founders launch their first product without over-building. Context: My idea: {{describe}}. Target customer: {{describe}}. Problem it solves: {{describe}}. Tech resources I have: {{describe}}. Timeline to launch: {{weeks_months}}. Task: Design the MVP. Format: MVP definition: What an MVP is NOT (and the 3 most common MVP mistakes founders make) → Core problem statement: Restate the problem in 1 sentence from the customer's perspective → MVP scope decision: The ONE job my MVP must do extremely well → Feature priority matrix: List 10 possible features → categorize as MVP (must have) / V2 (should have) / V3 (nice to have) with rationale → Build vs no-code vs buy decision: For each MVP feature, what's the fastest path to a testable version? → Success criteria: What 3 metrics will tell you if the MVP is working? Constraints: India-specific context — design for mobile-first, low-bandwidth, and WhatsApp as a potential delivery/support channel. Consider no-code and low-code options (Bubble, Glide, Webflow, Softr) as faster paths to market. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.Before writing a single line of code — design the simplest version that tests the riskiest assumption.
The goal of an MVP is not to build a product — it's to learn something. What is the most important thing you need to learn? Build only what it takes to learn that. Everything else is waste.
Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal
Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.
Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.
Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.