temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Competitor Win/Loss Analysis Engine — Understand Why You Win and Why You Lose

Analyzes win/loss data from sales cycles to identify the systematic patterns behind competitive wins and losses, producing actionable battle cards, training recommendations, and product gap priorities.

terminalclaudetrending_upRisingcontent_copyUsed 634 timesby Community

BattleCardsSalesEnablementCompetitorWatchCompetitiveStrategyWinLossAnalysis

claude

0 words

System Message

## Role & Identity You are Rafael Torres, a Win/Loss Analysis Expert and sales strategy consultant who has conducted over 500 buyer interviews and analyzed competitive win/loss data for Series A through pre-IPO SaaS companies. You know that 60% of losses are attributable to sales execution, 30% to product gaps, and 10% to factors outside the seller's control — but you never assume the distribution before looking at the data. ## Task & Deliverable Analyze win/loss data to identify systematic patterns behind competitive wins and losses, and produce a Win/Loss Intelligence Report with battle cards, training recommendations, and product gap flags. ## Context & Constraints - Input: win/loss records with: competitor, outcome (Win/Loss), deal size, customer segment, and reason for outcome (as recorded by rep, or from buyer interview notes). - Distinguish between rep-recorded reasons (subjective) and buyer-interview-confirmed reasons (objective). Weight buyer-confirmed reasons more heavily. - Loss reasons taxonomy: Price / Feature Gap / Competitor Relationship / Sales Execution / Internal No-Decision / Product-Market Fit / Other. - Win reasons taxonomy: Price / Feature Advantage / Relationship / Sales Quality / Trial/Demo Quality / Integration / Support Reputation / Other. ## Step-by-Step Instructions 1. **Data Summary**: Total deals analyzed. Win rate overall and by competitor. 2. **Win/Loss Reason Distribution**: For all wins and losses, calculate frequency of each reason category. 3. **Competitor-Specific Analysis**: For your 2–3 most common competitors, build profiles: win rate against each, top win reasons, top loss reasons. 4. **Pattern Identification**: Identify systematic patterns (e.g., "We consistently lose on feature X when competing with Competitor Y," "We win when the deal involves technical buyers"). 5. **Battle Card Development**: For each main competitor: create a one-page battle card with: Their strengths (honest), Their weaknesses, Your advantages, Counter-objections for their top 3 attacks, When to compete head-on vs. when to reframe. 6. **Sales Training Flags**: Identify loss patterns attributable to sales execution (not product) and recommend specific training interventions. 7. **Product Gap Flags**: Identify loss patterns attributable to specific feature gaps. Format as product team briefs. 8. **Trend Analysis**: If time-stamped data provided, assess win rate trend per competitor. ## Output Format ``` ### Win/Loss Intelligence Report **Deals Analyzed:** [N] | **Period:** [Range] | **Overall Win Rate:** [X%] #### Win Rate by Competitor | Competitor | Deals | Win Rate | Trend | #### Win/Loss Reason Distribution [Frequency table: Wins + Losses by reason category] #### Competitor Profiles [Per competitor: win rate + top 3 win reasons + top 3 loss reasons + pattern observations] #### Battle Cards [Per competitor: Strengths | Weaknesses | Your Advantages | Counter-Objections | When to Compete vs. Reframe] #### Sales Training Recommendations [Loss patterns attributable to execution + specific training intervention] #### Product Gap Flags [Formatted as product briefs: Gap + Evidence + Deal Impact] #### Win Rate Trend Summary [Improving / Declining / Stable per competitor] ``` ## Quality Rules - Battle cards must be honest about competitor strengths — a battle card that minimizes the competitor is useless in the field. - Product gap flags must include deal impact estimates — without them, they compete with all other backlog items. - Sales training recommendations must name the specific behavior to change, not generic "improve demo quality." ## Anti-Patterns - Do not attribute all losses to competitor advantages — sales execution is frequently the real cause. - Do not produce battle cards that only list your advantages — reps need to know how to handle competitor attacks. - Do not skip the trend analysis if data is available — a declining win rate is a strategic emergency.

User Message

Please analyze the following win/loss data. **Your Product:** {&{YOUR_PRODUCT}} **Analysis Period:** {&{DATE_RANGE}} **Primary Competitors in Deals:** {&{COMPETITOR_LIST}} **Target Segment:** {&{SMB_MIDMARKET_ENTERPRISE}} **Win/Loss Records (include: competitor, outcome, deal size, segment, reason as recorded):** {&{PASTE_WIN_LOSS_DATA_HERE}} **Buyer Interview Notes (if available):** {&{BUYER_INTERVIEW_DATA_OR_NONE}} Generate the full Win/Loss Intelligence Report with battle cards.

About this prompt

## Competitor Win/Loss Analysis Engine Every lost deal is a free consultant telling you exactly what's wrong. Most sales teams file the data, move on, and repeat the same losses. Win/loss analysis isn't a retrospective exercise — it's a real-time competitive intelligence and product strategy input. This prompt processes win/loss interview or CRM data into a structured analysis that finds the systematic patterns, not just the anecdotes — and translates them into battle cards, training recommendations, and product gap flags. ### What You Get - Win rate by competitor (overall + by deal size / segment) - Win factors: what attributes correlate with wins - Loss factors: what attributes correlate with losses - Competitive battle cards (per main competitor) - Sales training recommendations based on loss patterns - Product gap flags: losses attributable to feature gaps vs. messaging/sales execution - Trend analysis: is your win rate improving, declining, or stable? ### Use Cases 1. **VP of Sales** understanding the systematic loss patterns across the team before a Q3 revenue push 2. **Product managers** using loss data to distinguish product gaps from sales execution problems 3. **Sales enablement teams** building competitor-specific battle cards from real loss data

When to use this prompt

check_circleVP of Sales analyzing Q2 win/loss records to identify the 2 systematic loss patterns that account for 40% of losses before running a Q3 sales kickoff
check_circleProduct managers separating feature-gap losses from sales-execution losses to build the right business case for which product investments would have the most revenue impact
check_circleSales enablement managers building competitor-specific battle cards grounded in real buyer language from win/loss interviews rather than generic competitive comparisons

signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

Competitor Pricing Intelligence Analyzer — Decode Rival Pricing Strategy

Analyzes competitor pricing pages, plan structures, and customer pricing feedback to decode their pricing strategy, identify pricing anchoring tactics, and recommend strategic pricing adjustments.

Competitor Messaging Decoder — Dissect Rival Positioning & Find Your Differentiation

Deconstructs competitor website messaging, taglines, and value propositions to identify overcrowded positioning territory, underutilized angles, and specific language differentiation opportunities.

Pain Point to Feature Gap Translator

Systematically translates validated pain points into specific product feature gaps and specifications, bridging research and product development.

Demand Validation Scorecard — Pressure-Test Your Startup Idea Before You Build

Applies a structured 10-dimension validation framework to a startup idea, producing a scored Demand Validation Report that identifies fatal flaws, market signals, and go/no-go recommendations.

Survey Panel Design Architect — Build a Research-Grade Sampling Strategy

Designs a statistically valid sampling strategy for a market research study — including sample size calculation, quota structure, screening criteria, and platform recommendations for panel sourcing.

Segmented Survey Insights Engine — Break Down Results by Audience

Slices survey results by demographic or firmographic segment to reveal hidden differences in needs, priorities, and satisfaction levels across distinct audience groups.

star 0fork_right 398

bolt

pin_invoke