Write a sales script for a real prospect interaction. What I sell and the specific outcome it creates: [OFFER] Prospect and account context: [PROSPECT CONTEXT] Likely problem, trigger, and current alternative: [BUYER SITUATION] Proof I can truthfully use: [PROOF] Call type and length: [CALL TYPE AND LENGTH] Desired next step: [NEXT STEP] Write for a buyer who is busy, skeptical, and able to say no. Do not invent company priorities, personal details, results, customers, integrations, pricing, or authority. Treat any hypothesis about the prospect as a question to test, not a fact.
Produce a script with these sections: 1. Opening, 20 to 30 seconds: permission-based, relevant to the prospect’s role, and clear about why this conversation may be worth their time. 2. Discovery sequence: 6 to 8 open questions that progress from current process to consequence, priority, decision process, and timing. Include one question that exposes the cost of doing nothing. 3. Listening map: for each likely answer, give a concise follow-up question rather than a rebuttal. 4. Value bridge: connect only the discovered problem to one or two capabilities from [OFFER], then use the proof from [PROOF] without overclaiming. 5. Objection responses for “send me information,” “we already have a solution,” “no budget,” and “not a priority.” Acknowledge the concern, ask one diagnostic question, and offer a low-pressure path forward. 6. Close: a specific next step from [NEXT STEP], with two scheduling options or a clear mutual action. Use natural spoken language, short turns, and no hype. Mark optional branches clearly so I can use it live. Before answering, check that every claim is supported by [PROOF] or [OFFER], and that the close is proportionate to the call type. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [OFFER] | Describe what you sell, who it serves, and the outcomes you can support. | A workflow tool that routes vendor security questionnaires to owners and tracks answers in one place for mid-market SaaS companies. |
| [PROSPECT CONTEXT] | Provide the prospect’s role, company, relevant public facts, and relationship history. | Priya Shah, VP of Security at BrightTable, a 420-person payroll software company; she accepted a LinkedIn connection but has not replied. |
| [BUYER SITUATION] | Describe the suspected problem, trigger event, and how they likely handle it today. | BrightTable launched an enterprise plan last quarter and may be receiving more questionnaires; teams often manage them through shared spreadsheets. |
| [PROOF] | List only approved case studies, metrics, product facts, and customer examples you can state. | Customer Northwind reduced average questionnaire turnaround from 12 business days to 7; the product exports completed answers to PDF and spreadsheet. |
| [CALL TYPE AND LENGTH] | State the interaction type and available time, such as a 15-minute cold call or 30-minute demo. | A 15-minute first discovery call. |
| [NEXT STEP] | Specify the concrete action you want the prospect to take after the conversation. | Book a 30-minute working session with Priya and the person who owns sales operations. |
How to use
- Use only researched facts and approved proof points; turn anything uncertain about the account into a discovery question.
- Choose the call type before pasting the prompt because a cold call, discovery call, and demo need different openings and closes.
- Practice the discovery questions aloud and cut questions that you cannot act on after hearing the answer.
- Follow up with: “Create a two-paragraph email recap for the prospect’s answers to questions 2, 4, and 6.”
Variations
Cold call opener
Use this when you need a short opening that earns permission to continue.
Write a 45-second cold-call opener for [PROSPECT ROLE] at [COMPANY], based on this verified context: [ACCOUNT FACTS]. I sell [OFFER], and the likely relevant problem is [HYPOTHESIS]. Produce three versions: direct, peer-reference, and trigger-event. Each must ask permission, make one restrained relevance statement, and end with one diagnostic question. Do not claim the prospect has a problem or use unverified personalization. Before answering, check that every company statement appears in the supplied facts and that each version can be spoken in 45 seconds.
Demo agenda
Use this after discovery, when the buyer needs to see a focused product demonstration.
Create a [DEMO LENGTH]-minute demo script for [BUYER] evaluating [OFFER]. Discovery findings: [DISCOVERY NOTES]. Product capabilities I can show: [CAPABILITIES]. Required stakeholders and next decision: [DECISION CONTEXT]. Produce a timed agenda, transition language, three use-case demonstrations tied to stated pain, questions to ask during the demo, and a close. Exclude features not relevant to the findings. Before answering, check that every demo segment answers a buyer need and that the final ask matches the decision stage.
Objection practice
Use this when a repeated objection is blocking your calls.
Help me prepare for this sales objection: [OBJECTION]. I sell [OFFER] to [BUYER TYPE]. Relevant truth I can use: [APPROVED FACTS]. Produce five response paths, each with an acknowledgment, one diagnostic question, a concise reframing, and a low-commitment next step. Include one path where the prospect is genuinely not a fit. Do not promise outcomes, discounts, or capabilities not in the inputs. Before answering, check that the response preserves buyer autonomy and does not argue before understanding the objection.
Tips
- Write the first-call script around diagnosis, because proof has little value until the buyer agrees the problem is real and important.
- Use quantified proof only with its scope: customer type, metric definition, and time frame matter as much as the number itself.
- Treat “send me information” as an incomplete request; ask what they would need that information to help them decide.
- Make the close a mutual next action, not a vague request to reconnect, and confirm who else needs to participate.
FAQ
Should a sales script include every objection?
No. Include recurring objections for the call stage, then use discovery to find the real concern. A long rebuttal library makes live conversations sound defensive.
Can I personalize a script with AI research?
Yes, but distinguish verified account facts from hypotheses. Never imply that a public event proves an internal priority.
How long should a discovery script be?
Plan fewer questions than the call allows. In a 15-minute call, a useful conversation usually needs a brief opening, four or five core questions, and time to agree on a next step.