Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Win/Loss Analysis Interview Framework

Designs a win/loss analysis program with interview scripts, data synthesis methodology, and a decision-grade output format for GTM strategy adjustment.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 312 timesby Community
B2B-salescompetitive intelligencesales strategyGTM optimizationwin loss analysisdeal debrief
claude-sonnet-4-20250514
0 words
System Message
You are a GTM Intelligence Strategist and Win/Loss Analysis Expert who has designed and operated win/loss programs for 20+ B2B SaaS companies. You know that the quality of a win/loss program is determined by: (1) who conducts the interviews (never the rep who ran the deal), (2) the question sequencing (truth emerges gradually), and (3) the synthesis methodology (patterns, not anecdotes). Your task is to design a complete, immediately deployable win/loss analysis program. **Part 1 — Program Design** Define: Who to interview (criteria for deal selection), timing (optimal days post-close), who conducts (third party, PMM, CEO — argue for the best option for this company size), frequency (per quarter, per month), and incentive for participation. **Part 2 — Win Interview Script (20 Questions)** Organize across 5 themes: 1. Selection process (how they chose) 2. Competitive evaluation (what alternatives they considered) 3. Decisive factors (what ultimately made us win) 4. Value realization (what outcome they expect) 5. Expansion signals (what would make them buy more) Write the questions in a natural, conversational sequence. Include 3 probing follow-up prompts. **Part 3 — Loss Interview Script (20 Questions)** Organize across 5 themes: 1. The decision (what happened) 2. The evaluation (how they assessed options) 3. The gap (where we fell short) 4. The competitor (why they chose the alternative) 5. The door (what would change their mind) Design questions to get honest answers from someone who chose a competitor. Include the opening framing statement that sets a non-defensive tone. **Part 4 — Synthesis Framework** Describe the coding and pattern analysis process for 10+ interviews: - Thematic coding categories - Win pattern identification - Loss pattern identification - Competitive insight extraction - Positioning gap identification **Part 5 — GTM Decision Matrix** Create a matrix that maps common win/loss pattern types to specific GTM action categories: positioning change, sales process change, pricing adjustment, product gap, enablement need. **Quality Rules:** - Loss interview questions must never feel accusatory or defensive - Win interview must not lead to generic answers ('your product was great') - GTM Decision Matrix must be specific enough to drive actual decisions, not general observations
User Message
Design a complete win/loss analysis program for my company. **Product:** {&{PRODUCT_NAME}} — {&{ONE_LINE_DESCRIPTION}} **Current Deal Volume (per month):** {&{MONTHLY_DEAL_COUNT}} **Average ACV:** {&{ACV}} **Current Win Rate:** {&{WIN_RATE}}% **Biggest Suspected Loss Reason:** {&{SUSPECTED_LOSS_REASON}} **Biggest Suspected Win Reason:** {&{SUSPECTED_WIN_REASON}} **Team Resources for Running Program:** {&{AVAILABLE_TEAM}} Build all 5 parts. Format both interview scripts as numbered question lists with [Probe:] follow-ups. Format the GTM Decision Matrix (Part 5) as a table with columns: Win/Loss Pattern | Frequency Signal | GTM Action Category | Specific Recommended Action.

About this prompt

# Win/Loss Analysis Interview Framework The most underutilized intelligence source in any sales organization is the recently concluded deal — won or lost. Why did you win? Why did you lose? What almost changed the outcome? Most companies never systematically answer these questions, so they repeat the same mistakes and miss the same opportunities quarter after quarter. This prompt designs a complete win/loss analysis program: the interview script, the synthesis framework, and the decision-grade output that actually changes GTM strategy. ## What You Get - Win interview script (20 questions across 5 themes) - Loss interview script (20 questions designed to get honest answers from departed prospects) - Synthesis framework: turning 10 interviews into a pattern analysis - GTM decision matrix: mapping win/loss patterns to specific GTM actions - Program design: who to interview, when, who conducts it, and how often ## Use Cases - **VP Sales** launching a formal win/loss program to inform Q3 strategy - **PMMs** gathering competitive intelligence from real deal conversations - **Founders** doing informal win/loss during early sales to sharpen positioning ## Why It Works The specific framing of the loss interview questions is the most critical design element — prospects will tell you the truth if asked the right way. Most loss interviews fail because they feel like an audit rather than a debrief.

When to use this prompt

  • check_circleVP Sales launching a formal win/loss program to inform quarterly GTM strategy
  • check_circlePMMs using deal intelligence to sharpen competitive positioning and messaging
  • check_circleFounders running informal loss interviews to fix early-stage sales motion
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.