# Win/Loss Analysis for SaaS

> How to run win/loss analysis for SaaS deals, including data collection, buyer interviews, questions to ask, analyzing patterns and turning findings into product and positioning changes.

Source: https://comppound.com/blog/win-loss-analysis-for-saas (published 2026-09-18)

Win/loss analysis examines why deals are won or lost. Done well, it reveals what buyers value, why they choose competitors and where your sales process, product or positioning falls short. Many SaaS teams rely on the notes reps leave in the CRM after a deal closes, which tend to say "price" or "timing" and little else. Real win loss analysis for a SaaS company digs beneath those labels to find the reasons buyers would give if you asked them directly.

This guide covers why the practice matters, what data to collect, how to interview buyers, which questions to ask, how to analyze what you hear and how to turn findings into changes. It ends with a lightweight program a small team can run without a dedicated research function.

## Why win/loss analysis matters

The first benefit is sharper positioning. Buyers who chose you can tell you which messages and strengths actually influenced them, and those are often different from the ones your homepage emphasizes. Buyers who chose someone else can tell you which of your claims did not land.

The second benefit is better product decisions. Win/loss interviews surface missing capabilities that repeatedly cost deals, which is a stronger signal for the roadmap than a general feature request, because it is tied to revenue.

The third benefit is a better sales process. Interviews reveal where the buying experience frustrated people: slow responses, confusing demos, unclear pricing or a long security review that nobody prepared for. These are often fixable quickly.

The fourth benefit is a clearer view of competitors. Buyers describe how they compared options, what each vendor emphasized and how they perceived your pricing relative to others. That view comes from the people making the decision, rather than from a competitor's marketing site.

## Collect CRM data consistently

Interviews provide depth, but CRM data provides breadth. For each closed deal, record the outcome, the deal size, the customer segment, any competitor involved, the length of the sales cycle and the primary reason the deal was won or lost.

The reason field needs a fixed set of categories. If reps type free text, you end up with dozens of variations that cannot be compared. A list of around eight to twelve reasons, such as price, missing feature, integration, implementation effort, competitor relationship, timing, no decision and security requirements, makes the data usable. Add a short free-text field for context, so the category has a sentence behind it.

Be realistic about what this data can tell you. CRM reasons reflect the rep's interpretation, recorded at a moment when they may be disappointed or rushed. They are useful for spotting broad trends and choosing whom to interview, but they rarely explain why a deal went the way it did.

## Interview buyers

The most valuable insights come from buyers themselves. Interview won customers, lost prospects and deals that stalled without a decision. Each group tells you something different. Wins show what you do well and should emphasize. Losses show where you fall short. Stalled deals often reveal that the buyer's problem was not urgent enough, or that the purchase got stuck in an internal process you did not see.

Interviews are usually more candid when someone other than the sales rep conducts them. A buyer who chose a competitor may not want to tell the rep they liked why, and a rep may unconsciously steer the conversation toward explanations that reflect well on them. A founder, a product marketer or an outside interviewer tends to hear more. For a small company, the founder is often the right person, and buyers are frequently willing to speak with a founder who asks for honest feedback.

Reach out soon after the decision, ideally within a few weeks, while the details are fresh. Keep the request short, explain that you want to learn and are not trying to reopen the deal, and ask for 20 to 30 minutes.

## Questions to ask

### Background

Start with the situation that led to the evaluation. Ask what problem they were trying to solve and why it became a priority when it did. These questions set context and often reveal the triggering event behind the purchase.

### Evaluation

Move to how the buyer evaluated options. Ask which options they considered, including doing nothing or building something internally. Ask how they evaluated them, such as demos, trials, reference calls or scoring sheets, and who was involved in the decision. The answer to the last question frequently reveals stakeholders the sales team never spoke to.

### Decision

Then ask about the decision itself. Ask why they chose the winner, and what almost changed their decision. The second question is often the most revealing, because it surfaces the doubts that nearly tipped the outcome.

### Perception

Ask how they saw your company specifically. What were your strengths, and what were your weaknesses? How did your pricing compare with the alternatives? Listen for the difference between a product that was too expensive and one whose value was not clear enough to justify the price.

### Sales experience

Finally, ask about the buying process. How did it feel to buy from you, and what could have been better? Buyers often mention small things, such as slow follow-ups or demos that did not address their use case, that are easy to fix once someone knows about them.

Throughout the interview, avoid leading questions. Asking "Was it our pricing?" invites agreement. Asking "What made you go in a different direction?" invites the real answer.

## Analyze patterns

A single interview is an anecdote. Patterns across interviews are evidence. Once you have a handful, review them together and group findings by segment, competitor, deal size and reason. A simple spreadsheet with one row per interview and columns for each theme is enough for a small team.

Look for repeated themes. Examples of the kinds of patterns teams find include losing to a particular competitor on integrations, winning because of faster onboarding, deals stalling during security reviews, or price objections appearing only in one segment. Each of these points to a different response, which is why it matters to identify them precisely rather than lumping everything under a single label.

Compare interview findings with CRM data. If reps record "price" for most losses but interviews reveal implementation concerns, you have learned something important about how reasons are recorded as well as why deals are lost.

## Turn insights into action

### Product

Prioritize missing capabilities that repeatedly cost deals, especially in your core segment. A capability mentioned in several losses deserves a serious place in roadmap discussions. Be careful not to chase every request from a single lost deal, particularly if it came from a buyer outside your target market.

### Positioning

Emphasize the strengths buyers say they value. If wins frequently mention responsive support or fast setup, those belong in your messaging, sales materials and website. If buyers compare you mainly against spreadsheets, your positioning should address that comparison first.

### Sales

Use findings to improve discovery, demos and objection handling. If deals stall in security review, prepare security documentation in advance and raise the topic early. If buyers say demos felt generic, tailor them to the use cases buyers care about.

### Marketing

Create content that addresses common concerns uncovered in interviews. A clear guide to implementation, a comparison with the real alternative or a page that answers security questions can resolve doubts before they reach a sales call.

## Handling sensitive feedback

Win/loss interviews sometimes surface uncomfortable findings about specific people, such as a rep who was slow to respond or a demo that went badly. Handle these carefully. The aim of the program is to improve how the company sells, not to assign blame, and reps who feel targeted will stop cooperating with interview requests and may start recording vaguer reasons in the CRM.

Share individual feedback privately with the person involved and their manager, framed as coaching. In broader summaries, describe patterns rather than naming individuals. Protect buyers' confidentiality as well. If an interviewee shares details about a competitor's pricing or their own internal politics, keep those details to the people who need them, and never attribute a sensitive quote to a named buyer without permission.

## Share findings

Present findings to product, sales, marketing and leadership on a regular schedule, such as once a quarter. A short written summary, ideally one page, with the main themes, supporting evidence and recommended actions works better than a long report nobody reads. Include a few short, anonymized quotes, because buyers' own words persuade internal teams more than summaries do.

Follow up on the recommendations at the next review. Win/loss programs lose credibility when findings are shared and then forgotten.

## Common mistakes

Relying only on sales notes is the most common mistake, because those notes reflect one perspective under pressure. Interviewing only lost deals is another, since wins explain what to protect and amplify. Leading questions produce the answers you expected rather than the truth. And the most wasteful mistake is doing the analysis without acting on it.

## A worked example (illustrative)

A SaaS company believed it lost deals mainly on price, because "too expensive" was the reason reps entered most often in the CRM. The founder decided to interview a set of recently lost prospects and recent wins over a month.

The interviews told a different story. Several losses recorded as price were really about implementation effort. Prospects worried their team lacked time to set up integrations and chose a competitor that offered setup help. Wins frequently mentioned how responsive the founder had been during evaluation. A couple of losses came down to a missing integration with a specific accounting tool. And prospects compared the product mostly against spreadsheets, not the competitor the team focused on in its sales materials.

The company introduced free guided setup for annual plans, added implementation timelines to proposals, moved the missing accounting integration up the roadmap and rewrote its sales materials to compare against spreadsheets first. Over the following quarter, fewer losses were recorded as price, and the team's results in its core segment improved.

## A lightweight win/loss program

A small team can run a useful program with modest effort. Each month, interview two recent wins and two recent losses, for around 20 minutes each. Each quarter, summarize the themes on one page and share them with product, sales and marketing. On every deal, have reps record a reason from the fixed list plus a sentence of context. Interviews explain what CRM reasons cannot, and the CRM data shows whether the patterns hold across all deals.

## The takeaway

Win/loss analysis helps SaaS teams understand why buyers choose them or a competitor. Combine consistent CRM data with candid buyer interviews, look for patterns across segments and competitors, and turn what you learn into concrete changes in product, positioning, sales and marketing.

## Frequently asked questions

### What is win/loss analysis?

Analyzing why deals are won or lost to improve product, positioning and sales.

### Who should conduct win/loss interviews?

Often someone other than the sales rep, such as a founder, product marketer or third party, to encourage candor.

### How often should SaaS companies run win/loss analysis?

Many review findings quarterly and conduct interviews continuously.

## About Comppound

Comppound runs SEO and AI search for B2B SaaS companies: a person sets the plan and reviews samples and every high-risk page, and AI speeds up production.

- [See SEO Growth](https://comppound.com/services/seo-growth): Buyers compare before they book a demo. Are your pages there when they do?
- [Book a call](https://comppound.com/contact): Most of this works better when buyers can find you first