Turn closed deals into a change, not a post-mortem deck.
“We lost another deal and the reason in the CRM says price. What is the real reason?”
Who to interview, the question guide, how to code themes across deals, and how to turn the pattern into a messaging or product change.
What this skill does
Stands up a repeatable win/loss program instead of a one-off post-mortem. It chooses which won and lost deals to interview and why, hands you the question guide that gets past "price," codes the answers into themes across many deals so you act on a pattern and not the loudest anecdote, and turns that pattern into a named change to the message or the product.
Inputs
- Works today with: a list of recently won and lost deals, with segment, deal size, competitor if known, and the stated reason. Paste it or upload a CSV.
- More powerful connected to a CRM: it reads closed-won and closed-lost with stage history and loss reasons so the sample is not cherry-picked.
- Sharper with a call-recording or meeting tool: it mines what buyers actually said, not just the field a rep typed.
- Sharper with a survey or feedback tool: it folds structured buyer responses into the same theme coding.
How it works
- 1Who to interview
Do not only interview losses, and do not let reps pick. Build a slate across MIX so you learn from wins, losses, and no-decisions, because a no-decision is a loss to the status quo and it teaches the most. Prioritize by SELECTION so the sample spans segments and competitors, not just the three deals someone remembers. Use a neutral INTERVIEWER, because buyers do not tell the rep who lost them the real reason.
- 2The question guide
Get past the stated reason. "Price" is almost never the reason, it is the reason that is polite to say. Ask what they were solving, who else was in the room, what nearly changed their mind, and what the winner did that you did not. Ask the same core questions every time so answers are comparable across deals. Open questions first, then probe, never lead.
- 3Coding themes across deals
Tag every interview into THEMES, then count across the sample. One buyer saying the onboarding scared them is an anecdote. Five saying it is a finding. A theme is only a finding when it clears PATTERN_BAR across independent deals, so a single loud loss cannot set the roadmap. Show the theme counts and the deals behind each.
- 4From pattern to change
Every finding gets an owner and a specific change, not a discussion. A message theme goes to PMM as a positioning or objection-handling change. A product theme goes to product as a gap with the deals it cost. A trust or proof theme becomes a case study or a security page. The program has failed if it produces a deck nobody acts on, so each finding ends as a named change with an owner and a date.
Output format
WIN-LOSS PROGRAM · 14 interviews · illustrative
Sample: 6 lost · 5 won · 3 no-decision · mix of segments and 2 competitors
Themes (count across independent deals):
Product gap: integration missing 5 deals FINDING
Message: value story unclear early 4 deals FINDING
Trust: no proof at our size 3 deals FINDING
Price stated as reason 4 deals probe showed it was fit, not price
Changes:
1. Integration gap -> Product. Costed 5 deals this quarter. Roadmap review.
2. Value story -> PMM. Rewrite the first-call narrative, ship objection guide.
3. Proof gap -> PMM. Publish 2 case studies in the losing segment.
Tips
- Interviews are run by a neutral party, never the rep who owned the deal.
- Wins and no-decisions are in the sample, not only losses.
- No theme becomes a finding until it clears the pattern bar across independent deals.
- "Price" is probed, never accepted at face value as the real reason.
- Every finding ends with a named owner and a specific change, not a summary slide.
Walk into the forecast call with a number you can defend.
Sorts each deal into commit, best-case, or pipeline by evidence, flags one risk, and scripts what to press each rep on.
Run a pipeline review that finds problems, not recites them.
Coverage vs target, stage aging, week-over-week movement, stuck deals, and the question to ask per deal.