Price Objection

When a customer stopped over the number, sellers had one move for a long time. Cut the price. "Too expensive" earned a ten percent discount, and another stall earned twenty. Nobody asked why the deal had stopped, because there was no frame for asking.

Run that for a few quarters and the records get strange. The same product sold to two companies of the same size at contract values twice apart. The rep who held the price shows weaker numbers; the rep who discounted early closes more deals. Next quarter everyone opens with a discount, and the deals that discounting never fixed are still stuck.

Naming this objection is what moved it from something you treat to something you diagnose. Several unrelated situations arrive wearing the same sentence, so the useful step is figuring out which one you're in before choosing a response. That reframing is the whole contribution of the term: it turns a reflex into a question.

One sentence covers two different situations — the money genuinely isn't there, or the money is there but nobody can articulate what the number buys.

Say you quoted $4,600 a year and heard that it's too expensive.

1. If it's a budget problem, the tooling budget for the year is $3,000, or nothing has been allocated at all. No amount of explaining the value moves that. What does work is splitting the annual figure into quarterly payments, or starting with ten seats instead of forty so the number fits this year and grows next year.
2. If it's an evidence problem, the money exists but your contact has no sentence to bring to whoever approves it. Here you leave the price alone and build the case. Work out together how many hours a week the task eats today and what that costs in salary. Once the answer is $9,000 a year leaking out, $4,600 becomes a number someone can defend in a room.

Swapping the two answers is expensive. Offer a discount where the blocker was evidence and the price drops while the approval stays exactly as stuck as it was. Keep explaining value where the budget is empty and the prospect concludes you aren't listening to their situation, which costs you more than the deal — they stop telling you things, and the next conversation starts with less information than this one had.

Telling them apart takes two short questions. Asking what range the budget sits in usually exposes the first case. Asking whether they could move forward today at half the price exposes the second — if the answer is still no at half, the blocker isn't the number. Reluctance to change anything at all, which the status quo bias page covers, is one of the things that surfaces disguised as a price complaint.

There are roughly three points in a deal where this sentence appears.

1. Right after the first quote. You run a discovery call, learn the situation, name a number, and the objection arrives in the same breath. Objections here often come from missing information, so explaining value still works.
2. After your contact takes it upstairs. The practitioner is convinced but the approval stalled, and the person carrying your argument is no longer you. What's needed isn't a longer explanation — it's a short sentence and a figure your contact can repeat verbatim.
3. At renewal. A customer who has used the product for a year looks at the price again. An objection at this point is usually a signal that actual usage came in below expectations, so check usage before defending the number.

Who raises it also changes the answer. When the practitioner says it, the budget usually isn't theirs, so the conversation turns into finding a way to get it approved. When a procurement specialist says it, they're saying it because that is the job — value arguments land poorly there, and negotiating terms lands better.

Two neighboring objections show up alongside it: the timing objection, meaning now isn't the moment, and the competitor objection, meaning they're weighing another product. When all three overlap, the first one voiced is frequently not the real blocker, so take them one at a time. To move a price conversation onto other ground, sellers often reach for feel-felt-found, a three-beat technique that acknowledges the concern, cites a customer who had it, and reports what that customer actually found.

"They say it's expensive but won't tell me the budget range. There's still something to check here."

The rep hasn't yet worked out whether the problem is budget or evidence.

"We've hit a price objection at the same point three weeks running. I think the pricing page copy needs a look."

This is no longer about one deal — there's a hole in how the price is explained.

"This isn't a price problem. Our contact has nothing to bring to their boss."

A proposal to re-diagnose the objection and change the response.

At Pagedeck, when Sofia hears this she doesn't reach for a discount. She asks how many hours a week the prospect's team spends hunting for documents, then does the arithmetic with them using their headcount and salary costs. When that figure comes out at more than double the price of the product, the conversation moves off price and onto timing.

Some deals don't move regardless, and those are the ones where the budget truly isn't there. For those Sofia builds a smaller-seat version instead of lowering the rate, and asks when the next budgeting cycle lands so a date exists on the calendar.

The most common belief is that a price objection calls for a discount. The customer named the price, so touching the price looks like the answer, and a few remembered deals that closed on a discount make the case feel proven. But discounts only work on deals where the budget falls short. Where the blocker was evidence, the number comes down and the approval still doesn't come. Worse is what the customer learns from it. Discount once and the same request returns at renewal, and this time the reduced price is the baseline you're negotiating down from.

The other mistake is hearing "too expensive" as a no. It's phrased negatively, so it sounds like the end of the conversation. It's closer to the opposite, and the pattern is consistent enough that some teams treat a price objection as a stage marker rather than a warning. Someone arguing about the number has already decided the product would work and moved on to comparing figures; someone who genuinely doesn't want it never asks the price and just goes quiet. Back away at this point and you close a deal that had one step left in it yourself.