Install
openclaw skills install cold-call-script-generatorGenerate personalized cold call openers, voicemail scripts, cold email opening lines, and full multi-touch outbound sequences for B2B sales reps, SDRs, and f...
openclaw skills install cold-call-script-generatorGenerate personalized cold call openings, voicemails, and cold email opening lines for B2B sales motions. Combines real prospect research, ranked pain hypotheses, pattern-interrupt opening frameworks, and a full objection-handling library into ready-to-use scripts and 14-day multi-touch sequences.
Invoke this skill when you have a list of prospects (or one named account) and need a script that actually books meetings instead of getting hung up on.
Basic invocation:
Write me a cold call script for selling [product] to [ICP] Draft a voicemail for a CTO at a Series B fintech Build a 14-day outbound sequence for [target persona]
With context:
Here's the prospect's LinkedIn and the company's funding announcement, write the opener They already use Salesforce — write me an opener that doesn't sound like every other displacement pitch I'm a founder selling to heads of product, write three openers in different tones
The agent produces opener variations, full call scripts with branches, voicemail templates, objection rebuttals, and a touch-by-touch cadence — calibrated to the ICP's seniority, function, and likely buying stance.
Before writing a single line, the agent gathers (or asks for) signal. Cold scripts that reference nothing specific feel like spam — the goal is one concrete reference point per call.
The 9-point research checklist:
| Source | What to extract | Why it matters |
|---|---|---|
| LinkedIn profile | Tenure, prior roles, recent posts, mutual connections | Tenure under 6 months = fresh mandate, eager to change things |
| LinkedIn company page | Headcount, growth rate, recent hires by function | Hiring 10 SDRs = sales infra spend coming |
| Recent funding | Round size, lead investor, date | Just-funded buyers spend, 6-month-old funded buyers consolidate |
| Job postings | Open roles, especially in your buyer's function | "Hiring senior SRE" = pain in reliability tooling |
| Tech stack (BuiltWith, Wappalyzer, job posts) | Current tools they use | Avoid pitching what they already have; find adjacent gaps |
| News and press | Launches, layoffs, exec changes | Exec change = 90-day window of buying receptivity |
| G2 / Trustpilot reviews of competitors | What customers complain about | Direct pain language to mirror |
| Earnings calls / shareholder letters (public co) | Stated priorities | Map your pitch to their CEO's stated agenda |
| Podcasts / conference talks by the prospect | Their own words on priorities | Highest-trust opener: quote them back to themselves |
Minimum viable research: name, title, company, one specific signal. Anything less and the call is a coin flip.
For each ICP, the agent generates exactly three pain hypotheses, ranked by signal strength.
Signal strength tiers:
Example — ICP: VP Engineering at 200-person Series C SaaS:
Hypothesis 1 (A-tier): "You posted about on-call burnout three weeks ago on LinkedIn"
Signal: direct public statement
Opener angle: empathy + specific tool fix
Confidence: 95%
Hypothesis 2 (B-tier): "Series C scale typically breaks the homegrown CI pipeline around now"
Signal: stage-pattern inference
Opener angle: pattern-recognition expertise
Confidence: 60%
Hypothesis 3 (C-tier): "Engineering productivity metrics are probably hard to defend in board meetings"
Signal: category-default for the role
Opener angle: peer-benchmark conversation
Confidence: 30%
The agent always offers all three and recommends starting with A-tier; B-tier is fallback when A signals are absent.
The opener has three jobs in 8 seconds:
Eight tested opener variations:
1. The Honest Cold Call
"Hi [Name], this is [You] — I'll be transparent, this is a cold call. Can I have 27 seconds to tell you why I picked up the phone, and then you can tell me to go away?"
Works because: explicit honesty pattern-interrupts the "is this a sales call?" frame. The specific number ("27 seconds") signals you've thought about respecting their time.
2. The Permission-First
"Hey [Name], it's [You] from [Company]. Did I catch you at a terrible time?"
Works because: prospects expect "good time" — flipping it earns a "no, what's up?" 70% of the time (per Gong data on 100K+ calls).
3. The Reference-Their-World
"Hi [Name], I saw your post on [specific topic] — that's actually why I called. Got 30 seconds?"
Works because: signals you did homework before the call, not after they answer.
4. The Peer-Drop
"Hi [Name], I just got off a call with [peer at similar company] — they had this exact problem with [pain]. Wanted to ask if it's on your radar too."
Works because: lateral peer pressure is the strongest B2B social proof. Only use if the peer reference is real and verifiable.
5. The Disqualification Opener
"Hi [Name], I'm not sure if this is relevant to you — we work with engineering teams using [stack]. Are you running [stack] today, or have you moved off?"
Works because: framing as "not sure if relevant" lowers their guard. Asking about stack gives them an easy first answer.
6. The Provocative Insight
"Hi [Name] — quick question: how are you measuring [specific metric] today? Most VPs of [function] we talk to are flying blind on this and didn't realize it until they saw what we were measuring."
Works because: implies they might have a blind spot without insulting them. Triggers curiosity.
7. The Trigger-Event Opener
"Hi [Name], I saw [Company] just [funding/launch/hire] — congrats. The reason I'm calling: most companies hitting this stage start running into [pain] within 90 days. Wanted to check if you're seeing that."
Works because: ties the call to a specific event in their life. Creates relevance and time-pressure framing.
8. The Founder-To-Founder (founder-led sales only)
"Hi [Name], this is [You], I'm the founder of [Company] — calling personally because [specific reason]. I'll keep it under 90 seconds. Worth hearing?"
Works because: founder-on-founder asymmetry — heads of product / VPs accept founder calls they'd reject from SDRs. Only authentic when actually the founder.
Opener anti-patterns (the agent flags these):
80%+ of cold calls go to voicemail. A great voicemail gets a callback rate of 3-8%; a bad one is 0%. Target length: 17 seconds, no more.
The 17-second structure:
[0-3s] Name + company: "Hi [Name], this is [You] from [Company]"
[3-8s] Specific reason: "Calling because I saw [specific signal]"
[8-13s] Value tease: "We help [peer companies] with [specific outcome]"
[13-15s] Callback ask: "Worth a 15-min look?"
[15-17s] Number, slowly: "[Number], again [Number]"
Example voicemail (Series B fintech CTO, hiring SREs):
"Hi Maria, this is Jordan from Sentinel. I saw you're hiring three senior SREs — most fintechs hitting that scale waste six months on alerting noise before they fix the root cause. We helped Plaid cut their on-call pages by 60% in 90 days. Worth a 15-minute look? 415-555-0142, again 415-555-0142."
Word count: 47. Spoken at normal pace: ~17 seconds.
Voicemail rules the agent enforces:
The agent provides a scripted response for every common objection, with the underlying principle named so the rep can adapt.
"Not interested."
Principle: they're not rejecting you, they're rejecting the unknown. Acknowledge, narrow the claim, redirect to a question.
"Totally fair — you don't know me yet. Quick question, just so I don't waste your next call: are you handling [specific pain] in-house today, or have you outsourced it? If neither is a fit I'll get out of your way."
"Send me an email."
Principle: this is the polite hangup. Send the email AND keep the conversation going.
"Happy to — what's the best email? While I have you, just so I send something actually relevant and not a generic deck: are you more focused on [option A] or [option B] right now?"
Then: send the email within 5 minutes referencing the conversation. Subject line: "[Name] — as discussed, the [option they picked] piece"
"We already use [competitor]."
Principle: don't trash the competitor. Compliment-then-pivot.
"[Competitor] is a solid product — half our customers came from there. Most of them switched because of [specific gap]. Are you running into that, or has [Competitor] been working well on that front?"
Anti-pattern: "Oh, [Competitor] is terrible because..." — instantly destroys trust. The prospect picked Competitor; insulting it insults them.
"No budget."
Principle: budget objections are usually priority objections in disguise. Reframe.
"Got it — budget's tight everywhere right now. Just so I understand: if we could show that [outcome] would [save X / earn Y] within [timeframe], is this the kind of thing you'd find budget for, or is it genuinely not on the priority list this year?"
This separates "no money" (call back next quarter) from "not a priority" (disqualify).
"Call me back later / next quarter."
Principle: vague timing = soft brush-off. Pin down a specific reason or move on.
"Happy to. Just so the next call is useful — what would change between now and then? Is it [budget cycle / project finishing / hiring this role]? That way I can come back with something tied to whatever's actually shifting."
If they can't name a specific change, the timing is fake — politely disqualify and don't waste a follow-up.
"How did you get my number?" (hostile)
Principle: be honest, brief, and don't grovel.
"Public profile — your direct line was on [source]. Happy to remove you from our list if you'd prefer, or I can take 30 seconds to tell you why I called and you can decide?"
"Just put me on your do-not-call list."
Principle: comply immediately, do not pitch. This is a TCPA / GDPR moment. Confirm and close.
"Done — you're off the list now. Sorry for the interruption."
Then add to DNC list immediately (see Compliance section).
A cold call is not one event; it's the second or fourth touch in a sequence. Connect rates jump 3-5x when calls follow LinkedIn engagement and email warmup.
The 14-day, 11-touch sequence:
| Day | Channel | Touch | Purpose |
|---|---|---|---|
| 1 | View profile (no connect request yet) | Trigger profile-view notification | |
| 2 | Cold email #1, value-led | Plant the name | |
| 3 | Connection request, no pitch in note | Build the network bridge | |
| 4 | Call | Cold call #1, voicemail if missed | Voice + name pairing |
| 5 | — | Skip day (signal scarcity) | Avoid spam vibe |
| 6 | Cold email #2, different angle | Second hypothesis | |
| 8 | Call | Cold call #2, different time of day | Try off-peak hours |
| 9 | Engage with their content (real comment) | Earn presence in their feed | |
| 11 | Cold email #3, "breakup" framing | Trigger loss-aversion | |
| 13 | Call | Cold call #3, final attempt | Last call attempt |
| 14 | Breakup email — "closing the loop" | Often gets the highest reply rate |
Cadence design principles the agent applies:
The same words land differently with different buyers. The agent tunes vocabulary, pace, and stance per persona.
By function:
| Persona | Tone | Vocabulary | Pace | Stance |
|---|---|---|---|---|
| CTO / VP Eng | Peer-technical | Specific tools, metrics (p99, MTTR, etc.) | Fast, dense | Skeptical-equal — they assume you don't get it; prove you do in 10 seconds |
| CMO / VP Marketing | Story-led | Outcomes, brand, "lift", attribution | Conversational, warm | Curious-skeptical — they buy stories before specs |
| CFO / Finance | Numbers-first | ROI, payback period, $/unit, churn | Slow, precise | Adversarial-default — every claim needs proof |
| Founder / CEO (early-stage) | Direct, no fluff | Speed, leverage, distraction-cost | Fast, ruthless | Pragmatic-impatient — they hate process |
| Founder / CEO (PE-owned) | Boardroom-formal | EBITDA, multiples, governance | Measured | Risk-averse — they fear breaking what works |
| Head of Product | Outcome-and-craft | User outcomes, velocity, NPS, activation | Conversational | Curious-discerning — they probe judgment |
| Procurement | Process-and-terms | SOC2, MSA, payment terms, redlines | Slow, exhaustive | Default-no — their job is to slow deals down |
| End-user IC (no budget) | Peer-helpful | Their daily pain, time saved | Conversational | Eager-but-powerless — coach them on internal selling |
Calibration examples:
CTO opener: "Most platform teams at your scale are seeing p99 drift past 800ms on the deploy hot path — is that landing on your plate?"
CMO opener: "We just helped [peer brand] move from 'attribution is broken' to closing the loop on first-party data inside 60 days — wanted to ask if that story is one you're trying to tell to your CEO."
CFO opener: "I'll be quick — every dollar in [category] tooling at companies your size has a measurable payback window. We average 4.2 months. Worth 15 minutes to see if your numbers would line up?"
Founder opener: "Hey [Name], founder-to-founder — I won't waste your time. We do [one sentence]. Specifically for early-stage teams like yours. 10 minutes this week worth it, or not yet?"
Cold outreach is regulated. The agent always includes the relevant compliance reminders for the rep's region and prospect region.
TCPA (US — Telephone Consumer Protection Act):
GDPR (EU/UK prospects):
CAN-SPAM (US email):
Universal compliance hygiene the agent recommends:
The agent ends every script delivery with the metrics to watch and what "good" looks like.
The four cold-call metrics:
| Metric | Definition | Bad | Average | Good | Elite |
|---|---|---|---|---|---|
| Connect rate | Live conversations / dials | <5% | 8-12% | 15-20% | 25%+ |
| Conversation rate | Conversations >60s / connects | <30% | 40-50% | 60-70% | 80%+ |
| Meeting-set rate | Meetings booked / conversations | <10% | 15-20% | 25-35% | 40%+ |
| Meeting-held rate | Meetings attended / meetings booked | <50% | 60-70% | 75-85% | 90%+ |
Cold email benchmarks (B2B, well-targeted):
Sequence-level benchmark:
Diagnostic logic the agent uses:
Symptom: Connect rate < 8%
Likely causes: bad list, wrong time of day, spam-flagged number, ICP mismatch
Fix: list hygiene, rotate caller ID, test 7-9am and 4-6pm windows
Symptom: Connect > 15% but conversation rate < 30%
Likely cause: opener is failing the pattern interrupt
Fix: A/B test opener variations, record and review hangup points
Symptom: Conversation > 60% but meeting-set < 15%
Likely cause: weak value tease or no clear next step
Fix: rewrite the close, add specific calendar offer, reduce friction
Symptom: Meeting-set healthy but held rate < 60%
Likely cause: weak confirmation cadence, prospect not bought in
Fix: add same-day calendar invite + day-before reminder + value pre-read
Context: AE at observability platform, calling Maria Chen, CTO at a 250-person Series B fintech. Research signals: hiring 3 SREs (LinkedIn job post 2 weeks old), recent post about "alert fatigue is killing my team", company raised $40M Series B four months ago.
The call:
Rep: "Hi Maria, this is Jordan from Sentinel. I'll be straight — this is a cold call. Saw your post on alert fatigue two weeks back, that's actually why I picked up the phone. Got 30 seconds?"
Maria: "Uh, sure, go ahead."
Rep: "Appreciate it. Most fintechs at Series B with the SRE hiring you're doing tell us they spend the first 90 days drowning in noise from the legacy alerting setup before they fix it. We helped Plaid cut on-call pages 60% in their first quarter on us. Curious if alert noise is on your near-term list, or if you've already got someone solving it?"
Maria: "We're using Datadog and PagerDuty — it's working, but yeah, the noise is real."
Rep: "That's the most common stack we replace alongside, not against. We sit on top of Datadog and dedupe before PagerDuty fires. Worth 15 minutes next week to show you what that looks like with your alert volumes? I can do Tuesday at 11 or Thursday at 2."
Maria: "Thursday 2 works."
Rep: "Great — sending the invite now with two questions for you to skim beforehand so we don't waste your time. Talk Thursday."
Why it works: A-tier signal (her own post), CTO-tone (specific tools, peer-named), permission opener, complement-then-pivot on Datadog, two specific times instead of "what works for you?"
Context: Recruiter from a boutique exec search firm, calling David Park, Engineering Manager at a mid-stage AI infra startup. Research signals: 3.5 years tenure (long for the role), no recent LinkedIn activity, his old VP just left for a competitor.
The call:
Recruiter: "Hi David, this is Sam from Northpoint Search. Quick one — did I catch you at a terrible time?"
David: "I have a couple minutes, what's up?"
Recruiter: "I'll be transparent, I'm a recruiter — but I'm not pitching a job today. I work with senior eng managers in AI infra and I'm doing a market read. You've been at [Company] three and a half years which is impressive, especially given some of the recent moves on the team. Two questions, then I'll get out of your way: one, are you in build mode or coast mode right now? Two, if I called you in six months with the right director-level role, would that be useful or annoying?"
David: "Honestly, I'm in coast mode. Things have been weird since [VP] left."
Recruiter: "Heard. That's the third call this month I've had like that — there's a lot of motion in AI infra right now. Look, I won't push anything on you today. Can I send you one or two role specs over the next month, just for calibration, no commitment?"
David: "Yeah, that's fine."
Recruiter: "What's the best personal email — I don't want anything tied to your work account."
Why it works: disarms the recruiter-call defenses immediately ("I'm not pitching a job today"), references the VP departure as a real signal, low-commitment ask (just calibration emails), gets the personal email which is the real prize for a recruiter.
Context: Founder/CEO of a 12-person product analytics startup, calling Priya Rao, Head of Product at a Series C consumer app. Research signals: she gave a podcast interview 3 weeks ago about "product teams flying blind on activation metrics", company has 4M MAU.
The call:
Founder: "Hi Priya, this is Alex Kim, I'm the founder of Lumen Analytics. Calling personally — I heard your podcast with [Host] three weeks back and I literally pulled over to take notes when you described activation metrics as 'a Rorschach test'. That's the reason I picked up the phone today. I'll keep it under two minutes — worth hearing?"
Priya: "[Laughs] Sure, go for it."
Founder: "Thanks. We built Lumen specifically because every product team I worked with before this had the same problem you described — every PM had a different definition of activation, and the data team couldn't agree with any of them. We work with about 40 product teams now, and the wedge is dead simple: we let your PMs propose a definition, your data team approves it, and then everyone's looking at the same number forever. The reason I'm calling you specifically: with 4 million MAU and the segmentation you talked about, this is exactly the scale where the disagreement gets expensive. Two questions: one, does that resonate at all? Two, would 25 minutes with me — not a sales rep, me — be useful next week?"
Priya: "Yeah, that's a real problem for us. Send me a calendar link, I'll find time."
Founder: "Will do — and one favor: when you book it, tell me the one definition of activation your team most disagrees on. I'll come ready to talk through how we'd resolve it. Talk soon."
Why it works: founder-to-Head-of-Product asymmetry, A-tier signal quoted directly, specific stage relevance (4M MAU), real two-minute promise, asymmetric-value ask (25 min with the founder, not a rep), homework request that primes the demo to be customized.
The agent produces:
Provide the list with title, company, and any signals. The agent generates a templated sequence with per-prospect personalization tokens.
The agent runs the diagnostic logic in Step 9, asks about list source, dialing windows, and caller ID setup, and recommends the highest-leverage fix.
Provide your current opener. The agent diagnoses what's working and produces 2-3 alternatives from different patterns to test.
The agent uses the founder-to-buyer pattern, keeps language plain, builds in natural pauses, and writes for spoken delivery (short sentences, no jargon).
Stop. Add to DNC immediately on all channels. The agent walks through the suppression checklist and the polite "closing the loop" email if appropriate.