Price objection analysis: is "too expensive" always a price problem

Short answer

No — a price objection is often not a price problem. Behind "too expensive" there are at least four different situations: the customer does not see the product's value (a value objection), does not want to spend now (a timing objection), is comparing with another offer (a comparison objection), or genuinely lacks the budget (a budget objection). Each needs a different response, and only the last is directly about price.

Price objection analysis means separating these four kinds in conversations. Without that split, a company answers every "too expensive" with a discount, losing margin without solving the real problem.

Why everyone says "too expensive"

"Too expensive" is the easiest and most polite way to say no. Telling a salesperson "I didn't understand your product", "I don't trust you" or "I haven't decided yet" is awkward; "too expensive" offends nobody. That is why price almost always tops the loss reasons sales teams pick in the CRM — which also shows it is the easiest one to pick.

This is where conversation analytics earns its keep: reading what was said before and after "too expensive" to tell the real kind apart.

Kind 1: a value objection

The customer weighs the price against what the product will give them and sees no benefit. Signs: "why so much?", "what makes it expensive?", "what's the difference from a regular one?". Questions about the product's features often went unanswered or got very general answers.

The response is not a discount but an explanation: what the product gives this customer's specific need, a comparison, an example. The problem often lies in the presentation, the website copy or the ad's promise.

Kind 2: a timing objection

The customer accepts the price but does not want to pay now. Signs: "after payday", "next month", "I have a lot of expenses right now", "let me know when there's a sale". This customer is not lost — they are planning their timing differently.

Response: instalments, a reservation, a reminder and a follow-up on a specific date. This kind is lost most often in the follow-up system, because nobody comes back to the customer "next month".

Kind 3: a comparison objection

The customer is comparing with another offer. Signs: "it's cheaper at X", "I saw it online", "I've had quotes elsewhere". There are two sub-cases: the product being compared really is the same, or the customer is comparing different products (warranty, delivery, quality differ).

Response: show the difference clearly; if the product is identical, revisit the pricing policy. Record what the customer says about a competitor as unverified perception.

Kind 4: a budget objection

The customer wants it and sees the value, but genuinely cannot afford it. Signs: "my budget is X", "do you have a cheaper option?", "I can't pay that much". This is the real price objection.

Response: a simpler version, a smaller package, a payment plan — or accepting that this customer is not your target segment. Budget objections often show that ad targeting is too broad.

How to separate the four in conversations

1. 1Field"Price objection kind": value / timing / comparison / budget / unclear. Filled only in conversations with a price objection.
2. 2ContextIn the instruction, ask AI to look at the customer's messages before and after "too expensive".
3. 3EvidenceThe customer's specific sentence is kept for each kind.
4. 4OutcomeKind × sales outcome: after which kind are sales lost most?

An action table by kind

• Value → website and presentation copy, a comparison table, a benefit explanation for agents.
• Timing → instalments, reservation, a dated follow-up.
• Comparison → material showing the difference; reviewing pricing for identical products.
• Budget → a simpler package or narrower targeting.
• Unclear → one clarifying question to keep the conversation going: "what price range did you have in mind?".

When a discount is the right answer

A discount makes sense in only two cases: in a comparison objection, when the identical product really is cheaper at a competitor; or in a timing objection, when a short-term offer encourages the customer to decide now. A discount does not work on a value objection: a customer who does not see the value may not buy even at a lower price. On a budget objection, a small discount often does not close the gap.

Illustrative example

This is an illustrative example. A software company considered "price" the main reason for lost sales and was planning a discount campaign. A month of conversations is split by price objection kind: about half turn out to be value objections — customers do not understand the difference from a competing product. A quarter are timing objections — the annual payment is a large one-off sum. Budget objections are few.

Decisions: instead of a discount, a comparison page is prepared, a monthly payment option is added, and a benefit explanation goes into the sales script. Over the next two months the kind split and sales share are tracked.

Typical mistakes

• Treating every "too expensive" as a budget problem.
• Making a discount the standard reply — customers learn to wait for one.
• Not following up after a timing objection.
• Accepting what a customer says about a competitor's price without checking.

Price objections and agent behaviour

This article is about the kind of objection the customer raises, not how the agent answers it. Evaluating the agent's behaviour on a price call is a separate topic: price inquiry call evaluation. Combining the two gives a useful result: in which kind of objection the team answers worst.

Limits

• The kind is an AI estimate; it errs especially in short conversations — check with a sample.
• The budget a customer states is not always their real budget.
• Pricing decisions are made with margin, competitor and sales data, not conversations alone.

Price objection kind in Vexvon

In Vexvon the company builds a field such as "price objection kind" in its own panel; AI reads the conversation in context, picks from the list and keeps the customer's sentence as evidence. The panel's AI assistant gives the share of each kind, a two-period comparison and a product × kind cross-tab; a comparison with CRM lead status and loss reason can be asked from the same place. More: Vexvon analytics.

Next step

Read the conversations of 40 leads lost last month for "price" and assign each to one of the four kinds. The split is often surprising. For the full objection map, see sales objection analysis; we can build the field on your own conversations in a demo.