Library
Production-ready prompts curated by the SYNTHESE team — copy and use instantly.
Convert product URLs and notes into a structured competitor analysis you can actually use.
Act as a product strategist. Build a competitor teardown and comparison matrix for the products below. Products / URLs: [LIST PRODUCTS OR URLS] Our product: [DESCRIBE YOUR PRODUCT] Output: 1. Market Summary - What category this market is really in - What buyers appear to care about most 2. Competitor Matrix | Product | ICP | Core promise | Strengths | Weaknesses | Pricing signal | Notable differentiator | |--------|-----|--------------|-----------|------------|----------------|------------------------| 3. Messaging Patterns - Common claims across competitors - Overused language / cliches - White-space positioning opportunities 4. Feature Gaps - What competitors all have that we do not - What we have (or could own) that they do not 5. Strategic Recommendations - 3 product moves - 3 positioning or GTM moves Rules: - Be specific, not generic - Use evidence from the provided material - If something is unclear, mark it [VERIFY]
Turn messy customer calls into clear pains, motivations, objections, and product opportunities.
You are a senior product researcher. Analyze the customer interview notes or transcript below and turn them into a concise product insight report. Interview Material: [PASTE NOTES OR TRANSCRIPT] Output: 1. Interview Snapshot - Who this person is - Their context / workflow - What they were trying to accomplish 2. Core Problems - List the top 3-5 pain points in the customer's own words where possible 3. Jobs To Be Done - Functional job - Emotional job - Social job 4. Existing Workarounds - What they do today - What is frustrating or inefficient about it 5. Objections / Purchase Barriers - What made them hesitant - What proof or product change would reduce that hesitation 6. Product Opportunities - 3 concrete opportunities - For each: urgency, expected impact, and why it matters Rules: - Separate fact from inference - Quote short verbatim phrases when useful - Flag assumptions with [INFERENCE] - Keep it tight and useful for a product team
Build a detailed, research-quality user persona from a product description.
You are a UX researcher. Based on the product description below, generate a detailed user persona. Product: [PRODUCT DESCRIPTION] Output the persona in this format: - Name & Photo Prompt (describe the person for a stock photo search) - Demographics (age, occupation, location, income) - Goals (3 primary goals related to your product) - Frustrations / Pain Points (3 key frustrations) - Behaviors & Habits (how they currently solve the problem) - Quote (a one-sentence verbatim-style quote that captures their mindset) - Preferred Channels (where they discover products)
Draft a comprehensive Product Requirements Document for a new feature in seconds.
You are a Senior Product Manager. Write a Product Requirements Document (PRD) for the following app feature: [FEATURE NAME/DESCRIPTION]. Include: 1. Problem Statement — What user pain point are we solving? 2. Target Audience — Who is this for? 3. User Stories — Format: "As a [type of user], I want to [action] so that [benefit]." 4. Core Requirements & Acceptance Criteria — Bullet points of what must be built. 5. Out of Scope — What we are explicitly NOT building in this iteration. Target Platform: [iOS / Android / Web]