8 prompts across 6 disciplines. They work with Claude, ChatGPT and any serious LLM. Built for how product teams actually work, not generic templates.
Discovery & synthesis
User research synthesis
Turn raw interviews, surveys and analytics into prioritized, actionable insights.
LATAM context: Built for teams with no dedicated researcher: the PM runs the interviews and the synthesis.
See full prompt
You are a product researcher who specializes in insight synthesis. I'm sharing raw research data (interviews, surveys, analytics). Your job:
1. Identify and cluster recurring themes and pain points
2. Pull out actionable user needs
3. Flag contradictions or surprising findings
4. Prioritize insights by frequency and impact
5. Suggest product implications for each insight
Context: we're a product team in LATAM with no dedicated researcher. Give me a structured synthesis the team can use to prioritize the roadmap.
Structure feedback that comes from everywhere, WhatsApp included, into themes, sentiment and quick wins.
LATAM context: In LATAM feedback lives in WhatsApp and with the sales team. This prompt assumes that.
See full prompt
You are a product insights analyst. Analyze the following customer feedback from support tickets, reviews, WhatsApp messages and sales-team notes. Your goal:
1. Categorize the feedback by theme (feature requests, bugs, UX friction, price, etc.)
2. Compute frequency and sentiment per theme
3. Identify the top 5 pain points
4. Map the feedback to potential revenue impact
5. Separate quick wins from strategic initiatives
Give me actionable recommendations backed by evidence. If a theme shows up in only one channel, flag it: it may be channel bias, not the customer.
Prioritization & decisions
Prioritizing with scarce resources
Apply RICE or weighted scoring when the team is small and everything looks urgent.
LATAM context: Tuned for teams of 1-3 PMs where the CEO also has opinions on the backlog.
See full prompt
You are an expert in product prioritization. I have a list of competing features and initiatives, a small team and stakeholders with strong opinions. Help me prioritize:
1. Score each item on impact, effort, strategic alignment and customer value
2. Compute a composite priority score
3. Group into high / medium / low tiers
4. Identify dependencies and execution order
5. Write a narrative that explains the logic: I'll use it to defend the prioritization to leadership
Give me a prioritized roadmap that balances quick wins with long-term strategy.
Prioritization & decisions
Communicating hard trade-offs
Analyze conflicting priorities and draft the talking points to communicate the decision.
LATAM context: Includes the classic scenario: the big customer asking for custom work.
See full prompt
You are a product leader managing conflicting stakeholder requests (including a big customer asking for custom work). Help me analyze this trade-off:
1. State the competing priorities and constraints clearly
2. Lay out the pros and cons of each option
3. Quantify the impact on key metrics (revenue, engagement, churn)
4. Identify second-order consequences
5. Recommend a decision with clear reasoning
6. Draft talking points to communicate it to each stakeholder group
Keep the analysis transparent: even someone who disagrees should understand the logic.
Storytelling & communication
Product vision narrative
Build a vision story that works in a 5-minute pitch and in the daily standup.
LATAM context: Focused on mixed audiences: founders, engineering and sales in the same room.
See full prompt
You are a product strategist crafting our vision narrative. Create a compelling story that:
1. Opens with the customer's problem or opportunity
2. Paints the future state (the vision)
3. Explains why now is the moment
4. Connects to the company's strategy and values
5. Maps out the path and the key milestones
6. Inspires the team to commit
The narrative has to work in a 5-minute pitch to founders, in the quarterly review and in the team's daily communication. Skip the jargon: product, engineering and sales people will all hear it.
Product strategy
Positioning and differentiation
Define your strategic position and competitive edge, including what you are NOT focused on.
LATAM context: Accounts for global competitors landing in the region with bigger budgets.
See full prompt
You are developing our product's strategic positioning. Analyze our market opportunity and help me define:
1. Who is our core target customer?
2. What is our unique value proposition?
3. How do we differentiate from competitors, including the global ones landing in LATAM with bigger budgets?
4. What is our moat or defensibility (local context, distribution, data, community)?
5. What adjacent opportunities exist?
6. What are we NOT focused on?
The positioning should be concise, memorable, and guide every product decision.
Experimentation
Hypotheses and experiments with low traffic
Design rigorous but feasible experiments when you do not have the volume for classic A/B tests.
LATAM context: The reality of most B2B products in the region: small n, big decisions.
See full prompt
You are an expert in product experimentation. I want to validate a key hypothesis, but my product does not have enough traffic for a statistically significant A/B test. Help me:
1. State the hypothesis and the assumption it tests
2. Define the success metric and how to measure it
3. Pick the right method for low volume (smoke test, concierge, Wizard of Oz, validation interviews, customer pilots)
4. Estimate how many observations I need to decide with reasonable confidence
5. Identify biases and confounding variables
6. Define upfront what result would make me kill the idea
I'd rather have a reasonably informed decision this week than a perfect one in three months.
Retros & continuous improvement
Retro with no theater
Facilitate retros that capture real learning, not a post-it ritual.
LATAM context: With formats for remote teams spread across several time zones in the region.
See full prompt
You are facilitating a retrospective for a remote team spread across several LATAM time zones. Design a process that:
1. Creates psychological safety for honest reflection
2. Captures what worked, what didn't, and why
3. Separates systemic problems from one-off events
4. Prioritizes improvements by impact and effort
5. Turns insights into concrete actions with an owner and a date
6. Works async-first: part of it happens before the call
Structured but conversational. No empty rituals: if a format isn't generating learning, suggest killing it.