Claude Cold Email Prompts That Actually Book Meetings (2026)

TL;DR

• Six copy-paste Claude cold email prompts — first-line personalization, pain-point hooks, job-change signals, competitor displacement, 5-step sequences, and breakup emails.
• Every prompt uses XML tags (<context>, <task>, <constraints>) — the structure Claude parses most reliably.
• The single rule: replace every bracket with real data. "[Company]" produces templates. "Acme Corp, just hired a VP of Sales, Series B" produces replies.
• SyncGTM enriches each prospect automatically — job changes, LinkedIn posts, intent signals — so these prompts run at scale without manual research.
• Average B2B cold email reply rate is 1–5%. Personalized emails with relevant triggers consistently hit 3–8%.

Overview

Most Claude cold email prompts on the internet fail for the same reason: they treat Claude like a template engine. They give it a prospect's name, title, and company — and expect a personalized email back.

That's not how it works. Claude writes what you give it to work with. Generic input produces the kind of email that gets deleted in two seconds.

This guide covers six production-tested prompts for B2B outreach, built around the triggers that actually drive replies: job changes, pain signals from job postings, LinkedIn activity, competitor gaps, and intent data. Each prompt uses XML tags Claude is built to parse — with enough context to produce output worth sending.

For a broader library covering prospecting, discovery, and CRM workflows, see the full Claude Code prompts for sales guide.

Why Most Claude Cold Email Prompts Fail

There are two failure modes. Both are fixable.

Failure 1: Placeholder input.You paste in a prompt with "[Prospect Name]", "[Company]", "[Pain Point]" and don't replace them with real data. Claude fills the brackets with generic language. The output sounds like every other cold email in that prospect's inbox.

Failure 2: Missing context.You give Claude a name and title but no trigger — no reason why you're reaching out now. Without a trigger, Claude can't write a specific opening line. It defaults to "I noticed your company is growing" or "I wanted to reach out" — both of which scream automation.

The fix for both: feed Claude the trigger before asking it to write. A job change, a LinkedIn post, a recent funding round, a job posting that reveals a pain — these are the details that make an email worth opening.

According to McKinsey research, personalization done right increases revenue by 10–15%. Done poorly, it damages trust more than generic outreach does.

The Anatomy of a Meeting-Booking Prompt

Every prompt in this guide follows the same four-part structure:

1. Role: Tell Claude who it is. "You are a B2B copywriter specializing in outbound." This primes it to write from the right perspective.
2. Context block (<context>): Your prospect data — name, title, company, trigger, your product, one customer result. The more specific, the better the output.
3. Task block (<task>): What to produce. The email format, key elements to include, what to avoid.
4. Constraints (<constraints>): Word count, banned phrases, tone. Claude follows constraints reliably when they're explicit.

Claude handles XML tags better than plain brackets or numbered instructions. Separate your data from your instructions — don't mix them in the same block.

Prompt 1: First-Line Personalization

The opening line is where cold emails win or lose. This prompt generates a personalized first line from any trigger — LinkedIn post, company news, job posting, or recent hire.

Use it standalone to fill a [FIRST_LINE] slot in your existing template, or as part of a full email prompt.

You are a B2B cold email copywriter specializing in personalized openers.

<context>
Prospect: [Full Name], [Exact Title] at [Company Name]
Trigger: [Paste the LinkedIn post text / news headline / job posting title / funding announcement]
My product: [Product name] — [one-sentence value prop]
</context>

<task>
Write 3 personalized opening lines that:
- Reference the trigger directly (name the post, the hire, the news)
- Connect the trigger to a pain my product solves
- Are under 25 words each
- Sound like a human observed this, not a bot that scraped it
</task>

<constraints>
- No "I came across your profile"
- No "I wanted to reach out"
- No rhetorical questions as openers
- Do not mention my product in the first line
</constraints>

For more on crafting subject lines that match your personalized openers, see the subject line for cold email guide.

Prompt 2: Pain-Point Hook from a Job Posting

Job postings are a goldmine. They reveal the exact problem a company is trying to hire away. This prompt extracts the pain signal and builds a cold email around it.

You are a signal-based cold email writer.

<context>
Company: [Company Name]
Job posting title: [e.g., "Head of Revenue Operations"]
Job posting text:
[Paste the full responsibilities or requirements section]

My product: [Product name] — [one-sentence value prop]
Comparable customer result: [Specific metric — e.g., "cut RevOps reporting time by 4 hours/week"]
</context>

<task>
Write a cold email to the hiring manager or a senior stakeholder that:
1. Opens by referencing the hire (without saying "I saw your job posting")
2. States the underlying problem the hire is meant to solve
3. Positions my product as something that solves that problem now
4. References the customer result
5. Ends with a specific, low-friction CTA (15-minute call, not "let me know")
</task>

<constraints>
- Under 100 words in the body
- Include a subject line (under 8 words, no question mark)
- First person, plain language
- No buzzwords: "robust", "seamless", "leverage", "synergy"
</constraints>

Prompt 3: Job-Change Signal Email

A new VP, a new Head of Sales, a new RevOps hire — these are the highest-intent triggers in B2B outreach. New executives have 90 days to prove themselves and they're actively looking for tools to do it.

You are a B2B sales rep reaching out to a new executive at a target account.

<context>
Prospect: [Name], just started as [New Title] at [Company]
Previous role: [Previous title + company, if known]
Company context: [Size / industry / funding stage / recent news]
My product: [Product name] — [value prop]
One result a similar exec achieved: [Specific metric within 90 days of adopting the product]
</context>

<task>
Write a cold email that:
- Acknowledges the new role (congratulations without being sycophantic)
- States one specific challenge new [Title] typically face in the first 90 days
- Connects that challenge to what my product solves
- References the comparable exec result
- Ends with a soft ask (not a calendar link in the first email)
</task>

<constraints>
- Under 90 words
- Subject line included (reference their new role, under 8 words)
- No "I hope this email finds you well"
- Do not ask if they have time to chat — propose a specific time or ask a yes/no question
</constraints>

SyncGTM's job-change signal tracks when contacts switch roles across your target accounts. Pair that data with this prompt and you're reaching every new hire in your ICP within 48 hours of their start date.

Prompt 4: Competitor-Displacement Email

When a prospect uses a known competitor, the email that works isn't "we're better." It's the one that surfaces a pain the competitor creates — without attacking the competitor directly.

You are a competitive sales specialist writing displacement outreach.

<context>
Prospect: [Name], [Title] at [Company]
Competitor they use: [Competitor name — confirmed via tech stack or LinkedIn mention]
Known limitations of that competitor (from G2 reviews or public feedback):
- [Limitation 1]
- [Limitation 2]
My product's specific advantage:
- [Advantage 1 — specific, verifiable]
- [Advantage 2 — specific, verifiable]
My product: [Product name] — [value prop]
</context>

<task>
Write a cold email that:
1. Opens by validating their choice of [Competitor] (fair, not sycophantic)
2. Asks one question that surfaces a known gap without naming the competitor as the problem
3. Briefly introduces my product as an alternative worth 15 minutes
4. Ends with a low-friction CTA
</task>

<constraints>
- Do NOT say "[Competitor] is bad" or use attack language
- Under 90 words
- Subject line included
- Be honest — only reference real, verifiable competitor limitations
</constraints>

For teams doing this at scale against a defined set of competitors, see how to build this into a full Claude Code sales cadence.

Prompt 5: 5-Step Follow-Up Sequence

Most replies come after touch 3 or 4 — one email is never enough. This prompt generates a full five-email sequence in a single run, each with a different angle so nothing repeats.

You are a B2B outbound sequence strategist.

<context>
Prospect: [Title] at [Company type — e.g., "Series B SaaS, 80-200 employees"]
My product: [Product name] — [value prop]
Pain we solve: [Specific problem, not generic]
One customer result: [Metric]
</context>

<task>
Write a 5-email cold outreach sequence. Each email must use a different angle:

Email 1 (Day 1): Trigger-based opener — reference a specific signal + CTA
Email 2 (Day 3): Social proof — lead with a customer story, soft ask
Email 3 (Day 7): Teach something — one useful insight related to their role, no hard pitch
Email 4 (Day 14): Direct ask — "Have you had a chance to look at this?"
Email 5 (Day 21): Breakup email — leave the door open, close the loop

For each email:
- Under 80 words in the body
- Subject line (under 8 words)
- No email may repeat a point made in a previous email
- Escalate directness from Email 1 to Email 5
</task>

<constraints>
- No "just checking in" in any email
- No "I wanted to follow up on my last email"
- Each email must stand alone if the prospect missed the previous one
</constraints>

For more on personalizing each email in the sequence with real contact data, see how to personalize sales emails.

Prompt 6: Breakup Email

A well-written breakup email does two things: it closes the loop honestly, and it occasionally gets a reply from a prospect who forgot to respond. The key is removing guilt while making it effortless to re-engage.

You are a B2B sales rep sending a final outreach to a prospect who hasn't responded.

<context>
Prospect: [Name], [Title] at [Company]
Touchpoints sent: [Number — e.g., "4 emails over 3 weeks"]
What we discussed or offered: [Brief description]
Why they might not have responded: [Timing / budget / not the right person / just busy]
</context>

<task>
Write a breakup email that:
- Acknowledges the silence without guilt-tripping or passive aggression
- Gives them one specific, easy way to re-engage if the timing changes
- Is honest and direct — under 55 words
- Ends with "no action needed" framing

Include subject line. Do not use "I'll take the hint" or "I guess you're not interested."
</task>

How SyncGTM Makes These Prompts Better

Every prompt above has a <context>block with a "trigger" field. That field is where most outbound teams fall short — they either don't have the data, or they spend 20 minutes per prospect finding it manually.

SyncGTM automates the context. Here's what it feeds into each prompt type:

Instead of switching between LinkedIn, company websites, and Google to research each prospect, SyncGTM pulls structured data via MCP tools. Feed that into Claude's context block and run the prompt — the whole loop takes under 30 seconds per prospect.

SDRs using this workflow on Claude Code for SDRs report cutting research time from 15–20 minutes per prospect to under 2 minutes.

See SyncGTM pricing to explore the plan that fits your outbound volume.

Prompt Comparison

Conclusion

Claude can write cold emails that get replies. The barrier isn't the model — it's the input.

Every prompt in this guide is built around a specific trigger because that's what separates a cold email that lands from one that gets deleted. Job changes, job postings, LinkedIn activity, competitor tech stack — these signals exist in your target accounts right now. The prompts above are the mechanism to turn them into personalized outreach at scale.

Start with one prompt. Pick the trigger type most common in your pipeline — job changes if you sell to new executives, job postings if you sell to growing teams, competitor stack if you're displacing a known tool. Run it on 10 real prospects and compare results to what you were sending before.

For teams ready to automate beyond copy-paste, SyncGTM connects Claude to your enrichment data so these prompts run on every new lead automatically. Enrich, prompt, draft, send — no manual research. Start free or read the full personalized sales email templates guide for more email frameworks.