💥Работа с возражениями ДОРОГО, ПОДУМАЮ, НЕ НАДО, У ДРУГИХ ДЕШЕВЛЕ и пр. Скрипты и техники продаж

Presenter / source

• Vitaly Galitsyn (business sales trainer)

Core business idea: objection handling as a sales process (not “fighting”)

The video argues that in modern sales, objections rarely mean the buyer is close to buying. Instead, objections signal missing perceived value or an attempt to delay/escape negotiations.

Goal: move the deal forward by improving presentation and diagnostic questioning, not by clever “catchphrases.”

“4 myths” framework (as stated)

Myth 1: Objection-handling is the most important stage

• Correction: The key stages are:
  1. Identifying needs
  2. Presenting the product
• Objections should be handled so they are “practically eliminated” before/within the presentation.

Myth 2: An objection means the client is interested

• Correction: An objection often means the client does not see value.

Myth 3: You answer with a “magic phrase” and the client instantly changes their mind

• Correction: Focus on the real underlying situation/reason behind the objection using questions.

Myth 4: Objections must be fought

• Correction: Treat them as diagnosis/research; fighting creates counter-pressure and reduces closing chances.

Objections taxonomy (3 categories)

• Doubt / bargaining objection: “Give me a discount.” (price negotiation attempt)
• Refusal-type objection: the client tries to end interaction (e.g., “it’s expensive” as an exit ramp)
• The approach implies diagnosing which it is within the “refusal/doubt” area.

Playbook / process tactics (actionable techniques)

Universal instruction: pre-handle objections in your presentation

• Write down your top objections and “sew up” the supporting arguments directly in the presentation stage.

Example mapping

• If common objection: “It’s expensive” → include value/benefit justification when presenting.
• If common objection: “I’ll think about it” → include decision-support arguments so the client can decide now.

Technique: “Cut off” bargaining vs diagnose real constraints (“expensive”)

When the objection is “It’s expensive,” it can hide two different situations:

1. Budget mismatch (product is genuinely too expensive for that client)
2. Comparison / benchmarking (client compares you to another offer)

Suggested flow

• First, re-discuss benefits/value and clarify what the cost includes (signal you won’t bargain).
• If they keep repeating “expensive,” ask a clarifying question:
  • “Is it too expensive according to your budget, or are you comparing it with something else?”
• Then branch:
  • If budget: work within that constraint (implied: alternatives/options/adjustments)
  • If comparison: prepare positioning/defense vs the competing product

Technique: handle “I’ll think about it” by completing the “transaction cycle”

Avoid immediate interrogation or a defensive posture. Let the client “exhale.”

Recommended phrases / steps

• Acknowledge decision latency:
  • “Yes, of course, you should think and not rush—let me send you information to email/WhatsApp.”
• Optional follow-up questions after the client relaxes:
  • “How do you like it in general?”
  • “What do you like / what doesn’t suit you?”
• In some strong-relationship cases, ask what blocks closing today:
  • “What prevents you from completing the deal / making the purchase today?”
• For long-cycle deals (e.g., real estate), “thinking is normal”—don’t panic.

Critical timing/wording rule

• Don’t say “I’ll call you back.”
• Instead, say:
  • “Okay—I’ll contact you in a couple of days/tomorrow/the day after tomorrow to learn your decision.”

Technique: handle “I need to consult / get advice”

Use the same logic as “I need to think”: complete the cycle first, then diagnose.

Suggested flow

1. Acknowledge:
   • “Yes, of course—consulting is normal; you should consider different opinions.”
2. After the client relaxes, ask diagnostic truth questions:
   • “Do you like this product yourself?”
   • If yes: “What doubts might your spouse/management have?”
3. In B2B, map the decision process:
   • “What is your decision-making procedure—who participates, and when will the decision be made?”
4. Offer involvement:
   • “Can I get involved at some stage, present the product to your spouse, or communicate with management?”
5. If no concerns: confirm follow-up and later contact to determine the decision.

Technique: handle “We work with another organization / we already have everything”

Especially in B2B:

• Don’t argue—use market monitoring / contingency logic:
  • “No one cancels market monitoring.”
• Offer the proposal for consideration as a fallback: vendors are not a single “egg in one basket.”

Technique: handle technical objections (features/quality gaps)

When objections involve specs or must-have functionality (examples):

• Real estate: missing indoor parking
• B2B: missing a technical component the client emphasizes

Recommended response structure

• Normalize tradeoffs:
  • “There are no perfect systems; you always sacrifice something.”
• Ask the key diagnostic question first:
  • “Why is this so important to you?”
• Then tailor your argumentation based on their stated importance.

Technique: handle guarantees/contract dragging (“what guarantees do you provide?”)

Use a bypass sequence to prevent early derailment:

1. Align on:
   • Cost
   • Payment terms/schedule
2. Only then discuss:
   • guarantees, documents, contract details

Example phrasing

• “Let’s agree on the cost and payment terms first; then I’ll bring documents and show the guarantees.”
• Logic: once payment terms are agreed, guarantees become less adversarial.

Universal question set (two “always works” ideas)

1. Case-closure question (get the missing requirement)

   • “In what case would you make this purchase?”
   • or “What should be true for us to conclude the agreement?”
   • The client specifies what’s required; you satisfy it.

2. Product value diagnostic

   • If value is missing:
     • “What can we do to make you see the value?”
     • or “Why don’t you see the value for yourself?”
   • Use their answers to rebuild your presentation accordingly.

Metrics / KPIs / targets

• No specific KPIs, revenue targets, CAC/LTV/churn figures, or timelines are provided.
• Timing guidance is limited to follow-up suggestions like:
  • “tomorrow / the day after tomorrow / in a couple of days” for “I’ll think about it.”

Concrete examples mentioned

• Real estate: technical objection example—missing indoor parking
• B2B: technical gap objections, handled via:
  • decision-making process mapping
  • offering to communicate with management/spouse
• Long sales cycles: referenced idea (“bit-killing” segment)—allow clients to think rather than forcing a call immediately.

“Surprise” / offer at end

If viewers comment and register via link, the presenter offers:

• Book: “90 answers to client objections”
• Includes “more than 12 checklists” for sales stages

Summary of key actionable recommendations (condensed)

• Pre-load objection answers into your presentation (don’t rely on reactive “catchphrases”).
• Diagnose objections by underlying reason:
  • “Expensive” → determine budget vs comparison
  • “Think about it” → let the client exit defensively, then return on a scheduled follow-up
  • “Consult others” → identify who doubts and offer to involve yourself
  • “We have a vendor” → use market monitoring / contingency framing
  • Technical gaps → ask why it matters, then tailor the argument
  • Guarantees/contract dragging → bypass until cost/payment terms are aligned
• Use universal closure questions to extract what must be true to proceed.

Presenters/sources: Vitaly Galitsyn.