Sales Roleplay
Price Objections in Discovery Calls: How to Practice
Learn how to handle price and budget objections that surface during discovery before value is established.
RepLift · · 25 min read
Price comes up in discovery before you have earned the right to talk about it. A prospect says something like "what does this typically cost?" or "that sounds expensive" and you are still fifteen minutes away from understanding their situation. When that happens, reps tend to fall into one of two patterns: answering the price question directly and inviting a premature comparison, or shutting the conversation down with a deflection that feels evasive. Neither works well. The real skill is diagnosing what the objection actually means in that moment and responding in a way that keeps discovery moving.
This is a practice guide for that specific problem. Not general objection handling. Not broad discovery methodology. The intersection: price and budget concerns that surface before value has been established, and how to build the judgment and habits to navigate them without losing the call.
Why Price Objections in Discovery Are Different
A price objection at the close is a different conversation from a price objection mid-discovery, even when the words are identical. At the close, the prospect has heard your full case. They understand what the solution does, they have weighed it against their situation, and when they say it is too expensive, they are making a comparison with real information. Your job at that stage is to address the gap between perceived value and price. That is a different article: if you are working on closing-stage price objections, How to Handle the "It's Too Expensive" Sales Objection covers that framework directly.
For a broader framework, see our Sales Roleplay guide.
In discovery, none of that groundwork exists yet. The prospect has no value anchor. They do not know what the solution actually does for someone in their position, what problems it eliminates, or what it costs them to do nothing. When price comes up at this stage, defending it is generally premature. You are asking someone to evaluate a number without the context that makes the number meaningful.
There is also a structural difference in what the objection usually signals. At the close, a price objection tends to be about price. In discovery, it is frequently exploratory. The prospect is testing the water, not drawing a line. They want to know if this is a category of solution they should keep engaging with, or if they should mentally check out before investing more time. That is a reasonable thing to want to know, and it is not the same as telling you they cannot afford it or will not buy.
The same three words, "what does this cost," carry different weight depending on where you are in the conversation. Early in discovery, the question is often about fit and relevance. Later, after you understand their situation and they understand your solution, it is a buying signal. Treating both the same way is one of the most common mistakes reps make, and it is also one of the most trainable. The habit of pausing to read the stage before responding is a skill that practice can build.
What a Price Objection in Discovery Usually Means
Before you can respond well, you need to know what you are actually responding to. A discovery-stage price objection is rarely self-explanatory. Four distinct signals tend to produce the same surface behavior, and the right response to each one is different.
Real budget constraint
Sometimes the prospect genuinely does not have budget available. They may be operating under a spending freeze, working with a fixed and limited budget, or comparing your category against competing priorities. This is a real constraint, and it is worth uncovering early. The mistake is assuming this is the explanation before you have asked. A rep who hears "that sounds expensive" and immediately pivots to justifying the price has already assumed a constraint that may not exist.
If the constraint is real, you want to know it. Discovering a budget mismatch in discovery is far better than discovering it after a proposal. But you find out by asking, not by defending.
Confidence test or anchoring attempt
Some prospects raise price early specifically to see how you respond. They want to know whether you believe in what you are selling. If you immediately soften, apologize, or start explaining why the price is justified, you have signaled that the number is negotiable and that pressure works on you. That is useful information for a skilled buyer, and it often sets the tone for every price conversation that follows.
This kind of objection is not really about price at all. It is a read on your confidence and conviction. The rep who pauses, acknowledges the question without flinching, and redirects to understanding the prospect's situation comes across as someone who knows the value of what they sell. That posture is worth practicing deliberately, because it is easy to lose under even mild pressure.
Premature comparison to a competitor
A prospect who has already spoken to a competitor may raise price as a way of anchoring the conversation to a number they have already heard. "That sounds expensive" sometimes means "your competitor quoted me less." They are not necessarily committed to the competitor, but they are framing the comparison before you have had a chance to differentiate. Responding to the price directly at this point accepts the competitor's framing. The better move is usually to understand what they compared and what mattered to them in that comparison before engaging on price at all.
Proxy for a different concern
Price is one of the easiest objections to voice. It is concrete, it sounds reasonable, and it does not require the prospect to say something that feels more vulnerable, like "I am not sure this is actually relevant to my situation" or "I do not have the authority to approve this" or "I do not fully trust that this will work." When a prospect raises price early and the conversation has not yet gone deep enough to establish real urgency or fit, price is often standing in for something else.
The diagnosis matters because the response that works for a real budget constraint is different from the response that works for a confidence test, and both are different from the response that works when price is a proxy for low urgency or unclear fit. Reps who respond to the surface behavior without diagnosing the underlying signal tend to give the right answer to the wrong question. That is the habit this article is designed to help you practice out of.
When to Explore the Budget Conversation and When to Redirect It
When a price objection surfaces during discovery, the first decision is not what to say about price. It is whether to engage the topic at all. Getting that decision wrong in either direction costs you something: explore too early and you anchor the conversation on cost before the prospect understands value; redirect every time and you signal evasiveness or miss a genuine qualification signal.
The decision rule is straightforward in principle, harder to execute under pressure.
Explore when budget is a genuine qualification variable or when the objection reveals something worth understanding. If the prospect has mentioned a specific number, referenced a competing solution, or indicated that budget approval is part of their process, the concern is probably real and worth opening. You are not defending price at this point. You are qualifying. A question like "When you say that's a concern, is there a number you're working with, or is it more about whether this is the right priority right now?" keeps you in diagnostic mode without committing to a price defense.
Explore also when the objection carries information. A prospect who says "we tried something similar and it didn't justify the cost" is not just raising price. They are telling you something about a prior experience, a reference point, or a skepticism that will matter later. That is worth a follow-up question, not a redirect.
Redirect when price has surfaced too early and engaging it would derail discovery. If you are still in the problem-understanding phase and the prospect asks "what does this cost?" or says "that sounds expensive" before you have established what you are solving for, engaging price directly puts you in a position of defending a number that has no context yet. The prospect has no basis for evaluating it, and neither do you.
The redirect does not dismiss the question. It acknowledges it and moves forward. Language that works:
- "That's a fair question, and I want to make sure I give you a useful answer. Can I ask a couple more questions first so I understand what you're actually trying to solve?"
- "Pricing depends a lot on what you need. Before I get into that, help me understand what's driving this for you."
- "I'll get to that. First, I want to make sure this is even the right fit for what you're dealing with."
Each of these acknowledges the prospect's concern without validating price as the right frame for the conversation yet. The goal is to preserve discovery momentum while signaling that price will be addressed once there is enough context to make it meaningful.
One practical test: ask yourself whether you have enough information to justify the price if the prospect pressed you right now. If the answer is no, redirect. If the answer is yes, or if budget is the variable that determines whether a deal is possible at all, explore.
For a deeper look at how question strategy shapes the discovery conversation overall, see Discovery Call Questions: What to Ask and How to Practice Asking Them.
Follow-Up Questions to Ask When Price Comes Up in Discovery
Once you decide to explore a price or budget concern, the quality of your follow-up questions determines whether you learn something useful or get pulled into a negotiation you are not ready for. The questions below are organized by what each is designed to uncover. Use them selectively based on what the prospect has already said, not as a sequence to run through in order.
Questions to test whether the constraint is real
- "Is budget something that's already been allocated for this, or is that still being figured out?"
Purpose: Distinguishes between a funded initiative and an exploratory conversation where budget does not yet exist. - "When you say it sounds expensive, are you working from a number you have in mind, or is it more of a general concern?"
Purpose: Separates a specific constraint from a vague reaction, which often signals that value has not landed yet rather than that budget is genuinely limited. - "If this solved the problem completely, would budget be something you could make work, or is there a hard ceiling?"
Purpose: Tests whether the objection is conditional on value or whether it represents a fixed limit. A prospect who says "if it solved it, probably yes" is telling you the conversation is about value, not price.
Questions to understand the reference point or comparison
- "What are you comparing this to when you say it sounds like a lot?"
Purpose: Surfaces the benchmark the prospect is using, whether that is a competitor, a prior tool, an internal estimate, or nothing concrete at all. - "Have you looked at other options, or is this early in the process?"
Purpose: Tells you whether the prospect has a real comparison or is reacting without context. If they have looked at alternatives, you need to understand what they found. - "What did you pay for the last solution you tried for this?"
Purpose: Anchors the conversation in a real number the prospect has already accepted, which gives you a more honest baseline than a stated budget.
Questions to surface the decision process behind the concern
- "If we got to a number that worked, who else would need to be involved in approving that?"
Purpose: Identifies whether the person raising the price concern has authority or is anticipating a stakeholder objection they cannot control. This changes how you handle the rest of the call. - "Is budget the main thing that would determine whether this moves forward, or are there other factors?"
Purpose: Prevents you from over-indexing on price when there are other blockers. If budget is one of several concerns, solving it alone will not close the deal. - "What would need to be true for this to be worth the investment?"
Purpose: Shifts the frame from cost to outcome. The prospect's answer tells you what they actually need to see justified, which is exactly what your value conversation should address.
Questions to re-anchor on value before returning to price
- "Before we get into numbers, help me understand what this problem is actually costing you right now."
Purpose: Establishes a cost-of-inaction baseline. A prospect who has quantified what the problem costs them has a different relationship to your price than one who has not. - "What would it mean for your team if this was solved in the next quarter?"
Purpose: Moves the prospect's attention toward the value of the outcome rather than the price of the solution. This is not deflection; it is resequencing so that price lands with context. - "If the ROI was clear, would price still be the sticking point?"
Purpose: A direct test of whether price is the real objection or a proxy for uncertainty about value. A prospect who says no to this question is often telling you they need a better case, not a lower number.
These questions work because they treat a price concern as a diagnostic signal rather than a position to counter. The rep who asks "what are you comparing this to?" learns more in thirty seconds than the rep who spends two minutes defending their pricing. Practicing these questions in isolation, outside of a full discovery call, is one of the fastest ways to build fluency with them before they need to hold up under real pressure.
Common Mistakes Reps Make When Price Surfaces in Discovery
Many reps know, in principle, that discovery is not the place to negotiate price. In practice, when a prospect says "how much does this cost?" or "that sounds expensive" before any value has been established, the instinct to respond directly is hard to suppress. Three failure modes show up consistently, and each one has a specific practice fix.
Defending Price Before Value Is Established
This is the most common mistake, and it is also the most damaging. A prospect raises price early, the rep feels pressure to justify the number, and the conversation shifts from problem discovery to price defense. The rep explains what is included, mentions ROI, or compares the cost to alternatives. None of that lands because the prospect has not yet told the rep what they actually care about. Defending a number before you understand the problem is defending the wrong thing.
The practice fix is to treat any early price mention as a cue to ask a question rather than give an answer. Reps who drill this response pattern, specifically the moment when price surfaces before discovery is complete, build the habit of redirecting toward the problem rather than the price.
Collapsing or Going Silent Under Price Pressure
Some reps do not defend price. They freeze. A prospect says "that sounds like a lot" and the rep stumbles into an apology, offers a discount that was not requested, or loses the thread of the conversation. This is a confidence problem, not a knowledge problem. The rep usually knows what to say. Under live pressure, retrieval fails.
This failure mode is particularly hard to fix through preparation alone because it only appears under pressure. The practice fix is deliberate exposure: repeated roleplay sessions at higher difficulty levels where the prospect is skeptical early, so the rep builds tolerance for the discomfort before it costs a real conversation.
Over-Qualifying Budget and Killing Momentum
The third mistake runs in the opposite direction. A rep hears a price concern and decides to resolve it immediately by pinning down budget. They ask a series of direct budget questions, the prospect feels interrogated, and the call loses the collaborative tone that good discovery depends on. Budget qualification matters, but turning a discovery call into a budget audit the moment price surfaces is a different problem.
The practice fix here is sequencing: learning to acknowledge the price concern briefly, continue the discovery, and return to budget when the conversation has enough context to make the question feel natural rather than transactional.
How to Set Up AI Roleplay to Practice This Specific Moment
Generic discovery call practice will not reliably surface price objections mid-call. If you want to drill the specific moment when a prospect raises budget concerns before value is established, you need to configure the session to create that scenario. Here is how to do that in RepLift.
Selecting Discovery Call as the Practice Type
Start by selecting Live Call as the practice mode, then choose Discovery Call as the call type. Discovery Call practice is built around the skills that matter in that conversation: uncovering problems, asking follow-up questions, listening and responding to what the prospect actually says, and moving toward a clear next step. That framing matters because a price objection in discovery is not primarily an objection-handling problem. It is a discovery problem. The rep's job is to keep uncovering, not to switch into closing mode.
If you set up a Closing Call instead, the practice scenario shifts toward late-stage pressure and commitment, which is a different skill set. The Discovery Call type keeps the session focused on the right part of the conversation.
Using Company and Offer Context to Make the Scenario Realistic
Enter your actual company and offer in the setup fields. This makes the practice more relevant to the real conversations you are having. When the prospect raises a price concern mid-session, the objection will be grounded in your actual price range and offer category rather than a generic scenario. A rep selling a high-ticket consulting engagement needs to practice a different version of "that sounds expensive" than a rep selling a SaaS subscription with a published pricing page.
The prospect profile itself is server-generated after the session starts. You do not build or configure it. What you control is the context you bring in through company and offer, and that context shapes how relevant the practice feels when price comes up.
Setting Difficulty to Surface Pressure Earlier in the Call
Difficulty is the most direct lever for controlling when and how price pressure appears. At lower difficulty settings, the prospect is more patient and more willing to follow the rep's lead. At higher difficulty settings, the prospect is more skeptical, more likely to interrupt with concerns, and more likely to raise price before the rep has had a chance to establish value.
If you are working on the specific problem of price surfacing early, start at Medium difficulty to establish a baseline, then move to Hard or Expert once you can handle the objection without losing the thread of the discovery. Running the same scenario at Expert difficulty, where the prospect pushes on price almost immediately, is a more useful drill than practicing a cooperative conversation and hoping the skill transfers.
What to Focus on During the Session
Go into the session with a specific intention rather than trying to run a complete discovery call. The goal is to practice what you do in the thirty seconds after price surfaces. Do you ask a question? Do you acknowledge and redirect? Do you pause and lose the thread? Keep that moment in focus. You can run a full discovery call around it, but the moment of price pressure is what you are there to practice. If the session ends without that moment appearing, note it and run another repetition at higher difficulty.
Using Session Feedback to Target the Right Gap
After a Discovery Call practice session, RepLift returns an overall score, dimension-level scores, identified strengths, identified weaknesses, and evidence-based feedback. When the goal is to improve how you handle price objections in discovery, the session feedback tells you which specific failure mode you are actually dealing with. That distinction matters because the fix for collapsing under pressure is different from the fix for over-qualifying budget.
Which Dimension Scores Reveal Explore-versus-Collapse Behavior
Four scoring dimensions are particularly relevant when price objections surface during discovery call practice.
Discovery reflects how well you uncovered the prospect's situation, problems, and priorities. If price came up early and you shifted into defense mode, your Discovery score will likely show the gap: the session ended with less information than a well-run discovery should produce. A low Discovery score after a session where price surfaced is often a signal that the objection derailed the conversation rather than being absorbed into it.
Question Quality reflects whether your questions were purposeful and whether they opened the conversation rather than closed it. When price surfaces and the right response is to ask a follow-up question, Question Quality captures whether you did that, and whether the question you asked was the right one.
Listening and Responsiveness reflects whether you picked up on what the prospect actually said and responded to it. A rep who deflects a price concern with a scripted redirect without acknowledging what the prospect said will show a gap here. A rep who collapses and goes quiet will also show a gap here, for a different reason.
Value Articulation reflects how well you connected your offer to the prospect's situation. If you defended price before establishing value, this dimension will often surface that as a weakness: the articulation came too early, before the problem was clearly understood.
Reading Strengths and Weaknesses for Price-Handling Signals
The strengths and weaknesses RepLift returns are evidence-based, meaning they are tied to specific moments in the session rather than general impressions. When reviewing feedback after a session where price came up, look for whether the weakness description references the moment of price pressure directly. A weakness that says you shifted away from discovery when the prospect raised budget is a different coaching signal than a weakness that says your follow-up questions were too surface-level throughout the call.
The specificity of the feedback is what makes it actionable. A general score tells you something went wrong. The evidence-based feedback tells you where in the conversation it went wrong, which is the information you need to target the next practice session correctly.
Using Targeted Practice to Isolate the Specific Gap
RepLift can use weaknesses identified in a session to recommend more focused next practice. If your session feedback surfaces a gap in Discovery or Question Quality specifically around the moment price came up, a targeted practice recommendation gives you a way to focus the next session on that weakness rather than running another full discovery call from the beginning.
The goal of that recommendation is to concentrate repetition on the part of the conversation that needs work. You still choose to start the practice. But going into the next session with a specific gap identified, rather than a general intention to do better, makes the repetition more useful.
Repeating With Higher Difficulty Once the Baseline Holds
Once your dimension scores in Discovery and Question Quality are stable at a given difficulty level and the feedback no longer surfaces price-handling as a primary weakness, increase the difficulty. A rep who handles a Medium-difficulty prospect raising price mid-call without losing the thread of the discovery has not necessarily solved the problem. The same moment at Expert difficulty, with a more skeptical prospect who pushes harder and earlier, will reveal whether the skill is genuinely embedded or only available under low pressure.
You can compare your scores across sessions to see whether the same weaknesses keep appearing at higher difficulty settings. If Discovery and Question Quality hold at Hard but collapse at Expert, that is useful information: the skill is partially built, and the gap is specifically under high-pressure conditions. That is a more precise target than "I need to get better at handling price objections."
A Drilling Sequence for Price Objections in Discovery
Practicing price objections in discovery requires a specific sequence. If you start with full-call simulations before you have a reliable redirect or explore response, you will keep repeating the same collapse under pressure. The sequence below builds the skill in layers.
Phase 1: Redirect-only drills at lower difficulty
Start with a single objective: redirect a price question without losing the prospect and without defending your price. Set your roleplay to Discovery Call at Easy or Medium difficulty. The prospect will raise price early, before you have established much value. Your only job is to acknowledge the question, hold your position, and return to discovery.
A rep who cannot do this consistently at lower difficulty will not do it under pressure at Expert. Drill this segment in isolation until the redirect feels natural rather than rehearsed. You are not trying to win the deal in this phase. You are building a reflex.
Phase 2: Explore and qualify drills
Once the redirect is stable, shift to explore drills. Now the goal is to recognize when a price signal is worth opening rather than deflecting, ask a qualifying follow-up, and gather real budget information without making price the center of the conversation.
Raise the difficulty to Medium or Hard. The prospect's signals will be less obvious. You will need to decide in the moment whether the comment is a real constraint or a test of your confidence, ask a question that clarifies it, and keep discovery moving. After each session, review the feedback on your question quality and how well you maintained conversation control. If you defaulted to deflect when exploration was the right call, that is the gap to target next.
Phase 3: Full discovery sessions with price surfacing unpredictably
At this phase, run complete Discovery Call sessions at Hard or Expert difficulty. Price may surface early, mid-call, or not at all. You do not know when it is coming. This is the closest simulation to a live call, where you have to manage the full conversation while staying ready to handle a budget comment at any point without losing your place in the discovery.
Use session feedback to check whether your explore-or-redirect decisions were appropriate, whether your follow-up questions produced useful information, and whether price pressure disrupted your discovery momentum. If the same weakness keeps appearing across sessions, that is the signal to drop back to a focused drill before running another full session.
Frequently Asked Questions
Should I answer a price question during discovery or redirect it?
It depends on where you are in the conversation and what the question is actually asking. If a prospect asks for a ballpark before you have understood their situation, answering directly invites premature comparison. You have no established value to anchor the number to, so any figure you give will be evaluated in isolation.
The better move in most cases is to acknowledge the question honestly and redirect: something like, "I want to make sure what I share is actually relevant to your situation, so can I ask you a couple of questions first?" That is not evasion. It is the right sequence. The exception is when a prospect has a genuine hard constraint and continuing discovery without knowing it would waste both parties' time. In that case, a brief qualifying exchange on budget is appropriate before you go further.
What is the difference between a real budget constraint and a test of my confidence?
A real budget constraint usually comes with specifics: a number, a timeline, an approval process, or a reference to how they have handled similar purchases. The prospect is giving you information, not pressure.
A confidence test tends to be vague and early. "That sounds expensive" or "we don't have a big budget for this" before you have explained anything is rarely a factual statement about finances. It is often a way of seeing how you respond. Reps who immediately justify price or offer a discount have failed the test. The right response is calm curiosity: "What were you expecting something like this to run?" or "What does your budget picture look like for solving this?" Those questions shift the dynamic without surrendering your position.
How do I keep the discovery moving after a price objection surfaces?
Handle the price comment briefly, then bridge back to the problem. Acknowledge it, ask one clarifying question if needed, and return to discovery with a transition: "That's helpful context. Let me make sure I understand what you're trying to solve, and then we can talk through what makes sense." The prospect usually follows the redirect when it is delivered with confidence rather than hesitation.
The mistake is letting price become the topic. Once you are defending cost in the middle of discovery, you have lost the structure of the call. Your job in discovery is to understand the problem well enough to know whether your solution is even the right fit. Price is not answerable until that work is done.
How can I practice this without burning real prospects?
AI roleplay lets you run these scenarios repeatedly before going live. You can set up a Discovery Call session with company and offer context, run it at varying difficulty levels, and get scored on how you handled the price moment specifically. Reviewing the feedback on question quality and conversation control after each session shows you whether you explored, deflected, or collapsed, and gives you a clear target for the next drill. The practice loop is the same regardless of the tool: isolate the moment, drill it deliberately, review the feedback, and repeat with variation until the response holds up under pressure.