Handle the 4 canonical objections

What you’ll do

You'll recognize which of the 4 canonical objections you're hearing. Acknowledge it before you argue. Reframe in a way that opens the conversation back up. Offer something asymmetric — small for you, big for them. When fit is the objection, go back to discovery (it's usually your fault). When authority is the objection, multi-thread immediately. And when objections cascade, disqualify gracefully — they'll respect you more for it.

The steps

1. 01
   Recognize which of the 4 objections you're hearing

   Live, on the call

   Almost every B2B sales objection collapses into one of four categories: timing ('not right now'), budget ('we can't afford this'), authority ('I'd need to check with someone'), or fit ('this isn't quite what we need'). Each has a different cause and a different response. Misdiagnose the objection and you'll fix the wrong thing.

   • Timing: 'we're in the middle of [other project],' 'maybe next quarter,' 'too much going on right now.' Usually a priority signal, not a calendar signal.
   • Budget: 'we don't have budget,' 'too expensive,' 'we just spent on [other tool].' Often a value-perception signal, not a literal budget signal.
   • Authority: 'I'd need to check with my CTO,' 'we'd need legal/security/IT to weigh in.' Sometimes real, often a soft pass dressed up.
   • Fit: 'we already use [competitor],' 'we built this internally,' 'this doesn't quite match our workflow.' Almost always a discovery gap — you didn't surface the right problem.

   ↳ Reference: Objection handling reference
2. 02
   Acknowledge the objection — never argue with it

   First response · 5 seconds

   The instinct when you hear an objection is to immediately rebut. Don't. Acknowledging the objection — even when you disagree — disarms the prospect's defensiveness and earns you the right to keep talking. 'That makes sense, given where you are in the quarter' beats 'but here's why now is the right time' by a wide margin.

   • Acknowledgment language: 'That makes sense,' 'I get it,' 'I'd be wondering the same thing in your position.'
   • Then ask a question to surface the real driver: 'Help me understand — what would make this a priority?' / 'When you say it's too expensive, what number would feel right?'
   • Resist the temptation to explain or defend before you understand the real objection underneath the stated one.

   ↳ Reference: Discovery call architecture
3. 03
   Reframe the objection in a way that opens it back up

   Second response · per objection

   After acknowledging, reframe. The goal of reframing isn't to argue them out of their objection — it's to give them a different way to think about the problem that makes your solution feel more relevant. Each objection type has a specific reframe that works.

   • Timing reframe: 'Totally understand. Most of our customers had the same thing — they thought next quarter would be better, then realized the problem compounded by then. Worth 15 min to look at whether starting smaller now beats waiting?'
   • Budget reframe: 'I hear you on budget. If we could quantify $X in value over 12 months, would that change the conversation? Let's walk through the math.'
   • Authority reframe: 'That makes sense. What would help you take this to your CTO? Want me to prep a 1-pager that lays out the case?'
   • Fit reframe: 'Got it. Walk me through what specifically isn't a fit — is it the workflow, the integration, the pricing model?' This usually surfaces the real gap, which is rarely what they said first.

   ↳ Reference: Multi-thread (for authority objections)
4. 04
   Offer something asymmetric — small commitment for you, big value for them

   Third response · per objection

   After acknowledging and reframing, propose an asymmetric next step. Something that costs you little but gives them a lot — a custom ROI analysis, a 14-day proof-of-concept, a sandbox demo with their data, an intro to a peer customer. The asymmetry breaks the stalled conversation by giving them a low-risk way to take one more step.

   • Timing offers: 'Let's do a 14-day pilot with just one team — if it doesn't deliver, we walk.'
   • Budget offers: 'How about a 90-day annual contract at [discounted price] with a money-back clause if you don't see [specific outcome]?'
   • Authority offers: 'I'll prep the 1-pager. Want me to also jump on a call with your CTO directly?'
   • Fit offers: 'Let me show you exactly how [the specific workflow gap] could work in a 20-min sandbox demo — no commitment.'
   • The asymmetric offer earns the next step. If they refuse even the small ask, you're not losing a real deal — you're just losing a polite-but-uninterested conversation.

   ↳ Reference: Proposal design
5. 05
   When fit is the objection, go back to discovery — it's usually your fault

   After fit objection

   Fit objections almost always mean you didn't fully understand the prospect's problem in discovery. Don't try to talk them into the fit — go back to discovery questions. 'Walk me through how you're handling this today.' / 'What would have to be true for this to be a fit?' Most fit objections turn into deals when you surface the actual problem you missed the first time.

   • Bad fit response: 'Actually, we do handle that, here's how...' (you're arguing, not learning).
   • Good fit response: 'That's useful — help me understand where the gap is. Is it the workflow, the integration, the pricing structure, or something else?'
   • If they push back further, ask the kill question: 'Got it. What would have to change about our product for this to be a fit?' Their answer tells you whether the gap is real or whether they're soft-passing.

   ↳ Reference: Customer discovery playbook
6. 06
   When 'I need to check with [X]' comes up, multi-thread immediately

   After authority objection

   An authority objection is usually a multi-thread opportunity, not a soft pass. 'I'd need to check with my CTO' is the moment to ghost-write the introduction email for your champion. Don't let them go check internally without ammunition — they'll come back two weeks later with 'my CTO didn't see the value.'

   • Ghost-write the intro: 'Happy to give you a draft email you can send to your CTO that summarizes what we've discussed. Want me to send that over?'
   • Offer to jump on the call directly: 'Or, if it's easier, I'm happy to hop on a 20-min call with your CTO to walk through the technical piece.'
   • Provide the 1-pager: ROI in their company's numbers, specific case study from a similar account, answers to the 3-5 questions you know the CTO will ask.
   • Track this thread. The deals that die on authority objections almost always die because the founder went silent after sending materials. Check in every 5-7 days.

   ↳ Reference: Multi-thread playbook
7. 07
   Know when to disqualify and walk away gracefully

   When objections cascade

   Some prospects produce a cascade of objections — timing, then budget, then fit, then authority. Each individually feels like something you can address. The pattern means they're soft-passing politely. After 2-3 cascaded objections, disqualify gracefully: 'Based on what I'm hearing, I'm not sure this is the right time. Happy to reconnect in 6 months when things have settled.' You'll get respect, and sometimes a referral.

   • A pattern of weak objections that keep shifting is a signal that the real objection isn't being said out loud. The real one is usually 'I'm not actually that interested' — and you'll never close that with more arguments.
   • Graceful disqualification: 'I hear you on all of this. Want me to circle back in [3-6 months] when [the timing concern they raised] has resolved?'
   • Disqualified prospects sometimes come back. Burned prospects (who you over-pushed) never do.
   • Track every disqualification with the reason. Patterns across 10-20 calls tell you whether you have an ICP problem or a pitch problem.

   ↳ Reference: Reply triage and disqualification

What goes wrong

The failure modes that catch most founders.

• You argue with the objection instead of acknowledging it

  The instinct is to immediately rebut. Don't. 'But here's why now is the right time' triggers defensiveness. 'That makes sense' opens the conversation. Always acknowledge before you reframe.

• You misdiagnose the objection

  Budget objections are often value-perception problems. Fit objections are often discovery gaps. Timing objections are often priority signals. If you fix the stated objection instead of the real one, you don't advance the deal.

• You skip the asymmetric offer

  Without a low-friction next step, the prospect has nowhere to go. The asymmetric offer (small commitment for you, big value for them) is what re-opens a stalled conversation. Without it, 'let me think about it' becomes the permanent state.

• You let authority objections die in silence

  'Let me check with my CTO' often becomes the death of a deal because the prospect goes silent and the founder doesn't push. Ghost-write the email, offer the 1-pager, ask to join the internal call. Then follow up every 5-7 days.

• You don't disqualify when objections cascade

  A cascade of objections (timing, budget, fit, authority) usually means the prospect is soft-passing. Continuing to argue against each one burns goodwill. Disqualify gracefully — the relationship is more valuable than the dead deal.

• You take fit objections at face value

  Fit objections almost always mean you missed something in discovery. 'This doesn't quite match our workflow' usually means you didn't understand the workflow. Go back to discovery questions, not feature explanations.

Want the technical depth?

The chapters with the full reference detail.

• → Objection handling reference— The 4 canonical objections in depth
• → Discovery call playbook— Where you prevent objections by understanding the problem
• → Multi-thread playbook— What to do when authority objections come up
• → Proposal design— Where asymmetric offers get structured
• → Customer discovery playbook— Discovery prevents most objections from emerging