Win/loss analysis template for B2B SaaS founders

You lost the deal. Your CRM says “price too high.” The sales note says the prospect “went with a competitor.” Everyone moves on.

That might be true. It is also exactly the kind of tidy explanation that makes teams miss what actually happened.

A loss can look like a pricing problem from the inside and feel like a trust problem from the buyer’s side. A win can look like product superiority from the inside and turn out to hinge on one champion, one integration, or one well-timed follow-up. The CRM captures an outcome. It rarely captures the story behind the outcome.

That is what win/loss analysis is for: a structured conversation with people who recently chose you, chose someone else, or chose to do nothing. The goal is not to relitigate the sale. The goal is to reconstruct the decision while the details are still fresh enough to be useful.

This guide is written for a bootstrapped B2B SaaS founder, not an enterprise competitive-intelligence team. You do not need a 40-slide programme. You need a repeatable way to ask better questions, hear uncomfortable answers, and turn them into product, positioning, pricing, and sales decisions.

It pairs well with Maren’s guides on why founders should not run their own interviews, observed versus reported behaviour, how to avoid leading questions, and how to synthesise interviews into themes.

What win/loss analysis is

Win/loss analysis is a buyer interview after a sales decision.

For losses, you are trying to understand why the buyer did not choose you. For wins, you are trying to understand why they did, what nearly stopped them, and what they thought they were really buying.

The useful unit is the buyer’s story, not your team’s post-match analysis. That story usually includes:

• The problem or trigger that started the search
• The options they considered, including doing nothing
• The criteria they used to compare options
• The people who shaped the decision
• The moments that increased or reduced confidence
• The trade-offs they made at the end

The difference matters because your internal data is already filtered. A sales rep may log “price” because price was mentioned in the last email. The buyer may have mentioned price because the product felt risky, the business case was weak, or the competitor made the decision easier to defend internally.

Corporate Visions argues, based on its analysis of B2B purchase decisions, that sellers and buyers often disagree about why deals are won or lost. Clozd, another win/loss vendor, reports the same broad pattern in its own data: CRM loss reasons and buyer explanations often do not match.

Treat those vendor figures as directional, not as neutral academic benchmarks. The safer lesson is still important: if you only read the CRM, you are reading your own organisation’s interpretation of the buyer’s decision. Win/loss interviews give the buyer a chance to explain it in their own words.

Why interviews beat surveys for this job

Surveys are useful when you already know the answer choices. Win/loss research usually starts before you know what the answer choices should be.

If a buyer writes, “The product was not quite right,” a survey stops there. An interview can ask:

• What specifically felt off?
• When did that become clear?
• Who else noticed it?
• What would have made it feel safer?
• What did the alternative do differently?

That follow-up is where the useful information lives.

NN/g’s User Interviews 101 makes the same methodological point in a broader research context: interviews are strongest when you need to understand attitudes, experiences, mental models, and the reasoning behind behaviour. They are weaker when you treat self-report as a perfect record of what happened.

That caveat is especially important in win/loss work. Buyers are reconstructing a decision after the fact. They may simplify the timeline. They may give you the reason that sounds most professional. If the founder is asking, they may soften the answer to avoid an awkward conversation.

This is where a good interviewer earns the call. They do not ask, “Why did we lose?” They ask the buyer to walk through the decision from the beginning, then listen for the points where confidence changed.

When to run win/loss interviews

Reach out quickly. One to two weeks after the decision is ideal. Within a month is still useful. After that, details begin to blur and the buyer’s story becomes cleaner than the decision probably was.

You do not need to interview every deal. Start with decisions that can teach you something:

• A good-fit prospect who chose a competitor
• A deal you expected to win but lost late
• A buyer who chose you after comparing several options
• A prospect who chose to keep the status quo
• A buyer in your ideal customer profile whose reason surprised you

Cover both wins and losses. Losses tell you what blocked trust, fit, urgency, or internal approval. Wins tell you what created confidence and what almost broke it.

How many interviews is enough? There is no universal number. NN/g’s sample-size guidance for UX interviews is useful here because it avoids fake precision: the right number depends on the diversity of your audience, the complexity of the question, and how consistent the patterns are.

For a small SaaS team, a practical first batch is five to eight conversations across recent wins and losses. That is enough to notice early patterns without pretending you have statistical certainty. If the first five stories all point at the same friction, you have something worth investigating. If each story is different, keep going.

Should the founder conduct the interview?

For losses, usually no.

The founder is too close to the product. Even with good intentions, you carry hypotheses, pride, and the urge to explain. The buyer carries social pressure. They know you built the thing. They know you wanted the deal. A blunt answer can feel rude, even when you ask for honesty.

NN/g’s piece on the Hawthorne effect and observer bias is not about win/loss research specifically, but the mechanism applies: people change what they say and do when they know they are being observed. In a buyer interview, the observer is not neutral if they are also the person who sold, built, or founded the product.

If you can, have someone else run the loss interviews: a co-founder who was not in the sale, an advisor, a contractor, a researcher, or Maren. Give them the guide, the basic deal context, and a clear instruction: do not defend the product.

For wins, founder-led interviews are less risky, but still imperfect. Buyers may be generous because the relationship is starting. They may overstate how confident they felt. Keep the same discipline: ask for the story, not a testimonial.

The invite

Keep the outreach short and human. Do not pretend this is not research. Do not call it a “quick chat” if you need 25 minutes.

Use something like this:

Hi Sam, thanks again for taking the time to evaluate Maren. I am trying to understand how teams make decisions like this, including where we helped and where we made things harder. Would you be open to a 25-minute conversation this week? This is not a sales call, and I am not trying to change your mind. I would just value your honest read on how the decision unfolded.

For losses, add:

It is completely fine that you chose another route. The useful part for me is understanding what shaped that decision.

If you plan to record the conversation, say so before the call and ask again at the start.

The win/loss interview template

Aim for 25 to 30 minutes. You should speak for roughly 10 per cent of the call. The buyer should do the rest.

Use this guide as a spine, not a script. If the buyer says something specific and surprising, follow it.

1. Opening: lower the pressure

Start by removing the sales frame.

Thanks for making time. I am not here to pitch, defend, or change your mind. I want to understand how the decision actually unfolded from your side. There are no right or wrong answers, and the uncomfortable parts are often the most useful.

Then ask:

• Is it still okay if I record this for notes?
• Who else was involved in the decision, even informally?
• Is there anything sensitive I should avoid quoting directly?

2. Context: what started the search?

You need the trigger before you can understand the decision.

• What was happening in the business when you started looking?
• What made this worth solving now, rather than later?
• What were you using before?
• What had you already tried?
• What would have happened if you had done nothing?

This section helps you separate active pain from polite interest. A buyer with a board deadline, a failed manual process, or an angry customer behaves differently from a buyer browsing tools because a teammate asked.

3. Discovery: how did the options enter the room?

Your real competitor is not always the company you talk about internally.

• How did you first hear about us?
• What other options did you seriously consider?
• Was “do nothing” or “build it ourselves” on the table?
• What made an option credible enough to compare?
• Was there an option you dismissed quickly? Why?

Listen for language. Buyers will often describe the category differently from your website. That wording is positioning research you could not get from a CRM dropdown.

4. Criteria: what mattered most?

Ask for the buyer’s actual decision criteria, not the criteria you wish they had used.

• When you were comparing options, what mattered most?
• Which criteria were must-haves, and which were nice-to-haves?
• What risks were you trying to avoid?
• What did your team need to believe before saying yes?
• Did the criteria change during the evaluation?

For SaaS, the useful answers often sit around trust, implementation effort, internal proof, integrations, security, budget timing, and whether the buyer could defend the decision to someone else.

5. Decision: when did the outcome become clear?

This is the centre of the interview.

• Can you walk me through the decision from first conversation to final choice?
• Was there a moment when the decision started to feel clear?
• What happened in the last week before the decision?
• Who had the strongest influence?
• What was the hardest trade-off?

For losses, add:

• What would have needed to be different for the decision to go the other way?
• What concern about us was hardest to get past?
• Did we create any friction during the evaluation?
• What did the chosen option make easier?

For wins, add:

• What nearly made you choose another direction?
• What gave you enough confidence to choose us?
• What did you still feel unsure about when you signed?
• What should we make sure we keep doing?

The Win-Loss Agency suggests treating the status quo as an active choice rather than a non-decision. That is a useful frame. Instead of asking, “Why did you not buy?”, ask, “What made staying with the current process feel like the better path?”

6. Experience: how did the evaluation feel?

This section is about your process.

• How clear was our messaging before you spoke to us?
• What was helpful during the evaluation?
• What was confusing or slow?
• Was there a point where we lost momentum?
• What did we do that competitors did not?
• What did competitors do that we did not?

Founders often want losses to be about missing features. Sometimes they are. But many losses are about confidence: a late follow-up, a vague answer, a weak business case, a security concern that lingered, or a buyer who never understood why switching was worth the hassle.

7. Closing: give them room to say the thing

Do not end with a summary speech. Ask one more open question.

• Is there anything else that shaped the decision that I have not asked about?
• If you were advising us on how to reach teams like yours, what would you tell us?
• What should we stop saying because it does not match how buyers think about the problem?

Then thank them and stop. Do not argue with the answer. Do not sneak in a retention attempt. If they ask a product question, answer briefly after the interview is clearly over.

How to listen during the call

Steve Portigal’s Interviewing Users is useful because it treats interviewing as a craft, not a list of questions. The questions matter, but the posture matters more.

Three rules will keep you out of trouble:

1. Ask about specific moments.
2. Follow the buyer’s words, not your theory.
3. Let silence sit longer than feels comfortable.

Teresa Torres makes a similar point in her guidance on story-based customer interviews: concrete stories reveal context that opinion questions miss. In win/loss, that means “walk me through the week you made the decision” is better than “what was your main reason?”

Do not ask:

• “Was price the reason?”
• “Did we lose because we lack SOC 2?”
• “Would you have bought if we had this feature?”
• “Did you think our onboarding was easy?”

Ask:

• “Where did price come up in the conversation?”
• “What security questions did your team need answered?”
• “What would that feature have changed in the decision?”
• “What happened the first time you tried to set things up?”

The first set invites confirmation. The second set invites a story.

What to do after each interview

Write the notes while the call is still fresh. Do not wait until Friday.

Capture five things:

1. The buyer’s stated reason for the decision
2. The strongest evidence behind that reason
3. The moment when confidence increased or decreased
4. The words the buyer used to describe the problem
5. One thing your team could change

Separate quotes from interpretation. A quote is evidence. Your summary is a claim about the evidence. Keep them connected so the finding does not become a tidy story that floats away from what the buyer actually said.

After five to eight interviews, look for patterns across these buckets:

One interview can change how you think. A pattern across interviews should change what you do.

Where Maren fits

Win/loss is one of the places where a neutral interviewer matters most.

Maren can run the conversation without defending the product, ask follow-ups when a buyer gives a vague answer, and keep the interview anchored in what actually happened. She is especially useful when you need to collect several recent buyer stories quickly, or when the founder’s presence would make the answer softer.

You still choose the deals. You still decide what you need to learn. You still judge what the evidence means. Maren’s job is to talk to the buyer, gather the stories, and bring back the themes without turning the interview into a sales call.

If you are doing this manually, the same principle applies: put distance between the person asking and the person with something to defend.

Quick-reference template

Use this before each call.

Before the call

• Pick a recent win, loss, or no-decision worth learning from
• Reach out within one to two weeks if possible
• Use a personal invite
• Say clearly that it is not a sales call
• Confirm recording consent

Opening

• “I am not here to pitch, defend, or change your mind.”
• “I want to understand how the decision unfolded from your side.”
• “The uncomfortable parts are often the most useful.”

Core questions

1. What was happening when you started looking?
2. What made this worth solving now?
3. What options did you seriously consider?
4. What criteria mattered most?
5. Who shaped the decision?
6. When did the decision start to feel clear?
7. What nearly pushed you another way?
8. What did we make easier or harder?
9. What would you tell us to change?

After the call

• Write the notes within an hour
• Keep quotes attached to the claim they support
• Tag the story by product fit, positioning, pricing, sales process, or timing
• Review patterns after five to eight conversations
• Choose one thing to change or test

Win/loss analysis is not a reporting exercise. It is a habit of asking buyers what happened after the outcome is known, while the story is still fresh and before your team turns a messy decision into a convenient explanation.

That habit compounds. You stop guessing why good-fit buyers hesitate. You stop treating every loss as a price problem. You learn which parts of your product, promise, and process create confidence — and which quietly break it.