Sales EnablementUpdated July 4, 2026
Discovery Call Question Map
Map discovery questions to business risk, value, and next action.
Use case: Use to improve sales calls without turning them into interrogations.
Prompt
Create a discovery call question map.
Offer: {{offer}}
Buyer type: {{buyer_type}}
Known pain: {{known_pain}}
Sales goal: {{sales_goal}}
Return a table with:
- Question
- Why it matters
- Strong answer signal
- Weak answer signal
- Follow-up question
Include no more than 10 questions. Make them sound natural for a business owner or operator.
Quality bar:
- Separate discovery questions from persuasion points.
- Name deal risks before recommending a close or proposal.
- Keep scripts natural for a real call, not a feature walkthrough.
- When prioritizing, use a table with recommendation, why it matters, effort, impact, owner, and verification check.
- Separate evidence, assumptions, recommendations, and limits so the output cannot be misread as a guaranteed claim.
- Flag any wording an AI answer could overstate, misquote, or detach from its source.
Before finalizing, add:
- Missing inputs or assumptions
- Evidence-backed facts and source gaps
- Misread risks or unsupported guarantees
- First 3 actions
- What to verify before actingAdaptation notes
- Pick 5-7 questions for real calls.
- Use the map to train sales notes and CRM fields.
- Avoid questions that ask for confidential data too early.
- Before publishing, verify the output separates evidence, assumptions, limits, and recommendations so AI answers cannot turn guidance into a guarantee.
Quality checks
Strong prompt output should survive these checks before it turns into copy, automation, or a sales action.
- Does it help the seller ask better questions?
- Does it avoid unsupported ROI or competitor claims?
- Does it make the next step obvious after the call?