Pulse ← Trainings
Sales Trainings · sales-training
Current Quality5/10?

The Incumbent Displacement Map — 60-Min Training

📖 2,026 words⏱ 9 min read5/23/2026

The Incumbent Displacement Map

A 60-Minute Team Working Session Where Every Rep Documents the Buyer's Current Vendor Pain Before Pitching a Switch

Why Run This Session

Competitive deals rarely die because your product is weaker. They die because the rep pitched features before mapping incumbent pain, contract timing, and switching costs the buyer already lives with. Procurement then hears a feature parade while the incumbent still holds the relationship, the data, and the renewal calendar.

When reps skip the displacement map, they sound like every other challenger: louder marketing, sharper demo, zero proof they understand what switching actually costs. Buyers nod politely and default to the vendor that already passed security review and already has budget line items.

This session forces every rep to build an Incumbent Displacement Map on one real competitive deal—incumbent named, pain in buyer words, switching costs honest, wedge defined—before the next call. Managers inspect the map in CRM the same week; no map means no competitive forecast commit.

What Reps Will Walk Out With

Who Should Be in the Room

Full sales team plus the manager facilitating. Bring RevOps or sales ops if they own competitive fields in CRM. Every rep needs one real deal where an incumbent vendor is in place—renewal within eighteen months or an active evaluation. No greenfield accounts; displacement discipline only matters when someone already has a vendor.

Before the Meeting (Manager Prep — 15 Minutes)

  1. Ask each rep to pick one competitive opportunity and open CRM notes, last discovery recording, and any support or success tickets the buyer mentioned.
  2. Share the Displacement Map worksheet table (below) in Slack or print one copy per rep.
  3. Manager prepares one lost competitive deal where the rep never named the incumbent—use as the opening cautionary tale.
  4. Confirm CRM fields exist for incumbent vendor, contract end, displacement wedge, and competitive status—or create a temporary note template.
flowchart TD A[Pick one competitive deal] --> B[Map incumbent + contract end] B --> C[List switching costs honestly] C --> D[Capture buyer-stated pain quotes] D --> E[Define displacement wedge] E --> F[Align next call to wedge only] F --> G[Log map in CRM]

The 60-Minute Agenda

This session runs 0:00 to 1:00. The agenda blocks below sum to exactly 60 minutes.

Frame — Why Feature Parades Lose to Incumbents (0:00–0:08, 8 minutes)

Open with a lost deal story where the rep never documented the incumbent. Manager says: "We lost to the logo already on the contract because we pitched features while they were still paying for the old tool." State the room rule: no incumbent on the map, no competitive commit in forecast.

Facilitator script: Ask for three quick hands: who has a competitive deal in Commit without the incumbent vendor field filled? Those deals get discussed last today—not first—because the session fixes the gap.

CRM setup (first two minutes): Each rep opens their chosen opportunity and creates a note titled "Displacement Map — [date]." If your CRM has an Incumbent field, fill it now; if not, the note is mandatory.

Close this block: One volunteer shares account name and incumbent only—no pitch. Manager writes incumbent names on the board to normalize transparency.

Teach the Four Layers of the Displacement Map (0:08–0:20, 12 minutes)

Walk the four layers: (1) incumbent facts—vendor, contract end, buyer owner; (2) pain in buyer words—minimum three quotes with source call date; (3) switching costs—data, people, politics, timeline; (4) wedge—one pain your proof can own. Show a filled example on screen. Manager says: "Marketing adjectives are banned on this worksheet—only words the buyer said."

Facilitator script: Read a good and bad wedge aloud. Good: "Cut manual reconciliation from four hours to forty-five minutes—CFO cited on 3/12 call." Bad: "Better analytics platform."

Live demo in CRM: Demonstrate logging pain quotes in the opportunity timeline with @mention to SE or manager if your org uses collaboration—quotes must be findable in sixty days.

Manager checkpoint: Deal desk or ops confirms which competitive fields roll to reporting; reps tag Competitive Status = Active Displacement if available.

Timer and room mechanics (Teach the Four Layers of the Displacement Map): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Solo Build on a Real Competitive Deal (0:20–0:35, 15 minutes)

Silent work for twelve minutes, then four minutes of manager circulation. Each rep completes the worksheet row by row. Circles on "guess" in the Source column are mandatory discussion items.

Facilitator script: On each desk ask: "Says who? Which call is quote two from?" If the rep cannot cite a call, mark the row discovery gap in red on the worksheet.

CRM action (required before timer ends): Paste the completed table into the CRM note before the timer ends. Minimum three pain quotes and contract timing—or the deal is downgraded one forecast category.

Circulate and challenge: Challenge any wedge longer than one sentence. Split into wedge vs. nice-to-have feature list stored separately so the next call stays focused.

Timer and room mechanics (Solo Build on a Real Competitive Deal): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Pair Role-Play — Procurement vs. Challenger (0:35–0:48, 13 minutes)

Pairs: Partner A is procurement defending the incumbent; Partner B delivers only the ninety-second wedge opening. Procurement attacks with switching cost, security re-review, and "we just renewed." Swap at six minutes.

Facilitator script: Call time at ninety seconds. Interrupt any feature dump: Manager says: "Reset—wedge only."

Pair exercise rules: Partner A must use switching costs from Partner B's real worksheet—not generic objections. Partner B may not introduce new features not on the map.

CRM action after swap: After swap, each rep logs a Task: "Deliver wedge talk track on [next call date]" with the wedge sentence in the task description.

Timer and room mechanics (Pair Role-Play — Procurement vs. Challenger): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion.

Facilitator circulate: Walk the perimeter; sit with the quietest pair first. Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack.

Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing. These norms keep the block dense and protect the sixty-minute boundary.

Counter-Case and Rational Displacement (0:48–0:56, 8 minutes)

Facilitate group discussion: when is displacement irrational? Long contract, zero admitted pain, sponsor leaving, or switching cost exceeds value. Reps flag their own deal go/no-go.

Facilitator script: Ask: "Who moved a deal to Nurture today based on honesty?" Celebrate one park decision—protects the forecast.

Capture on whiteboard: List five valid park reasons on the whiteboard; manager adopts them in pipeline review language this week.

Each rep commits: Each rep writes one discovery question to fill the biggest gap on the map for the next buyer call.

Timer and room mechanics (Counter-Case and Rational Displacement): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Commit — Wedge and Forecast Hygiene (0:56–1:00, 4 minutes)

Round-robin: account name, incumbent, wedge in one sentence, next call date, go/no-go. Manager captures revised forecast categories for irrational displacement.

Facilitator script: Manager says: "If I open CRM tonight, I should see the map note on every deal you committed."

Forecast / pipeline tie-in: Any competitive Commit without incumbent + wedge in CRM is discussed first in Monday pipeline—not honored as Commit.

Manager records in CRM or tracker: Manager exports a list of competitive opps missing incumbent field; RevOps sends reminder automation if still empty in forty-eight hours.

Timer and room mechanics (Commit — Wedge and Forecast Hygiene): Keep the countdown visible. At the halfway mark, pause only for CRM confirmation—not for open discussion. Facilitator circulate: Walk the perimeter; sit with the quietest pair first.

Ask each rep to show their screen: opportunity updated, task logged, or worksheet row complete before they earn the break. If someone finishes early: They peer-review a partner's CRM entry or listen for the pair role-play—never email or Slack. Manager line to repeat: "The artifact in CRM is how we know this hour worked—not attendance." Energy: Stand during pair work; sit only for solo CRM writing.

These norms keep the block dense and protect the sixty-minute boundary.

Agenda check: 8 + 12 + 15 + 13 + 8 + 4 = 60 minutes.**

Worksheet / Artifact

Displacement ElementYour Deal (fill in)Source (buyer / data / guess)
Incumbent vendor____________
Contract / renewal timing____________
Incumbent relationship owner (buyer side)____________
Pain quote #1 (verbatim)____________
Pain quote #2 (verbatim)____________
Pain quote #3 (verbatim)____________
Switching cost: data / migration____________
Switching cost: training / change mgmt____________
Switching cost: political / risk____________
Displacement wedge (one sentence)____________
Rational to displace this quarter? (Y/N)____________

How to Use This With the Buyer

  1. Use the map to open the next call with their language: repeat one pain quote and ask what changed since they said it.
  2. Share switching-cost honesty early—it builds trust when you name migration work instead of pretending it is free.
  3. Co-build mitigation: ask which switching costs they have budget or staff to absorb this quarter.
  4. Turn the wedge into a mutual next step: one pilot scope, one metric, one executive sponsor—not a full platform rip-and-replace pitch.

Manager Coaching Notes

The Bottom Line

Displacement is a discipline problem before it is a product problem. Reps who map incumbent pain, switching costs, and a single wedge stop sounding like interchangeable challengers—and managers who inspect the map in CRM stop forecasting competitive fiction. Run this session before the next competitive quarter, not after three losses to the same logo.

Download:
Was this helpful?  
Sources cited
Pulse RevOps sales training methodologyPulse RevOps sales training methodology
⌬ Apply this in PULSE
Gross Profit CalculatorModel margin per deal, per rep, per territory
Deep dive · related in the library
sales-training · 60-min-meetingThe Executive Access Workshop — 60-Min Trainingsales-training · competitive-sellingThe Competitive Knockout Session — 60-Min Trainingsales-training · 60-min-meetingThe Split Documentation Standup — 60-Min Trainingsales-training · 60-min-meetingThe Territory Signal Stack — 60-Min Trainingsales-training · 60-min-meetingThe Win-Loss Sprint — 60-Min Trainingsales-training · 60-min-meetingThe Contract Pre-Flight — 60-Min Trainingsales-training · 60-min-meetingThe Three-Touch Outbound Sprint — 60-Min Trainingsales-training · 60-min-meetingThe Renewal Rescue Standup — 60-Min Trainingsales-training · 60-min-meetingThe Discovery Debrief Ritual — 60-Min Trainingsales-training · 60-min-meetingThe Mutual Action Plan Co-Build — 60-Min Training
More from the library
revops · economy-modeHow do you attribute expansion revenue to customer success vs sales overlays?revops · revops-500What is the RevOps playbook for legal redline cycle time during event-sourced pipeline on Salesforce when sales on Outreach (batch 1 #406)?revops · revops-500How do you standardize broken lead routing when no dedicated RevOps hire yet and leadership only reviews churn reason integrity monthly on Dynamics 365 (batch 1 #470)?revops · revops-500Why do most vendors get expansion white space wrong for outbound SDR RevOps teams using HubSpot (batch 1 #408)?revops · revops-500How do you attribute call recordings not tied to opps when sales on Outreach and leadership only reviews stage conversion monthly on Dynamics 365 (batch 1 #460)?revops · revops-500What is the RevOps playbook for commission disputes during services-led sales on Salesforce when sales on Outreach (batch 1 #436)?revops · revops-500What CRM fields prove you fixed UTM loss across subdomains after migrating to Zoho CRM for pod-based selling (batch 1 #474)?revops · revops-500How do you model renewal ghosting when no dedicated RevOps hire yet and leadership only reviews expansion rate monthly on Dynamics 365 (batch 1 #485)?revops · revops-500How do you measure renewal ghosting when no dedicated RevOps hire yet and leadership only reviews pipeline coverage monthly on Dynamics 365 (batch 1 #425)?revops · economy-modeHow do you integrate Salesforce opportunity data into Palantir Foundry for account planning?revops · economy-modeHow do you reconcile usage-based consumption with CRM ARR fields after a pricing model change?revops · revops-500What is the RevOps playbook for commission disputes during BDR-to-AE split on Salesforce when parent-company rollup reporting (batch 1 #396)?