How to respond to “it’s too expensive” in B2B sales
Ask what the buyer is comparing the price with. Check the impact using their evidence, then separate disagreement about value from a funding constraint. A discount should follow a clear discussion of scope and a verifiable exchange; it should not substitute for understanding the objection.
A practical way to approach it
Clarify the comparison
Ask whether the concern is the cost of the problem, another option or the available funding. Treat the response as something to investigate.
Verify the impact
Ask how the buyer measured the time, cost or risk, and who can confirm it. Six hours of lost time does not automatically become cash savings or a return on investment.
Separate value and funding
When the impact is confirmed, ask whether an existing budget can fund the change or a new investment must be approved. Discuss concessions only with an explicit scope and counterpart.
Meet the fictional deal.
Acme is considering your approval software. Julien confirms missed customer deadlines, then says the price is too expensive. At first, the deal has no customer-confirmed measure of the problem’s impact.
Software purchase · Multiple stakeholders. The declared context guides method selection; it does not prove any part of the buying decision.
- Julien
- Operations lead
- Owns the daily problem. His role does not prove buying authority or internal influence.
- Maya
- Finance lead
- A fictional participant. Her title alone does not prove that she can approve this purchase.
- You
- Software seller
- Preparing a proposal. You choose what to ask and send.
See what changes the strategy.
Fictional deal. These states are calculated with the same evidence checks and strategy rules as 3xrep. A source match does not independently verify the speaker or the truth of a claim.
The problem is documented, but no measured impact supports the price conversation.
Declared stage: proposal. This is the seller’s stage, not proof that the buyer is ready.
- Measured impactUnknown
- Buying authorityUnknown
- Decision criteriaUnknown
- Internal supportUnknown
- Buyer deadlineAssumed
- Decision processAssumed
- Buyer problemSupported
Put this strategy to work in your AI chat.
From your deal to your next move.
Fictional Acme deal. Your assistant brings the context; 3xrep builds the strategy.
Uses the notes or connected sources you make available.
View this fictional deal’s context
Acme · proposal · seller-declared stage
“Our approval delays are a problem: the team misses customer deadlines.”
Checks the evidence. Finds the gap.
Builds a strategy for this deal.
- Measured impact
- Unknown
- Buyer problem
- Supported
Priority gap: Measured impact
Explore what the price is being compared with and confirm the cost of the problem before discussing a concession.
You said: “Our approval delays are a problem: the team misses customer deadlines.” When you say the price is too high, are you comparing it with the cost of the problem, an alternative or the available budget?
You review the wording and decide what to send.
All arrows stay visible. No prospect is contacted.
Apply this strategy to your own deal.
Bring your notes or the buyer’s exact words into your assistant. Ask 3xrep to check the evidence, choose a next move and prepare for possible replies. Add the new evidence after your next conversation to review the strategy.
Show the request to copy into your assistant
The buyer said it is too expensive. Use the exact objection and the evidence I provide to distinguish impact, alternatives and funding. Suggest the next question and conditional follow-ups without inventing savings or offering an automatic discount.
Enrollment does not guarantee a selected free-forever place.
The evidence file
- Measured impact Unknown
- No accepted proof for this point.
- Buying authority Unknown
- No accepted proof for this point.
- Decision criteria Unknown
- No accepted proof for this point.
- Internal support Unknown
- No accepted proof for this point.
- Buyer deadline Assumed
- No accepted proof for this point.
- Decision process Assumed
- No accepted proof for this point.
- Buyer problem Supported
“Our approval delays are a problem: the team misses customer deadlines.”
Read the fictional source passages
pain
Rep: What problem does your team face? Julien: Our approval delays are a problem: the team misses customer deadlines.
Your next move
Explore what the price is being compared with and confirm the cost of the problem before discussing a concession.
Before the proposal or contract
Priority gap: Measured impact
A number supplied by the seller afterward does not replace the buyer’s own measure.
Evidence you can use
“Our approval delays are a problem: the team misses customer deadlines.”Buyer problem
How you could ask
You said: “Our approval delays are a problem: the team misses customer deadlines.” When you say the price is too high, are you comparing it with the cost of the problem, an alternative or the available budget?
What would count as progress
The buyer confirms a measure, its source and the consequences of the problem.
If the buyer replies…
Hypothetical replies, not predictions or new evidence. Exploring a reply leaves the evidence file unchanged.
Why these methods appear here
The engine selected MEDDIC + CRAC from the declared buying context and the current objection. Selection and priority are 3xrep rules, not a universal prescription.
The links below show how each open or supported point relates to a method. A method name does not establish a proof.
- Measured impact
- MEDDIC: Metrics · MEDDPICC: Metrics · BEBEDC: Stakes · Cost of inaction: Number
- Buying authority
- MEDDIC: Economic Buyer · MEDDPICC: Economic Buyer · BANT: Authority · BEBEDC: Decision-makers
- Decision criteria
- MEDDIC: Decision criteria
- Internal support
- MEDDIC: Champion · MEDDPICC: Champion
- Buyer deadline
- BANT: Timeline · BEBEDC: Deadline
- Decision process
- MEDDIC: Decision process · MEDDPICC: Decision process
- Buyer problem
- MEDDIC: Identify pain · BANT: Need · BEBEDC: Need
Limits of this next move
- Do not invent a person, number, date or quotation.
- Never send the suggested message automatically.
- Do not offer a discount without a counterpart and a confirmed cost.
Scenario and calculation provenance
Scenario sources are invented for this public example. The diagnostic, evidence states, gaps and actions are calculated by the product engine. Surrounding explanations and reviewed English translations are editorial.
- engine
6d8b03a442f1bdb351c4ddfffe95c54954dab77033ee313492d6aaaf7761e40f- scenario
f0b8f452b7ada9940a74514e57b6a2fc0a86b214876dae9653e2609de1195f22- output
559d1675a31e389c84461ca5973774869fc4f1bf7b7a0b35fe702ed071b93465- presentation
d03ac294ca71d85b0b72080199b53212f3817ba7682a2954eb62483ab62c69c3- rule
pain-to-impact
Where this approach has limits
The scenario measures lost time, not revenue, guaranteed savings or willingness to pay. A budget constraint may remain even when the buyer recognizes value. The next move is a question to test, not a guaranteed way to overcome the objection.