How to handle price objections in a B2B sales conversation
Learn how to clarify price objections, compare scope, explain relevant value and agree a next step, with a practical sales-team role-play exercise.
By VoicePower ·
“Your competitor is cheaper.”
It is tempting to answer with a list of features, a promise about service or a discount. Before choosing a response, find out what the buyer is comparing and what the price concern means for their decision.
A useful sequence is to acknowledge the concern, clarify it, connect your answer to the buyer's priorities and agree a next step. Here is how to practise that conversation.
1. Acknowledge the concern without making a concession
Keep the opening calm and brief:
“Thanks for being direct. Can we look at what is driving the difference?”
This recognises the concern and creates space to understand it. You have not agreed that your offer is overpriced or promised to change it.
Avoid beginning with “Yes, but…” followed by a defence of the entire proposal. The buyer may have one specific concern that needs a specific answer.
2. Clarify which price problem you are solving
The same objection can refer to a budget limit, an incomplete comparison, uncertainty about the value or a request to negotiate. Ask one question, then listen.
- “Is the concern the total budget, the payment timing or the difference between the two offers?”
- “What is included in the alternative you are considering?”
- “Which part of the proposal is hardest to justify internally?”
Follow the answer. If the issue is a fixed budget, repeating the benefits will not remove that constraint. If the buyer cannot explain the value to their own manager, another discount may leave the underlying problem untouched.
3. Compare scope before defending value
Use an explicit comparison. Relevant items might include implementation work, support, training, integrations or ongoing responsibilities, depending on what you sell.
Do not assume the other supplier excludes something. Ask the buyer to confirm, or acknowledge that you do not know.
For an illustrative software sale:
“Our proposal includes the implementation work we discussed. Is that also included in the other quote? If it is, we should compare the remaining differences directly.”
That is more useful than an unsupported claim that the cheaper option will cost more later.
4. Connect the difference to an agreed priority
An extra feature matters only if it helps this buyer. Return to something they have said:
“You said the internal team's capacity was the main concern. The additional support is intended to reduce the work they need to take on. Let's check whether that scope addresses the problem well enough to justify the difference.”
Use evidence you can substantiate. If the financial benefit has not been calculated, explain what would need to be measured. Avoid presenting an estimated return as a guaranteed saving.
5. Agree a next step that resolves the uncertainty
The conversation may end with a scope comparison, a discussion with another stakeholder, a revised proposal or a decision that the offer is not a fit.
Make the next action specific:
“Shall we compare the implementation responsibilities with your operations lead before you decide?”
If you discuss a concession, stay within your authority and make the change clear. A lower fee with reduced scope should be explained as a different offer, with its consequences made explicit.
A ten-minute team rehearsal
Use a fictional or anonymised opportunity. One person plays the buyer; another plays the salesperson; a third observes.
Give the buyer a private reason for the objection: a hard budget cap, uncertainty about implementation, or difficulty securing internal approval. The salesperson should discover that reason through questions rather than being told it in advance.
Run a three-minute conversation, then review:
- Did the salesperson clarify the actual concern?
- Did they check the comparison before making claims?
- Did they connect the answer to a stated priority?
- Did the next step address the unresolved issue?
Repeat the conversation with one improvement. On a later attempt, change the buyer's reason so the team practises listening rather than memorising a script.
Build practice around the objections your team hears
Choose two recurring objections and rehearse them regularly. Keep a short record of what buyers actually say and which questions help clarify the concern. Review patterns without treating every lost deal as a communication failure.
VoicePower's sales communication and presentation training in Dubai uses tailored practice to work on discovery, value explanation, demonstrations and objections.