The objection behind the objection: why 'too expensive' can mean something else

An offer may be expensive in at least three distinct senses. Its purchase price exceeds available funds. Its overall cost appears greater than the benefits. Or its price feels unreasonable in relation to the category, alternative suppliers or contractual terms. These evaluations need not agree. A company can regard an investment as profitable yet lack short-term liquidity. Another company can afford a contract comfortably and still consider it poor value compared with what competitors provide.

Zeithaml's (1988) synthesis of perceived price, quality and value provides a useful basis for separating those dimensions. The lesson is not a universal mathematical formula. It is that buyers evaluate benefits and sacrifices from their perspective. Sacrifices go beyond the number on the quotation: implementation time, dependency, disruption, management attention and the consequences if expected benefits do not materialise. Yet one important limit remains. If there is insufficient budget, rewriting the value story cannot change the bank balance.

Begin with objective constraints before discussing meanings. What is the approved spending limit? Which financial period applies? Does the commitment run for one year or several? Are there procurement thresholds or legal requirements? What are the genuine alternatives? Only then ask what expectations are activated by the price. Confusing these levels leads to two opposite errors: treating a hard financial constraint as psychological resistance, or attempting to solve a trust problem with a nominal discount.

For a buyer, a price can also signal quality, confidence, exclusivity, reliability or how a supplier treats its customers. Lichtenstein, Ridgway and Netemeyer (1993) studied several positive and negative roles of price perception in consumer behaviour. Their findings do not prove how every enterprise procurement manager will respond. They do support the broader point that a price does not always function as a purely financial input.

A high fee might evoke 'specialist expertise' and 'careful service' while simultaneously suggesting 'distance' or 'not meant for companies like ours'. A low fee may imply accessibility, but it can also prompt questions about capability or hidden conditions. In B2B, such meanings are shaped by prior supplier relationships, category norms, expected service levels, tender rules and the consequences of getting the decision wrong.

The practical question is therefore: what is the reference point? Is the buyer comparing a full-service agreement against a basic licence? A guaranteed maintenance commitment against ad-hoc repair hours? An annual fee against benefits that arrive over several years? An associative value proposition matters only when the promised advantage connects with the customer's actual decision criteria. Claiming 'premium quality' can miss the point when the buyer is concerned with scope, control and accountability.

A discount has one immediate and measurable effect: the quoted amount falls. Whether the buyer becomes more willing or able to decide depends on the underlying barrier. With a genuine affordability problem, the reduction might help. With uncertainty about liability, service performance or internal capacity, the number alone may change very little. And if the previous price already seemed arbitrary, a sudden concession could create additional questions about how it was set.

Xia, Monroe and Cox (2004) developed a framework for perceived price fairness. It is a conceptual contribution, not proof that discounts always reduce trust. It does, however, motivate an important distinction that can be investigated: is the offer financially impossible, or does the buyer regard the price-setting logic and terms as unfair? Those are different conversations and may require different remedies.

Discounting can also camouflage missing evidence. If the supplier cannot substantiate an outcome, a slightly cheaper unsubstantiated promise remains a promise. If someone fears being held responsible for a failed implementation, five per cent off does not necessarily remove personal accountability. Conversely, it would be patronising to describe a customer who simply wants a lower price as suffering from unconscious anxiety. Sometimes the competing offer really is better, or the buying organisation quite reasonably values price above other features. The diagnosis has to allow those conclusions.

The first is affordability: there is insufficient funding, budget authority or approved purchasing capacity. No implicit process needs to be invented. The practical task is to determine whether a smaller scope, different timing or lawful payment structure genuinely fits the requirement. If not, a non-sale may be the right outcome.

The second is weak or insufficiently proven value. The buyer understands the features but does not believe the improvement over the current option, or assigns low importance to that improvement. Anderson, Narus and Van Rossum (2006) argue for specific, credible value propositions in business markets rather than broad, unsubstantiated benefit claims. If evidence is missing, a discount is not a substitute for credible proof.

The third is perceived risk. Savings sound attractive, but a buyer anticipates downtime, data exposure, reputational harm or supplier dependency. Sweeney, Soutar and Johnson (1999) studied perceived risk in a retail setting. Translating that evidence directly into a rule for enterprise purchasing would be inappropriate, but it supports a relevant hypothesis to test. The fourth explanation is trust or fairness: uncertainty over whether the supplier will fulfil its commitments or whether contractual terms are balanced. The fifth is social and organisational decision-making: one stakeholder wants the product while another must provide budget, sign-off or compliance evidence. The sixth is negotiation or deferral: the buyer is seeking better terms, preserving options or simply prioritising another project. Samuelson and Zeckhauser (1988) examined preferences for the status quo, while Anderson (2003) reviewed different forms of decision avoidance. These concepts motivate hypotheses, but do not establish that this specific buyer is acting under a bias.

These explanations can coexist. They should not be collapsed into a single personality trait or a score labelled 'buying resistance'. Their value lies in being testable. What observation would make one explanation more plausible? What would count against it? Which intervention would help only if the hypothesis were correct?

A supplier describes a multiyear maintenance contract as 'certainty'. The customer may hear 'being locked in'. The contract promises predictable support but can also raise worries about dependency on one provider. A consulting programme may mean 'better decisions' to the CEO and 'an outsider judging my work' to a department head. In both cases price may become the most convenient label for several separate expectations.

Gawronski and Bodenhausen (2006) distinguish associative activation from propositional evaluation. Fazio (2007) conceptualises attitudes partly as object-evaluation associations that vary in strength. These frameworks make it reasonable to study meanings activated by an offer, but they do not establish that every price objection secretly represents fear. The existence, prevalence and behavioural relevance of a particular association have to be demonstrated in the relevant population and situation.

A core conflict between associations might be 'we want less operational risk' together with 'we do not want greater supplier dependence'. In that case, transparent exit conditions or a staged contract might be relevant. Yet even an apparently sensible intervention should not be prescribed before the concern has been confirmed. Otherwise the sales team might introduce doubts that the customer did not have. The aim is diagnosis and a better decision, not to convince every prospect that an expert understands them better than they understand themselves.

This table is a practical diagnostic aid, not a validated psychological instrument. The second column lists possibilities, not findings about any individual buyer.

Look deliberately for evidence that could disprove the explanation you favour. If the buyer accepts the business case yet still lacks authority to purchase, better value communication is unlikely to resolve the entire barrier. That does not automatically imply an implicit association is responsible. Procurement rules and organisational priorities are real constraints. Evidence-led sales means being able to say 'we do not know yet' rather than filling uncertainty with a confident psychological story.

A fictional food manufacturer is considering a multiyear service contract for industrial cooling equipment. The supplier proposes preventive maintenance, defined response arrangements and periodic inspections. Its quote exceeds the current arrangement, under which the plant mostly pays for repairs when problems occur. The technical manager appreciates the possible benefits: fewer emergency interventions, clearer responsibilities and improved preparation. Nevertheless, procurement reports after two meetings: 'It's too expensive.'

This is a constructed example, not an actual Neurofactor case study and not a source of sales performance data. In the scenario, the buyer's questions are not confined to the headline price. Procurement wants to know which work is included and which is separately billed. Operations wants to avoid dependence on a single maintenance partner. Finance needs to justify a higher regular commitment against savings that remain uncertain.

The supplier initially prepares a discount. A more disciplined response is to compare like-for-like scopes, make exclusions explicit and investigate transparent review or termination conditions. Finance receives scenarios with visible assumptions rather than a single optimistic forecast. The technical manager evaluates whether response-time promises fit the plant's operating requirements. These actions do not manipulate resistance; they clarify genuine conditions for a decision.

The outcome remains deliberately unknown. We cannot say whether a discount would have closed the deal, whether the customer ultimately signs or whether all stakeholders share the association with dependence. A real study would test those propositions separately. The case illustrates the value of distinguishing price level, price meaning, evidential confidence and the authority to approve a contract.

An exploratory conversation does not need to be long, but it does need to leave space for answers the seller may not like. Start with 'When you say it is too expensive, what are you comparing it with?' This reveals the reference point. Continue with 'Which part is financially difficult and which part still needs substantiation?' That separates affordability from uncertainty about returns. Ask who must approve the commitment and which decision criteria apply.

Steindl and colleagues (2015) reviewed psychological reactance when freedom of choice feels threatened. This is a reason to question pressurising tactics, not a reason to diagnose every sceptical prospect as reactant. Avoid leading questions such as 'Are you perhaps worried about making the wrong choice?' They insert a psychological interpretation before the customer has supplied one. 'Which consequences do you need to evaluate before making this decision?' is more neutral. The buyer may identify concrete risks or may report no such concern at all. Both outcomes are valuable. And buyers have legitimate limits on what they can disclose about internal finances, negotiation tactics or other suppliers.

Record statements accurately. Distinguish quotations from the seller's interpretation. Check whether the issue concerns the price amount, scope, timing, contract, trust, comparison or decision mandate. When the evidence remains incomplete, state that uncertainty. A salesperson who only looks for signs of hidden objection may become very confident without becoming more accurate.

Work by Homburg, Koschate and Hoyer (2005) also connects customer satisfaction and willingness to pay in studied settings. This is not a universal price-elasticity rule for maintenance contracts. An enterprise buyer is not merely buying an object. Someone also accepts responsibility for a supplier, contractual obligations and effects on colleagues. Mayer, Davis and Schoorman (1995) developed a model of organisational trust involving perceptions such as ability, benevolence and integrity. The framework does not show that every price objection is a trust issue. It provides a basis for distinguishing different reasons why a relationship may feel uncertain.

A procurement manager can regard a supplier as technically skilled yet doubt its willingness to resolve disputes fairly. A finance director may regard the price as acceptable only if liability and exit terms are clear. An end user may demand a discount because implementation work has been shifted onto their team without acknowledgment. The price then becomes associated with expectations about accountability, reciprocity and the burden of changing suppliers.

Price fairness should not be confused with cheapness. A consistent quote with understandable inclusions may be perceived as fairer than an unexplained last-minute concession. But fairness is not only a communications challenge. If the terms genuinely allocate risk unfairly or hide charges, changing the language is insufficient. The commercial solution is to improve the underlying offer. Research is useful when it leads to substantive improvements, not merely to better-sounding descriptions of the same imbalance.

The following options should be evaluated in context. They are not universal persuasion techniques and none has a guaranteed conversion effect.

An intervention should do two jobs. It must address the alleged barrier and generate a chance to see whether that barrier was relevant. Otherwise the sales team may explain every win as proof of its preferred model and every loss as 'resistance we did not reach'. That is not a scientific diagnosis; it is an unfalsifiable story. Careful sales research allows the initial explanation to be wrong.

1. Step 1 - Record the exact words. Capture what was said, when and to whom. Keep the observation separate from the initial explanation. At this point, you know only that a pricing objection was expressed.
2. Step 2 - Establish hard constraints. Discuss budget, contract, timing, procurement rules and mandate where disclosure is appropriate. Identify conditions that genuinely cannot be changed.
3. Step 3 - Keep several explanations open. Consider affordability, value evidence, risk, fairness and authority rather than defaulting to a favourite story about unconscious resistance.
4. Step 4 - Look for discriminating evidence. Decide which questions or observations would support one hypothesis over another, including evidence that challenges the salesperson's first assumption.
5. Step 5 - Choose the smallest suitable intervention. Clarify the contract, improve substantiation, revise scope or design a pilot with proper decision criteria. A discount is one possible choice, not the automatic next move.
6. Step 6 - Observe what happens and revise. Record the next actual step, the conditions under which it occurred and remaining uncertainties. If a deal does not progress, do not silently relabel the failure as hidden psychological resistance.

Return to the fictional maintenance contract. For the technical manager, the fee relates to uptime, response arrangements and fewer emergencies. For procurement, it relates to comparable scope, contract flexibility and defensible negotiations. For finance, it relates to cash commitments, forecast uncertainty and the burden of recurring costs. Senior management may judge it against continuity risk or dependency on a single supplier. There is no single uniform buyer attitude behind that quotation.

Webster and Wind (1972) described organisational purchasing as a process shaped by multiple participants and contexts. A target-group profile and association map can help structure differences across roles, provided those findings are not turned into stereotypes about every CFO or purchasing manager. A job title supplies a hypothesis about responsibility, not evidence about a particular person's hidden motive.

That does not mean creating a different manipulative pitch for each stakeholder. It means showing relevant evidence for the responsibilities each person must discharge. Operations needs credible service conditions, finance needs transparent cost scenarios and procurement needs comparable offers and balanced terms. If the customer organisation itself cannot agree on a priority, that may be a governance issue which a better sales message cannot solve.

'Too expensive' may mean exactly what it says. It may also reflect insufficient proof of value, an unsuitable comparison, expected risk, mistrust or a fragmented buying process. The mistake is not to consider several explanations. The mistake is to choose one without evidence and describe it as the real reason.

An associative perspective adds value because it asks which meanings attach to an offer, what attracts the buyer and which expected consequences may create resistance. Yet sound sales practice starts with the reality of the customer's constraints. It connects what people say, what can be tested and what people actually do. Sometimes the right answer is better evidence; sometimes different contract terms; sometimes a lower price; and sometimes accepting that the customer should not buy. The ability to distinguish those outcomes is more valuable than a clever response to a price objection.