Categories

10‑Minute Discovery Call Script — One‑Shot Generator

Produce a time‑boxed, verbatim 10‑minute discovery script with 6 diagnostic questions, value‑framing transitions, 3 objection branches, and a single next‑step close (Markdown ou...

What You'll Get

• A ready‑to-read Markdown script: timeboxed opening, agenda, and a concise next‑step close using your exact primary CTA.

• Exactly 6 diagnostic questions; each includes: question text, intent, 2-3 ideal answer signals, and a short follow‑up for ambiguous responses.

• Three inline value‑framing transitions (after Q2, Q4, Q6) that link prospect pain to your offer using a provided proof point.

• Three objection branching replies (top 3 objections) with 20-30s scripted responses and the intended next outcome for each.

• One fallback close for stakeholders needing internal buy‑in and strict enforcement of claim hygiene and single‑CTA rules.

• Validation behavior: if any required input (offer, ICP, pain points, decision criteria/timeline, buyer roles/channel, proof points, common objections, primary CTA) is missing, the generator asks one targeted clarifying question instead of producing the script.

How to Use

• 1Provide concise required inputs: offer + primary benefit, ideal customer profile, up to 3 top pains, decision criteria & buying timeline, buyer roles & channel (phone/Zoom/in‑person), short proof points, top common objections, and the exact primary CTA text.

• 2Run the generator and review the Markdown script; personalize only the 2-3 bracketed fields (names, single example) and confirm proof points cited match your input.

• 3Create 2-3 A/B variants by changing question order, wording, or objection phrasing and run small tests across SDRs/AEs to compare conversion to demo/POC.

• 4Embed the chosen script variant into call coaches, sequencing platforms, and sales playbooks; train reps to follow intent/signals and use the single CTA close verbatim.

Lock required inputs and supply crisp proof points

Always populate the proof_points and common_objections fields with short, verifiable bullets. The script links claims only to those proof points; vague or missing proof points will either trigger a clarifying question or force the generator to frame claims as questions. Keep proof points one‑line and avoid long narratives.

Works Best With

When to use this 10‑minute discovery script pack

• You have concise inputs for offer, ICP, top pain points, proof points, common objections, and a single primary CTA.

• Buyer channel and roles are specified (phone/Zoom/in‑person) so the script respects meeting conventions.

• Proof points include short, verifiable outcomes or integrations the script can cite directly (no invented metrics).

• Use for A/B testing short discovery calls that must finish with a single, production‑ready next step (demo/POC).

Prompt Template

# Revenue Copy Prompt Blueprint (Conversion & Sales)

## Goal
- Convert a 10‑minute discovery call into a confirmed next step: secure a commitment to {{primary_cta}} (demo / POC / evaluation) by the end of the call. Measure success as a clear verbal agreement or scheduled calendar invite.

## Inputs
Provide the following concise inputs (if any required input is missing, the generator must ask one targeted clarifying question before producing the script):
- Offer + primary benefit: {{offer_and_primary_benefit}}
- Ideal customer profile: {{ideal_customer_profile}}
- Top prospect pain points (3 max): {{top_pain_points}}
- Decision criteria and buying timeline: {{decision_criteria_and_buying_timeline}}
- Buyer roles and meeting channel (phone/Zoom/in-person): {{buyer_roles_and_channel}}
- Proof points (short bullets: metrics, case studies, customer names): {{proof_points}}
- Common objections (short bullets): {{common_objections}}
- Primary CTA text (exact ask you want on the call): {{primary_cta}}

## Prompt
You are a sales enablement copywriter. Use the inputs to generate a one‑shot, time‑boxed 10‑minute discovery call script that a seller can read verbatim or lightly personalize. Produce outputs in the exact order and headings specified below. Enforce specificity: every claim must cite one of the provided {{proof_points}} or be framed as a question. If any input above is missing, stop and ask exactly one targeted clarifying question naming the missing input.

Script requirements (must follow precisely):
1. Timebox the call: open with a 15-30s purpose + agenda check and state the measurable outcome (schedule demo/POC). Keep opening <= 60s total.
2. Provide exactly 6 diagnostic discovery questions. For each question include: 
   - the question text (one line),
   - the intent (one short phrase),
   - the ideal answer signals (2-3 bullet phrases the rep should listen for),
   - one concise follow-up prompt if the prospect gives a short/ambiguous answer.
3. After questions 2, 4, and 6 include a single-line value‑framing transition that links the prospect's likely pain to {{offer_and_primary_benefit}} using a concrete proof point from {{proof_points}}.
4. Provide 3 objection branching replies for the top 3 objections from {{common_objections}}. For each objection include:
   - the objection label,
   - a 20-30s scripted reply (verbatim) that acknowledges, reframes, and offers a low‑risk next step,
   - a short note on the ideal outcome after using the reply (e.g., "move to scheduling demo", "agree to send ROI data").
   Responses must not make fabricated claims; use only items from {{proof_points}} for credibility.
5. Include a concise next‑step close (one paragraph, 2-3 lines) that asks for {{primary_cta}}, proposes a specific time window, and gives a single commitment choice (e.g., "Yes—book demo" or "Not right now—send brief summary"). Only one CTA must be used in the script.
6. Add a 1-2 line optional fallback close for prospects who need internal buy‑in, specifying the exact artifact to send and the decision criteria to confirm.
7. Keep total script length suitable for a 10‑minute call: opening + six questions + three transitions + objection replies + closes. Use plain, professional language; avoid hype, clichés, and unsupported guarantees.

Produce the call script with these exact section headings and formatting. Use bold for timeboxes and important phrases. Do not add extra CTAs, marketing copy, or administrative chatter.

## Output Format
Produce the final script in Markdown with these sections in strict order:
- Opening (timeboxed)
- Agenda check (bullet list)
- Diagnostic Questions (numbered 1-6; each question with intent, ideal signals, follow-up)
- Value‑Framing Transitions (inline after Q2, Q4, Q6)
- Objection Branching Replies (3 items)
- Next‑Step Close (primary CTA)
- Fallback Close (for internal buy‑in)
- Assumptions (only include this short block if any input was missing; list what was assumed in 1-2 bullets)

Assumptions must be omitted entirely when all inputs were provided.

## Guardrails
- No hypey language or marketing clichés (ban phrases like “industry‑leading”, “game‑changer”, “best-in-class”).
- Claim hygiene: do not invent metrics, customers, or guarantees. Only use facts from {{proof_points}} or frame as questions (e.g., “Do you …?”).
- One primary CTA only: use {{primary_cta}} verbatim in the Next‑Step Close; do not present alternatives in the main close.
- Keep each scripted reply ≤ 30 seconds of spoken time (~45-60 words).
- Respect meeting channel conventions (use “screen share” only if {{buyer_roles_and_channel}} includes Zoom).
- Language must be professional, concise, and oriented to scheduling a follow-up evaluation.

## Examples
Example excerpt (style guide — use this tone and specificity):

Opening (30s)
- **Purpose:** Quick 10‑minute check to confirm whether we should schedule a 45‑minute demo to validate ROI.
- **Timebox:** 10 minutes total.

Proof block (used in a transition)
- **Proof:** In a recent deployment we reduced onboarding time by 42% for a company in your sector (customer: Acme Corp; outcome: 6‑week acceleration).

Variables

Usage Notes

Not for

• • Generating medical, legal, or regulated financial advice or claims

• • Replacing long technical discovery or workshops (>30 minutes)

• • Producing multi‑page proposals or formal contracts

Do not include

• • Fabricated metrics, customer names, or guarantees (the generator will only cite supplied proof points)

• • Multiple CTAs in the primary close (the script enforces one CTA)

• • Hypey marketing clichés (e.g., “industry‑leading”, “game‑changer”) or extra administrative chatter outside the script

10‑Minute Discovery Call Script — One‑Shot Generator

Generate a one‑shot, production‑ready 10‑minute discovery call script (Markdown) that includes a short opening, exactly six diagnostic questions with intents/signals/follow-ups, value‑framing transitions after Q2/Q4/Q6, three objection branching replies tied to supplied proof points, and a single primary CTA close.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

• Auto-fill & personalize from your inputs

• AI-assisted edits: tone, structure, constraints

• Attach context so outputs stay consistent

• Iterate and save versions

What you'll get

Output format

Markdown

Best used when

• When working on template or detailed.

Avoid when

• Generating medical, legal, or regulated financial advice or claims

Sign in to save, like, or rate this prompt.

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

Primary Cta

Provide the key details needed for this variable.

Offer And Primary Benefit

Provide the key details needed for this variable.

Ideal Customer Profile

Provide the key details needed for this variable.

Top Pain Points

Provide the key details needed for this variable.

Decision Criteria And Buying Timeline

Provide the key details needed for this variable.

Buyer Roles And Channel

Provide the key details needed for this variable.

Proof Points

Provide the key details needed for this variable.

Common Objections

Provide the key details needed for this variable.

Rules

• Provide concise required inputs: offer + primary benefit, ideal customer profile, up to 3 top pains, decision criteria & buying timeline, buyer roles & channel (phone/Zoom/in‑person), short proof points, top common objections, and the exact primary CTA text.

• Run the generator and review the Markdown script; personalize only the 2-3 bracketed fields (names, single example) and confirm proof points cited match your input.

• Create 2-3 A/B variants by changing question order, wording, or objection phrasing and run small tests across SDRs/AEs to compare conversion to demo/POC.

• Embed the chosen script variant into call coaches, sequencing platforms, and sales playbooks; train reps to follow intent/signals and use the single CTA close verbatim.

Canonical Examples

Input: Sales enablement automation for mid-market B2B SaaS (Zoom meeting). Primary CTA: "Schedule a 30-minute demo". Offer: Automate personalized outbound assets to reduce proposal turnaround and increase reply rates. ICP: Mid-market B2B SaaS with >50 sales reps. Top pains: inconsistent outreach, slow proposal generation, poor personalization. Decision criteria/timeline: must integrate with Salesforce; trial within 30 days. Buyer roles/channel: Head of Sales + SDRs; Zoom. Proof points: "Reduced proposal turnaround by 40% for BetaCo"; "20% increase in reply rates in pilot with Delta Inc." Common objections: "Too expensive", "No bandwidth to implement", "We're happy with current tools."

Loading result...

Failed to load output.

Opening (30s)
- **Purpose:** Quick 10-minute check to confirm whether we should Schedule a 30-minute demo.
- **Timebox:** 10 minutes total.

Diagnostic Questions (excerpt):
1. What is your current process for generating proposals? (Intent: process mapping; Ideal signals: manual PDF edits, >48h turnaround...)

Value‑Framing Transition after Q2: **Proof:** Reduced proposal turnaround by 40% for BetaCo — we typically automate the parts that add the biggest time savings.

Why it works: The script enforces a tight timebox, six diagnostic questions that map to listed pains and decision criteria, and uses only the provided proof points for credibility. It includes three objection branches that reference proof points and ends with a single explicit CTA — making it production-ready for SDRs and AEs to A/B test.

Input: Compliance automation for healthcare SaaS (phone meeting). Primary CTA: "Book a 45-minute POC". Offer: Automate SOC 2 evidence collection to shorten audit prep. ICP: Healthcare SaaS handling PHI, 200-1,000 employees. Top pains: manual audit evidence collection, audit delays, resource drain. Decision criteria/timeline: must maintain PHI controls; procurement within 60 days. Buyer roles/channel: CISO and Head of Security; phone. Proof points: "Enabled MidHealth to cut audit prep time from 6 weeks to 2 weeks (customer: MidHealth)"; "Integrated with Okta and Splunk in production for HealthCorp." Common objections: "Too expensive", "Audit not for another 6 months", "Need legal review."

Loading result...

Failed to load output.

Opening (20s)
- **Purpose:** 10 minutes to confirm fit and Book a 45-minute POC to validate SOC 2 evidence automation.

Value‑Framing Transition after Q2: **Proof:** Enabled MidHealth to cut audit prep time from 6 weeks to 2 weeks — we focus on automating evidence collection for the highest-effort controls.

Why it works: This script is tailored to security buyers on a phone call: it focuses on audit preparation pain, asks technical fit and decision questions, references only supplied proof points for credibility, and ends with a single, timeboxed POC ask so security teams can move quickly to a trial.

Works Best With

When to use this 10‑minute discovery script pack

• You have concise inputs for offer, ICP, top pain points, proof points, common objections, and a single primary CTA.

• Buyer channel and roles are specified (phone/Zoom/in‑person) so the script respects meeting conventions.

• Proof points include short, verifiable outcomes or integrations the script can cite directly (no invented metrics).

• Use for A/B testing short discovery calls that must finish with a single, production‑ready next step (demo/POC).