Business
Business

"It's Too Expensive" — Five-Meaning Disambiguation

Business

"It's Too Expensive" — Five-Meaning Disambiguation

1. Too expensive to pay right now — cash-flow timing problem, not price-structure problem 2.
developing·concept·1 source··May 27, 2026

"It's Too Expensive" — Five-Meaning Disambiguation

The Three Most Misunderstood Words in Sales

When a prospect says "it's too expensive," every operator hears it the same way: as a price-objection. The book makes a precise argument that "it's too expensive" can mean at least five different things, each requiring a different response, and operators who treat all five as the same lose deals because they're answering the wrong question.1

What This Actually Is

The five meanings the book identifies2:

  1. Too expensive to pay right now — cash-flow timing problem, not price-structure problem
  2. Too expensive compared to a competitor — competitive-positioning problem
  3. Too expensive to pay up front; they need a payment plan — structural-terms problem
  4. They don't have the budget for it at all — budget-allocation problem
  5. It's too expensive in relation to what — value-perception problem (the implicit comparison missing)

Each meaning requires a different operator-response. Meaning 1 (cash-flow) calls for payment-timing flexibility. Meaning 2 (competitor) calls for differentiated-value articulation. Meaning 3 (terms) calls for payment-plan options. Meaning 4 (budget) calls for value-vs-priority discussion (see Money Allocated to Priorities). Meaning 5 (value-perception) calls for value-framework establishment.

Operators who treat all five as Meaning 4 (budget) and respond with budget-objection-rebuttals fail when the actual meaning is Meaning 1, 2, 3, or 5. Operators who disambiguate first and respond second close more deals.

The Disambiguating Construction

The book's recommended response3:

Prospect: "This is just too expensive for our company."

Operator: "What do you mean by 'it's too expensive'?" or "How do you mean it's too expensive?" or "In what way?"

The clarifying question forces the prospect to articulate the specific meaning. Whatever they say, the operator now knows which of the five (or other) meanings is operating.

The book's worked example4: prospect says it's too expensive. Operator asks "how do you mean it's too expensive?" Prospect: "Well, the most we could pay for this service is about $10K a month maximum, and you're quoting me around $15K a month." Now the meaning is clear (budget-allocation specifically capped at $10K).

Operator follow-up: "Can I ask you how you arrived at that monthly figure of $10K a month?" Prospect: "That is what our CEO has allocated us to be able to spend on this type of service because of cutbacks in our department from the merger." The disambiguation has now reached Meaning 4 (budget-allocation), with the specific underlying cause (CEO allocation, post-merger cutbacks). The operator can now negotiate intelligently — perhaps restructured terms, perhaps a phased rollout, perhaps an escalation conversation with the CEO.

Internal Logic

The mechanism is simple but consistently violated: assumptions cost sales. The operator who assumes they understand "it's too expensive" responds to their assumption rather than to the prospect's actual situation. The response mismatch produces deal-failure because the prospect's actual concern goes unaddressed.

The disambiguation discipline is one specific instance of the broader "don't assume, ask" principle that recurs throughout the methodology. "It's too expensive" is one of many phrases that operators have learned to interpret without checking; the book treats price-related ambiguity as the most-costly instance of the broader pattern.

Synergies & Handshakes

The page is the operational expression of Clarifying Questions applied specifically at the price-objection moment. Pairs with Concerns Not Objections Reframe (the upstream framing), Objection as Risk Signal Reframe (the deeper interpretive shift), and Money Allocated to Priorities Doctrine (the downstream response framework for Meaning 4).

Analytical Case Study — The Anti-Pattern

The book gives a worked dialogue showing the failure mode5:

Prospect: "These TVs are just too expensive for our company to buy in bulk."

Average Salesperson: "Too expensive? They are really not expensive if you think about the added benefits they will bring to your customers in your restaurant. Your customers will like the picture quality compared to what you are using now. They will want to come to your restaurant to watch sports just because of the picture quality of your TVs."

Prospect: "Well, I still believe they are just too much to pay for."

Average Salesperson: "Keep in mind that you get twenty-four-hour customer service with our TVs, so, if anything happens, we are available twenty-four hours a day for you."

The book's analytical commentary6: "This conversation will go to a blank screen, absolutely nowhere, and alas, the sale is lost because of the way the salesperson communicated. Regardless of the features and benefits the salesperson talked about, the objection is still weighing on the mind of the prospect. The customer is thinking, 'I've told this guy twice now that I think it's too expensive, and he's just not listening to me.'"

The operator assumed "too expensive" meant the customer needed more value-justification (Meaning 5). The customer's actual meaning might have been budget-allocation (Meaning 4), or up-front-payment (Meaning 3), or competitor-comparison (Meaning 2), or timing (Meaning 1). The operator never asked. The mismatch killed the deal.

The contrasted new-model response7:

Prospect: "This is just too expensive for our company."

Operator: "What do you mean by 'it's too expensive'?"

Prospect: "Well, another company I am looking at is 12 percent cheaper for the same product."

The disambiguation revealed Meaning 2 (competitor-comparison). The operator now knows the deal has a competitive-positioning problem, not a value-justification problem. The response shifts accordingly.

Implementation Workflow

Friday afternoon. You sit with a list of every "it's too expensive" moment from your last quarter's pipeline. For each, you ask: did I assume what it meant, or did I disambiguate first? Most operators discover they assumed in 80%+ of cases. Each assumption was a guess; some guesses were right; many weren't.

You commit for two weeks to one discipline: when any prospect says "it's too expensive" or any variant, your first response is "what do you mean by that?" or "how do you mean?" Before any other response. Before any value-justification. Before any payment-flexibility offer.

The prospect's clarification will reveal which of the five (or other) meanings is operating. Your subsequent response calibrates to the actual meaning. Watch what happens to your close rate on price-objection moments over the next month. Most operators see significant lift because they stop responding to assumed-meanings and start responding to actual meanings.

The Disambiguation Failure (Diagnostic Signs)

  • Immediate value-justification response: assumes Meaning 5; misses all four other meanings
  • Immediate payment-plan offer: assumes Meaning 3; misses the other meanings
  • Repeated value-stack without disambiguation: cascades down the wrong path
  • Treating the second "too expensive" as confirmation of the first: the prospect is telling you you're not listening; you're not hearing them
  • Asking the disambiguating question with leading framing: "What do you mean — is it the cash-flow timing or...?" — gives the prospect a multiple-choice instead of letting them articulate

Evidence / Tensions / Open Questions

Practitioner-derived. The five-meaning decomposition is one possible categorization; alternative decompositions exist in pricing-research literature. The disambiguation principle (clarify before responding) is well-supported in clinical-interview and negotiation literatures; the specific sales application hasn't been A/B tested.

A tension: some price-objections are genuine (the prospect actually means "your price is structurally higher than I'll pay regardless of meaning"). The disambiguation discipline still applies but the eventual response may need to be honest about pricing-structure rather than restructured-flexibility.

Author Tensions & Convergences

Joint Acuff/Miner; the disambiguation discipline reads as a methodological foundation rather than an Acuff-or-Miner-specific contribution. Cross-source with Hormozi's Details Are Death Traps — Ask About the Question: structurally identical discipline applied broadly across objection-handling. Both methodologies converge on clarify-before-responding.

Cross-Domain Handshakes

The plain-sentence version: the principle that ambiguous claims need clarification before response recurs across professions; price-ambiguity in sales is one instance of the broader pattern.

  • PsychologyClarification in Clinical Interviews: clinical training emphasizes never assuming the patient's meaning. The same five-different-meanings problem operates in clinical contexts (the patient says "I'm depressed" — could mean five different clinical states requiring different interventions). The clinical literature has decades of training on disambiguation discipline.

  • Behavioral MechanicsElicitation and Meaning-Checking: intelligence-elicitation tradition treats meaning-checking as a fundamental operator-skill. Same mechanism applied to different ends.

  • Legal PracticeDisambiguation in Legal Questioning: legal professionals are trained extensively in disambiguation discipline. Witnesses say things that have multiple meanings; the lawyer's job is to clarify which meaning operates. Same skill, different domain. Sales operator training could borrow significantly from legal-questioning pedagogy.

The Live Edge

Sharpest Implication. Most sales training treats "it's too expensive" as a single objection requiring a single rebuttal-strategy. The five-meaning analysis reveals that most price-objection handling is a 20%-fit-rate guess. Operators who learn to disambiguate before responding shift from guess-and-hope to diagnose-and-respond, which moves close rate on price-objection moments by significant percentages.

The deeper implication: most operator-assumptions about prospect-statements are similarly under-checked. "I need to think it over," "we already have a vendor," "send me some information" — each of these phrases has multiple distinct meanings that operators consistently collapse into one assumed meaning. The price-objection disambiguation is the tip of a broader assumption-pattern.

Generative Questions.

  • Are there other common prospect-statements with similar multi-meaning structure that warrant similar disambiguation discipline?
  • The clinical-disambiguation literature has decades of training material. Could the methodology be ported wholesale?
  • Can the five-meaning classification be machine-detected from disambiguation-question responses? Operator-training feedback would benefit.

Connected Concepts

Footnotes

domainBusiness
developing
sources1
complexity
createdMay 27, 2026
inbound links4