Handle objections in discovery

Respond to the common discovery objections of budget, timing, authority and competition with a five-step pattern that keeps the conversation honest and ends with a clear next step.

Treat the objection as a question

An objection is rarely a final no. It is usually a worry in the shape of a statement. "It is too expensive" can mean "I cannot see the value yet", "I have no budget this year", or "I need to look careful in front of my boss". Each needs a different response, so your first job is to find out which one you have.

Use a five-step pattern

Use the same order every time:

  1. Pause and let them finish. Do not start answering halfway.
  2. Acknowledge: "That is a fair concern."
  3. Clarify with a question: "What makes you say that?"
  4. Answer the real concern with one fact or a short example.
  5. Check and move on: "Does that change how you see it?"

Step three is the one most people skip. Without it you answer a worry nobody had.

Budget: "We do not have the budget"

Find out which budget they mean. Ask: "Is it that there is no money for this at all, or that the problem does not rank high enough yet?" If there is no money, ask where the cost of the problem sits today. If they cannot say, the pain is low and you have a qualification issue, not an objection. See Prepare qualifying questions.

Do not offer a discount in a discovery call. You have not yet shown value, so a discount only teaches them to ask for one.

Timing: "Not now, maybe next quarter"

Ask what will be different next quarter. A real reason, such as a budget cycle or a product launch, gives you a date to agree on. A vague answer usually means low priority. Say: "Shall we agree a date to speak again, and what would need to be true by then?" Put the date in the calendar before you hang up.

Authority: "I need to check with my boss"

Do not try to avoid the boss. Ask who else will be involved, what they care about, and whether the person you are speaking to would recommend you. Offer a short summary they can forward, and suggest a call with all of them. The person on the call rarely signs alone.

Information: "Send me some information"

This often means "I want to end this call politely". Ask: "Happy to. What would you want to see in it to decide whether it is worth a next call?" Then agree a specific time to discuss it. If they will not name a time, treat the deal as cold.

Competition: "We already use someone" or "we will do it ourselves"

Do not criticise the other option. Ask what works well and what they would change. The gaps they name are your opening. For "we will do it ourselves", ask what it costs in hours each week and who does it. Many internal solutions work only while one person stays.

Log every objection

After each call, record the objection, the real concern behind it, and what happened next. A column in HubSpot or a short sheet will do. If you record calls with Gong or Fireflies.ai, tag the moments. After 20 calls you will see the same five patterns, which feed Train on common objection patterns.

Common mistakes

  • Answering before you understand the worry.
  • Rebutting with features.
  • Offering a discount to end the discomfort.
  • Accepting "send me information" with no follow-up.
  • Treating every objection as a sales problem when some are qualification problems.
  • Forgetting to write the objections down.

How you know it works

Fewer calls end with a vague "we will think about it". More end with a booked next step, or a clear no that you can log. You can name the top three objections of the month, and your answers to them improve in the next review of call recordings.

Tools in this play

Some links are affiliate links: we may earn a commission at no cost to you. It never decides a ranking. How we work with partners