TL;DR In this article I share the win/loss framework I use at every company I join and the repositioning story that proved why this is the highest-ROI work a PMM can do.
“Most PMMs build positioning on guesswork“
Here’s what usually happens. You join a company, read the existing messaging, talk to the product team, skim a few Gartner reports, and build your positioning. Maybe you look at the competitor’s website. Maybe you listen to a few sales calls. Then you ship messaging and hope it sticks.
Six months later, the sales team is still losing deals to the same competitor. The messaging feels right to you, but conversion tells a different story. Nobody knows why deals are slipping, and the theories keep changing depending on who you ask.
I’ve been in this exact situation multiple times. And the fix was always the same: stop guessing and start talking to the people who made the buying decision. That’s win/loss analysis. You call customers who chose you (wins) and prospects who chose someone else (losses), and you ask them what actually drove the decision. Not what your sales team thinks happened. Not what your CRM says. What the buyer remembers.
The output isn’t a research report that lives in a folder. It feeds directly into repositioning, competitive battle cards, sales coaching, and pricing conversations. It’s also one of the highest-impact things a PMM can do with 20-30 hours of work.
The repositioning that came from listening to lost deals
Let me start with the story that changed how I think about this.
I was working with an enterprise digital workplace platform that had superior technology compared to its main competitor. Better APIs. More customizable. The product team believed those were winning advantages, and the messaging reflected it: “The most flexible, API-first enterprise intranet platform.”
But we kept losing to the same competitor. So I set up win/loss interviews with recent losses. Within the first five conversations, the pattern was obvious: in 70% of losses, the reason wasn’t “your product isn’t as good.” It was “we chose them because they promise faster implementation.”
The buyer wasn’t a CTO optimizing architecture. It was usually an IT director or VP trying to get a solution deployed before the fiscal year ended, before staffing changed, before priorities shifted again. Implementation speed mattered more than technical sophistication. We were leading with the wrong value prop entirely.
So we repositioned. The headline became “Deploy your digital workplace in weeks, not months.” We built comparison materials showing implementation timelines. We created a case study around a complex intranet deployed in 6 weeks.
That’s what win/loss analysis does. It doesn’t tell you to build new features. It tells you what to emphasize and how to fight the battles you were losing.
How I set up win/loss at a new company
Every time I join a company, win/loss is one of the first things I build. Here’s the framework.
Who to talk to. The person who made or heavily influenced the buying decision. For smaller deals, that’s the buyer directly. For enterprise deals, the economic buyer or internal champion. Avoid implementation contacts or junior team members who weren’t in the room when the decision happened.
Timing matters. For wins, I talk to customers within 90 days of close. Memory is sharp and they’re still reflective about why they chose you. For losses, 30-45 days after the deal closes. Soon enough that it’s top of mind, but with enough distance that the conversation isn’t emotional.
How many. I aim for 10-15 win conversations and 8-12 loss conversations per round. After 5-6 in each category, themes start repeating. The remaining interviews confirm if those patterns hold across company sizes and industries.
Getting people to say yes. Your sales team is the gateway. Have them ask: “We’re doing research to get better at serving customers like you. Would you be open to a 20-minute call with our team?” Frame it as learning, not a follow-up. When the ask comes from the rep who worked the deal, response rates jump significantly.
For losses, I coach the rep to say: “Would you be open to sharing feedback on your evaluation process? No pitch, just genuine feedback.” People almost always say yes. They spent time evaluating you. They have opinions. They want to share.
The questions that actually surface the real reasons
Tight scripts kill good conversations. I use a loose structure and follow the thread wherever it goes.
For wins: “Walk me through your evaluation. What were you trying to solve? Who made your shortlist? What made you pick us?” Then the question that reveals the most: “If I took away [your biggest feature], would you still have chosen us?” That separates core value from nice-to-haves.
For losses: “Walk me through your evaluation. What problem were you solving? We made your shortlist. Why did you go with [competitor]?” Then: “What would have needed to be different for us to win?” Don’t get defensive. Listen. The things that sting are usually the insights you need most.
In both cases, I ask about pricing, timeline, implementation concerns, and how they compared vendors. You want to know if they chose the competitor on features, price, sales experience, or implementation speed. Those are different problems with different fixes.
Turning raw feedback into something your team will act on
After 15-20 interviews, you have pages of notes. The synthesis is where most PMMs lose momentum, so I keep it simple.
For example, I use Confluence tables. Rows are interviews. Columns are themes: company size, industry, decision drivers, why they won or lost, objections raised, competitor mentioned, implementation concerns. Within a few conversations, patterns start clustering.
Build winner and loser profiles. I write a one-page summary: “We lose to [competitor] when the buyer is IT-focused, has a short timeline, and cares about ease of implementation. We win when the buyer is compliance-driven, willing to invest in adoption, and needs deep integration.” This tells sales which deals to pursue hard and which might not be fits.
Look past the surface. A loss that feels like “they wanted a lower price” is often actually “they didn’t see why our solution justified premium pricing.” That’s a positioning problem, not a pricing problem. Positioning problems are fixable.
Present it so people act on it. A 20-page report sits unread. I present findings as a short deck with four elements: the numbers (“We analyzed 12 wins and 10 losses”), the patterns (“Against [competitor], we lose 60% when implementation timeline is a deciding factor”), the revenue impact (“That’s $600k in lost ARR per quarter”), and the recommendation (“Reposition to lead with deployment speed, build battle cards, coach sales on surfacing implementation concerns early”).
Share actual quotes. An anonymized buyer quote hits harder than a statistic. “Your product is technically better, but they promised a deployed solution by Q4 and you said Q1. We can’t wait.” Sales teams remember quotes like that because they’ve heard the same thing in their own deals.
The mistakes that make win/loss useless
Talking to the wrong people. Implementation staff tell you about product usability, not about why they bought. Talk to whoever signed the contract or pushed hardest for the purchase.
Accepting surface-level answers. Someone says “they were cheaper.” Push back: “If they were the same price, would you still have chosen them?” Often price is a smokescreen for a different concern. If you don’t dig, you’ll make the wrong strategic decision.
Doing it once and moving on. Markets shift. Competitors change positioning. Buyer priorities evolve. I run full win/loss rounds twice a year and monthly pulse checks with sales (“What’s the most common reason we’re losing to [competitor] right now?”). This keeps positioning current instead of stale.
FAQ
How do I start this if I have no budget for it?
You don’t need budget. You’re already doing customer research. This is making those conversations more structured. The interview takes 30 minutes. Synthesis takes 5-10 hours after a round. It’s reframing existing work, not adding a new program. I’ve run every win/loss program I’ve built alongside my regular work.
What if my sales team doesn’t want me talking to their customers?
Reframe it: “These conversations help me build better messaging and battle cards for your deals.” Offer to have them join the first call. In my experience, after one joint interview, they see the value and hand you a list of 10 more people to talk to. The resistance almost always disappears once they see the output.
Should I hire an external firm?
External firms add credibility and prospects sometimes open up more to a third party. But they cost €15-40k and take 8-12 weeks. Start in-house. You’ll learn more by being in the conversations yourself. Use external research later if you want third-party validation or need to scale beyond what you can handle solo.
How does win/loss feed into other PMM work?
Everything. Competitive battle cards get rebuilt around real objections instead of assumed ones. Positioning shifts to what buyers actually care about. Sales coaching gets specific (“here’s the exact objection you’ll hear from [competitor] buyers”). Pricing conversations get grounded in how buyers actually evaluate cost. It’s the foundation that makes every other PMM deliverable more accurate.
Questions about running win/loss at your company? Let’s connect, always happy to talk through what’s working.
