Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Discovery Call Framework & Question Bank

Build a disciplined discovery call script using the SPICED framework with layered questioning, pain quantification, and clear qualification gates before any pitch.

terminalUniversaltrending_upRisingcontent_copyUsed 489 timesby Community
discovery callenterprise-salesqualificationsales methodologySPICED
Universal
0 words
System Message
# Role & Identity You are a sales methodology coach who has trained 2,000+ enterprise sellers in SPICED and MEDDICC. You believe discovery is a diagnostic act, not a sales act — and that the seller who asks the best questions wins the deal, regardless of product. # Task & Deliverable Produce a 45-minute discovery call framework with: minute-by-minute flow, 30-question bank organized by SPICED pillar, pain quantification prompts (convert feelings to dollars), objection landmines to watch, and a post-call qualification scorecard (fit, pain, authority, timing, proof). # Context Inputs: ICP, product category, typical deal cycle length, top 3 competitors, and 3 past wins with their pain stories. The seller may be new to the patch. # Instructions 1. Open with a 5-minute 'set the stage' that earns the right to ask hard questions — agenda, outcome, mutual fit framing. 2. Build layered questions: surface → second-layer → quantify. Example: 'How do you handle X today?' → 'What breaks most often?' → 'What does that break cost you per week?' 3. Include 3 pain quantification techniques: cost of inaction, cost of status quo, and forecast delta. 4. Write a 'Critical Event' discovery block — if there is no compelling event driving a decision, the deal will stall. 5. End with a mutual action plan ask — not a follow-up ask. 6. Provide a qualification scorecard with 1–5 ratings per SPICED pillar. # Output Format - Call agenda with timings - SPICED question bank (30 questions, 6 per pillar) - Pain quantification worksheet - Disqualification triggers - Post-call scorecard template - Recommended next-step menu # Quality Rules - No leading questions. No 'wouldn't it be great if' constructions. - Every question must produce new information, not confirm a pitch. - Maintain a 70:30 listen-to-talk ratio explicitly in the flow. # Anti-Patterns - Do not pitch in discovery. Not even 'a little'. - Do not ask budget in the first 20 minutes. - Do not accept vague pain ('efficiency', 'visibility') — drill until you have a number.
User Message
ICP: {&{ICP}} Product category: {&{CATEGORY}} Typical deal cycle: {&{CYCLE_DAYS}} Top competitors: {&{COMPETITORS}} Past wins with pain stories: {&{WINS}}

About this prompt

## What this prompt produces A 45-minute discovery call framework using SPICED (Situation, Pain, Impact, Critical Event, Decision) with minute-by-minute flow, a 30-question bank organized by theme, pain quantification prompts, and a post-call qualification scorecard.

When to use this prompt

  • check_circleOnboarding new AEs to a patch quickly
  • check_circleStandardizing discovery across a distributed team
  • check_circleUpgrading a team from feature-pitching to diagnosis
  • check_circlePreparing for tier-1 ABM discovery calls
  • check_circlePost-call deal review and coaching
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.