How to Conduct Win-Loss Interviews: A Complete Guide

Organize around topics, not a script

The temptation when building a guide is to start writing individual questions right away. Resist it. Start by deciding what you actually want to talk about—the topics, not the questions. For a typical B2B software deal, that might mean starting with the overall decision (why the deal was won or lost, and the main drivers) before moving into more specific areas like product, pricing, sales process, and competitor feedback. The exact topic list will vary by business, but organizing this way lets the interviewer move topic-to-topic with the buyer instead of marching through a fixed sequence of questions.

Write headline questions, with optional drill-downs

Within each topic, develop a small number of high-level, open-ended headline questions designed to get the interviewee talking freely, and pair them with optional, more specific drill-down questions you can use if something interesting surfaces. If a buyer says the integrations were a strength, a headline question won't get you much further — you need drill-downs ready: which systems, what data needed to move, was it one-way or two-way, native or open API. Those drill-downs are what turn a vague compliment into a usable insight.

Keep questions open-ended and unbiased

How you phrase a question shapes whether you get an honest answer. Clozd program manager Lauren Beall put it this way: rather than asking "What did the sales team do poorly?"—which plants an assumption of "poorly" in the buyer's mind—ask "What was your interaction with the sales team like?" If the buyer volunteers something negative, follow up on what specifically didn't work. Starting open keeps you from tainting the data with your own assumptions about what went wrong.

This also means avoiding the phrasing of a traditional survey. Questions like "To what extent did you like this product?" aren't how people talk in a normal conversation, and yes-or-no or 1-to-10 scaled questions tend to produce one-word answers that don't tell you much. Save that kind of quantitative, scaled feedback for a post-interview survey — the interview itself should stay qualitative and conversational.

Keep the guide efficient

Thirty minutes is generally enough time to uncover a lot, if you're organized, and asking for more time tends to lower response rates and increase no-shows. A 20-page guide for a 30-minute call is overkill. Two ways to keep it tight:

• Prioritize what matters most. If the interview's purpose is to learn about the buyer's experience with the product UI, don't open with questions about the sales rep or the demo — start with the topic you actually need answered.
• Skip demographic questions you can find elsewhere. How long someone's been in their role, or at the company, is a waste of interview time if it's on LinkedIn. A win-loss interview isn't a market research survey. Stick to the open-ended questions only a conversation can answer.

As Lauren Beall noted, the buyer showing up for a win-loss interview isn't doing it as part of their job; they're giving up 30 minutes of their day. Coming prepared with a tight, well-thought-out guide is how you show that their time was worth planning for, and it's what frees you up to be adaptive during the actual conversation.

Adapt the guide to who you're talking to

Not all buyers are the same, even within the same deal. One stakeholder in a purchasing decision may be focused on budget while another cares more about technical requirements, so the questions you lead with should be based on who's actually on the call and what matters to them. This requires strong active listening and a willingness to adjust your approach per interviewee, not just per deal.

Treat the guide as a living document

Don't chase a perfect guide before your first interview. Your interview guide should evolve as your priorities shift and as you learn more about what your buyers actually care about. Make continuous adjustments based on what each interview teaches you. If this is new to you, expect to get better with volume; interviewing is a skill you build by doing it repeatedly, not by over-preparing up front.

It's a conversation, not a phone survey

Nobody enjoys being read a script. Rigid, question-after-question delivery (the same wording, the same order, every time) misses the critical feedback people want to give, because you're not adapting to what they're actually telling you. Academic researchers sometimes push back on this, arguing that identical wording every time makes results more comparable. The counter: a win-loss interview is qualitative research, not a quantitative, statistically-controlled instrument. That kind of rigor belongs in a post-interview survey, not the interview itself.

Ask qualitative, open-ended questions—and don't just move to the next one

Ask questions that start with why and how, not ones that invite a yes/no or a number. And when a buyer gives you something rich, don't move robotically to your next scripted question. That's the single biggest way to lose the value of an interview. Listen, and be willing to change direction, sometimes more than once in a single call, based on what the interviewee says matters most to them.

Be flexible: three ways to do it in practice

Structure matters, but so does giving the buyer room to tell their own story. Three specific techniques:

This same flexibility shows up in the broader strategy of adapting to each interview rather than forcing every call into an identical shape. Every buyer has unique priorities, use cases, and decision processes, and a skilled interviewer is prepared to go off-script to chase the answer to the real question that matters.

Start broad, and ask directly.

After a brief introduction, ask straightforwardly: "Why was this deal won or lost?" or, with more context, "What gave [competitor] the edge in this deal?" Don't dance around it. The answer buyers give tells you where to spend the rest of the interview, and where not to waste questions.

Once you know why, follow the "why" down.

Focus your remaining questions on the topics that are actually critical to the purchase decision, and don't be afraid to ask "why" multiple times in a row. Buyers often haven't consciously thought through the deeper reasons behind a decision until you push them to.

Don't chase obscure products or competitor minutiae.

Buyers often don't think about your product, or a competitor's, in nearly as much detail as you do. Chasing very specific feature-level comparisons they may not even be able to speak to risks eating the interview without ever landing on why the deal actually happened. Put yourself in the buyer's shoes: they may simply have picked the cheapest option, and the nuances that matter internally to your team may not have mattered to them at all.

Record and transcribe, don't rely on notes.

Notes taken live during a conversation are never going to capture the full richness of what was said, and without a recorded quote to point to, it's hard to convince skeptical stakeholders that a piece of feedback is real and not paraphrased. Recording followed by transcription turns the interview into something people can actually read and reference.

Summarize and analyze immediately.

Do this right after each interview, while it's fresh. Write a summary of the high-level takeaways and identify the major themes. If you also have a full transcript, you can go back and refine your takeaways later, but the immediate summary is what keeps your analysis accurate.

Tag three to five themes per interview.

Identify the key drivers, typically centered on the same topics your guide is organized around, that motivated the buyer's decision, positive and negative. Tag too few and you'll miss nuance; tag too many and after a batch of interviews you'll have a pile of data that doesn't actually tell you why deals are won or lost. Three to five per interview is the general range that keeps themes meaningful. When the same theme shows up across multiple interviews, that's your signal of a real trend worth acting on.

Don't just hand over a data dump.

Sharing raw transcripts, or PDFs of every interview word-for-word, asks too much of your stakeholders' time and nobody reads it. Package each interview into a short summary with tagged themes and supporting quotes so people can consume the analysis, not just the raw interview.

Share continuously, not once a quarter (or once a year).

A single large deliverable, a 50-to-70-slide readout delivered months after the deals actually closed, arrives too late to be useful and risks being stale by the time anyone sees it. Pushing out a summary and tagged themes shortly after each interview lets the organization act on what it's learning in near real time, rather than waiting for a big periodic report.

The steps in this guide will get your first 10–20 interviews right. What gets harder as a program matures is everything downstream of the interview itself: keeping theme-tagging consistent across multiple interviewers, tracking trends quarter over quarter, and getting findings in front of the people who can act on them before the insight goes stale.

That operational layer, not the interview skill itself, is usually what determines whether a win-loss program is still running a year in. It's also where a dedicated platform and team earn their keep: Clozd's expert interviewers and win-loss analysis software exist specifically to keep that machinery running as your interview volume grows.

Starting your first round of interviews? Use this guide. Ready to make it a durable, company-wide program? Talk to Clozd about what that looks like.