3.2Handle objections (methods)
The essentials in 30 seconds
- LACE: Listen fully, Acknowledge/clarify (reformulate + yes), Counter (targeted proof), Engage (“does that answer it? Shall we move on?”).
- 4 answers: proof, customer story, framed concession (give-and-take), deferral of minors.
- Screens: name them kindly (“is that the real point?”) + silence: 80% collapse.
Running mini-case — Younes handles the fear of “complicated”
Younes's customer adds: “your tool looks complicated for my team”. Younes listens, reformulates (“if I understand: fear of learning time, right?”), gets a yes, answers with proof (2-h training + 1-day onboarding at a neighbouring customer) then re-engages: “does that answer it? Shall we schedule Thursday's demo?”. The objection becomes a step forward.
Sequel of case 3.1 — Younes moves from welcoming to LACE handling.
1. The 4-step method: LACE
Listen (fully), Acknowledge/clarify (reformulate + get a yes), Counter (targeted proof, not a plea), Engage (“does that answer it? Shall we move on?”). Without the re-engage, a handled objection serves nothing: verify and advance.
Never contradict head-on: prefer partial agreement (“I understand, and precisely…”). Handling means lifting a brake together, not being right against the customer.
2. Stock answers and screens
Proof (number, demo, case), story (“a customer thought the same — here's what happened”), framed concession (“if I do X, do you sign Thursday?”), deferral (“let's revisit after the demo?” for minors).
Screen objections: “To be frank: is that the real point, or is there something else?” + silence: 80% of screens collapse. Handling a screen with proof means answering beside the point.
🔎 Concrete example — Objection handled end to end
Younes chains the 4 steps with no pleading.
“Your tool is complicated.” → listen
→ “If I understand: fear of team learning time, right?” yes
→ proof: “2-h training + 1-day onboarding (neighbouring customer)”
→ “Does that answer it? Shall we schedule Thursday's demo?” yesReading: reformulation + proof + re-engage = progress.
Lesson: concessions only against commitment.
Section vocabulary
- Objection handling
- A method to lift a brake: dig, reformulate, answer, confirm.
Simple example: Younes chains LACE on the fear of “complicated”.
What it is not: answering fast with no digging and no check.
Reflex: check the 4 steps after each objection.
- Digging
- Getting the objection clarified with questions to grasp its true nature before answering.
Simple example: “When you say complicated, for whom, and at which moment?”
What it is not: pleading 10 minutes without getting anything clarified.
Reflex: one question before any answer.
- Partial agreement
- A technique of acknowledging the customer's point before answering (“I understand, and precisely…”), to avoid flinching.
Simple example: “I understand the concern, and precisely the training lasts 2 h.”
What it is not: contradicting head-on (“that's wrong”).
Reflex: start with “I understand” before “precisely”.
- Proof
- A concrete element (testimonial, number, guarantee, trial) backing the answer to an objection.
Simple example: The neighbouring customer operational in 1 day after 2 h of training.
What it is not: a claim with no fact (“it's very simple”).
Reflex: every answer backed by a verifiable fact.
- Confirmation
- Checking that the objection is truly lifted before moving on (“does that answer your concern?”).
Simple example: “Does that answer it? Shall we schedule Thursday's demo?”
What it is not: moving on without checking the brake is lifted.
Reflex: always re-engage after answering.
In practice — Handle objections with method
- Dig: get the objection clarified with questions to pin down its true nature.
- Reformulate to show you understood (“if I understand, your concern is…”).
- Answer with the argument, proof or solution lifting the brake — no head-on contradiction (partial agreement).
- Confirm the objection is lifted (“does that answer your concern?”) before moving on.
Ready-to-say script — LACE in 1 minute
“If I understand, your concern is the team learning time, right? I understand, and precisely: 2-h training and 1-day onboarding at a customer like you. Does that answer your point? If so, shall we schedule Thursday's demo?”
Say after full listening; wait for the reformulation yes before the proof.
Copy-paste template — LACE sheet
OBJECTION (customer's words): _______________
DUG (question asked): _______________
REFORMULATION + YES: _______________
ANSWER (proof / story / deferral): _______________
RE-ENGAGE (“does that answer it? Shall we…?”): _______________SMB / freelancer
Prepare 3 reusable proofs (number, case, guarantee) for recurring objections.
SME Algiers
Younes cites a neighbouring customer in the same industry: local proof reassures more than a distant case.
Services
Replace the product demo with a framed trial or pilot step to prove without overpromising.
Beginner
Defer minors (“let's revisit after the demo?”) instead of handling everything at once.
✓ Best practices
- Apply full LACE, re-engage included.
- Answer with proof or story, not pleading.
- Kindly name screens before proving.
✗ Common pitfalls
- 10-minute pleading with no proof.
- Handling with no re-engage: it falls back.
- Conceding with no counterpart.
Key takeaways
- Method: dig (get clarified) → reformulate → answer (with proof) → confirm (check it is lifted).
- Never contradict head-on: prefer partial agreement (“I understand, and precisely…”).
- Lean on proof (testimonials, numbers, guarantees) rather than bare claims.
- Handling an objection = lifting a brake together, not “being right” against the customer.
48h challenge — apply tomorrow
Handle 1 real objection in full LACE (re-engage included) with the template above. Note the answer to the re-engage.
- I can cite the 4 LACE steps without hesitating.
- I can answer with proof and name a screen.
- I handled 1 objection with re-engage.
Frequently asked questions
Should you answer an objection immediately?
No: answering too fast risks handling the wrong objection and sounding self-justifying. Welcome, dig, reformulate, then answer with proof, and finally confirm: this slight delay shows listening and makes the answer more effective.
What to do facing an objection you have no good answer to?
Don't bluff: acknowledge a real limit while putting it in perspective, or promise a precise answer (“I'll check and come back tomorrow”). Digging sometimes reveals a less blocking brake; noting the objection prepares next time.
Younes answered with proof. What must he do next?