Sales Win-Loss Analysis Example — Lost Deal Debrief
Example document for Sales Win Loss Analysis. Use this as a reference when creating your own.
For Informational Purposes
This document template is provided for informational purposes. Customize it for your specific needs.
Document: Sales Win Loss Analysis
Example Document
Last updated 6/4/2026
Sales Win-Loss Analysis — Lost Deal Debrief: Northwind Logistics
Deal / account: Northwind Logistics Analyst: Priya Nair, Sales Enablement Date completed: 18 May 2026 Source: 30-minute buyer interview with VP Operations
1. Deal information
| Field | Detail |
|---|---|
| Account | Northwind Logistics |
| Opportunity | Northwind — Fleet Analytics Platform |
| Deal size | $96,000 ARR |
| Sales rep | Daniel Osei |
| Sales cycle | 14 weeks |
| Stage reached | Final evaluation (2 vendors) |
| Date closed | 9 May 2026 |
2. Outcome
Result: [x] Lost
Lost to RouteIQ in the final round after a three-month evaluation that we led for most of the cycle.
3. Decision criteria & ranking
| Rank | Criterion | Why it mattered to the buyer | How we scored |
|---|---|---|---|
| 1 | Telematics integration | Their fleet runs on Geotab; data had to flow in without manual export | Weak — Geotab connector is on our roadmap but not shipped |
| 2 | Implementation speed | They needed live before peak season in Q3 | Adequate — 8 weeks vs RouteIQ's quoted 4 |
| 3 | Reporting depth | Ops team lives in dashboards | Strong — they preferred our analytics |
| 4 | Price | Budget existed but was scrutinised | Adequate — we were ~12% higher |
4. Our strengths (as the buyer saw them)
- "Your dashboards were clearly the best we saw — the team actually got excited in the demo."
- Responsiveness during evaluation: "Daniel answered everything within a day."
5. Our weaknesses (as the buyer saw them)
- No live Geotab integration: "We would have had to keep exporting CSVs, which is the exact problem we are trying to kill."
- Longer time-to-live: "Eight weeks put us uncomfortably close to peak season."
6. Competitor
| Field | Detail |
|---|---|
| Competitor chosen | RouteIQ |
| Why they won / we lost | Native Geotab connector plus a quoted 4-week go-live removed the buyer's two biggest risks |
| Where they out-positioned us | They led every conversation with the integration; we led with analytics and treated integration as a footnote |
7. Price factor
- Stated role of price: "Price mattered but it was not the deciding factor — we would have paid the premium for the better fit."
- Our read: Price was a secondary concern. Naming it as the loss reason would have been wrong; the real driver was the missing integration and the timeline risk it created.
8. Lessons
- The Geotab integration gap is now costing real, named revenue — this is at least the third Geotab-heavy account we have lost to RouteIQ.
- We sold our strength (analytics) and let the buyer's top-ranked criterion (integration) go unaddressed until it was too late.
- Our 8-week implementation reads as a risk against competitors quoting 4 — we need either a faster path or a stronger story about why ours is safer.
9. Action items
| Action | Owner | Function | Due |
|---|---|---|---|
| Add Geotab integration to the roadmap review with the three lost-deal names attached | Priya Nair | Product | 30 May 2026 |
| Build a "fleet integrations" qualifying question into discovery so we surface this in week one | Daniel Osei | Sales | 23 May 2026 |
| Draft a RouteIQ battle card covering integration and go-live timeline | Sales Enablement | Sales | 6 Jun 2026 |
| Document a 6-week accelerated implementation option for time-sensitive deals | Implementation Lead | Operations | 13 Jun 2026 |
Notes
A realistic worked example showing how a lost deal is debriefed end to end; the account, competitor, and numbers are illustrative.
About this Example
Part of the Sales Win Loss Analysis document collection
Document Type
Sales Win Loss Analysis
A review of why deals were won or lost, turning outcomes into a better sales motion.