Win-Loss Interview Analysis

Template Overview

Understanding why enterprise prospects choose your solution—or select a competitor—provides the highest-fidelity input for product roadmaps and sales enablement. The Win-Loss Interview Analysis template structures post-deal debriefs, dissects competitive strengths and weaknesses, and extracts actionable product takeaways in Markdown.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Win-Loss Analysis: [Account Name]"
date: [YYYY-MM-DD]
interviewer: "[[Product Marketing Lead / Win-Loss Analyst]]"
account_executive: "[[Account Executive]]"
prospect_name: "[Prospect Organization Name]"
deal_outcome: "Closed Won / Closed Lost"
deal_arr: "$48,000"
primary_competitor: "Granola / Otter / Obsidian DIY"
tags: [win-loss, sales-intelligence, competitive, product-strategy]
---

# Win-Loss Interview Analysis — [Account Name]

## 1. Deal Background & Decision Summary
- **Outcome:** **Closed Won (300 Seats)**.
- **Decision Timeline:** 6-week evaluation cycle from initial discovery to formal contract execution.
- **Buyer Persona:** VP of Engineering and CISO co-decision.

## 2. Primary Decision Drivers (Why We Won / Lost)
### Top 3 Reasons We Won
1. **Zero-Cloud Architecture:** The competitor required uploading meeting audio to multi-tenant cloud servers. Our local on-device Whisper processing was non-negotiable for their CISO.
2. **File Sovereignty:** Notes save directly into the user's local filesystem as standard Markdown, opening instantly in Obsidian without vendor lock-in.
3. **No Meeting Bot Friction:** The executive team refused to adopt solutions that send visible bot avatars into client Zoom meetings.

### Identified Product Gaps & Buyer Hesitations
- **Initial Hesitation:** Lack of a mobile application; mitigated when the buyer acknowledged that 95% of engineering meetings occur on MacBooks.
- **Feature Request:** Requested deeper keyboard shortcut customizability in the desktop client.

## 3. Competitor Perception & Pricing Dynamics
| Dimension | Our Solution (Oyma) | Competitor Solution | Buyer Verdict |
|---|---|---|---|
| **Privacy & Security** | 100% on-device local execution | Multi-tenant cloud transcription | Strong Win for Us |
| **Pricing Model** | Transparent $8/mo annual equivalent | $14/mo + cloud overages | Favorable for Us |
| **Ecosystem Openness** | Plain Markdown files in vault | Closed proprietary web database | Decisive Win for Us |

## 4. Sales Process Feedback
- The buyer commended the sales engineer's technical transparency and the availability of verified Little Snitch packet capture traces.
- Suggested shortening the procurement security questionnaire review by publishing a pre-filled compliance package.

## 5. Strategic Takeaways & Action Items
- [ ] [[Product Marketing]] Incorporate the "No Cloud Bots" buyer quote into enterprise landing page copy.
- [ ] [[Product Lead]] Add configurable keyboard shortcuts to the Q1 engineering roadmap.
- [ ] [[Sales Enablement]] Share win story recording during weekly sales team all-hands.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Win-Loss: Apex BioTech (Closed Won)"
date: 2026-10-06
interviewer: "[[Claire Evans]]"
prospect_name: "Apex BioTech"
deal_outcome: "Closed Won"
tags: [win-loss, competitive]
---

# Win-Loss: Apex BioTech (Closed Won)

## 1. Key Finding
Claire Evans interviewed the VP of Research at Apex BioTech. The buyer revealed that competing cloud notetakers were disqualified within 48 hours by legal counsel due to cloud audio storage policies, making our local-first architecture the only approved alternative.

When to Use and When to Avoid

When to Use

• Use following the conclusion of enterprise sales opportunities (both Closed Won and Closed Lost).
• Use to extract objective competitive intelligence from buyer debriefs.
• Use to inform product roadmap prioritization and refine sales positioning.

When to Avoid

• Avoid using during active mid-funnel sales negotiations.
• Avoid using for internal employee performance evaluations.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the win-loss post-deal debrief recording:
1. Summarize the decisive factors that led to the final purchase decision (won or lost).
2. Outline the buyer's candid perceptions of competing alternatives and pricing models.
3. Extract actionable product improvements and sales enablement takeaways into clean Markdown.

Your data remains securely on your Mac with zero cloud exposure.