LINE 01
Pre-call prep
04 PROMPTS · RUN BEFORE THE BLOCK
Nobody wins the call during the call. These four run before you pick up — research, angles, pain hypotheses, and the ask ladder — so section 2 of every script has something true to say.
NO. 01
The 90-Second Account Brief
Use this when a name pops up on your dial list and you know nothing beyond the domain.
SDRPRE-CALLRESEARCH
SCRIPT FEED — READS IN FULL
You are a sales research analyst prepping an SDR for a cold call. I sell [YOUR PRODUCT] to [PERSONA] at companies like [PROSPECT COMPANY]. Here is what I have: [PASTE COMPANY WEBSITE COPY, RECENT NEWS, OR LINKEDIN ABOUT SECTION]. Produce a pre-call brief I can absorb in 90 seconds, formatted exactly as: COMPANY IN ONE LINE (what they sell, to whom); MONEY MODEL (how they likely make money, one sentence); THREE THINGS THAT CHANGED RECENTLY (funding, hires, launches, leadership — only if present in my inputs, never invented); ONE PLAUSIBLE PRESSURE this creates on [PERSONA]; ONE OPENING ANGLE tying that pressure to [YOUR PRODUCT]. Plain language, no marketing adjectives. If my inputs don't support a section, write "NOT IN SOURCE" instead of guessing. Keep the whole brief under 120 words. Ask me up to 3 questions first if [YOUR PRODUCT] or [PERSONA] is unclear.
NO. 02
The Trigger-Event Angle Finder
Use this when you have a real signal — funding, a job post, a launch — and need a call reason that doesn't sound like surveillance.
SDRPRE-CALL
SCRIPT FEED — READS IN FULL
Act as a cold-call strategist. I am calling [PERSONA] at [PROSPECT COMPANY] because of this trigger event: [PASTE NEWS ITEM, JOB POST, FUNDING NOTE, OR LINKEDIN POST]. I sell [YOUR PRODUCT]. Give me three distinct "reason for the call" angles that connect the trigger to a problem [PERSONA] owns — not to my product. For each angle: a one-sentence version I can say out loud in under 8 seconds; the assumption it makes about the prospect; a follow-up question to ask if they confirm the assumption; and the risk if the assumption is wrong. Rank the three by how specific they are to this prospect versus any company in [INDUSTRY]. Conversational spoken English only — contractions, no jargon, nothing I'd be embarrassed to say to a real person. Mention the trigger no more than once per angle; nobody wants to feel monitored.
NO. 03
The Persona Pain Hypothesis Builder
Use this when you're opening a call block on a persona you haven't worked before.
SDRAEPLANNING
SCRIPT FEED — READS IN FULL
You are a revenue strategist who has sat through hundreds of discovery calls in [INDUSTRY]. I'm about to run a cold-call block targeting [PERSONA] at [COMPANY SIZE] companies, selling [YOUR PRODUCT]. Build me three pain hypotheses I can test on calls. For each: the pain in the prospect's own words (one spoken sentence, the way they'd complain about it to a peer — not vendor language); what in their world probably causes it; a yes/no test question I can ask in the first minute of a call to confirm or kill the hypothesis; and what to listen for in the answer. Then tell me which single hypothesis to lead with and why, in two sentences. No more than 220 words total. If [YOUR PRODUCT] can't credibly touch a pain, exclude it — I'd rather have two honest hypotheses than three padded ones.
NO. 04
The Call Objective & Fallback Ladder
Use this before a block so every dial has a primary ask and two smaller asks ready to go.
SDRPLANNING
SCRIPT FEED — READS IN FULL
Act as a sales manager who hates calls that end with "I'll send some info." For a cold-call block targeting [PERSONA] at [PROSPECT COMPANY] about [YOUR PRODUCT], define my ask ladder. PRIMARY ASK — the meeting ask, worded exactly as I'd say it, with a specific day/time pattern and a reason the meeting is worth their 20 minutes. FALLBACK ONE — a smaller commitment if they decline the meeting: a referral to the right owner, or a yes to one specific follow-up. FALLBACK TWO — the minimum viable outcome that still moves the account: permission to call back after [TIMEFRAME OR EVENT], or confirmation of who owns [PROBLEM AREA]. For each rung: exact spoken wording under 25 words, plus the signal in the conversation that tells me to drop to that rung. Never invent pressure and never offer to "send a deck" as an ask. Output as a numbered list of three rungs only.
LINE 02
Openers & full scripts
08 PROMPTS · THE CORE SHEET
Eight complete call scripts, every one drafted in the five-section structure the ticker keeps repeating: opener, reason for the call, value probe, objection pre-empt, the ask. Section 4 is the difference — the objection gets answered before it's raised.
NO. 05
The Permission-Based Opener Script
Use this as the default first-touch dial on a genuinely cold account.
SDRCOLD CALLSCRIPT
SCRIPT FEED — READS IN FULL
Write me a cold-call script for [PERSONA] at [PROSPECT COMPANY]. I sell [YOUR PRODUCT]; the problem I solve in one sentence: [ONE-SENTENCE PROBLEM]. Structure the script in exactly five labeled sections. 1. OPENER — a permission-based open ("I know I'm calling out of the blue — can I take 30 seconds?") reworded to fit my context, under 20 spoken words. 2. REASON FOR THE CALL — why them, why now, one or two sentences tied to [PERSONA]'s role, not to my product. 3. VALUE PROBE — one open question that gets them talking about how they handle [PROBLEM AREA] today. 4. OBJECTION PRE-EMPT — name the objection this persona raises most (for example "we already have something for this") and fold a disarm into the script before they can say it. 5. THE ASK — a specific 20-minute meeting ask with two day/time options. Spoken register throughout: contractions, short sentences, no adjective a rep wouldn't say on a live line. Total script under 170 words.
NO. 06
The Trigger-Event Script
Use this when a funding round, exec hire, or launch gives the call a legitimate spine.
SDRCOLD CALLSCRIPT
SCRIPT FEED — READS IN FULL
You write cold-call scripts that sound like a sharp colleague, not a telemarketer. Build a script for calling [PERSONA] at [PROSPECT COMPANY], anchored on this trigger: [TRIGGER EVENT]. I sell [YOUR PRODUCT]. Use the five-section call structure, labeled. 1. OPENER — name and company, one line, no fake familiarity. 2. REASON FOR THE CALL — the trigger, stated once, connected to a pressure it creates for [PERSONA]; "congrats on the funding" is never the whole reason. 3. VALUE PROBE — a question about how the trigger is changing their priorities in [PROBLEM AREA]. 4. OBJECTION PRE-EMPT — pre-answer "why is that your business?" by making the trigger-to-problem link explicit in one sentence. 5. THE ASK — a meeting framed as relevant to the trigger, with one concrete time. Also give me a single line to exit gracefully if they say the trigger changes nothing for them. Script under 180 words, spoken English, no exclamation points.
NO. 07
The Referral-Name Script
Use this when someone inside the account pointed you at this person.
SDRAESCRIPT
SCRIPT FEED — READS IN FULL
Draft a cold-call script for [PERSONA] at [PROSPECT COMPANY] where my way in is a referral: [REFERRER NAME AND ROLE] told me [WHAT THEY SAID — e.g. "talk to her, she owns that process"]. I sell [YOUR PRODUCT]. Five labeled sections. 1. OPENER — lead with the referrer's name in the first sentence, honestly ("[REFERRER NAME] suggested I call you") — never imply a relationship that doesn't exist. 2. REASON FOR THE CALL — what the referrer said, plus the one problem it points to. 3. VALUE PROBE — a question that checks whether they see the problem the way the referrer described it. 4. OBJECTION PRE-EMPT — handle "why didn't [REFERRER NAME] just loop me in by email?" inside the script, before it comes up. 5. THE ASK — a short meeting, with an offer to include the referrer if that's useful. Keep it under 160 words, spoken register, and flag any line where I risk overstating what the referrer actually said.
NO. 08
The Competitor-Displacement Script
Use this when the account already runs a rival tool and you know exactly which one.
AECOLD CALLSCRIPT
SCRIPT FEED — READS IN FULL
Act as an enterprise sales coach. Write a cold-call script for [PERSONA] at [PROSPECT COMPANY], who currently uses [COMPETITOR] for [PROBLEM AREA]. I sell [YOUR PRODUCT]; our honest difference: [ONE REAL DIFFERENTIATOR]. Rules first: never trash the competitor, never claim companies are abandoning them, no invented statistics. Five labeled sections. 1. OPENER — direct; name the reason you're calling into a [COMPETITOR] account without apologizing for it. 2. REASON FOR THE CALL — the one situation where [COMPETITOR] users tend to feel the gap our differentiator covers. 3. VALUE PROBE — a question that surfaces whether that gap is live for them: "when [SPECIFIC SITUATION] happens, how does the team handle it?" 4. OBJECTION PRE-EMPT — script the response to "we're happy with [COMPETITOR]": agree first, then narrow to the gap. 5. THE ASK — a comparison-shaped meeting ("worth 20 minutes to see it side by side"), one specific time. Script under 180 words, spoken English.
NO. 09
The Pattern-Interrupt Opener Pack
Use this when your usual opener is buying you hangups inside ten seconds.
SDROPENERS
SCRIPT FEED — READS IN FULL
My current cold-call opener is getting me hangups in the first ten seconds. Opener: [PASTE CURRENT OPENER]. Persona: [PERSONA] in [INDUSTRY]; product: [YOUR PRODUCT]. First, diagnose in two sentences why this opener probably trips the "salesperson alarm." Then write five replacement openers, each using a different mechanism: honest-cold ("this is a cold call — want to roll the dice?"), question-first, observation-first, permission-based, and blunt-value. Each under 22 spoken words, nothing gimmicky I couldn't repeat 60 times a day with a straight face. Mark the one you'd bet on for this persona and say why in one sentence. Finally, build that winning opener into a full five-section call script, labeled: 1. Opener; 2. Reason for the call; 3. Value probe; 4. Objection pre-empt; 5. The ask. Script under 150 words, contractions everywhere, zero marketing adjectives.
NO. 10
The Executive-Line Script
Use this when you're dialing a C-level title and you'll get one shot and roughly forty seconds.
AEENTERPRISESCRIPT
SCRIPT FEED — READS IN FULL
Write a cold-call script for reaching [C-LEVEL TITLE] at [PROSPECT COMPANY] ([INDUSTRY], roughly [COMPANY SIZE]). I sell [YOUR PRODUCT]; the business outcome it touches: [BUSINESS OUTCOME]. Executives forgive directness and punish waffle, so: five labeled sections, total under 140 words. 1. OPENER — name, company, and an honest "I'll be brief," one line. 2. REASON FOR THE CALL — the business outcome in operator language (revenue, cost, risk, or speed — pick the one that matches [BUSINESS OUTCOME]), one sentence. 3. VALUE PROBE — a peer-level question about how they currently see [PROBLEM AREA], phrased so a yes and a no both teach me something. 4. OBJECTION PRE-EMPT — script the redirect for "talk to my [SUBORDINATE ROLE]": accept it, but ask one qualifying question first so the handoff lands warm. 5. THE ASK — 15 minutes, framed as a briefing, not a demo. No flattery, and no "I know you're busy" filler beyond the opener.
NO. 11
The Closed-Lost Revival Script
Use this when you're calling back an account that went quiet or picked another option months ago.
AERE-ENGAGEMENTSCRIPT
SCRIPT FEED — READS IN FULL
Build a cold-call script for re-opening a closed-lost account. Context: [PROSPECT COMPANY] evaluated [YOUR PRODUCT] about [TIMEFRAME] ago and [WHAT HAPPENED — chose a competitor, went quiet, lost the budget]. I'm calling [PERSONA], who [WAS / WAS NOT] part of the original deal. Five labeled sections. 1. OPENER — own the history in the first sentence ("we talked last [TIMEFRAME] — it wasn't the right time"); never pretend it's a first touch. 2. REASON FOR THE CALL — what has genuinely changed since then: [WHAT CHANGED — new capability, new team, new pricing model]. Facts only; invent nothing. 3. VALUE PROBE — a question about whether the original problem got solved, stayed put, or got worse. 4. OBJECTION PRE-EMPT — script the answer to "we already made this decision": agree the decision made sense then, narrow to what changed. 5. THE ASK — a short second look, explicitly low-pressure, one concrete time. Under 170 words, spoken register, and no guilt-tripping the prospect for going quiet.
NO. 12
The Warm-Signal Call Script
Use this when they downloaded a guide or sat through a webinar and you're calling within 48 hours.
SDRINBOUNDSCRIPT
SCRIPT FEED — READS IN FULL
Write a call script for following up on a warm signal: [PERSONA] at [PROSPECT COMPANY] just [SIGNAL — downloaded a guide, attended a webinar, visited the pricing page]. I sell [YOUR PRODUCT]. The trap on these calls is assuming interest that isn't there, so calibrate for that. Five labeled sections. 1. OPENER — reference the signal in plain words, once, without any "I saw you were checking us out" creepiness. 2. REASON FOR THE CALL — the honest version: people who [SIGNAL] are usually wrestling with [PROBLEM AREA], and I'm checking whether that's true here. 3. VALUE PROBE — a question about what prompted the [SIGNAL], phrased so "just curious" is a safe answer. 4. OBJECTION PRE-EMPT — script for "I was just looking": release the pressure, then offer one useful thing with no strings attached. 5. THE ASK — branch it: a meeting ask if the probe hits a live problem, a permission-to-follow-up ask if it doesn't. Under 170 words total, both ask branches written out.
LINE 03
Live objection handling
04 PROMPTS · FOR THE MOMENT THE SCRIPT ENDS
Three stalls with worded responses, plus a drill for rehearsing the pre-empt before anyone picks up. When you want a deeper bench than four, the full collection of AI prompts for objection handling runs the same treatment across every flavor of no.
NO. 13
The Incumbent-Vendor Response Set
Use this when "we already use [COMPETITOR] for that" arrives in the first minute.
SDROBJECTIONS
SCRIPT FEED — READS IN FULL
You are a cold-call objection coach. The prospect — [PERSONA] at [PROSPECT COMPANY] — just said: "We already use [COMPETITOR] for that." I sell [YOUR PRODUCT]; our honest edge: [ONE REAL DIFFERENTIATOR]. Give me three response options I can deliver in under 10 seconds each, one per style. AGREE-AND-NARROW — validate the choice, then ask about the one situation where the incumbent tends to strain. CURIOSITY — a genuine question about how the current setup handles [SPECIFIC SITUATION]. FUTURE-SEED — accept the no, plant one specific marker, and ask permission to check back after [TIMEFRAME OR EVENT]. For each: the exact spoken wording, a tone note (pace, softness), and what a good response from them sounds like. Never argue, never disparage [COMPETITOR], never say "a lot of our customers switched from them." End with the single follow-up question that keeps the call alive if all three land flat.
NO. 14
The Send-Me-An-Email Counter
Use this when the brush-off lands and you have about five seconds to keep the line.
SDROBJECTIONS
SCRIPT FEED — READS IN FULL
The classic brush-off just happened: [PERSONA] said "just send me some information." Coach me through it for this context — product: [YOUR PRODUCT]; what I actually wanted from the call: [PRIMARY ASK]. Give me three things. (1) The two-second read: how to tell a polite hang-up from a genuine ask, based on their tone and what they said just before it. (2) Three responses under 12 spoken words each: one that agrees and attaches a single qualifying question ("happy to — so I don't clutter your inbox, is [PROBLEM AREA] even on your plate this quarter?"); one that trades the email for a micro-commitment; one that takes the email path gracefully but books the follow-up call while still on the call. (3) The subject line and first sentence of the email I'd actually send, referencing something specific they said, under 30 words combined. Spoken register, zero passive-aggression, and no "as promised" openers.
NO. 15
The No-Budget Reframe
Use this when the money or timing objection shows up — real or reflex.
SDRAEOBJECTIONS
SCRIPT FEED — READS IN FULL
Act as a sales coach who has heard "no budget" ten thousand times. [PERSONA] at [PROSPECT COMPANY] just said: [EXACT OBJECTION — "no budget," "next quarter," "bad timing"]. Product: [YOUR PRODUCT]. First, give me a two-sentence read on whether this is a money problem, a priority problem, or a polite no — and the one question that tells them apart. Then write two paths, fully worded. PATH A (it's priority, not money): a response that separates the conversation from spending — "I'm not asking you to buy anything this quarter" — and re-anchors on whether [PROBLEM AREA] is worth 20 minutes of learning. PATH B (it's a real budget cycle): lock a specific follow-up tied to their cycle — get the month, the owner, and permission to reconnect, all in one exchange. Each path under 60 spoken words. No fake discounts, no manufactured pressure, no "budgets are meant to be broken" lines.
NO. 16
The Objection Pre-Empt Drill
Use this the night before a block — rehearse section 4 before anyone picks up.
SDRPRACTICE
SCRIPT FEED — READS IN FULL
Build me an objection rehearsal set for tomorrow's call block. Context: selling [YOUR PRODUCT] to [PERSONA] in [INDUSTRY]. List the five objections this persona most plausibly raises on a cold call, ranked by likelihood, with one sentence on the fear behind each (too busy, burned before, not the owner, incumbent loyalty, money). For each objection: the exact wording I'll probably hear; a response under 25 spoken words; and a one-line "pre-empt" version — how I'd defuse it inside section 4 of my call script before it's ever raised. Then turn the set into a drill: quiz me one objection at a time in random order, wait for my typed response, and grade it on tone, brevity, and whether it re-opens the conversation before showing your version. Don't start the drill until I type "go." Keep every model response free of jargon and adjectives — spoken words only.
