The Win Map™: The Narrative Positioning System Behind Every Sales Asset That Actually Works
Your last positioning exercise probably went something like this:
You hired a consultant or ran internal workshops. You landed on a positioning statement. Everyone nodded. Someone put it in a Google Doc or a slide deck. It got shared in Slack.
Then nothing changed.
Sales kept rewriting the deck. Marketing kept guessing what to put in campaigns. Product kept building features based on the competitor checklist. Three months later someone referenced the positioning doc in a meeting and everyone went quiet.
The positioning wasn't necessarily wrong. It just wasn't enough.
The problem isn't your positioning. It's that positioning alone doesn't build anything.
Positioning tells your market what you are — we do X, for Y, unlike Z. It's the statement. And most positioning work stops there.
But a statement doesn't tell your sales team what to say on a call. It doesn't tell your champion how to pitch you to the CFO. It doesn't tell marketing which pain to lead with in an ABM campaign. It doesn't tell product whether to prioritize speed or security.
A statement is a conclusion. What your team needs is the story that leads to that conclusion — told in the right order, with the right evidence, for the right people.
That's narrative positioning. And it's what the Win Map™ is built to produce.
Positioning tells your buyers what you are. Narrative positioning tells them why they should care — in the order that makes them act.
The first one fits on a slide. The second one is the slide deck.
Quick Answer: What is The Win Map™
The Win Map™ is a system — built in Notion — that connects buyer research, competitive reality, and narrative positioning into one living workspace. Everything your team produces downstream — the sales deck, the champion deck, the persona one-pagers, the talk tracks — flows from the same narrative foundation.
It's not a document. It's not a messaging framework that dies in Slack. It's the single source of truth that answers three questions every team member asks daily:
What do we say? (the narrative)
Why does it work? (the evidence)
Which version do I use? (the assets, linked to the personas who need them)
Key Takeaway: The system has five connected sections. But they're not five equal parts — they're a funnel. Everything feeds into the narrative at the center. Everything else flows from it.
The architecture: How the five sections connect
Section 1: Buyer Truth
What lives here:
This is the evidence base. For each persona in the buying committee — the champion, the CFO, the VP of Eng, the end user — the Win Map captures what they actually care about, not what you assume they care about.
What lives here:
Pain points voiced in real sales conversations, not hypotheticals
Decision criteria ranked by frequency (what comes up in 8 of 10 calls)
Objections with the actual language buyers use
Win/loss quotes that reveal why deals really moved or died
The "boring stuff" — implementation timelines, admin requirements, compliance — that buyers quietly care about but nobody highlights
This section is evidence-based. Every entry is traceable to a call recording, a CRM note, a win/loss interview, or a customer email. That's what makes the narrative defensible later — it's built on buyer truth, not executive opinions.
51% of B2B deals are lost to status quo — not to competitors. Your buyer's default isn't "choose competitor A." It's inaction. Buyer Truth reveals what actually makes inaction feel riskier than change, which is the foundation of any narrative that creates urgency.
How teams use it: When marketing asks "what should our next campaign focus on?", the answer is in Buyer Truth — not in a brainstorm. When product asks "should we build Feature X?", the answer is in how many deals it shows up in, and which personas care.
Key Takeaway: Buyer Truth isn't your assumptions. It's evidence-based patterns from real deals. This is what makes the narrative defensible.
Section 2: Capability Map (Your Competitive Reality)
What lives here:
A structured view of your capabilities mapped against competitors, tied directly to the buyer pains in Section 1.
This isn't a feature comparison chart. Each row connects a capability to the buyer benefit it creates, the persona who cares about it, and the win rate data that proves it matters.
| Capability | Competitor A | Competitor B | Buyer Benefit | Which Persona Cares | When This Wins Deals |
|---|---|---|---|---|---|
| Fast mplementation time (2 weeks) | Impossible (12 weeks) | Impossible (8 weeks) | Faster time to value | VP Eng | 80% of wins when speed matters |
| Zero admin requirements | Impossible (requires dedicated admin) | Partially possible (occasional admin) | No hiring needed | VP Eng + CFO | 65% of wins cite this |
| SOC 2 compliance | Possible (SOC 2 + ISO 27001) | Impossible (ISO only) | Good enough for mid-market | Security team | Lost 90% when ISO required |
| Transparent pricing | Impossible (custom) | Partially possible (tiered but unclear) | CFO can budget easily | CFO | 40% mention as decision factor |
Why this format matters:
It shows real differentiation, not "we're better." Every capability is tied to evidence. Product uses it to prioritize the roadmap. Sales uses it to know which battles to fight when a specific competitor shows up. Marketing uses it to build campaigns around the differentiators that actually win deals.
How teams use this:
Product and Engineering use it to prioritize roadmap:
"Should we build ISO 27001 compliance?"
→ Look at table: "We lose 90% of deals when it's required, but it's only required in 20% of deals"
Decision: "Build it if we're moving upmarket. Skip it if staying mid-market."
Sales uses it to know when to fight:
Competitor A shows up in deal
→ Look at table: "We beat them on speed and admin—lead with that. Find out early how critical ISO is right now."
Marketing uses it to build campaigns:
"What should our next competitive campaign focus on?"
→ Look at table: "Implementation speed is our strongest differentiator in 80% of wins—let’s test ads leading with that and landing pages that speaks about it in the hero.”
Key Takeaway: This is how you turn competitive intelligence into strategic decisions across all three teams.
Section 3: Defensible Narrative (The core)
What lives here:
This is the center of the system. Everything in Sections 1 and 2 feeds into this. Everything in Section 4 flows from it.
The narrative isn't a tagline or a positioning statement. It's the story arc — the sequence of ideas that takes a buyer from "I'm fine with how things work today" to "I need to do something about this, and these are the people who get it."
What the narrative contains:
The named problem: Not your category — the specific problem your ICP faces that they may not have language for yet. The Win Map names it and quantifies it using evidence from Buyer Truth.
The reframe: How the "old way" of thinking about this problem leads to the wrong solutions. This is where you earn the right to be different — by showing the buyer that the way they've been approaching this is what's holding them back.
The capability stack: Your distinct capabilities, stacked together in a way that's hard for any single competitor to replicate. Not features listed in a row — capabilities connected to the pains and benefits that matter, drawn directly from the Capability Map.
The "why now": The evidence that this problem is getting worse, not better. Without urgency, the buyer's default answer is always "we'll revisit next quarter." The narrative builds the case for why waiting costs more than acting.
When we win / when we walk away: Honest scenarios — built from the Capability Map — that tell sales which deals to pursue hard and which ones to qualify out early.
Won deals involve an average of 17 buyers across the buying committee. Lost deals? Five. The narrative has to work for all of them — not just the champion. That's why it's built per persona, not as a single monolithic story.
Before Win Map™, a company might say:
"AI-powered analytics platform that helps enterprises make data-driven decisions with machine learning."
Generic. Sounds like everyone. Sales used 2 slides and went rogue with the rest.
After Win Map™ finds a defensible, owned narrative:
What we do:
“We get Eng teams live with analytics in 2 weeks, not 3 months, without needing to hire and train a data engineer or build custom integrations.”
Why it matters:
Eng teams are stuck waiting 12 weeks for analytics vendors to implement, which delays product launches. We're live in 2 weeks because we don't require custom data pipelines.
From → To story, directly tied to pains and benefits
Engineering teams are forced to implement new systems from scratch and struggle to meet internal launches
Implementation delays with custom data structures that break your code → 2-week from start to go live with native integrations
Hiring and training a dedicated admin → self-serve model and a dedicated CSM
Bloated project cost and frequent delays with required professional services → Predictable cost and built-in templates that don’t slow you down
When we win:
Our platform is best suited for teams when speed matters. We beat complex competitors when "no admin needed" is critical. We walk away when enterprise security (ISO 27001) is required—we're working towards it but will not have it in the next 12 months.
The second version works because it names a specific pain (12-week implementation delays), a specific persona (engineering teams), and a specific capability (2 weeks, no admin). It came from Buyer Truth and the Capability Map. Sales uses it because it matches what they actually hear on calls.
Key Takeaway: Defensible means it's built from evidence, not aspirations. If a competitor challenges you on it, you can prove it with data.
Section 4: Sales Assets (the output)
What lives here:
Every asset your team uses in the field — built from the narrative, not from scratch.
What gets built:
Narrative slides: structured around the narrative arc, not a feature walkthrough
Champion deck: 12 slides, not 40 - built for internal selling to the buying committee, not for your first call
Persona-specific one-pagers — each one speaks to what that specific stakeholder cares about, pulled directly from Buyer Truth
Competitive talking points — embedded in the narrative, not in a separate battlecard no one will open
Talk tracks — what to say when a specific competitor shows up, tied to the Capability Map scenarios
83% of winning vendors actively helped buyers navigate their buying committee. The champion deck and persona one-pagers are how. They give your champion the language, evidence, and structure to sell you internally — to people you'll never get on a call with.
Why reps actually use these assets:
Because the reasoning is visible. When a rep opens the deck and wonders "why are we leading with implementation speed instead of AI capabilities?", they can trace it back through the narrative to the Capability Map to the Buyer Truth evidence. They don't have to trust marketing on faith. They can see the logic.
Traditional approach:
Deck in Google Drive, battlecards in a separate folder, one-pagers that are feature dumps, every rep running a rogue version. The Win Map approach: everything linked to the same narrative, version-controlled in one place, updated from one source of truth.
Key Takeaway: Assets work when they're connected to the why. The Win Map™ makes the reasoning visible and the assets easy to update.
Section 5: Feedback Loops (the system stays alive)
The competitive landscape doesn't stay still. Neither does your narrative.
What lives here:
Win/loss patterns updated from CRM and conversation data
Competitive shifts — new features launched, new messaging spotted
Emerging buyer pains that weren't present six months ago
Win rate changes that signal something in the narrative needs updating
How it works in practice:
When Competitor A launches a new feature, you update one row in the Capability Map. You check whether it changes the narrative. If it does, the linked assets flag what needs updating. If it doesn't — most changes don't — you move on. Without this system, that same competitive shift triggers weeks of "should we update the battlecards?" conversations with no clear answer impact.
Maintenance time: About 2 hours per month. Significantly less than the time your team currently spends debating what to say, recreating assets from scratch, and reacting to competitive moves without a framework.
Key Takeaway: The Win Map™ is a living system that updates as competitive reality changes.
Why Notion (and why it matters less than you think)
Notion isn't the point. The narrative is the point. But Notion's structure makes the system work better than alternatives:
✅ Everything is linked: Click from a capability to metrics that prove it matters, features, use cases and the personas that care about them
✅ Everyone can access it
✅ Easy to update (no version control nightmare)
✅ Embeds research, recordings, screenshots (not just text)
✅ Connects to other tools in your tech stack
✅ Mobile-friendly (sales can pull it up in real-time)
✅ Exportable as markdown files for your AI stack. Feed it directly into customGPTs, Claude projects, Gems, or whatever your team uses
A Google Doc can't do the linking. A slide deck can't stay current. A Confluence page gets buried. The system needs to be alive and accessible — Notion happens to be the best tool for that right now.
Key Takeaway: The system is more important than the tool—but Notion's natural knowledge base structure, built-in search, linking and native accessibility makes it convenient.
How The Win Map Gets Built
Phase 1: Diagnosis (Weeks 1-2)
Strategic conversations with customer-facing teams to find where alignment breaks and hidden buyer truths.
Audit win-loss, calls, CRM, existing assets, ICP, messaging and positioning to speed up on the current story, identify what’s working, and gaps
Research competitive, market and personas in the buying committee
Output: Draft Buyer Truth and Capability Map. Usually surfaces 2–3 "oh — that's why we're losing" moments.
Phase 2: Build (Weeks 3-4)
This is where the Win Map earns its name. Using the evidence from Phase 1, we build the narrative together — the story arc that connects buyer pain to your capabilities in the right sequence. This isn't me handing you a doc. It's a collaborative process where your team sees the evidence and arrives at the narrative with conviction.
Output: Defensible narrative — the story your entire GTM team agrees on, built on evidence, not opinions.
Phase 3: Asset Creation (Weeks 5-8)
Sales deck, champion deck, persona one-pagers — everything built from the narrative. Each asset is linked back to the Win Map so the reasoning is visible. When a new team member joins in six months, they can trace any slide back to the buyer evidence that informed it.
Output: Market-ready sales assets connected to the narrative.
Phase 4: Launch + Feedback (Week 6-9+)
Training for sales, marketing, and product — not "here's a deck" but "here's the system, here's the evidence behind it, here's how to use it." Feedback loop established so the system stays current as the market shifts.
Total timeline: 6–12 weeks depending on scope and number of assets.
Investment: Most full engagements run $30–45K. Advisory starts at $2,500/month for teams that need strategic guidance while they execute internally.
Key Takeaway: Building the system takes time. But once it's live, alignment happens automatically because everyone can see the same truth.
What changes after the Win Map™ is live
Before
Product's reality:
Product builds features based on the competitor checklist, not on what wins deals
Marketing runs campaigns based on "everyone's talking about AI," not on what buyers actually care about
Sales rewrites the deck because "this won't land in a real convo"
Everyone works hard. Alignment is theater. Win rate declines.
After:
Product opens the Capability Map: "We lose 90% of deals where ISO is required, but it's only required in 20% of deals. Deprioritize. Double down on speed."
Marketing opens Buyer Truth: "CFOs care about ROI timeline and consolidation — run the ABM play around that, not AI."
Sales opens the narrative before calls: knows exactly what to say and why it works. Uses the deck because it matches real conversations.
Win rate improves. Content, campaigns, and selling motion tell the same story. Champions can retell it without you in the room.
Key Takeaway: The Win Map doesn't add more work. It eliminates wasted work by aligning everyone on what actually matters.
Common Questions About The Win Map
Q: This sounds like a lot of work to maintain. Who owns keeping it updated?
A: Product Marketing owns the system. But updates take ~2 hours/month. Much less work than constantly explaining "why did we lose that deal?" to leadership. And, it is possible to extend the engagement on advisory basis to assist with maintenance.
Q: What if our team doesn't use Notion? Can we build this in other tool?
A: Technically, yes. But Notion's linking and simplicity is what makes this work. Another option is to export the system into a custom GPT, train it and update the source files as part of the maintenance.
Q: Do we need to hire you to build this, or can we DIY it?
A: You can DIY if you have:
- Someone who can run the diagnosis objectively (usually requires outside perspective)
- Access to solid good win/loss data
- The ability to spot patterns across deals
Most teams struggle with the diagnosis, narrative and translating them to effective assets - not with the Notion build part. The hardest part isn't building the system. It's seeing what your own team can't see from the inside.
Q: How is this different from our existing positioning doc?
A: Your positioning doc tells you what to say. The Win Map™ shows you:
- Why to say it (evidence from buyers)
- When to say it (which scenarios)
- How to say it (assets ready to use)
It’s also simple and intuitive enough for teams outside product marketing to use. It's not a replacement for positioning—it's the system that makes positioning work stick.
Q: What if our competitive landscape changes dramatically?
A: That's exactly why you need this system. When Competitor A launches a new feature:
1. Update one row in Capability Map
2. Check if it changes Defensible Narrative
3. Update affected sales assets (linked, so easy to find)
4. Alert sales via Slack
Without The Win Map™, you'd spend weeks updating battlecards that aren’t tied to a narrative; possibly without zooming out to understand if the change even matters.
Q: Can we use this for multiple products or just one?
A: One Win Map™ instance in Notion could support different use cases or products, but every set of assets should be tied to a specific use case. We could filter the Capability Maps per product or use case. This would impact the scope (timeline and cost) but if you prefer one joint system it’s possible, if there’s no concern it might confuse your team when they reference it.
Q: What's the difference between this and a sales playbook?
A: Sales playbooks focus on process (how to run discovery, how to demo).
The Win Map™ focuses on substance (what to say, why it works, what wins deals).
They're complementary. Best teams have both.
Q: What's the difference between this and what April Dunford or Fletch does?
A: April's framework is excellent for defining competitive positioning — what you are and why you win. Fletch is great for homepage-first positioning. The Win Map builds the narrative layer that turns positioning into a complete system of assets — the sales deck, champion deck, and persona one-pagers that your team uses every day. If you've done positioning work but your deck still isn't landing, the missing piece is usually the narrative.
What to Do Next
If your sales deck looks good but isn't converting — if your champion can't retell your story without you in the room — if product, marketing, and sales are telling three different versions of why you win:
The problem isn't your positioning statement. It's that there's no narrative connecting everything together.
Book a diagnostic call: 30 minutes diagnosis. If you’d like, bring in your deck - I'll tell you where the narrative breaks and whether the Win Map™ is the right fix.
Related Resources
Why Sales Assets Fail (And the 3-Conversation Fix): How diagnosis works before building The Win Map
How to build sales assets that multhithread and win the entire buying committee
Competitive Intelligence Beyond Battlecards: How the Capability Map section turns CI into strategy
About The Win Map
Origin: The Win Map system emerged from 18 years of fixing misalignment across enterprise (HP), military intelligence (high-stakes diagnosis), and startups (resource-constrained teams that need clarity fast).
Why it works: Because it's a system, not a document. Static docs die in Google Drive. Living systems become the single source of truth teams actually use.
Last Updated: April 2026
Author: Talya Heller, Down to a T
