Price objection handling - four AI roleplays

"That is too expensive" is one sentence carrying four unrelated messages, so price objection handling starts by telling them apart. Reps answer all four the same way, usually with a discount, and a discount is the correct response to roughly one of them. So this is not one objection to practise but four, and it belongs in a set of sales roleplay scenarios rather than in a single rebuttal.

Price objection handling starts with four hidden shapes

The reason price objections feel unbeatable is that reps treat them as a single event with a single counter. They are not. Almost every one of them is one of these four, and the four need opposite responses.

  • No money in this period. The buyer wants it and cannot pay for it now. The constraint is a calendar and an approved budget line, not an opinion about worth. This is the only one of the four where the number itself is genuinely the blocker.
  • No value established. The money exists. The case does not. Nothing in the conversation gave the buyer a way to compare your price to a cost they are already paying, so the price is being weighed against zero, and any number loses that comparison.
  • A cheaper option exists. The buyer is holding a comparison, spoken or silent. Sometimes it is a competitor, often it is an internal build, a spreadsheet, a junior hire, or doing nothing at all with the current tool.
  • The polite exit. Price is the socially acceptable way to end a conversation without an argument. Nobody has to defend "it is too expensive". The real reason may be timing, an internal politics problem, or simply that you never had the deal.

These four are not degrees of the same thing. A buyer with no budget and a buyer who is stalling are in opposite situations, and the move that helps the first one actively harms the second.

One question that separates them

The question is boring and it works: "Too expensive compared to what?" It is neutral, it does not argue, and it is nearly impossible to answer without revealing which of the four you are in. Say it, then stop talking. The value is entirely in the pause afterwards.

If a rep cannot say it without sounding defensive, the fix is not a better script. It is reps role playing the sentence until it comes out flat and curious rather than wounded. That tone difference is the whole thing.

Shape What comes back What actually moves it
No money now A date, a frozen budget, a fiscal year, an approval they do not have Terms, phasing, a smaller starting scope, or a scheduled return with the event attached
No value Silence, or a vague answer about it being a lot of money Back to diagnosis. Price the current situation before you defend yours
Cheaper option A name, a number, or "we could do this ourselves" Make the comparison explicit and honest, including where the cheaper option is genuinely fine
Polite exit Agreement, warmth, and no detail at all Give them the exit. Ask directly whether this is a no, and believe the answer

The buyer who has a real budget problem gives you specifics. The buyer who is leaving gives you agreement. Detail is the tell, not tone.

Why the discount reflex is expensive

Watch what a discount does in each of the four. In the first, it can genuinely help, particularly as a change to terms rather than to the number. In the second, it is a disaster: cutting the price of something whose value was never established confirms the buyer's suspicion that the price was invented, and it invites them to wait for the next cut. In the third, you are conceding a comparison you have not seen, which means you may be discounting against an option that was never a real threat. In the fourth, you have handed a leaving buyer a better reason to keep not deciding, since a price that drops when challenged will drop again later.

So the reflex answers one case out of four and damages two of the remaining three. That is not an argument for never discounting. It is an argument for finding out which of the four you are in before you spend the only concession you have.

The same four shapes, mirrored

The structure is not specific to selling software. Turn the deal around and put the rep on the buying side, as an acquisitions rep making an offer on a property. Now the objection arrives as "that is too low", and it splits into the same four.

  • A hard floor. There is a mortgage payoff, a lien, or a number the seller must clear to walk away whole. This is arithmetic, not negotiation, and no amount of rapport moves it.
  • No value established. The seller is comparing your offer to a retail listing price and nobody has priced what the difference actually buys them: certainty, speed, no repairs, no showings, a closing date they choose.
  • A comparison. A neighbour sold for a number last spring, or another buyer said something higher on the phone yesterday. The comparison is real to them whether or not it is comparable.
  • The polite exit. The seller has decided not to sell, or not to sell to you, and "too low" is the version of that which ends the call without a discussion.

Raising the offer answers the first one. It does nothing for the second, because the gap there is an explanation rather than a number. It is guesswork against the third, since you are bidding against a figure you have not seen. And on the fourth it buys a conversation that was already over. Same structure, same trap, opposite direction.

When a discount is the right answer

Every article about objections eventually implies that holding firm is always correct, and that is not true either. Discounting is the right move when the value is established and the constraint is real, when you are buying something specific in return such as a longer term or a reference, when a smaller scope genuinely fits the buyer better, or when the relationship is worth more than the margin on this particular deal.

The rule that keeps this honest is simple: a concession should always be traded, never donated, and it should never be the first thing you say after the word "expensive".

Roleplaying it as four scenarios, not one

Most objection training runs one price roleplay and calls it covered. That teaches reps a single reflex for a moment that needs four. The better structure is the same product, the same rep, and four different customers, where the only variable is which of the four shapes the buyer is actually in and nothing in the wording gives it away.

The measurable skill is diagnosis speed: how many turns it takes the rep to identify which one they are in, and whether they conceded anything before they knew. Reps improve at that quickly, because the failure is obvious in a debrief and almost invisible in the moment.

That is exactly the kind of repetition pichi.ai is built for. A rep roleplays the price conversation by voice against an AI customer whose real reason is fixed in advance and never announced, four times with four different reasons, and sees afterwards which one they diagnosed and which one they discounted their way through. The fourth shape deserves a run of its own, because it usually arrives as the send me an email objection. Doing all of this on live deals works too. It just costs the deals.

Run your price objection four different ways

Tell us how your buyers say no to the number. We will show what roleplaying all four versions of that conversation looks like for your team.

Sales roleplay scenarios → See pricing - $49 per seat