7 AI Prompts for Discovery Calls and Objection Handling

Discovery calls fail in the prep, not the call. The owner who "wings it because I know my stuff" spends fifteen minutes asking what the website already said, never gets a budget number in the room, and sends a follow-up written from memory and hope. None of that is a charisma problem.

These seven AI prompts for discovery calls cover the whole arc: research before, questions and objection handling during, the decision and follow-up after. Paste them into ChatGPT or Claude as-is; the [SQUARE BRACKETS] are yours to fill. Most of us sell time or expertise, so the examples lean service business, but the structure holds for products too.

Before the call

1. The five-minute prospect brief. Run this the morning of, not the week before; stale prep reads as no prep.

I have a discovery call with [COMPANY / PERSON]. Here is their website
text and anything else I have: [PASTE].
Give me a one-page brief: what they appear to sell and to whom, their
likely size, 3 hypotheses for why they booked this call with
[YOUR BUSINESS TYPE], and for each hypothesis one question that would
confirm or kill it. Mark everything you inferred as a guess to verify.

Good output sounds tentative in the right places. If the brief states things confidently that the website never said, tell it to re-mark those as guesses.

2. The question set that isn't an interrogation. Generic discovery scripts feel like a survey. This one builds questions from your actual hypotheses.

Using this brief: [PASTE OUTPUT OF PROMPT 1], write me 8 discovery
questions in a natural order: 3 that open the story ("walk me
through..."), 3 that test my hypotheses, and 2 that surface budget and
timeline without cornering anyone. Phrase them the way a [YOUR TRADE]
owner talks, not a consultant. Flag the one question I will be most
tempted to skip.

The flagged question is nearly always the budget one. Ask it anyway; a deep bank of alternatives lives in our Discovery Call Question Bank.

During: objections, without the script voice

3. The objection map. Build this once per offer, not per call.

I sell [OFFER] at [PRICE RANGE] to [CUSTOMER TYPE]. List the 8
objections I most likely hear on a first call, from polite ("send me
some info") to hard ("we tried someone like you and it failed"). For
each: what the objection usually means underneath, one honest
clarifying question, and a 2-sentence response that concedes whatever
is true in it. No scripts that pretend the concern is silly.

The concede-what's-true instruction is the difference between a response and a deflection. For the ten toughest ones your business specifically hears, the Objection Handling Playbook goes deeper.

4. The price-flinch line. One prompt for the moment the number lands badly.

My price for [OFFER] is [PRICE]. Write 3 ways to respond when a
prospect flinches at it: one that unpacks what the price includes, one
that offers a smaller scope honestly (not a discount), and one that
gracefully names that we might not be the right fit. Each under 40
words, in a calm owner's voice. No "investment in yourself" language.

After: the part everyone fumbles

5. The debrief, while it's warm. Do this in the parking lot.

I just finished a discovery call. Here's my ramble about it: [TALK OR
TYPE EVERYTHING YOU REMEMBER]. Extract: stated pain, budget signals,
who decides, timeline, objections raised, and the questions I forgot
to ask. Then give me a one-line recommendation: pursue (with the next
step) or pass (with the reason). If I'm rationalizing a bad fit, say
so.

6. The follow-up that doesn't sound desperate.

Using this debrief: [PASTE OUTPUT OF PROMPT 5], write a follow-up
email under 120 words. Reference two specific things they said, in
their words. One clear next step with a date. No "just checking in,"
no false urgency, no recap of my own pitch. Match this voice: [PASTE
AN EMAIL YOU LIKED SENDING].

If a good call goes quiet afterward anyway, that's a different problem with its own tool: Follow-Up Sequences handles the revive.

7. The pattern check, monthly.

Here are one-line summaries of my last [N] discovery calls with their
outcomes: [PASTE]. What patterns predict the wins and the losses?
Where in the arc (prep, questions, budget talk, follow-up) am I
leaking deals? Give me the single highest-leverage change for next
month, with how to measure it.

Where this breaks

Prompts don't fix a pipeline problem. If the calls themselves are with the wrong people, better questions produce better-documented bad fits; qualification comes first. And prompt 5 only works if you're honest in the ramble: a debrief fed on optimism returns optimism. The honest limitation of all seven is that they prepare and record the conversation; they don't have it. The uncomfortable budget question still needs your voice saying it.

Make it a system instead of seven pastes

These prompts are the manual version. If you run discovery calls weekly, our Discovery Call Copilot skill chains the whole arc into a standing routine: it keeps your offer and dealbreakers in memory, preps each call, debriefs each ramble, forces the pursue/pass line, and builds the pattern log across weeks so prompt 7 happens on its own. For the wider craft of writing prompts that sound like you, start with prompt engineering for small business, and the sales toolbox has the rest of the pipeline.