Objection Handling — Introduction

Objection vs. pretext

An objection is grounded resistance — the person gives a concrete reason. A pretext is a defense formula without argument ("no interest", "no need"). The distinction decides how you continue.

• Objection = with argument ("too expensive", "no time now", "no fitting solution").
• Pretext = without argument ("no interest", "not for us").
• The beer analogy: "I get headaches from light beer" is an objection (researchable). "I generally don't like beer" is a pretext.

Why objections are good

Objections are a gift. They show that the person actually listened and cared enough to give a reason. That's the stage where every good objection handling happens.

• Whoever voices an objection has listened — that's more than most calls deliver.
• Objections open conversations, they don't close them.
• A grounded no teaches more than a hollow yes to a meeting.

The most common objections

"No need", "no interest", "no time", "please don't call again" — the classics every BDR hears daily. Besides these, project-specific objections related to the industry or product.

• Generic classics: no need, no interest, no time.
• Project-specific objections — e.g. "we already have that", "doesn't fit our sales cycle".
• Some objections are actually pretexts — the right question reveals what really sits behind them.

Active listening

The most important step. Not just hearing, but understanding. From what the person says, generate a fitting follow-up question — not a generic script question.

• Listening = grasping meaning, not just registering words.
• The follow-up question grows out of the previous answer, not from the script.
• Whoever hears "no need" and answers with a software question hasn't listened.

Empathy as a tool

When the contact is stressed or in a meeting, a 15-minute pitch is the wrong move. Show understanding, agree on a follow-up time, call later — the person feels respected, not hunted.

• Spot the contact's stress — don't barrel through.
• Understanding message: "I respect your time, I'll call later."
• Someone who feels respected answers differently next time.

Asking the right question

Pitching at an objection is the most common trap. Instead: an open question that fits the answer and lets the person respond honestly.

• Pull back the pitch, ask the question — dialogue starts here.
• Good questions feel relevant to the contact — not scripted.
• A fitting follow-up signals "you matter to me" — and opens the door.

Script vs. dialogue

Whoever follows the script loses the other person. Scripts give safety, but objection handling happens in dialogue — not in pre-written lines. Experience and project knowledge overwrite the script.

• Script = safety net, not screenplay.
• With experience, the script gets left consciously.
• Project knowledge + empathy = real conversation.

Handling a pretext

When the person really doesn't want to talk, pressure isn't worth it. Reflect — was it the wrong day, the wrong script, the wrong person? Try again in a few months with a better mindset.

• Reflection: was I the reason, the market, or the person's daily mood?
• Pretext ≠ final no — in a few months the situation often looks different.
• Franjo's own example: after a clear pretext, called again months later and booked a meeting.

Persistence without intrusion

Don't lose courage, but don't hunt. A door is not closed forever after a no — it's just closed now. With smart intervals and an honest attitude, it opens again.

• Six calls isn't too many if the tone is right.
• Threatening reminders ("you promised…") are counterproductive.
• Whoever stays respectfully in touch gets perceived differently in the decisive call.

Backing off as a technique

Sometimes the best is a short email and a new call two weeks later. Give space, withdraw, return with fresh preparation. The other person doesn't feel chased.

• Short summary email as "anchor" for the next call.
• Pause between two and four weeks, depending on industry and situation.
• The hunt continues — but respectfully, not intrusively.

Building trust

Closing without relationship building is gambling. Whoever generates no trust can only hope the need happens to be acute. Whoever builds relationship can also close — the two are not opposites.

• Trust beats any pitch technique — the person must know who they're talking to.
• "We're not looking for someone who builds relationships, we want a closer" is a false dichotomy.
• Relationship + honest promise = sustainable deal.

Franjo's favorite technique

The positive question. Instead of frontally attacking an objection, ask a question that lets the contact answer honestly. "Would it be helpful for you if we discussed this in a meeting?"

• Positive question opens — frontal counter-arguments close.
• Positioning a meeting as a "helping offer" is low-threshold.
• Works because the person feels supported, not attacked.

The hypothetical "If budget weren't a thing…"

On "no budget": open a hypothetical world. "Imagine budget weren't the issue — would it then be interesting for you?" That separates real disinterest from a pure budget block.

• Hypothesis isolates the budget problem from the product match.
• Yes answer opens the door for budget workarounds and a later call.
• No answer shows that "no budget" was a pretext — the product didn't fit anyway.

Knowledge as a prerequisite

Without project knowledge, objection handling is gambling. Whoever doesn't know the product can't react to specific objections. Briefings, research, and partner communication are the base.

• Project knowledge + empathy + listening = the working trio.
• Generic answers to specific objections only produce frustration.
• Best-practice exchange with partner and colleagues is mandatory.

Game Time — objection speedrun

Five classics in 30 seconds. Franjo's quick answers: "Too expensive" → take the budget out hypothetically. "No time" → understanding + new appointment. "Can't transfer" → offer email. "No interest" → ask about negative past experiences. "No need" → solution already implemented or development potential open?

• Too expensive → "If budget weren't a thing, would it be interesting?"
• No time → "No problem, when does it work for you better?"
• Can't transfer → "Understood — can I send you an email?"
• No interest → "Is that because of past experiences with similar providers?"
• No need → "Have you already implemented this solution or is there still development potential?"

What's the difference between an objection and a pretext?

An objection is grounded resistance with a concrete argument ("too expensive", "no time now"). A pretext is a defense formula without argument ("no need", "no interest"). Both need different answers.

Which three tools are decisive for good objection handling?

Active listening (not just hearing, but understanding), empathy (respecting the contact's situation and tone), and the right question at the right moment — not a script question, but one that fits the answer.

When is a second attempt worth it after a pretext?

After a pretext, a second attempt is worth it after weeks or months. The situation may have changed, and the person often doesn't remember the first call — you start fresh.

How do you respond to "too expensive" in B2B outbound?

The hypothetical question: "If budget weren't a thing, would it be interesting?" That separates real disinterest from a pure budget block. A yes opens workarounds; a no shows "too expensive" was a pretext.

Does a strict sales script work for objection handling?

No. Scripts give safety, but objection handling happens in dialogue. Whoever follows the script instead of listening loses the person. Script as foundation; experience and project knowledge overwrite it in conversation.