---
name: ai-powered-cold-call-script-generator
description: >-
  A cold call script for one persona that opens, finds the pain, pitches value, handles common objections, and asks for the meeting. Adapted from Christian Krause.
  Task type: Create. Built for Sales.
  Use when the request sounds like "Cold Call Script".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Outbound and Prospecting
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/ai-powered-cold-call-script-generator
---

# Cold Call Script

A cold call script for one persona that opens, finds the pain, pitches value, handles common objections, and asks for the meeting. Adapted from Christian Krause.

One job only: a cold call script for one persona that opens, finds the pain, pitches value, handles common objections, and asks for the meeting. Anything outside that job belongs in another file in the Outbound and Prospecting suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You will be writing a cold call script to book a meeting with a specific persona at a target company. The goal is to pique their interest, establish a need, pitch your solution's value proposition, and close for a meeting while handling common objections.

First, start with a friendly greeting and brief introduction:
<Greeting>
"Hi, this is [Your Name] from [Your Company]. I'm calling to speak with the [PERSONA] at [COMPANY]."
</Greeting>

Next, highlight a relevant research observation about their industry/role and ask for permission to pitch a potential problem:
<Research Observation>
"Before I explain why I'm calling, I wanted to mention [insert research observation, e.g. "many companies in your industry struggle with X"]. Would it be okay if I took 2 minutes to explain a common [PERSONA] challenge we help solve?"
</Research Observation>

If they agree, deliver a persona-specific problem statement linked to a trigger event or pain point:
<Problem Statement>
"Many [PERSONA] like yourself at companies like [COMPANY] face issues with [state a relevant problem, e.g. "inefficient processes leading to missed sales opportunities"]. This is often triggered by [insert trigger, e.g. "lack of visibility into the full sales pipeline"]."
</Problem Statement>

Follow this with a high-level value proposition for your solution:
<Value Proposition>
"We help [PERSONA] at [type of company] address this by [explain how your solution solves the problem, e.g. "providing a centralized CRM that gives full transparency into every deal"]."
</Value Proposition>

Close by highlighting the value of taking a meeting for the prospect:
<Close>
"I'd be happy to walk you through exactly how we've helped other [PERSONA] in [INDUSTRY] overcome similar challenges. Would you have 30 minutes sometime this week or next to discuss further? I'm confident our solution could drive significant [value props] for [COMPANY]."
</Close>

Be prepared to handle common objections:
<Objection Handling>
"I'm not interested": "I understand. Could you share more on what your current process is for [problem area]? I may have some quick suggestions that provide value."

"We already have a vendor": "That's great you have an existing solution. How has it been working for addressing [specific problem]? I'd be curious to learn more about any gaps you've experienced."

"We don't have budget": "No problem. A lot of our clients find our solutions pay for themselves very quickly through [value props]. If you're open to it, I'm happy to share some ROI examples from similar companies."

"Call me in 6 months": "Absolutely, I'm happy to follow up then. Just to prepare, what are your main priorities for [problem area] over the next 6 months?"

"Send me an email": "Will do. Could I get your email address? And what would be most helpful to include in that email to make it valuable for you?"
</Objection Handling>

The key is to be consultative, establish a need, showcase your value, and handle objections professionally to book that meeting. Let me know if you need any clarification or have additional questions!
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/ai-powered-cold-call-script-generator
- Suite: https://www.therevenueaireport.com/agent-skills/suites/outbound-and-prospecting
- Publication: The Revenue AI Report, https://www.therevenueaireport.com