# Mid-Discovery Objection Scripts: Keep or Kill the Call > Word-for-word scripts for the 8 objections that most commonly derail a discovery call before qualification is complete, with a one-line diagnosis and a binary keep-or-kill decision rule for each. Print it, put it next to your phone, and stop losing calls you could have saved. Free cheat sheet for sales reps. Topic: [Discovery & Qualification](https://www.peerlab.ai/library/topic/discovery-qualification/). Published by PeerLab in the [Sales Enablement Resource Library](https://www.peerlab.ai/library/). Source: https://www.peerlab.ai/library/mid-discovery-objection-scripts-keep-or-kill/ ## How to use it Print this sheet and keep it visible during every discovery call. When an objection lands, find it, read the diagnosis first to know what you are actually dealing with, then deliver the script. Apply the keep-or-kill rule at the end of your response: if the threshold is not met, end the call cleanly rather than grinding through a dead conversation. ## What's inside - 8 mid-discovery objection scripts, each word-for-word with bracketed fill-ins - One-line diagnosis for each objection: stall, brush-off, or genuine blocker - Binary keep-or-kill decision rule with a specific threshold for every objection - A short note on when NOT to fight the objection - A timing note explaining why mid-discovery objections need different handling than cold-call or late-stage objections - A quick-reference summary table covering all 8 objections, their diagnosis type, and their keep-or-kill threshold ## Why mid-discovery is its own category A cold-call objection lands before you have any information. A late-stage objection lands after you have everything. A mid-discovery objection lands in between: you know enough to be interested but not enough to evaluate whether this is real. That gap is the problem. If you fight too hard, you waste time on a dead end. If you fold too fast, you lose a deal that was actually there. The scripts below are built for that specific moment. Each one is designed to get one more useful data point, not to "handle" the objection in the traditional sense. The keep-or-kill rule tells you what to do with whatever comes back. --- ## The 8 Objections ### 1. "We already have something in place." **Diagnosis:** Stall. Almost always means "I haven't thought about whether what we have is working." Rarely a genuine blocker at this stage. **Script:** "That makes sense, and I'm not here to pull you away from something that's working. Can I ask: when did you last properly review whether [current solution] is still the right fit for where the business is now? I'm asking because [specific trigger that prompted this call, e.g. 'your team has grown by 40% in 18 months'] tends to change what good looks like." **Keep-or-kill rule:** Keep if they engage with the review question or acknowledge any uncertainty about current performance. Kill if they say it is fine, they reviewed it recently, and they see no reason to look. Do not push past one redirect. --- ### 2. "Just send me a brochure / some information." **Diagnosis:** Brush-off. The prospect wants to end the conversation without saying no. Sending material almost never leads anywhere. **Script:** "I'll do that. Before I do, I want to make sure I send you the right thing rather than everything we have. Can I ask you two quick questions so I'm not wasting your inbox? [Pause for yes.] What's the actual problem you're trying to solve right now, and what would make you say yes, this is worth a proper look?" **Keep-or-kill rule:** Keep if they answer both questions with any specificity. Kill if they say "just send whatever you have" or deflect a second time. Send a short, targeted follow-up email with one relevant case study and a single clear call to action. --- ### 3. "We're not looking to change right now." **Diagnosis:** Stall or genuine blocker. Needs one probe to distinguish them. **Script:** "Understood. When you say not right now, is that because there's no live problem, or because the timing is genuinely wrong even if the problem exists? I ask because those are two different conversations and I don't want to waste your time having the wrong one." **Keep-or-kill rule:** Keep if they confirm a problem exists but timing is the constraint. Agree a specific date to re-engage and log it. Kill if they say there is no problem and no planned review. Do not book a vague "touch base in six months." --- ### 4. "This isn't the right time." **Diagnosis:** Stall. Almost identical to objection 3 but usually signals an internal pressure (budget cycle, project freeze, change fatigue) rather than a lack of problem. **Script:** "I hear you. What's driving the timing, if you don't mind me asking? I want to understand whether this is a calendar issue or something bigger, because it changes whether it's worth us staying in touch." **Keep-or-kill rule:** Keep if they name a specific event that changes: end of quarter, budget approval, a project going live. Set a follow-up tied to that event. Kill if they cannot name anything specific. "Things are just busy" is not a threshold. --- ### 5. "We don't have the budget for this." **Diagnosis:** Genuine blocker or stall, depending on timing. At mid-discovery, you almost certainly do not know enough about their problem to know whether budget is real or a reflex. **Script:** "That's fair, and I'm not going to push on budget when we're still figuring out whether there's even a fit. Can I ask what you're spending on [the problem area] at the moment, including [internal cost, workaround cost, or cost of doing nothing]? That usually tells us both whether a conversation is worth having." **Keep-or-kill rule:** Keep if they engage with the cost question and reveal any number or acknowledge the current cost is unknown. Kill if they say the budget is zero, fixed, and committed elsewhere with no flexibility. Do not quote price mid-discovery to justify the spend. --- ### 6. "I need to check with my manager / colleague first." **Diagnosis:** Stall or genuine gating. The distinction matters: is this person the right contact, or are they hiding behind authority to end the call? **Script:** "Of course. So I can make it easy for you to have that conversation: what's the one thing your [manager/colleague] is going to want to know before deciding whether to take this further? And is it worth us booking a short call with both of you, so the questions come up once rather than twice?" **Keep-or-kill rule:** Keep if they can name the key question or agree to a joint call. Kill if they will not name the decision-maker, cannot say what the question is, or commit to nothing specific. A vague "I'll pass it on" is not a positive signal. --- ### 7. "We tried something like this before and it didn't work." **Diagnosis:** Genuine blocker with emotional weight. This one is often disguised as a factual objection but is usually about trust, not evidence. **Script:** "That's really useful to know, and I'd rather hear that now than later. What specifically went wrong? I'm asking because [our approach / what we'd do differently] tends to be where that type of implementation breaks down, and I want to know whether what you experienced is the same failure mode or something different." **Keep-or-kill rule:** Keep if they describe the failure and it differs from your known risk factors, or if they are willing to hear how your approach addresses their specific issue. Kill if they say it is the same type of solution and they are not open to the distinction. Do not argue with their experience. --- ### 8. "Can you just tell me the price first?" **Diagnosis:** Brush-off or a signal that a previous rep over-promised and under-delivered. Answering too early almost always kills the call. **Script:** "I can give you a range once I understand what you actually need, because the difference between our lowest and highest engagement is significant and I don't want to anchor you on a number that ends up being wrong either way. It'll take me three or four more questions to give you a figure that means something. Is that fair?" **Keep-or-kill rule:** Keep if they agree to continue. Kill if they refuse to continue without a price and push a second time. Do not give a range just to keep the call alive. A prospect who will not answer qualification questions before demanding price is almost never a good fit. --- ## Quick-reference table | # | Objection | Diagnosis | Keep threshold | Kill trigger | |---|-----------|-----------|----------------|--------------| | 1 | We already have something | Stall | Any uncertainty about current performance | "It's fine, we reviewed it recently" | | 2 | Just send a brochure | Brush-off | Answers both qualification questions with specificity | Deflects a second time | | 3 | Not looking to change | Stall/blocker | Names a problem even if timing is wrong | No problem, no planned review | | 4 | Not the right time | Stall | Names a specific event that changes | Cannot name anything concrete | | 5 | No budget | Blocker/stall | Engages with cost-of-doing-nothing question | Budget is zero and committed | | 6 | Need to check first | Stall/gating | Names the question or agrees to joint call | Will not identify decision-maker | | 7 | Tried it before | Genuine blocker | Failure mode differs from your risk factors | Same type of solution, not open | | 8 | Tell me the price first | Brush-off | Agrees to answer qualification questions | Refuses to continue without price | --- **One rule that applies to all eight:** If you have applied the script and the keep threshold is not met, end the call. Say: "I appreciate your time. Based on where things are, it doesn't sound like the moment is right. I'll drop you a note in [specific timeframe] and you can ignore it or pick it up, no pressure either way." Then stop. Grinding past a kill signal costs you more than the call is worth.