Buyers discuss cost when harder concerns remain difficult to name.

The proposal has been presented.

The solution is credible. The customer agrees that the problem matters. The team has answered the technical questions, addressed the delivery model and explained the expected outcomes.

Then the customer says, “The price is too high.”

The seller reacts quickly.

Can we reduce the scope? Extend the term? Change the payment profile? Find a discount?

A revised number is produced.

The opportunity still does not move.

Weeks later, the real concerns begin to surface. Operations is not confident about the transition. Technology is worried about integration risk. The sponsor cannot yet defend the business case internally. Finance understands the cost but does not trust the value. Another executive questions whether the initiative is important enough to absorb organizational attention.

Price was discussed first because price was the safest objection.

It was visible. It was measurable. It could be raised without exposing uncertainty, internal disagreement or political risk.

This does not mean price is never the problem. Budgets are real. Procurement has responsibilities. Customers should challenge commercial assumptions, compare alternatives and expect value for money.

But a price objection is not always a price diagnosis.

Price is data. It is not the diagnosis.

In complex B2B sales, “too expensive” can mean several different things.

The value is not clear enough.

The risk feels too high.

The customer does not believe the organization will adopt the change.

The solution is being compared with an alternative that solves less.

The initiative has not earned priority.

The buyer needs a defensible reason to slow the process.

Or yes—the price may genuinely exceed what the customer can justify or afford.

The seller’s job is not to argue with the objection. It is to understand what the objection means in this decision.

That requires a better conversation than immediately reaching for a discount.

What specifically makes the price feel high? Compared with which alternative? Which expected outcome is least credible? If the commercial number were accepted, what else would still prevent the organization from moving forward?

Those questions must be asked with curiosity, not as a technique for cornering the buyer. The customer may not yet have a complete answer. Different stakeholders may mean different things when they use the same objection.

A discount offered too early can make the situation worse. It reduces margin without reducing uncertainty. It may also signal that the original price lacked discipline—or teach the customer that waiting produces concessions.

The more useful response is to reconnect price to the decision.

What outcome is being funded? What risk is being transferred or reduced? What must the customer invest beyond money? What happens if they choose a cheaper alternative, delay the change or do nothing?

Sometimes that conversation validates the original value.

Sometimes it reveals that the offer should change.

Sometimes it confirms that the opportunity is not commercially viable.

All three outcomes are more useful than discounting an answer the customer still does not trust.

If your team keeps negotiating price while the real objection remains somewhere else, I am always happy to compare notes.