© 2026 Sales Bytes.
Prompt:
Build a discovery question framework for a first call with a {TITLE} at a {COMPANY_TYPE} company. I sell {PRODUCT}. Create 15 questions organized by:
- Current state (how they do things today)
- Pain identification (what's not working)
- Impact quantification (what it's costing them)
- Future state (what good looks like)
- Decision process (how they'd evaluate a solution)
Make questions open-ended and conversational. No yes/no questions.
💡 Why this works: A structured framework prevents you from asking random questions and missing critical info.
🔄 Platform tip: Claude builds more natural conversational flows. ChatGPT gives more structured frameworks.
Prompt:
I have a discovery call tomorrow with {NAME}, {TITLE} at {COMPANY}. Here's what I know:
- Company: {COMPANY_DESCRIPTION}
- Size: {EMPLOYEE_COUNT}, {REVENUE_ESTIMATE}
- Industry: {INDUSTRY}
- Their current stack: {KNOWN_TOOLS}
Give me:
1. Three hypotheses about their current pain points
2. Five tailored discovery questions based on these hypotheses
3. Two industry-specific insights I can reference
4. One competitor they're likely evaluating besides us
5. Potential landmines to avoid
💡 Why this works: Walk into every call with a hypothesis, not a blank slate.
Prompt:
I'm on a deal with {COMPANY} for {PRODUCT}. Here's what I know so far:
{PASTE_CALL_NOTES}
Map what I know to the MEDDIC framework:
- Metrics: What economic impact have we identified?
- Economic Buyer: Who controls the budget?
- Decision Criteria: What are they evaluating on?
- Decision Process: What are the steps to close?
- Identify Pain: What's the core pain?
- Champion: Who's selling internally for us?
For each element, tell me what I know, what I'm missing, and give me a question to fill the gap.
💡 Why this works: MEDDIC gaps are deal killers. Map them early.
Prompt:
My prospect {NAME} at {COMPANY} described this pain: "{PAIN_IN_THEIR_WORDS}"
Help me quantify the business impact. Calculate:
- Time wasted per week/month on this problem
- Revenue impact (lost deals, slower cycles, etc.)
- Cost of inaction over 12 months
- Headcount implications
Give me back a simple ROI statement I can use in a follow-up email. Use reasonable assumptions and show your math.
💡 Why this works: Champions sell internally with numbers, not stories. Give them the math.
🔄 Platform tip: Claude is stronger at showing reasonable assumptions and building credible financial models.
Prompt:
Write a recap email after a discovery call with {NAME} at {COMPANY}. Here are my call notes:
{PASTE_NOTES}
The email should:
1. Thank them genuinely (not generically)
2. Summarize the 3 key pain points they mentioned IN THEIR WORDS
3. Confirm the agreed next steps
4. Attach a relevant resource: {RESOURCE}
5. Set clear expectations for timeline
Keep it under 150 words. Professional but not stiff.
💡 Why this works: A good recap email confirms alignment and creates accountability for next steps.
Prompt:
Based on my discovery call notes below, identify every stakeholder mentioned or implied. For each person:
- Name/Title (if mentioned) or likely title
- Their likely role in the decision (champion, influencer, blocker, decision-maker, end-user)
- What they probably care about most
- A suggested next action for engaging them
Call notes: {PASTE_NOTES}
💡 Why this works: Every name and role dropped in a discovery call is a clue. Don't miss them.
Prompt:
I'm on a discovery call with a prospect who currently uses {COMPETITOR}. Create 10 questions that:
- Uncover what they like about {COMPETITOR} (don't skip this)
- Identify frustrations WITHOUT leading the witness
- Understand what would make them consider switching
- Gauge how locked in they are (contracts, integrations, training)
Don't make these sound like I'm trying to trash the competitor.
💡 Why this works: If you don't understand why they chose the competitor, you can't position against it.
Prompt:
Generate 10 discovery questions tailored for a {TITLE} in the {INDUSTRY} industry. The questions should reference:
- Industry-specific challenges and trends
- Regulatory or compliance pressures
- Common KPIs for their role in this industry
- Technology adoption patterns in their space
I sell {PRODUCT}. Make the questions feel like I understand their world.
💡 Why this works: Generic questions get generic answers. Industry knowledge earns trust.
Prompt:
Here are my notes from a discovery call:
{PASTE_NOTES}
Analyze these notes for red flags:
- Signs of low buying intent
- Missing information that should have come up
- Vague answers that need follow-up
- Potential blockers or competitors
- Misalignment between their needs and our solution
For each red flag, give me a specific follow-up action to address it.
💡 Why this works: Most reps miss red flags because they're too focused on the pitch. Let AI catch what you missed.
🔄 Platform tip: Claude is excellent at nuanced analysis of conversation dynamics and subtle warning signs.
Prompt:
Based on this discovery call recap, build an agenda for the second call:
Discovery recap: {PASTE_RECAP}
The second call should:
1. Validate the 3 key pain points from call 1
2. Introduce how our solution addresses each pain
3. Identify remaining stakeholders to involve
4. Discuss timeline and decision process
5. Agree on a concrete next step
Give me the agenda with time allocations for a 30-minute call.
💡 Why this works: A structured second call separates pros from amateurs.
Prompt:
Generate 8 questions to uncover budget information from a {TITLE} at a {COMPANY_TYPE} company WITHOUT directly asking 'What's your budget?' Approach it from:
- What they're currently spending on the problem
- What solving this problem is worth to them
- How they've allocated budget for similar tools
- Their fiscal year and planning cycle
- Previous purchases of this type
💡 Why this works: Nobody answers 'What's your budget?' honestly. Ask around it.
Prompt:
I'm an AE (not technical) selling {PRODUCT} to a {TITLE} who IS technical. Generate 10 discovery questions about their technical environment that:
- Sound informed without pretending to be an engineer
- Uncover integration requirements and tech stack
- Identify potential implementation blockers
- Show I respect their technical expertise
Include follow-up questions for common answers.
💡 Why this works: Technical buyers respect reps who ask smart questions, not reps who fake expertise.
Prompt:
Generate 8 questions to identify whether my contact at {COMPANY} is a true champion or just a friendly contact. The questions should assess:
- Do they have organizational influence?
- Are they personally invested in solving this problem?
- Can they sell internally without me in the room?
- Do they have access to the economic buyer?
- Have they championed similar purchases before?
Make the questions natural, not interrogation-style.
💡 Why this works: Deals die when you're building on a 'champion' who has no influence.
Prompt:
I just finished a discovery call. The prospect said {THEIR_RESPONSE_TO_NEXT_STEPS}. Help me:
1. Evaluate if this is a real commitment or a polite brush-off
2. Suggest what to say next to lock in a concrete action
3. Draft a follow-up message that creates gentle accountability
4. Identify 2 backup next steps if they go dark
Be direct with me about whether this deal is real.
💡 Why this works: Vague next steps are the #1 reason deals stall. Pressure-test every commitment.
Prompt:
I just gave a demo to {NAME} at {COMPANY}. Help me transition from demo to deeper discovery with 8 questions that:
- Gauge their reaction without asking 'What did you think?'
- Connect specific features to their pain points
- Identify who else needs to see this
- Uncover concerns they're not volunteering
- Move toward a decision timeline
These should feel natural right after a product walkthrough.
💡 Why this works: The best discovery happens AFTER the demo, when the prospect has context.
Prompt:
I have a call with 3 people from {COMPANY}:
- {NAME_1}, {TITLE_1}
- {NAME_2}, {TITLE_2}
- {NAME_3}, {TITLE_3}
Help me:
1. Predict what each person cares about
2. Create 2 questions for each stakeholder
3. Plan how to manage airtime so no one dominates
4. Identify potential conflicts between their priorities
5. Draft my opening that acknowledges everyone's time
💡 Why this works: Multi-stakeholder calls require choreography, not improv.
Prompt:
Based on my discovery findings, create a mutual action plan for closing a deal with {COMPANY}. Key details:
- Pain points: {PAIN_POINTS}
- Decision-makers: {STAKEHOLDERS}
- Timeline: {TARGET_CLOSE_DATE}
- Budget: {BUDGET_INFO}
Build a step-by-step plan with:
- What we do / What they do
- Target dates for each milestone
- Key decision points
- Potential risks and mitigation
Format as a shareable doc I can send to the prospect.
💡 Why this works: Mutual action plans create shared accountability and compress deal cycles.
Prompt:
I just finished a discovery call. Here are my notes:
{PASTE_NOTES}
Score my call on a 1-10 scale across:
- Pain discovery depth
- Decision process clarity
- Stakeholder mapping
- Budget/priority understanding
- Next step commitment quality
- Rapport and trust building
For each area below a 7, give me the specific question I should have asked. Be brutally honest.
💡 Why this works: Self-coaching after every call is how top reps get better.
🔄 Platform tip: Claude gives more diplomatic but still honest feedback. ChatGPT is more blunt.
Prompt:
Before my call with {NAME} at {COMPANY}, predict the top 5 objections they'll raise based on:
- Their role: {TITLE}
- Their company size: {SIZE}
- Their industry: {INDUSTRY}
- Their current solution: {CURRENT_TOOL}
For each predicted objection:
1. The likely phrasing they'll use
2. My best response
3. A proactive way to address it BEFORE they raise it
💡 Why this works: Anticipating objections before the call means you're never caught off guard.
Prompt:
I'm meeting with the CFO (or VP Finance) at {COMPANY}. They care about
different things than my usual buyers. Generate 8 discovery questions that:
- Focus on financial impact, not workflow
- Connect our solution to revenue, cost reduction, or risk mitigation
- Show I respect their time and perspective
- Avoid technical jargon
I sell {PRODUCT} at a price point of
{PRICE}.
💡 Why this works: CFOs buy outcomes, not features. Speak their language.