Inbound Lead Qualification and Discovery Call Script

Role: Senior Inbound Sales Development Representative & Pipeline Strategist with deep expertise in B2B software qualification.

Context

• Prospect title: {{prospect_role}}
• Software category: {{target_software_category}}
• Inbound trigger: {{lead_source_trigger}}
• Primary reported challenge: {{primary_pain_point}}
• Current tooling: {{tech_stack_environment}}
• Qualification methodology: {{qualification_framework}}

Task

Draft a structured, conversational phone qualification script that enables an SDR to validate inbound software interest, diagnose core operational bottlenecks, and book a qualified AE demonstration.

Method

1. Analyze the context provided by {{lead_source_trigger}} to craft a contextual opening hook that avoids generic greetings.
2. Formulate two rapport-building transition statements acknowledging the prospect's role as {{prospect_role}}.
3. Develop three open-ended discovery questions centered on {{primary_pain_point}} and how it impacts their team daily.
4. Draft two technical qualification probes exploring compatibility and friction with {{tech_stack_environment}}.
5. Align the qualification logic directly with the parameters of {{qualification_framework}} (e.g., assessing economic buyer, criteria, or timeline).
6. Script a brief 30-second value teaser showing how the {{target_software_category}} solves the diagnosed friction without over-pitching features.
7. Write an assertive demonstration close that secures a calendar commitment alongside two objection-handling pivot lines for hesitation.

Constraints

• MUST structure the script with distinct conversational turns indicating speaker lines and delivery cues.
• MUST include explicit qualification checkpoints mapping to {{qualification_framework}}.
• MUST NOT exceed 750 words across the entire script.
• Do not include robotic monologue pitches; keep prospect speaking time above 60%.

Output format

• Section 1: Opening Hook & Permission Statement (under 75 words)
• Section 2: Core Discovery & Technical Diagnostic Prompts (4-5 structured question-response pairs with SDR cues)
• Section 3: Value Alignment Teaser & AE Handoff Close (scripted bridge and calendar lock-in)
• Section 4: Quick-Fire Objection Matrix (table with 2 columns: Prospect Pushback, SDR Pivot Script)

Self-review

1. Did I reference {{primary_pain_point}} and {{tech_stack_environment}} naturally within the discovery dialogue?
2. Does the closing sequence enforce a concrete calendar invite rather than a vague follow-up?
3. Are delivery cues present to guide pacing, tone, and active listening pauses?