Handle the "Your Price Is Too High" Objection
Practice a live sales-call roleplay for the “your price is too high” objection. Learn how to acknowledge the concern, defend value with specifics, and move the buyer to a next step without discounting too fast.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Saas · Professional Services · Financial Services · Healthcare · Education
Overview
This roleplay template simulates a live sales call right after a product demo, when the buyer says the price is higher than expected and asks whether you can do better. It is built to help reps practice the exact moment where many conversations go off track: the rep either gets defensive, discounts too quickly, or talks only about features instead of value.
Use this template when the buyer has already shown interest, understands the product solves a real problem, and is now testing whether the price is justified. The learner objective is to acknowledge the concern, reinforce value with specific business outcomes or differentiators, ask a clarifying question, and move the conversation toward a concrete next step. The persona, Morgan, is cautious, practical, and mildly skeptical, so the learner has to earn trust rather than bulldoze through the objection.
Do not use this template for early discovery calls, pure qualification, or situations where the buyer has not yet seen the product. It is also not the right fit if the main issue is legal review, procurement process, or a hard budget stop unrelated to value. The best use is deliberate practice: repeated attempts with immediate feedback so the rep can build a more natural, confident response under pressure.
How to use this template
- Read the situation carefully so you understand that the buyer already likes the product but is challenging the price after the demo.
- Start the roleplay and respond to Morgan’s opening line as you would on a real sales call, using a calm and direct opening.
- Talk to the persona by acknowledging the concern, asking at least one clarifying question, and connecting price to a specific business outcome or differentiator.
- Complete the attempt and review the scored rubric to see whether you defended value without caving too quickly or skipping the acknowledgment.
- Retry the scenario with a tighter answer, adjusting your language until you can move the buyer toward a concrete next step.
Best practices
- Acknowledge the price concern before you explain anything else, or the buyer will hear your response as a rebuttal.
- Ask what specifically feels high so you can separate budget limits, scope concerns, and value skepticism.
- Name one or two concrete outcomes the buyer would get from the product instead of listing every feature.
- Use the buyer’s own language from the demo to connect price back to the problem they said they want solved.
- Avoid offering a discount in your first response unless the buyer has clearly raised a pricing constraint you can confirm.
- Keep your tone calm and practical; sounding defensive makes the objection feel bigger than it is.
- End with a specific next step, such as a follow-up call, a revised scope review, or a decision conversation.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this roleplay template help me practice?
This template helps you practice responding when a buyer likes the product but pushes back on price after hearing the quote. The goal is to acknowledge the concern, explain value in concrete terms, and keep the conversation moving. It is designed for objection handling, not for generic discovery or closing practice. You can use it to rehearse how to avoid sounding defensive or rushing into a discount.
Who should run this scenario?
A sales manager, enablement lead, or rep can run it, depending on how your team practices. It works well for 1:1 coaching, team roleplay, or self-guided repetition. The best facilitator watches for whether the learner names the concern, asks a clarifying question, and proposes a next step. If you are using it for onboarding, pair it with a simple rubric and a pass threshold.
How often should reps practice this objection?
Use it during onboarding, before first customer calls, and again whenever pricing pushback starts showing up in live deals. It is also useful as a short refresher before pipeline reviews or quarter-end selling. Because this is a high-frequency objection, repeated attempts help reps build a steadier response. The template is especially useful when reps tend to cave too quickly or over-explain.
Is this template only for SaaS pricing conversations?
No. It fits any sales motion where the buyer questions price after seeing value, including services, subscriptions, and higher-consideration products. The scenario is written around a post-demo sales call, but you can customize the product, buyer persona, and pricing context. Keep the objection specific so the learner practices a realistic response instead of a generic pitch.
What is the most common mistake this roleplay surfaces?
The most common mistake is jumping straight into discounting or feature dumping before acknowledging the concern. Another frequent issue is treating the objection as a debate instead of a conversation, which makes the buyer more skeptical. Strong responses usually start with acknowledgment, then ask a clarifying question, then connect price to business outcomes. This template makes those behaviors visible in the rubric.
Can I customize the buyer persona and pricing pressure?
Yes. You can make Morgan more skeptical, more budget-constrained, or more open if the learner handles the objection well. You can also change the pricing context, such as annual contract value, implementation fees, or a comparison to a lower-cost competitor. The key is to keep the persona realistic and reactive so the roleplay feels like a real sales call. If the learner dismisses the concern, the persona should push back.
How does this compare with practicing objections ad hoc?
Ad hoc practice often skips the exact moment where reps freeze: the buyer says the price is too high and expects a response. This template gives the learner a repeatable scenario, a clear objective, and scored criteria so feedback is consistent. It also makes it easier to compare attempts and see whether the rep improved. That structure is what turns a vague objection drill into deliberate practice.
What should I look for in a strong answer?
A strong answer acknowledges the concern without over-apologizing, then ties the price to a specific outcome, differentiator, or cost of inaction. It should include at least one clarifying question so the rep learns whether the issue is budget, timing, scope, or value perception. The best responses avoid an immediate discount and instead guide the buyer toward a concrete next step. If the buyer still hesitates, the rep should keep control of the process calmly.
Related templates
Go deeper on the topic
-
Healthcare employee engagement ideas to reduce burnout, boost retention, and improve patient outcomes in your health system.
-
Discover how technology and employee engagement strategies reduce healthcare burnout, protect staff well-being, and improve patient care quality.
-
Discover how digital transformation improves healthcare employee experience—streamlining communication, reducing admin burden, and boosting frontline...
-
Learn the key signs of physician burnout—emotional exhaustion, depersonalization, and more—and discover proven methods to measure and address them in...
Ready to use this template?
Get started with MangoApps and use Handle the "Your Price Is Too High" Objection with your team — pricing built for small business.