Run Win/Loss Interviews That Actually Change Your GTM [2026]
Why reps skip win/loss (and what it costs)
After a loss, the team moves to the next opp. The story becomes folklore: “they went with HubSpot,” “timing,” “security.” Without a buyer quote, product builds features for ghosts and marketing copies competitors incorrectly. Wins are wasted too — you rarely ask why you won, so you cannot repeat it.
Who to interview
| Outcome | Contact | Priority |
|---|---|---|
| Lost — commit stage | Champion or EB if relationship allows | High |
| Lost — competitive | Champion who engaged | High |
| Won — new logo | Champion + economic buyer if possible | Medium |
| Won — expansion | Admin or power user | Low unless strategic |
| No decision | Champion who went dark | Medium — timing vs fit |
Log outreach and outcome on the opportunity in Momentum — requested, scheduled, completed, declined.
Question bank — losses
- What problem were you trying to solve when you started evaluating us?
- What were your top three decision criteria — ranked?
- Where did we fall short versus the vendor you chose?
- Was there a moment you lost confidence in us — what happened?
- What would we need to change for you to reconsider in 12 months?
Do not argue. Do not pitch. Thank them and close. If they name a competitor feature, note exact wording — product needs the buyer’s words, not your paraphrase.
Question bank — wins
- What almost made you choose someone else?
- Which proof point tipped the decision — demo, reference, pricing, migration?
- Who internally fought for us — and who resisted?
- What do you need in the first 30 days to call this a success?
Wins reveal your real differentiators. If every win cites mail on deals, double down in demos — do not lead with features buyers ignored.
Turn interviews into GTM fixes
After each batch, tag themes — not one-offs:
- Product — missing capability cited three times
- Proof — reference segment gap, case study need
- Process — EB never engaged, security questionnaire late
- Positioning — compared to wrong category
- Pricing — TCO misunderstanding, not list price
Store summary in Workspace linked to the account. Review in weekly pipeline review — one slide, five bullets, owner per theme.
Monthly rollup — 30-minute founder ritual
Last Friday of the month: pull all completed interviews. Sort by theme. Answer three questions:
- What did we hear three or more times on losses?
- What did we hear three or more times on wins?
- What will we change before next month — one product, one proof, one process item?
If the third answer is empty, you are collecting theater. Pick one change, assign an owner, review completion at the next rollup.
Competitive losses — separate bucket
When the buyer names a competitor, log: which vendor, which feature or proof point they cited, and whether you were in a formal evaluation or a solo pilot. Aggregate monthly — if three losses cite the same integration gap, that is a product priority, not a rep coaching issue. Run a war room before the next bake-off.
Sample outreach email
Subject: Quick feedback on your evaluation — 15 minutes
“Hi [Name] — we respect the decision to go another direction. I am not selling — I am trying to learn what we should fix for teams like yours. Would you spare 15 minutes this week for five structured questions? Your candor helps us more than a polite no.”
Short. No attachment. No calendar link without permission — ask first.
Tie to lost deal review
Pair interviews with your lost deal review — internal review diagnoses process; buyer interview validates it. If they disagree, the buyer is right.
Win/loss checklist
- Interview request within 14 days of close
- Neutral interviewer on losses
- Five core questions — same every time for comparability
- Themes tagged; one owner per recurring theme
- Notes on CRM opportunity — not a orphaned doc
- Quarterly review: top three loss reasons vs top three win reasons