Extract win and loss drivers from CRM notes
Turn raw CRM deal records into actionable product, pricing, and sales execution patterns. Use it to prepare roadmap reviews and board updates.
You getTop 3 Win Drivers, top 3 Loss Drivers and immediate Product Takeaway
Prompt
Act as a product operations analyst. Synthesize the provided raw CRM win/loss deal notes into clear decision drivers and recurring themes.
Rules:
- Separate product feature gaps from commercial, pricing, and sales execution reasons.
- Group findings by frequency: primary drivers (repeated across multiple deals) versus isolated one-offs.
- Contrast what won closed-won deals against what killed closed-lost opportunities.
- Keep insights concise, factual, and strictly based on the text.
Output format:
- Top 3 Win Drivers (Theme, evidence summary, affected segments)
- Top 3 Loss Drivers (Theme, product vs. commercial classification, deal impact)
- Immediate Product Takeaway (One clear priority to unblock pipeline)
CRM deal notes are below:Example output
Export 10 to 30 deal notes from Salesforce or HubSpot and paste them after the prompt in ChatGPT, Claude, or Gemini. Ask the model afterward to prioritize the losses by estimated deal value if dollar amounts were included.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Transform Customer Interview Transcripts into Ranked Pain-Point Matrix
Turn raw interview notes into a structured matrix that ranks customer pain points by frequency and business impact to guide your product roadmap.
Score beta readiness for general availability release
Evaluate qualitative feedback, bug logs, and usage stats to decide if a beta is ready for general availability. Use this to make unbiased release decisions.
Build a Competitor Feature Comparison and Positioning Summary
Get a feature comparison table with every cell tagged as user-provided or needing verification, plus win/lose points, a positioning statement and a fact-check list.
Draft a working-backwards press release and FAQ
Write an Amazon-style press release and hard FAQ to clarify customer value and address tough technical questions before writing code.
Define Feature Non-Goals and Scope Boundaries
Sort requested features into three clear out-of-scope buckets with explicit business reasons to prevent scope creep.
Prioritize a Feature Backlog Using the Kano Model
Sort backlog items into Must-Be, Performance, or Delighter buckets based on user reaction to absence, clarifying which features prevent churn versus drive growth.
- Prioritize Your Feature Backlog with RICE Scoring and Flagged Weak Assumptions
- Create a quarterly win-loss brief for sales teams
- Design a customer grandfathering plan for pricing changes
- Draft a customer advisory board charter
- Plan a listening-first advisory board agenda
- Rewrite empty state copy to accelerate user activation