Competitive Strategy
Win/loss analysis: the PMM's most underused revenue weapon
TL;DR
Every lost deal has a reason that's safe to say and a reason that's true. Price is almost always the safe one, and it's the one that lands in the CRM and shapes the roadmap. Win/loss analysis is a structured program of interviewing buyers after the decision, with someone neutral asking about the process instead of the product. Two to four a month, tagged the same way every time, routed to product and sales so it doesn't die in a deck.
Ask a sales leader why a deal was lost and you get one of three answers.
Price. Timing. A feature the other vendor had.
Ask the buyer who chose someone else and you hear this instead.
"Your rep only called when it was time to close."
"We never understood how you were different from the other two."
"The proposal read like it was written for a different company."
Nobody lied. The buyer just gave the answer that cost the least to give.
The sayable reason
Every lost deal has a reason that's safe to say out loud and a reason that's true.
Price is almost always the safe one. It's neutral, it implies no judgment about anyone in the room, and it ends the call politely.
Call it the sayable reason. It's what lands in the CRM, and from there it quietly shapes two quarters of roadmap.
Ask a kid how lunch was and you get "fine," and the container comes home with the sandwich still in it. Fine was true enough to say and it explained nothing.
Win/loss analysis is the structured version of opening the container. We interview buyers after a cycle ends, win or lose, with someone neutral asking the questions.
And here's what keeps most programs from ever starting. It's uncomfortable. Calling the person who picked a competitor and asking them to walk through why feels like asking someone to explain the breakup.
So it stays rare. Which is most of the argument for owning it.
Who gets the call
Not every deal needs an interview. Focus on the deliberate ones. Multiple stakeholders, a real evaluation, a competitor in the room.
Two to four interviews a month is a program. Much more than that is a research department nobody funded.
Don't skip the wins. Understanding why we won is worth as much as understanding why we lost, wins are far easier to schedule, and they're what tell us which claims are actually defensible.
Cold outreach gets ignored. What works is a warm introduction from the account executive, framed as research rather than a rescue attempt. A modest incentive helps too, a $25 or $50 gift card, once the buyer can see there's no agenda attached.
The AE introduction does most of the work here. Without it, the request reads as an attempt to reopen the deal, and the buyer goes diplomatic before the first question.
Reach out within two weeks of the decision, while the evaluation is still vivid.
Questions about the process
This is where most programs go wrong.
"What did you think of our product?" produces a diplomatic non-answer. So does "why did you pick them over us?" Both of them invite the sayable reason.
Ask about the process instead:
- What was happening in the business that started this?
- Who was involved, and what did each of them care about?
- What criteria mattered most, and how did you assess each vendor against them?
- Was there a moment when the decision started to feel settled? What happened?
- Looking back, which two or three factors decided it?
- If the winner hadn't been an option, what would you have done?
No product questions. No feature comparisons. Nothing about whether the pricing felt fair.
The buyer surfaces all of that unprompted once they're describing how the decision got made. And the version that comes out is the one they actually believe rather than the one that's least awkward to say.
Anecdote into pattern
One interview is a story. Enough of them is a signal.
Every interview should end in a structured summary with consistent tags. Decision factors as the buyer ranked them, competitive considerations, sales process observations, and deal context.
The tags are the whole mechanism. A story becomes data the moment it's tagged the same way as forty others.
Pragmatic Institute's guidance is to look for repeated themes across a set of interviews rather than react to one vivid story, and twenty or more is the practical floor before betting strategy on what you're seeing.
Four patterns are worth watching for.
When buyers describe the product in language that doesn't match ours, we have a translation problem. Either the framing never reached the market or it isn't landing when it does.
When buyers keep naming criteria we don't lead with, we're losing deals before the demo starts.
When one buyer says "we felt managed toward a close" and another says "they were genuinely trying to work out whether this was a fit," those are two different companies from the outside. The difference shows up in the win rate.
And when buyers describe our competitors, they're telling us what they believe rather than what's true. Those beliefs, accurate or not, are what every rep argues against in every deal.
Where the findings go
Research that lives in a slide deck isn't research. It's therapy.
Product marketing gets the first pass. Rewrite the differentiation claims buyers shrugged at, and update competitive positioning using the language they used instead of ours. Battle cards should carry objections in the buyer's words.
Sales enablement gets the objection patterns and the criteria buyers actually weighed. If everyone who walked away mentioned feeling rushed, that's a coaching conversation rather than a messaging fix.
Product gets nuance rather than a feature list. The most common finding is a buyer who knew we had the capability and never understood why our version of it mattered. Bring product managers into an interview as listeners once a quarter, because what they take from hearing a buyer directly doesn't survive a secondhand summary.
Leadership gets a quarterly readout. Win rate by segment, the factors cited in wins against those cited in losses and whether they're moving, and two deals worth reading in full.
Two habits reliably kill a program. Interviewing only losses, which over-indexes on what's broken and hides what's defensible. And accepting the sales team's account as data, since price is the reason a rep can name at no cost to anybody.
The first month
Start before the process is any good. Five imperfect interviews teach more than a quarter spent designing the perfect program.
Week one, pull closed deals from the last ninety days, filter for competitive mid-market and enterprise, and pick ten buyers. Five wins, five losses.
Week two, draft the outreach and the interview guide. Get the AEs to agree to the warm introduction and to the promise that nobody is reopening anything.
Week three, run three to five interviews. Record with permission and write the summary immediately, while the detail is still sharp.
Week four, share what came back. Five interviews organized well will surface something actionable, and the reaction to it is what buys the program a second month.
What the program feeds
Competitive intelligence tells us what competitors are doing. Win/loss tells us what buyers believe about them. The gap between those two is where most of the strategic value sits.
Product launches get sharper when interviews ran in the six months beforehand, because the day-one objections are already known and already answered.
Sales enablement built on real buyer language outperforms enablement built on internal assumptions. The battle card reps actually open is the one carrying an objection a buyer raised, plus the answer that changed their mind.
Run this for a year and product marketing becomes the function that knows why the business wins. Almost nobody does it well, which is the opportunity.
Open the container.
What to do next
If the CRM says price and nobody in the room quite believes it, the real problem is usually a difference the buyer never heard. That's a positioning audit, and it starts with the buyer conversations nobody has time for.
If that's where you are, start here. The first conversation is free.
Frequently asked questions
Five will give you directional insight and tell you which questions to ask next. Twenty or more is where reliable patterns show up and where it's safe to change strategy. Two to four a month builds toward that without becoming a second job, and segmenting by deal size, industry, and product line gets you more out of the same interviews.
Rarely. Buyers are far more candid with someone who has nothing riding on the answer, and when the rep calls, the buyer assumes the deal is being reopened and turns diplomatic within a minute. A PMM who wasn't on the deal works well, as does an external research firm or a CSM for post-sale feedback. If budget is tight, have the AE send the warm introduction and then step back entirely.
Three things move the response rate. A warm introduction from the AE they worked with, a modest incentive like a $25 or $50 gift card, and an explicit promise that this is research with no sales agenda attached. Timing matters as much as any of them, so reach out within two weeks of the decision while the evaluation is still fresh in their head.
Present it as intelligence rather than accountability, and show patterns instead of individual post-mortems. Lead with the wins. What worked, what messaging resonated, what reps did that accelerated a decision. Then introduce the loss patterns as systemic problems the whole team is carrying. Done that way, the strongest reps usually become the program's loudest advocates, because it makes their job easier.
Related reading
Positioning
The complete B2B SaaS positioning guide: what it is, why it breaks, and how to fix it
March 20, 2026 · 8 min read
Go-to-Market
The product launch tier framework: how PMMs prioritize launches without burning out their teams
March 7, 2026 · 8 min read
Product Marketing
The PMM tech stack: tools product marketers actually use in 2026
March 6, 2026 · 7 min read
The author
Nick Pham
Founder of Bare Strategy. Twenty years in B2B marketing, the last decade in product marketing inside enterprise software.
More about the operator →If this is where you are
Bring the problem, not a brief, and you'll leave the first conversation with something useful either way.
Start a conversation