Win Loss Analysis for B2B SaaS
Run win loss analysis that changes messaging: sample size, who interviews, the question set, coding losses and feeding findings back to product.
On this page 10 sections
- Why CRM close reasons are fiction
- What the programme is actually for
- Sample size, cadence, and who gets interviewed
- Who interviews, and why it cannot be the account executive
- Getting consent, and the incentive that works
- The question set
- A coding scheme that does not lie to you
- Closing the loop into messaging, battlecards and roadmap
- What this costs and what it will not do
- Start this month
- Frequently asked questions
The short answer
Win loss analysis for B2B SaaS means interviewing buyers from closed deals to learn why they chose or rejected you, because CRM close reasons are recorded by the losing rep and are systematically wrong. A working programme runs 12 to 20 interviews per quarter, uses an interviewer who is not the account executive on the deal, and codes findings into a scheme that separates genuine price objections from failures to communicate value. Findings feed messaging, battlecards and roadmap on a fixed cadence.
Key points before you start
Open your CRM and pull the close reasons for last quarter’s losses. Count how many say price. Now pull the recordings from Gong for three of those deals and listen to the last two calls. In most SaaS companies the two stories do not match, and the CRM version is the one feeding your pricing conversations. That gap is the entire reason win loss analysis exists as a discipline.
Why CRM close reasons are fiction
A close reason is recorded by the person who just lost, from a dropdown, while they are already thinking about next quarter’s number. It is the single least reliable field in your system, and it is the one most frequently quoted in board decks.
Three forces bend it. Reps pick the reason that reflects least badly on them, and price reflects on the company rather than on the rep. The dropdown itself is usually five options long, so anything nuanced gets rounded to the nearest available word. And the rep often never learned the real reason, because the buying committee made the decision in a meeting the rep was not in.
The gap that shows up almost everywhere
Programmes that run interviews alongside CRM data consistently find that a large share of deals logged as price losses are actually value communication failures: the buyer thought the price was fine for a product that did what they needed, and did not believe yours would. The price is not the objection. The proof is.
This matters commercially because the two diagnoses lead to opposite actions. Price losses point at discounting or a new tier. Value communication failures point at your battlecards, your proof assets and your demo script. Cut price to fix a proof problem and you lose margin without lifting the win rate at all.
What the programme is actually for
Three outputs, and if you are not producing all three you have built a research habit rather than a programme.
Messaging changes, meaning specific claim edits on specific pages, sourced from interview language. Sales enablement changes, meaning battlecard updates and objection responses that use the words buyers actually said. Roadmap input, meaning coded counts of capability gaps that product can weigh against everything else in the queue.
The fourth thing people expect and rarely get is a precise win rate explanation. Win loss will not tell you why your win rate is 22 percent instead of 30. It will tell you what the 78 percent believed at the moment they chose somebody else, which is more useful and less tidy.
Editable CSV worksheet
Get the benchmark evaluation worksheet
A worksheet for checking source dates, definitions and sample limitations before you use an industry benchmark.
Sample size, cadence, and who gets interviewed
Twelve to twenty interviews per quarter is the working range for mid-market SaaS. That is roughly four to seven a month, which one person can hold alongside other work.
Weight the sample deliberately rather than taking whatever closed:
- Two thirds losses, one third wins. Losses carry the diagnostic information, wins carry the proof that closes.
- Concentrate on your core ICP. An interview with a prospect you should never have pursued teaches you about qualification, not positioning.
- Include at least one no-decision per quarter. Deals lost to “we did nothing” are a different failure mode and they are usually your largest competitor.
| Approach | Cost per quarter | Latency to insight | Neutrality | Best for |
|---|---|---|---|---|
| In-house, PMM runs it | Mostly time, 15 to 25 hours | Days | Medium | Mid-market teams that can hold a monthly cadence |
| In-house with external interviewer | $4,000 to $9,000 | 1 to 2 weeks | High | Teams with a PMM who cannot protect the time |
| Full vendor programme (Clozd, DoubleCheck) | $15,000 to $40,000 | 4 to 10 weeks | High | Enterprise deals, or when the board needs a third party name on the findings |
| Annual outsourced study | $25,000 plus | One quarter or more | High | Almost nobody, and it arrives after you needed it |
My position: run a small in-house programme monthly rather than an annual outsourced study. The annual study produces a better-looking document and worse decisions, because the findings land after messaging is locked and the competitor set has moved. Six interviews a month that reach the PMM’s inbox within a week will change more behaviour than sixty interviews delivered in a 90 page deck in February.
Who interviews, and why it cannot be the account executive
The buyer will not tell the person they rejected the real reason. This is not a theory, it is basic social behaviour, and every programme that has tried both approaches finds the same thing: AE-conducted interviews return more price and fewer product gaps.
There is a second problem. The AE has a live incentive to reopen the deal, and the moment the conversation turns into a re-pitch the research value collapses and the buyer stops answering their email.
The awkward internal politics
Sales leadership often resists this, because it feels like marketing going behind the rep’s back. Solve it by sharing the interview list with the AE beforehand, sending the invitation from a neutral address, and giving the rep the recording afterwards. If a rep refuses to let you contact a lost buyer, treat that as a signal worth investigating on its own.
Getting consent, and the incentive that works
Ask within two weeks of the decision, while memory is intact and before the buyer starts rationalising. Keep it to 25 minutes and say so in the first line of the email. Offer a 100 dollar gift card or an equivalent charity donation, and state plainly that you are not trying to win the deal back.
Record with explicit permission at the top of the call, in the recording. If you plan to quote anyone externally, that needs separate written consent, and the rules for that overlap with how you run a customer reference program. Internal use is a different bar from a published quote, and conflating the two will eventually cause a problem.
The question set
Order matters more than wording. Start with the trigger, end with the decision, and never mention your product until they do.
A 25 minute interview structure
- The trigger (3 min)
What changed that made you start looking? You are listening for the business event, not the feature need.
- The process (5 min)
Who was involved and what did each person care about? This is where you map the buying committee properly.
- The shortlist (4 min)
Who else did you evaluate and how did each get on the list? Note who they name before you name anyone.
- The comparison (6 min)
What separated the finalists? Ask for the specific moment they felt more confident in the winner.
- Our part (4 min)
Where did we lose you? Push gently past the first answer, which is almost always price or timing.
- The counterfactual (2 min)
What would have had to be true for you to pick us? The single highest-value question in the set.
- Close (1 min)
Anything you expected me to ask that I did not? Surprisingly productive about a third of the time.
The full version with probes and follow-ups is in the win loss interview questions template. Do not read it verbatim on the call. A script read aloud produces survey answers, and survey answers are exactly what you already have in the CRM.
Consultation request
Talk to a SaaS marketing strategist
Tell us about your marketing bottleneck and request a working session. We will confirm availability before scheduling.
A coding scheme that does not lie to you
This is the part most programmes get wrong, and it is where the work pays off. Code each loss into one primary category and up to two secondary ones.
| Code | Definition | Owner of the fix |
|---|---|---|
| Capability gap | We genuinely cannot do a thing they required | Product |
| Value not proven | We can do it, they did not believe we could | Product marketing, sales enablement |
| Price above budget | Real budget ceiling, no negotiation possible | Pricing, packaging |
| Price to value mismatch | Budget existed, our value case did not justify the number | Product marketing |
| Process failure | Slow response, wrong stakeholder, poor demo | Sales leadership |
| Incumbent inertia | Switching cost beat any product argument | Product marketing, customer success |
| Wrong fit | Should not have been in pipeline | Demand gen, qualification |
| No decision | Nothing bought, status quo won | Product marketing, exec sponsor |
The load-bearing split is between “price above budget” and “price to value mismatch”. Collapse those two and every quarter’s report will say you are too expensive. Keep them separate and you will usually find the second is several times larger than the first, which redirects the work from pricing meetings to proof assets. That is also the point where a positioning exercise earns its keep, and the positioning sprint is built around exactly this kind of evidence.
One more discipline: code from the transcript, not from memory, and have a second person code every fifth interview independently. If the two of you disagree more than a third of the time, your definitions are too loose.
Closing the loop into messaging, battlecards and roadmap
Findings that stay in a document change nothing. Attach each output to an owner and a date.
The quarterly loop
0 of 7 done
That last item is the one everyone skips. If “value not proven against a named competitor” was your top code two quarters ago and you rewrote the comparison page, the count should have fallen. If it has not, the rewrite did not work and you should stop congratulating yourself for shipping it.
Feed the competitive patterns into your ongoing competitive intelligence work as well, because interviews surface competitor claims that never appear on the competitor’s own website. Buyers repeat what they were told in a sales call, and that is intelligence you cannot get any other way. Keep your battlecard rooted in what buyers actually said rather than in what your product team wishes were true.
What this costs and what it will not do
Budget 15 to 25 hours a quarter for an in-house programme, plus 600 to 2,000 dollars in incentives. The real cost is the cadence. Programmes die because the person running them gets pulled into a launch, misses two months, loses the rhythm and never restarts.
It also will not settle arguments on its own. Twelve interviews is enough to see a pattern and not enough to win a fight with a sales leader who does not want to hear it. Pair the coded counts with your win rate benchmarks and CRM data so the conversation has two independent sources pointing the same way.
Start this month
Pick six closed deals from the last six weeks, four losses and two wins, all inside your core ICP. Send the neutral invitation today. Run the interviews yourself, code them with the scheme above, and post a one page summary where sales can read it. Do it again next month. The programme is not a project, it is a habit, and the habit is the whole value. The rest of the product marketing function gets sharper the moment it stops guessing what buyers believed.
Editable CSV worksheet
SaaS Product Marketing planning worksheet
A practical pmm planning worksheet: decisions, owners, evidence and next actions.
Frequently asked questions
How many win loss interviews do you need for the data to be useful?
Twelve to twenty per quarter covers most mid-market SaaS. Below about eight you are reading anecdotes; above thirty the marginal interview rarely changes a conclusion. Weight the sample toward your target segment rather than taking whatever closed. Six losses and six wins in your core ICP tells you more than twenty interviews spread across segments you do not sell to.
Who should conduct win loss interviews?
Anyone except the account executive who worked the deal. Buyers are polite to the person they rejected and will say price to avoid saying the product felt unfinished. Product marketing, a customer research function, or an external interviewer all work. If product marketing runs it, they must not be the person who wrote the messaging being evaluated.
How do you get lost prospects to agree to an interview?
Ask within two weeks of the decision, keep it to 25 minutes, and offer a modest incentive such as a 100 dollar gift card or a charity donation. Response rates of 20 to 35 percent are normal for losses when the ask comes from someone neutral. The email that works says you are not trying to win the deal back and explains you want to know where the process failed them.
Should you use a win loss vendor like Clozd or DoubleCheck?
Use a vendor when you need volume, neutrality for enterprise buyers, or when nobody internally has the time to hold a cadence. Vendors typically charge per interview and deliver a structured report. The tradeoff is latency and distance: findings arrive as a quarterly deck rather than as a Slack message to the PMM who can act on it that week.
What is the difference between CRM close reason data and win loss interviews?
CRM close reasons are the rep's interpretation, recorded under time pressure, from a menu that usually includes price. Interviews capture the buyer's account, including the parts the rep never heard. In most programmes the share of losses attributed to price falls sharply once you interview, because much of it turns out to be unproven value at the stated price.
How often should win loss findings be reviewed with product?
Monthly for a rolling summary, quarterly for a formal read-out with themes and counts. Product needs the same loss coded the same way three times before it moves a roadmap item, so the value comes from consistent coding over quarters rather than from any single dramatic interview.
Do you interview customers you won as well as deals you lost?
Yes, and skipping it is the most common design flaw. Wins tell you which proof point actually closed the deal and which of your differentiators the buyer never noticed. Comparing the two sets is where the useful findings live, because a claim that appears in every win and no loss is the claim worth putting on the homepage.
The saas-marketing.net editorial team Research and editorial
We research, write and maintain every page on this site. The library explains marketing decisions through practical frameworks, explicit assumptions and references. Corrections can be requested through the contact page.
Published September 11, 2026. Last updated .