The core set
| Question | What it recovers |
|---|---|
| Walk me through how this decision got made internally. Who had to sign off? | The real buying committee against the one in the CRM |
| What changed in the business that put this project on the list? | Whether the compelling event was real or manufactured by the rep |
| How did the vendor shortlist get built, and who built it? | Whether you were a serious candidate or a required second quote |
| What did you need to see before you would take this to your approver? | The evidence bar, which is usually not the demo |
| At the point of decision, what separated the options? | The actual deciding criterion, stated late enough to be honest |
| Where did our process cost you time? | Friction in security review, pricing approval, or legal |
| What did the vendor you chose say that we did not? | Positioning gaps in the buyer's own words |
| If this had stalled instead, what would have restarted it? | The urgency mechanics behind no decision outcomes |
Questions to cut
Leading questions produce agreeable answers and no information. Asking whether price was the issue gives the buyer a polite exit, and they will take it. Ask what the approved budget was and where the number came from instead.
Numeric rating scales without a follow up are the other common waste. A 7 out of 10 on the demo tells you nothing you can act on, while the sentence explaining the 7 usually names a specific missing capability or a stakeholder who was never convinced.
Feed the answers back into the codes
Interviews earn their cost when they change the structured data rather than sitting in a slide deck. If four interviews reveal that deals coded as price were really lost on a missing integration, the code list needs a new option and the roadmap needs a dollar figure attached to it.
Run the program continuously on a small sample instead of as an annual study, since the patterns move when the market moves. See win rate for the metric these findings are meant to lift, and deal slippage for the stall pattern the last question is designed to surface.
Frequently Asked Questions
Who should run the interview?
Anyone except the rep who owned the deal or their manager. Buyers soften their answers for the person they turned down, and the rep hears confirmation of whatever they already wrote in the CRM. A RevOps analyst, a product marketer, or an outside interviewer gets materially different answers to the same questions.
How many questions should the set contain?
Eight to ten, sized for a 30 minute call with room to follow the buyer where they go. Longer sets turn into surveys read aloud, and the value in these interviews sits in the follow up rather than in the scripted question. Ask what happened, then ask what happened next until the story has no gaps.
Should you interview wins as well as losses?
Yes. Won deals reveal which claims survived the internal business case, who pushed the decision through, and what nearly derailed it. A program that only interviews losses collects failure modes and learns nothing about what to repeat.
How soon after the decision should you call?
Within two to four weeks. Buyers still recall the sequence of internal conversations, and the relationship is warm enough that a lost prospect will take the call. After a quarter, the answers compress into a single tidy reason that is usually the same reason your rep already recorded.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like win loss interview questions into prescriptive action for your team.
Schedule a Demo