How to Handle Price Objections Without Losing the Diagnosis

• A price comment can be a real affordability limit, an unanswered value question or resistance deeper in the buyer’s reasoning.
• Use the canonical layers: Surface Criteria, Mechanism Belief, Felt Outcome and Identity. Budget, habit and emotion are observations, not replacement layer names.
• Hold a clear price for a clear scope; when scope changes, explain the trade-off. Rebuild impact from the buyer’s numbers rather than promising payback.
• For an Identity objection, COR includes a genuine Non-Negotiable Checkpoint. A requirement the offer cannot meet can end the conversation.

“I like it, but that is a lot of money.” The seller hears a threat to the deal and starts defending the number. More features. Another ROI claim. A small concession. None of those moves establishes what “a lot” means to this buyer.

Price can be the problem. It can also be the language a buyer uses for uncertainty about the mechanism, a weak connection to the outcome, or a decision rule tied to identity. The job is to distinguish those possibilities before changing the offer. A good diagnosis can protect margin and expose a genuine mismatch; it cannot guarantee a full-price sale.

Start with the meaning of the number

Absorb the comment. Let the buyer finish. Ask, “What feels high about it compared with what you had in mind?” If they have already described the concern, follow that answer rather than restarting a diagnostic script.

An OR question can help: “Is the amount beyond what you can allocate, or is it more that the return is not clear yet?” Both directions are legitimate. Leave room for a different answer. A hypothetical check—“If we set the amount aside for a moment, what else would you need to feel comfortable?”—can surface another issue, but a hypothetical yes is not a promise to buy.

Surface Criteria: the amount, terms and scope

At Surface Criteria, establish what the buyer is comparing: total cost, payment timing, included work or an alternative proposal. A real budget ceiling can exist even if the buyer cannot disclose a number or sounds emotional. Do not require a particular tone of voice as proof of affordability.

When the ceiling is real, use scope-before-price: “The proposal covers both teams and implementation. At the amount you mentioned, we could cover one team; implementation would still be required. Would that smaller scope solve enough of the problem?” A cheaper offer that cannot achieve the necessary outcome is not a useful compromise.

If the buyer simply asks, “What is your best price?” a calm hold can be appropriate: “That is the price for the scope we discussed.” Then stop adding nervous justification. Answer any substantive question about the amount. Holding price is a commercial choice, not a test of dominance. If flexibility exists, explain its basis and conditions clearly.

Mechanism Belief: will this actually produce the outcome?

“We bought something similar and it did not work” is not answered by a discount. Ask what failed. Was adoption weak? Did the product lack a required capability? Was the promised result unsupported? Then test whether your mechanism addresses that specific failure.

“What would you need to see to distinguish this from the last attempt?” creates an evidence standard. Show the relevant workflow, implementation requirement or bounded test. If the offer has the same weakness, acknowledge it. Repeating a testimonial without resolving the causal concern leaves the Trust objection intact.

Felt Outcome: reconnect cost to what matters

A buyer may understand a spreadsheet and still feel that the change is not worth the effort. Return to the destination they described: “Earlier you said the main reason to change was getting your evenings back. How are you weighing that against the disruption of switching?” The question connects the decision to their actual priority.

Impact math gives that priority structure. Build it from inputs the buyer recognizes, separating a current cost from a future saving. If a workaround takes ten hours a week at an assumed internal cost of $40 per hour, four weeks represents $1,600 of capacity. That is a hypothetical calculation, not $1,600 guaranteed cash savings. Ask how much of the work the solution can realistically remove and whether the time can be redeployed.

Include implementation effort, subscription cost and ramp time. Do not annualize a one-off bad week or assume every hour disappears. The buyer should be able to explain the case after the call without borrowing your confidence.

Identity: separate the value from the rule serving it

“I always get three quotes” can express a comparison process, a procurement requirement or an identity: “I am a careful buyer.” Clarify which. Respecting that identity can lead to a better comparison: “What do the quotes need to establish for you to feel you have done the right homework?”

When there is genuine Identity resistance and the criterion may conflict with the buyer's stated outcome, VIVID uses Criteria-Outcome Realignment, or COR. The six steps are: identify the stated outcome; identify the criteria; get permission to explore; reveal misalignment via a contextual variable; reposition as a genuine upgrade; get buy-in with autonomy. Between Steps 2 and 3 sits 2.5, the Non-Negotiable Checkpoint. Ask whether the specific requirement is fixed or whether the underlying outcome is what matters. If the requirement is fixed and you cannot meet it, stop COR.

A deadline can be a contextual variable only if it is real. If the buyer needs work completed before a known event but their comparison schedule extends beyond it, explore that conflict together. Do not invent a deadline to defeat comparison. A real upgrade must serve their outcome better, not merely make your offer acceptable.

A worked price conversation

This fictional example uses hypothetical figures to teach diagnosis.

Buyer: Six thousand is more than I expected.

Seller: What had you expected, and what are you comparing it with?

Buyer: Around four thousand. But I could get approval if the value is there. Last time the team ignored the training.

Seller: That makes the implementation question important. What happened after the last sessions?

Buyer: Everyone enjoyed them. Then managers went back to the old routine.

Seller: So enjoying the sessions is not enough. What would managers need to do differently for this to be worth funding?

Buyer: Review one real call with each rep every week. We need that built in.

Seller: The proposal includes manager practice and a review process. It still needs protected time from your managers. Is that available?

Buyer: One hour each week could be. I need the director to agree.

Seller: Then let's test the routine with the director before asking for the full investment. What evidence would you both want from that review?

Buyer: Whether managers can identify one useful change and coach it. Send the outline and I will bring her in.

Why this works as diagnosis: the opening amount suggests Surface Criteria, but the buyer's explanation reveals a Mechanism Belief: training does not change manager behavior. The seller validates the concern and tests the implementation requirement. No discount repairs absent management time. The next step evaluates the mechanism with the person who owns it.

If the buyer had instead said, “Four thousand is the absolute limit and no further approval is possible,” the correct route would be scope, timing or no fit. The seller should not run the same adoption conversation to make that ceiling disappear.

Use the five-step flow and practice the branch

Keep the Layer 6 flow visible in your review: Absorb → Diagnose → Validate → Dissolve → Confirm. Confirm asks whether the specific concern is answered: “Does that address the adoption issue, or is something still missing?” It is separate from VRP=C, the exchange-level pattern Validate → Respond → Probe = Control.

Role-play three versions of “too expensive”: a hard ceiling, doubt about implementation and a careful-buying identity. Your partner must not reveal which version until you ask a clarifying question. Practice a scope comparison for the first, an evidence test for the second and the Non-Negotiable Checkpoint for the third.

On the next five price conversations, note the exact phrase, your initial hypothesis, the question that tested it and what the buyer actually said. Review where you defended price before diagnosis or discounted without changing the source of resistance. Continue with the five-step dissolution flow and the four buyer-psychology layers.

Common questions

Are most price objections secretly about something else?

There is no supported percentage established here. Some are real affordability limits; others involve value, trust, timing or identity. Clarify the specific concern.

Should I always discount when budget is limited?

Compare scope and terms first, and explain what changes. A smaller offer is useful only if it still serves the necessary outcome. Commercial flexibility should be explicit.

What if the buyer wants three quotes?

Ask what the comparison must establish. A genuine procurement rule or non-negotiable requirement should be honored. COR applies only when Identity resistance is present and the buyer permits exploration.

Put it into practice

Choose a conversation to practise.

Explore the framework and put this idea to work on your next call.

Explore VIVID Layer 6: Objection Dissolution →