The Sales Objections You Actually Hear, and How to Answer Them

The most useful responses to common sales objections clarify what is blocking the purchase: price, budget, timing, urgency, an incumbent, or procurement. Ask a question that separates the possible causes, then agree on a step that resolves the actual blocker instead of arguing against the objection.

I would take a clear “we cannot fund this” over a friendly “send something over” every time. One lets you make a decision. The other gives you an attachment to name.

Use these common sales objections and responses as conversation starters, not rebuttals to memorize. The suggested wording below is for generic software deals. Adapt it to what the buyer has actually told you.

How do you find the real objection?

Treat the first objection as a description, not a diagnosis. “Too expensive” could mean the buyer lacks funds, doubts the value, or thinks your scope is excessive. Those require different conversations.

Start with:

“What specifically makes this difficult to move forward with?”

Then listen for the missing evidence:

Objection	What you need to establish
Too expensive	The comparison behind the judgment
No budget	Whether funding is unavailable or unallocated
Bad timing	The competing priority or dependency
Happy with an incumbent	Whether a meaningful gap exists
No urgency	What happens if nothing changes
Procurement needs to approve	The remaining decisions and their owners

Ask one question at a time. A discovery call should not feel like the buyer accidentally opened a mortgage application.

Is this a price problem or a funding problem?

These objections sound similar. Price concerns the proposed exchange. Budget concerns access to money. Do not discount before you know which conversation you are having.

“Your price is too high.”

What it can mean: The buyer sees a cheaper alternative, cannot justify the difference, or does not need everything you proposed.

Try:

“What are you comparing it with: another option, what you spend now, or what you expected this to cost?”

Then follow the answer. Against another option, compare the requirements the buyer actually cares about. Against current spending, examine the cost of the current process using buyer-supplied inputs. Against expectations, revisit scope.

Advance with:

“Let’s separate what you need for the initial rollout from what can wait. Then we can price that scope.”

Use when: The buyer challenges price. Reduce scope only if the smaller purchase still solves a useful problem. A cheaper failure is not a good deal.

“We don’t have budget.”

What it can mean: No money was allocated, available funds are committed, or this project has not earned priority.

Try:

“Is there no funding available, or would someone need to approve funding for this project?”

If approval is possible:

“Who makes that decision, and what would they need to see to consider it?”

Build the case with the buyer’s facts: affected workflow, consequences, implementation effort, and desired outcome. Do not send your champion off with a generic ROI slide and call that enablement.

Use when: The buyer names funding as the blocker. If funds are genuinely unavailable, agree on the budget-planning trigger rather than negotiating a price they still cannot pay.

Is timing the blocker, or is there no reason to act?

A timing objection needs a sequence. A lack of urgency needs a reason to change. Another demo solves neither by default.

“This isn’t a good time.”

What it can mean: A competing project takes precedence, the team lacks capacity, or a dependency must finish first.

Try:

“What needs to happen before your team could take this on?”

If they name a dependency:

“Would it help to finish the evaluation before that, or would evaluating now create more work than it saves?”

Use the answer to separate evaluation from implementation. Sometimes the buyer can decide now and deploy later. Sometimes even attending your next meeting is extra work they cannot absorb.

Use when: The buyer identifies a workload or scheduling conflict. Agree on a real trigger for reconnecting, such as completion of an internal project, rather than an arbitrary calendar reminder.

“We can live with the current process.”

What it can mean: The problem exists, but its consequences do not justify the cost and effort of switching.

Try:

“If the process stays as it is, what gets harder, if anything?”

If they identify a consequence, ask who feels it and how they observe it. Then connect the evaluation to that outcome, not your feature list.

If nothing meaningful gets worse, accept the answer. Do not manufacture urgency with a seller deadline.

Use when: The buyer acknowledges friction but sees no reason to act. If they cannot name a consequence worth addressing, move the opportunity out of the active forecast.

How do you respond when they already have a vendor?

“We’re happy with our current provider.”

What it can mean: The incumbent meets their needs, changing would be disruptive, or they do not see a worthwhile difference.

Try:

“What would have to change for you to consider another option?”

If they name a gap:

“Could we test that specific workflow against what you use today, including the effort of switching?”

Keep the evaluation narrow. Agree on the workflow, who will judge it, and what outcome would justify continuing. Ask about migration, retraining, integrations, and contractual commitments before proposing a replacement.

The incumbent does not need to be brilliant. It already has everyone's login details.

Use when: The buyer has a working alternative. Pursue a comparison only when there is an acknowledged gap. If the incumbent meets their requirements, leave them with a clear reason to reconnect if that changes.

How do you handle procurement without losing the deal?

“We need procurement to approve this.”

What it can mean: The buyer supports the purchase, but commercial review, contract terms, vendor setup, or internal approval remains unfinished. It can also mean your contact does not know the buying process.

Try:

“What does procurement need to review, who owns each step, and what can we prepare now?”

Then ask:

“Apart from those approvals, is there anything unresolved about whether the team wants to buy?”

That question separates buying intent from administrative progress. A contract in review is not proof that the business decision is settled.

Build a shared checklist:

• Requirements: Documents, reviews, and approvals needed.
• Owners: The person responsible for each item.
• Dependencies: What must finish before another step starts.
• Open decisions: Anything that could change scope or stop the purchase.

For each meeting, agree on who will do what next. If procurement requests a concession, ask what requirement it addresses before offering one.

Use when: A purchase enters formal review. Work with procurement early where possible. Do not ask your champion to bypass a process they will still have to complete.

FAQ

What are the most common sales objections and responses?

Recurring objections concern price, budget, timing, an incumbent, urgency, and procurement. A useful response asks what specifically blocks the purchase, then proposes a step that addresses that cause. Match the response to the answer, not just the objection’s wording.

How do you handle a price objection without discounting?

Ask what the buyer is comparing your price with. Then examine relevant differences, validate value using their inputs, or reduce scope while preserving the intended outcome. Discounting before that conversation can leave the original concern unresolved.

When should you stop trying to overcome an objection?

Stop when the buyer clearly declines or when discovery shows no meaningful problem, workable funding path, or willingness to evaluate. If the obstacle can change, agree on a specific trigger for reconnecting. Keep the opportunity out of the active forecast until there is a credible path forward.