Objections are information, not attacks
On this page
Sales Academy · interview preparation for AE / account manager / BD / presales roles in UK life sciences and health tech. All companies and people in the examples are fictional unless stated otherwise.
This is the pointy end of the sale — the part most people picture when they hear the word "selling", and the part new sellers fear most. The fear is misplaced: handling objections, negotiating and closing are learnable processes, not personality traits.
This module builds each one from the ground up — no sales background assumed — and they are also the most role-played topics in AE interviews, so everything here does double duty as interview preparation.
Quick vocabulary:
- a prospect is a potential customer
- a deal or opportunity is a specific potential sale
- pipeline is all your live opportunities
- an AE (Account Executive) owns deals to signature and carries a quota (a revenue target)
- presales (Solutions Consultant / Sales Engineer) owns demos, proof-of-concept evaluations and technical objections
- discovery is the questioning phase where you learn the prospect's problems and buying process
- a champion is the insider who sells on your behalf when you're not in the room
What you'll learn
- Why objections are usually buying signals; surface vs root objections
- A repeatable process (LAER/LAARC) for handling any objection without scripts
- Worked handling for the nine objections you'll hear constantly in NHS, clinical AI and lab-software sales
- Stalls vs objections, and objections vs conditions
- Negotiation for AEs: give-get trading, anchoring, discount hygiene, procurement tactics and counters, BATNA, the Chris Voss essentials
- Closing as the natural end of good process: asking for the business, trial closes, next-step discipline, mutual action plans, the break-up email
- How to lose well — and why "no decision" is your biggest competitor
1. Objections are information, not attacks
An objection is any stated concern or obstacle against moving forward — "too expensive", "clinicians won't use it". New salespeople hear rejection; experienced ones hear the most useful data in the conversation:
- An objection means engagement. People don't argue with things they've dismissed. A buyer pushing back on price has imagined owning your product and hit a snag — which is why objections are buying signals (behaviour indicating genuine purchase interest). Vague pleasantness is a worse sign than pushback.
- An objection tells you what stands between you and the deal. Without it, you're guessing.
- Objections reveal how the buyer thinks — what they compare you against, what burned them before, whose approval they fear.
Surface vs root: the objection stated is often not the objection meant. The surface objection is the words said; the root objection is the real concern underneath.
"Too expensive" might mean:
- I don't yet believe the value
- I can't get this approved
- championing this is a career risk
- someone quoted less
Each root needs a different response — which is why reacting to the surface words (say, instantly discounting) fails.
Voice from the fieldAs Zig Ziglar taught for decades, every sale has five basic obstacles — no need, no money, no hurry, no desire, no trust. Half a century on it remains the best map of root objections there is: almost anything a buyer says to you compresses to one of the five, and each one calls for a different response.
2. The process: listen → acknowledge → explore → respond → confirm
Objection handling is a process, not scripts. Scripts answer the surface; process finds the root. The steps:
- Listen — fully, without interrupting or visibly loading your counter-argument. Pause a beat; the pause signals seriousness.
- Acknowledge — show the concern is legitimate: "Fair challenge — imaging budgets are brutal this year." Acknowledging isn't agreeing; it lowers defences. People can't hear your answer while braced for a fight.
- Explore / isolate — ask questions until you find the root ("expensive compared to what?"), then isolate it: "If we solved the pricing question, is there anything else that would stop you going ahead?" Isolation prevents the pattern where you resolve one objection and a fresh one instantly appears — a sign the stated one was never real.
- Respond — only now, and only to the root you found: evidence, a reframe, a customer story, or an honest "we don't do that; here's the workaround".
- Confirm — "Does that deal with it, or is some of it still live?" Skipping this is the commonest failure: the objection silently survives and kills the deal in a meeting you're not in.
Two named variants for interview vocabulary: LAER (Listen, Acknowledge, Explore, Respond — Carew International) and LAARC (Listen, Acknowledge, Assess, Respond, Confirm). The acronym doesn't matter; the sequence does, and it compresses to one rule: never respond to an objection you haven't explored.
Voice from the field"In every sales conversation, the person who exerts the greatest amount of emotional control has the highest probability of getting the outcome they desire."
— Jeb Blount, Objections (2018)
3. Stalls, objections and conditions
Three different things get called "objections":
- A genuine objection is specific and contentful ("your price is 40% above the incumbent's renewal"). Work it with LAARC.
- A stall is delay without content ("call me next quarter", "let me think about it"). There's nothing to answer — probe it into either an objection or a truth: "Of course — is it timing, or is something about the approach not landing?" A stall surviving two gentle probes usually means the deal isn't qualified (no real pain, power or urgency); downgrade it rather than chase it.
- A condition is a fact you can't talk past: "purchases over £30k go to competitive tender", "we're contracted until 2028", "regulation requires certification you don't hold". You don't overcome conditions — you meet them, plan around them, or qualify out (deliberately withdraw to spend the time on winnable deals). Arguing with a condition wastes months and looks naive.
The tell: objections come with specifics and energy; stalls are vague and polite; conditions are stated flatly as facts about how their world works.