Diagnose Discounting Before Teaching a Price Response
A coaching design conversation for teams discounting as soon as buyers mention price.
Immediate discounting often looks like an objection response issue. A surrounding management system often shapes a pattern. Sellers sometimes receive praise for quick closes. Deal reviews sometimes skip a reason behind a concession. Managers often lack rehearsal for exploring a buyer concern after price enters a conversation. An enablement consultant should investigate a pattern before offering new language.
Start with a simple distinction. A buyer saying, “Your price is high,” has not supplied a diagnosis. Those words might refer to a budget ceiling, a competing offer, uncertainty around scope, a delayed decision, or an internal request for leverage. Each situation calls for more understanding before a seller discusses a commercial option. A rehearsed response has little value when a seller uses one response for every meaning behind one sentence.
Gather a small set of evidence before designing practice. Ask for three recent deals where a concession entered discussion, plus recordings or notes where available. Include one deal which progressed without a discount when such an example exists. Request manager guidance used in deal reviews and a path for commercial approval. You are not auditing a seller. You are tracing decision points. Ask what happened immediately before price moved from concern into a concession request.
In a fictional design session, Rae meets Victor, a regional vice president. Rae asks, “When a buyer says a price is high, what do sellers usually do next?” Victor answers, “They ask what price will win.” Rae asks for an example. He opens notes from a recent conversation. A buyer mentioned a lower priced alternative. A seller asked for a target number within one minute. Rae says, “Let’s mark evidence available before a question. Did anyone ask whether offers covered similar work, who would decide, or why price became urgent?” Victor says, “We need a better rebuttal.” Rae replies, “A response belongs in practice. First, we need a manager review process which rewards a seller for learning why price matters.”
Read each example as a timeline. Note customer words, seller response, manager involvement, approval request, and a result of a next conversation. Do not infer motive from a missing note. Write “no reason for concern recorded” rather than “buyer was price focused.” A blank record is useful. A blank shows where a manager lacked material to coach a decision. If a seller mentioned a competitor, record whether a seller asked which terms differed or whether a conversation moved immediately toward a number.
One fictional example shows a common gap. A buyer says, “Another provider offered a lower figure.” A seller replies, “What figure would make us competitive?” A buyer gives a number. Later, a manager approves a concession without knowing whether a buyer compared equivalent scope, whether another stakeholder raised a concern, or whether a decision date changed. The issue is not an absence of polite language. A deal contains unanswered questions. A stronger review identifies unknowns before anyone frames price as a sole issue.
Another example brings a different lesson. A buyer says, “Finance will ask why this costs more.” A seller says, “What will finance need to understand about a difference?” A buyer explains a concern about staff time during a process change. A seller restates a concern and asks whether a later conversation with a relevant internal owner would help. No promise, prediction, or price discussion appears in this exchange. Yet a seller learned what evidence matters for a future conversation. A manager has a specific behavior to recognize: a seller moved from a broad price statement toward a decision factor.
Look at manager language during deal review. A manager who asks, “How far are you from a buyer’s number?” signals one kind of attention. A manager who asks, “What did you learn after price came up?” signals another. Neither question decides a concession. A second question leaves room for a seller to surface missing context. Follow with, “Who raised a concern?” “What comparison did they describe?” “What part of a decision is still unclear?” Questions like these make inquiry part of a review routine.
Avoid requiring sellers to interrogate buyers. A buyer who says a competitor costs less owes no detailed briefing. A seller should ask one relevant question, listen, and respect a refusal. For example: “When you compare two options, which difference matters most to your team?” If a buyer says, “I am not prepared to discuss details,” a seller might say, “Understood. Would a later conversation after your review be useful, or should we pause here?” A seller has maintained a professional conversation without forcing disclosure or offering a concession from discomfort.
In practice, separate exploration from commercial discussion. Begin a roleplay with a buyer statement: “Your competitor is cheaper.” Give a seller a customer context card with basic information, such as a pending internal review and several people involved. A seller asks two context questions before mentioning a commercial option. A manager listens for questions linked to buyer words. “What number do you need?” does not explore context. “What comparison led your team to focus on price today?” does.
Use varied buyer replies so practice does not become a memorized exchange. In one round, a buyer says an alternative includes less work. In another, a buyer says finance requested a comparison. In a third, a buyer says no details are available yet. These are fictional practice situations, not a prediction about real buyers. Each reply changes a seller’s next choice. Managers ask participants what information they received, what stayed unknown, and what action fits information available.
Give managers an observer role with a tight focus. They should not grade charisma or invent an ideal answer. Ask them to record a buyer’s exact concern, a seller’s first response, and a first question after a concern appears. During a debrief, start with: “What did a seller learn before discussing price?” If an answer is little or nothing, ask which single question fits a situation. If a seller learned something useful, ask how a manager would reinforce a move during a real deal review.
Reinforcement changes when deal quality enters a conversation. A manager might say, “You did not rush toward a number. You learned finance needs a comparison and confirmed who owns a question. Bring those answers to our next review.” This feedback recognizes a visible choice without claiming a result. Managers also need to resist treating a concession request as proof of weak selling. A request sometimes follows a thoughtful conversation. The coaching issue lies in whether a seller and manager understand a reason for a request and record a next decision.
Create a review prompt for two weeks. Add four fields to a meeting note: buyer words about price, information learned, information still unknown, and agreed next action. A manager reads them during an existing review.
For a fictional practice situation, write a buyer line at a page top: “We like your approach, yet a cost is higher than another option.” Beneath, write two questions a seller might ask before mentioning price. Then write one manager response identifying what a seller learned. Choose a fifteen minute deal review on your calendar, bring one current conversation with price pressure, and complete four review fields before your manager joins.
Practice these next
Build feedback practice from observed behavior and a clear request for another attempt.
An enablement consultant builds trust in AI coaching through a review process.
Create rehearsal conditions which respect experience and still reveal a skill gap.
Guide a manager from a broad judgment toward a fair, useful performance conversation.
Build a respectful feedback conversation from enough observations and a follow up plan.
Guide regional coaching conversations through shared expectations and local sales conditions.