Answering "That's Too Expensive" Without Discounting on Reflex
The sentence "that's too expensive" lands, and the first thing that happens is a small physical event: your shoulders tighten and your mouth opens to justify the price, or to lower it, or to prove you are worth it.
None of those is a response. They are all attempts to stop the discomfort, and they all give away the thing the sentence was testing.
The useful assumption to start from: "too expensive" is not a price complaint. It is an information gap with four possible shapes. The gap decides what the correct answer is, and the correct answer is rarely "cheaper."
The four things the sentence can mean
A buyer says "too expensive" in four different situations, and they are not the same situation.
One: the budget genuinely cannot reach. The number is real, the work is real, there is simply no money for it. Nothing you say about value fixes this, because it was never about value. The only honest moves are a smaller version of the work, a later start, or a clear no that leaves the door open.
Two: the value was never explained. The buyer knows what the work is, not what it does for them. "Too expensive" here really means "too expensive compared to nothing" — the price is being measured against the absence of the thing, and no product beats free on that comparison. The fix is not to lower the number but to attach the number to the outcome.
Three: a test. Some buyers say "too expensive" to see what happens when they push. There is no gap at all; the price is fine, and the question is whether you will hold your own number. Discounting on reflex here converts a buyer who was ready to pay into a buyer who now wonders whether the original price was honest.
Four: a polite no. "Too expensive" is also the socially smooth way to end a conversation the buyer doesn't actually want. No price would have worked. The distinguishing sign: the sentence arrives early, with no real questions attached, and the buyer seems relieved when the call is about to end.
How to tell which one you are in — before answering
You cannot respond correctly until you know the shape, and you cannot know the shape from the sentence alone. The sentence gives you nothing except the trigger. The shape only appears in the next few questions, which is exactly why the next questions must be questions and not defenses.
The fastest way to sort the four: ask one question that costs the buyer nothing to answer honestly.
"Help me understand where that sits for you — is it that the number itself doesn't work in your budget, or that you're not sure what this gets you?"
Budget and clarity cover the first two shapes. What is left is the test and the polite no, which you do not need to resolve in the same breath. A test answers itself when the price holds. A polite no answers itself by becoming clear-that-it-is-not-this-month-something — which you learn by leaving the door open instead of chasing it.
The responses, in order of usefulness
For a real budget gap, make the scope smaller, not the price.
"Understood. The full scope doesn't fit. I can cut it to [core deliverable], which gets you [outcome], for [amount]. Or if the timing is the issue, I can move the start to [month]."
This is the same trade mechanism as scope creep, pointed at your own offer. It keeps the rate honest and moves the conversation to which version, which is a conversation you can win.
For an unexplained value, attach the number to the outcome, once, in their terms.
"The number is [amount]. The thing it buys is [outcome they actually mentioned]. Compared to that, where does it land?"
Note the structure: you repeat your own number without defending it, you state the outcome in their words, and you end on a question that makes them do the comparison. If the gap is real clarity, this resolves it. If they were testing you, this resolves it too, because you did not flinch.
For the test, the correct move is to not move.
"It's the rate for this scope. If you want it lower, tell me what comes out and I'll re-quote."
Short, holds the number, offers a trade instead of a discount. A discount says "my price has slack in it." A trade says "my price is the price of the work."
For the polite no, make leaving easy.
"No problem. If it becomes a priority in the next quarter, my calendar opens again in [month]. Want me to send the one-pager so it's on file?"
This costs you nothing, keeps the relationship alive for the next budget cycle, and — useful side effect — it is the only one of the four responses that distinguishes itself from a test. A tester reacts to an easy exit with confusion; a genuine polite-noer takes it with relief.
What not to do, in any of the four
- Do not discount on reflex. A discount is the one response that all four shapes interpret the same way: as evidence that the first number was negotiable. You have not closed a deal; you have re-priced a relationship.
- Do not start justifying. Justification is the shape of someone defending a mistake, and it invites the buyer to find the crack in your reasoning. The work, if it needs explaining, gets explained in one sentence about the outcome — not in a defense of the hours.
- Do not fill silence. This is the earlier failure, one step before the price is even spoken: the instinct to talk until the buyer feels comfortable. The price has been said. What follows the refusal is exactly the moment to stop talking and let the buyer sort the four shapes in their own head.
What a model can and cannot do here
The mechanical part is real: turning a messy email into a sorted list of which of the four shapes this looks like, and what the buyer actually said that supports each reading. That draft is genuinely useful, because the same paragraph can contain one budget clue and two value clues, and they are easy to miss mid-trigger.
What a model cannot do is hold the number for you. The decision to not flinch is a temperature decision, made in real time, under a small amount of social pressure — and it is the only part of this conversation that actually closes the deal. A draft can give you the sentences. It cannot give you the nerve, and pretending it can is how people end up with beautifully drafted discounts.
The test
Next time you hear the sentence, do not answer with a number. Answer with the shape question, and note which of the four it turns out to be.
Then check your history: of the last three times you discounted, which shape were you actually in? If the answer is "I never found out, I just lowered the price," you have the diagnosis, and it was never about the number.
This note describes a method. No revenue outcomes, client engagements, or success rates are claimed. Amounts shown as [amount] or [core deliverable] are placeholders to be filled from your own scoping; the number you quote stays yours.
Related notes
- The Four Seconds After You Say Your Price — the failure this article depends on comes one step earlier: the silence after the price, filled by reflex.
- Scope Doesn't Creep. It Gets Invited. — the "smaller scope, not smaller price" move is the same trade mechanism, pointed at your own offer.
- The Proposal Doesn't Need Writing. It Needs Deciding. — where the outcome you attach the price to is actually written down, before the objection ever arrives.