Get 25 AI prompts that generate discovery call questions for any sales scenario. Copy the prompt, fill in your prospect details, and get conversation-ready questions in 30 seconds.
These prompts pair well with Jasper AI for Sales-specific tone control, or Copy.ai for fast iteration.
Enterprise Deal Discovery
You are a B2B sales rep preparing for a discovery call with a large enterprise prospect.
Prospect: {company_name} Industry: {industry} Contact: {contact_name}, {job_title} Deal size: {estimated_deal_value} Pain points mentioned: {known_pain_points} Competition: {competitor_names} Call length: {30_45_60_minutes} Your solution: {product_service_description}
Write 12-15 discovery questions organized into opening, problem exploration, and closing sections. Start with 2-3 warm-up questions, then 6-8 deep problem questions using the SPIN methodology, then 3-4 closing questions about decision process and timeline. Each question should build on the previous answer and move toward a clear next step.
When to use it: When you have a qualified enterprise lead but limited intel on their specific challenges and decision-making process.
Pro tip: Ask the budget question second-to-last, not last. It gives you room to reframe value if their number is lower than expected.
You are a sales rep conducting discovery for a complex enterprise software sale with multiple stakeholders.
Primary contact: {contact_name}, {title} Other stakeholders: {stakeholder_names_titles} Current solution: {existing_vendor_solution} Implementation timeline: {desired_timeline} Team size affected: {number_of_users} Integration needs: {systems_to_integrate} Compliance requirements: {regulatory_requirements} Previous failed implementations: {past_failures}
Create 8-10 stakeholder-mapping questions that uncover who influences the buying decision, what each person cares about, and how decisions get made. Focus on political dynamics, approval processes, and individual win conditions. Include 3 questions specifically about past vendor relationships and what went wrong.
When to use it: When you’re selling into a large organization where the person you’re talking to isn’t the final decision maker.
Pro tip: Ask “Who would be unhappy if this project failed?” to uncover hidden stakeholders and political landmines.
You are a sales rep preparing discovery questions for a prospect switching from a major competitor.
Prospect: {company_name} Current vendor: {competitor_name} Contract end date: {renewal_date} Reason for exploring: {initial_reason_given} Your differentiator: {key_competitive_advantage} Their current spend: {estimated_current_spend} Implementation complexity: {high_medium_low} Risk tolerance: {conservative_moderate_aggressive}
Write 10-12 questions that uncover specific frustrations with their current vendor, switching costs concerns, and criteria for change. Include 4 questions about their current vendor relationship that help you position against weaknesses. End with questions about their evaluation process and success metrics for a new solution.
When to use it: When a prospect is evaluating alternatives to their current vendor and you need to understand switching motivations.
Pro tip: Don’t bash the competitor directly. Instead ask “What would need to change about your current solution for you to stay with [competitor]?” Let them criticize.
You are a sales rep conducting discovery for an urgent enterprise purchase with a compressed timeline.
Prospect: {company_name} Urgency driver: {business_event_causing_urgency} Decision deadline: {hard_deadline} Budget status: {approved_pending_unknown} Key decision maker: {primary_decision_maker} Consequences of delay: {cost_of_waiting} Interim workarounds: {temporary_solutions_tried} Success definition: {how_they_measure_success}
Create 8-10 rapid discovery questions focused on immediate needs, decision criteria, and implementation requirements. Prioritize questions about timeline, approval process, and showstoppers. Include 2-3 questions about what happens if they don’t solve this by their deadline. Keep responses actionable and next-step oriented.
When to use it: When a prospect has an urgent business need and compressed evaluation timeline, usually driven by a specific event or deadline.
Pro tip: Ask “What’s the backup plan if you don’t find a solution by [deadline]?” This often reveals hidden budget or decision-making authority.
You are a sales rep preparing discovery for an enterprise prospect evaluating multiple vendors in a formal RFP process.
Company: {company_name} RFP timeline: {submission_deadline} Evaluation committee: {committee_members} Budget range: {stated_budget_range} Current process: {existing_workflow_description} Must-have features: {non_negotiable_requirements} Vendor shortlist: {competing_vendors} Implementation window: {go_live_deadline}
Write 12-15 discovery questions that help you stand out in the RFP process. Focus on uncovering unstated requirements, political preferences, and evaluation criteria not in the RFP. Include questions about past vendor selections, committee dynamics, and what would make them choose you over the lowest bidder.
When to use it: When you’re competing in a formal RFP process and need to differentiate beyond just answering the written requirements.
Pro tip: Ask “What questions should we have asked that we didn’t?” at the end. RFPs rarely capture everything that matters to buyers.
SMB Quick Discovery
You are a sales rep conducting a 20-minute discovery call with a small business owner.
Business: {business_name} Industry: {industry_type} Owner: {owner_name} Employee count: {team_size} Current monthly spend: {current_solution_cost} Main challenge: {primary_pain_point} Growth stage: {startup_growing_established} Tech comfort: {low_medium_high}
Create 8-10 concise discovery questions for a fast-moving call. Focus on immediate pain, budget reality, and decision speed. Include questions about current solutions, growth plans, and what success looks like. Keep questions simple and avoid jargon. End with clear next steps and timeline expectations.
When to use it: When you have a short window with a small business owner who makes quick decisions but has limited time.
Pro tip: Ask about their biggest business worry right now, not just problems related to your product. SMB owners buy solutions to business problems, not feature sets.
You are a sales rep talking to an SMB prospect who’s never bought this type of solution before.
Contact: {contact_name}, {title} Company: {company_name} Industry: {industry} Problem trigger: {what_made_them_look} Current workaround: {manual_process_description} Team size: {number_of_people_affected} Budget discussions: {have_they_discussed_budget} Timeline pressure: {when_they_need_solution}
Write 10-12 educational discovery questions that help them understand what they need to know without sounding condescending. Include questions about their current process, what they’ve researched, concerns about change, and success criteria. Focus on building confidence in both your solution and their ability to implement it.
When to use it: When talking to a first-time buyer who doesn’t know what they don’t know about your product category.
Pro tip: Ask “What worries you most about making the wrong choice?” Early buyers often have more fear than knowledge. Address the fear first.
You are a sales rep conducting discovery with an SMB prospect comparing you to a much larger, established competitor.
Prospect: {company_name} Your main competitor: {big_competitor_name} Contact: {contact_name}, {role} Business size: {revenue_or_employee_count} Current solution: {what_theyre_using_now} Competitor advantages: {why_big_competitor_appeals} Your advantages: {your_key_differentiators} Their priorities: {speed_cost_features_support}
Create 8-10 questions that highlight the benefits of working with a smaller, more agile vendor. Focus on service level, customization, decision speed, and personal attention. Include questions about their experience with large vendors and what matters most in a partnership. Position size as an advantage, not a limitation.
When to use it: When competing against a much larger competitor for an SMB deal where you need to turn your size into an advantage.
Pro tip: Ask “When you call [big competitor] for support, do you talk to the same person?” SMBs value relationships more than features.
You are a sales rep speaking with an SMB prospect who’s price-shopping and focused mainly on cost.
Company: {company_name} Contact: {buyer_name} Current budget: {stated_budget_limit} Cheapest option: {low_cost_competitor} Price difference: {how_much_more_you_cost} Value drivers: {your_roi_advantages} Risk of cheap solution: {potential_problems} Growth plans: {expansion_timeline}
Write 8-10 discovery questions that shift focus from price to value and total cost of ownership. Include questions about hidden costs of cheap solutions, growth plans, opportunity cost of delays, and what expensive problems they’re trying to avoid. Help them calculate the real cost of the decision.
When to use it: When an SMB prospect is fixated on upfront price and you need to demonstrate value beyond the initial cost.
Pro tip: Ask “What does it cost you every month that you don’t solve this?” Help them see the expense of inaction, not just the price of action.
You are a sales rep conducting discovery with an SMB prospect who needs to convince their business partner or spouse before buying.
Primary contact: {contact_name} Decision partner: {partner_name_relationship} Business structure: {partnership_family_business} Partner involvement: {how_involved_in_operations} Budget authority: {who_controls_spending} Risk tolerance: {conservative_moderate_aggressive} Partner concerns: {known_objections_or_worries} Timeline: {when_decision_needed}
Create 10-12 questions that help you understand the partner dynamic and prepare your contact to sell internally. Include questions about decision-making process, partner priorities, past purchase decisions, and what information the partner needs. Focus on giving your contact tools to advocate for the purchase.
When to use it: When your main contact likes the solution but needs to convince a business partner, spouse, or co-owner who isn’t on the call.
Pro tip: Ask “What questions will [partner] ask that I should help you prepare for?” Turn your contact into a coach, not just a buyer.
Technical Discovery
You are a sales rep conducting technical discovery with an IT director evaluating software integration requirements.
Contact: {it_director_name} Current tech stack: {existing_systems} Integration requirements: {must_integrate_with} Data migration needs: {data_to_migrate} Security requirements: {compliance_standards} IT team size: {technical_team_capacity} Implementation timeline: {preferred_rollout_schedule} Downtime tolerance: {acceptable_outage_windows}
Write 10-12 technical discovery questions that uncover integration complexity, security concerns, and implementation risks. Include questions about API requirements, data formats, authentication methods, and rollback procedures. Focus on technical decision criteria and potential showstoppers.
When to use it: When selling to IT professionals who need to understand technical requirements and implementation details before making a decision.
Pro tip: Ask “What integration has gone wrong in the past and why?” Learn from their technical scars to avoid repeating mistakes.
You are a sales rep conducting discovery with end users who will actually use the technical solution daily.
User group: {department_or_team} Contact: {end_user_name}, {role} Current workflow: {how_they_work_today} Pain points: {daily_frustrations} Tech comfort level: {beginner_intermediate_advanced} Training needs: {learning_preferences} Success metrics: {how_they_measure_productivity} Change resistance: {team_attitude_toward_new_tools}
Create 8-10 user-focused discovery questions about daily workflows, usability requirements, and adoption concerns. Include questions about current tools, learning preferences, resistance to change, and what would make them love using your solution. Focus on practical usage scenarios.
When to use it: When you need to understand how end users actually work and what will drive adoption of your technical solution.
Pro tip: Ask them to walk you through their worst day using current tools. Pain in context is more powerful than abstract feature requests.
You are a sales rep conducting security and compliance discovery with a risk management or compliance officer.
Contact: {compliance_officer_name} Industry regulations: {applicable_compliance_standards} Current security tools: {existing_security_stack} Audit requirements: {reporting_and_documentation_needs} Risk tolerance: {organizational_risk_appetite} Past security incidents: {relevant_security_history} Vendor requirements: {procurement_and_vendor_standards} Implementation oversight: {who_manages_compliance_rollouts}
Write 10-12 compliance-focused discovery questions about regulatory requirements, security standards, audit trails, and risk management. Include questions about vendor evaluation criteria, documentation needs, and past compliance challenges. Address both technical and procedural compliance requirements.
When to use it: When selling into regulated industries or security-conscious organizations where compliance requirements drive purchase decisions.
Pro tip: Ask “What would happen if auditors found gaps in [specific area]?” Compliance officers think in terms of audit findings and regulatory consequences.
You are a sales rep conducting discovery about data and reporting requirements with a business intelligence or data analytics stakeholder.
Contact: {analytics_lead_name} Current reporting: {existing_reports_and_dashboards} Data sources: {systems_with_relevant_data} Reporting frequency: {daily_weekly_monthly_requirements} Key metrics: {most_important_kpis} Audience: {who_consumes_reports} Export needs: {required_data_formats} Integration tools: {bi_tools_in_use}
Create 8-10 discovery questions focused on data requirements, reporting needs, and analytics integration. Include questions about current data challenges, custom reporting needs, real-time vs. batch requirements, and how insights drive decisions. Focus on data workflow and business intelligence requirements.
When to use it: When your solution generates data or integrates with analytics tools and you need to understand reporting and data requirements.
Pro tip: Ask “Show me the report you look at first every Monday morning.” This reveals their most critical metrics and reporting priorities.
You are a sales rep conducting discovery with a DevOps or systems administrator about operational and maintenance requirements.
Contact: {devops_lead_name} Current infrastructure: {hosting_and_infrastructure_details} Monitoring tools: {existing_monitoring_stack} Maintenance windows: {acceptable_update_schedules} Support requirements: {response_time_expectations} Scaling needs: {growth_and_capacity_planning} Backup procedures: {disaster_recovery_requirements} Team responsibilities: {who_manages_what} Budget for operations: {ongoing_operational_budget}
Write 10-12 operational discovery questions about system administration, maintenance, monitoring, and support requirements. Include questions about current operational challenges, scaling concerns, disaster recovery, and ongoing management responsibilities. Focus on total operational overhead.
When to use it: When selling solutions that require ongoing operational management and you need to understand operational requirements and constraints.
Pro tip: Ask “What keeps you up at night about your current systems?” DevOps professionals worry about uptime, scaling, and operational complexity.
Competitive Displacement
You are a sales rep conducting discovery to displace an incumbent vendor during their renewal period.
Current vendor: {incumbent_vendor_name} Contract details: {renewal_date_and_terms} Relationship history: {years_with_vendor} Recent issues: {problems_with_current_vendor} Switching concerns: {migration_and_change_worries} Budget implications: {cost_comparison} Internal champions: {who_wants_change} Switching decision makers: {who_decides_on_change}
Create 10-12 displacement-focused discovery questions that uncover switching motivations, change requirements, and incumbent weaknesses. Include questions about vendor relationship satisfaction, switching costs, implementation concerns, and success criteria for a new vendor. Focus on change justification and risk mitigation.
When to use it: When targeting prospects who are currently using a competitor and evaluating whether to switch during their renewal cycle.
Pro tip: Ask “What would have to stay exactly the same for you to renew with [current vendor]?” This reveals non-negotiable switching triggers.
You are a sales rep conducting discovery with a prospect who had a bad experience with a previous vendor in your category.
Contact: {contact_name} Previous vendor: {failed_vendor_name} What went wrong: {specific_failure_points} Impact of failure: {business_consequences} Lessons learned: {what_they_want_differently} Current situation: {how_theyre_managing_now} Risk tolerance: {appetite_for_trying_again} Success requirements: {what_success_looks_like_now}
Write 8-10 discovery questions that address past vendor failures and rebuild confidence in the category. Include questions about specific failure points, lessons learned, risk mitigation requirements, and success criteria. Focus on differentiation from failed vendor and risk reduction.
When to use it: When a prospect is gun-shy about your product category because of a previous bad experience with a different vendor.
Pro tip: Ask “What would you do differently in vendor selection this time?” This shows you respect their experience and want to help them avoid past mistakes.
You are a sales rep conducting competitive discovery when you know a specific competitor is also being evaluated.
Known competitor: {competitor_name} Evaluation stage: {early_middle_late_stage} Competitor strengths: {what_competitor_does_well} Your advantages: {your_key_differentiators} Evaluation criteria: {how_theyre_comparing_options} Decision timeline: {when_decision_gets_made} Evaluation process: {how_theyre_running_evaluation} Key stakeholders: {who_influences_decision}
Create 10-12 discovery questions that position your strengths against known competitor weaknesses without directly attacking the competitor. Include questions about evaluation criteria, stakeholder priorities, implementation requirements, and decision factors. Focus on differentiation through questioning.
When to use it: When you know you’re competing against a specific competitor and need to understand how decisions will be made and what matters most.
Pro tip: Ask “What concerns you most about making the wrong choice?” This reveals evaluation anxiety and gives you chances to provide reassurance your competitor can’t.
You are a sales rep conducting discovery with a prospect who’s building an internal solution instead of buying.
Contact: {contact_name} Internal team: {who_building_solution} Build timeline: {development_schedule} Resource allocation: {people_and_budget_assigned} Technical challenges: {development_risks} Opportunity cost: {what_team_not_working_on} Success requirements: {internal_solution_must_haves} Backup plan: {what_if_build_fails}
Write 8-10 discovery questions that uncover build vs. buy decision factors. Include questions about development resources, opportunity costs, timeline risks, ongoing maintenance, and total cost of ownership. Focus on hidden costs and risks of internal development.
When to use it: When competing against internal development teams who want to build rather than buy a solution.
Pro tip: Ask “What other strategic projects get delayed while your team builds this?” Help them see the opportunity cost of internal development resources.
You are a sales rep conducting discovery to understand why a prospect is considering switching to a newer, trendy competitor.
Trendy competitor: {new_competitor_name} Appeal of new vendor: {why_prospect_interested} Current solution: {what_theyre_using_now} Change motivation: {driver_for_considering_switch} Risk tolerance: {comfort_with_newer_vendors} Proven solution needs: {importance_of_track_record} Innovation priorities: {new_features_vs_stability} Implementation complexity: {change_management_concerns}
Create 10-12 discovery questions that balance innovation appeal with proven reliability. Include questions about change risk tolerance, track record importance, feature requirements vs. stability needs, and implementation support requirements. Position experience and stability as advantages.
When to use it: When a prospect is considering a newer, trendy competitor and you need to emphasize the value of proven solutions and established vendors.
Pro tip: Ask “What’s your backup plan if the new solution doesn’t work out?” Newer vendors often lack proven support and recovery options.
Frequently Asked Questions
What makes AI-generated discovery call questions better than generic templates?
AI prompts create questions tailored to your specific prospect, industry, and competitive situation. Instead of asking the same questions to every prospect, you get customized discovery that uncovers the unique challenges and motivations driving each buyer’s decision.
How do I modify these prompts for different industries or deal sizes?
Change the variables in {curly_brackets} to match your situation. For larger deals, add stakeholder complexity variables. For technical sales, include integration and compliance variables. The prompt structure works across industries when you customize the input variables.
Can I combine multiple prompts for complex sales situations?
Yes, use different prompts for different stakeholders or call stages. Start with broad business discovery, then use technical prompts for IT stakeholders and competitive prompts when you learn about other vendors. Each prompt builds a complete picture of the buying situation.