The Objection Handling Framework for Founder-Led Sales Teams

Most objection-handling training I've seen is a laminated sheet of rebuttals nobody wrote from a real conversation. "When they say X, say Y." It reads well in a training deck and falls apart the second a real prospect says something slightly different than the script anticipated — which is every single time, because real objections aren't lines, they're moments loaded with specific context the rep has to read.

The fix isn't a better script. It's a system: know the objections your team actually hears, understand the real reason behind each one, and drill the underlying reframe until a rep doesn't have to think about it mid-call. Here are the ten objections that show up over and over for founder-led teams — the ones I'd build a training program around before touching anything else.

The 10 objections worth building a system around

1. "Send me some information" / "Just email me"

This is the single most misread objection in sales. Reps hear it as a request and comply — they send the deck, and the deal goes quiet forever. It's rarely a genuine information request. It's the lowest-friction way for a prospect to end a call without saying no to your face. The reframe isn't a clever line, it's a question: "Happy to — what specifically would be most useful in there, so I don't just send the generic deck?" That single follow-up either surfaces a real objection hiding underneath, or it exposes that there wasn't one and the prospect has to engage.

2. "We already have a vendor and we're happy"

This one triggers a defensive reflex — reps immediately start trashing the competitor or listing features. Don't. The prospect just told you switching cost feels high and status quo feels safe. The reframe is curiosity, not comparison: "Makes sense — what would have to be true for you to even consider a change?" If the answer is "nothing," you've saved everyone time. If it's not nothing, you've found the actual gap.

3. "It's too expensive"

Price objections are almost never about the number in isolation — they're about the number relative to a value the prospect hasn't fully connected yet. Before defending price, reps need to ask what it's being compared to: "Expensive relative to what?" Sometimes it's a real budget ceiling. More often it's that the cost of the current problem was never made concrete.

4. "I need to think about it"

A close cousin of "send me an email" — a polite exit, not a real request for time. The useful move is to make the "thinking" specific instead of open-ended: "Totally fair — what's the piece you're least sure about?" Vague hesitation becomes a nameable concern, which is something a rep can actually work with.

5. "I need to run this by my partner / my boss"

Legitimate more often than the others on this list — but it also gets used as a stall by a prospect who is the actual decision-maker and just doesn't want to commit. The reframe is to get in the room, not around it: "Would it help if I joined that conversation, or gave you something specific to bring to them?"

6. "We tried something like this before and it didn't work"

This objection carries real information — a scar from a bad past experience — and reps who dismiss it lose credibility instantly. The move is to get specific about what "didn't work" actually meant: was it the tool, the rollout, or the team? Understanding the failure mode is how you show you're not the same mistake twice.

7. "Can you do anything on price?"

Not really an objection — a negotiation opener. Reps who cave immediately teach the prospect that your price is soft, which erodes trust in everything else you say. The reframe is to trade, not concede: "I can look at that — what would you be able to move on in return, contract length, start date, seats?"

8. "Now isn't a good time"

Timing objections are often a proxy for priority, not calendar availability. The useful question isn't "when's better?" — it's "what would need to change for this to become a priority?" That answer tells you whether you're dealing with a real timing constraint or a soft no.

9. "How is this different from [competitor]?"

A gift, not a threat — the prospect is actively comparing you, which means you're still in the deal. The mistake is answering with a feature list. The reframe is to answer with the specific problem you solve that the alternative doesn't, tied to what the prospect already told you they care about.

10. "I don't really have time for a full demo/call"

Often a test of whether you can respect their time, not a hard no. Reps who push for the full 30 minutes anyway lose credibility before they've said anything of value. The reframe: offer the version that fits — "Give me 10 minutes on the one thing that's relevant to what you told me, and if it's not useful we're done."

Why the reframe matters more than the rebuttal

Notice none of the above are scripts. They're questions and framings that require the rep to actually listen to what comes back and adjust. That's the difference between "handling" an objection and reciting a rebuttal at it. A rep who's memorized "when they say too expensive, say X" will freeze the moment a prospect says something adjacent but not identical — which happens constantly, because real conversations don't follow scripts.

This is also why objection-handling training built on generic internet lists underperforms training built on your own team's actual calls. Your prospects don't object in the abstract — they object in your market, at your price point, against your specific competitors. Call intelligence that extracts the exact objections and phrasing from your own recorded calls, along with a Deal Break Analysis of which objections actually correlated with lost deals, tells you which of the ten above to prioritize first. For most founder-led teams we work with, it's not evenly distributed — one or two objections (usually price and "we have a vendor") account for the majority of stalled pipeline.

Drilling it in

Knowing the reframe intellectually and deploying it under pressure, live, with a real prospect pushing back, are different skills. The gap between them is repetition — the same objection, ten or fifteen times, until the reframe comes out without the rep having to consciously retrieve it. That's the entire logic behind our approach to objection-handling practice: AI buyer personas built from your team's real deals push back with the actual phrasing and actual pressure your reps will face, not a sanitized version. We wrote about the drill structure that makes this stick in how to run roleplay practice reps don't hate — the short version is: one objection at a time, short sessions, high repetition.

The bottom line

A laminated script gets abandoned the first time a prospect says something it didn't anticipate. A system built on your team's real objections, with reframes practiced until they're instinct, holds up under the actual chaos of a live sales call. Start with the ten above, pull your own team's frequency data if you have it, and build the drill schedule around whichever two or three are actually costing you the most deals.