Claude Code Prompts for Sales: 50 Copy-Paste Templates

TL;DR

• 50 copy-paste Claude Code prompts organized by sales task — prospecting, email, LinkedIn, discovery, objection handling, follow-up, proposals, CRM cleanup, and pipeline analysis.
• Every prompt uses role + task + output format — the structure Claude needs to return consistent, usable results.
• Prompts work in the Claude Code terminal or inside skill files for repeatable workflows.
• CRM-connected prompts (via MCP) can read and write records directly — no manual data entry.
• One rule: replace every bracket with real data. "[Company]" gets deleted. "Acme Corp, Series B, just hired a VP Sales" gets a reply.

Overview

Most Claude Code prompt libraries for sales are shallow. They show you a prompt like "Write a cold email to [company]" and call it done. That produces generic output that gets deleted.

This post is different. Every prompt here is production-tested with the full structure Claude needs — role, context, task, constraints, and output format. You'll find 50 prompts across nine sales workflows, from first-touch prospecting to CRM data hygiene.

SDR running 50 accounts or a founder doing your own outbound — these cut research and writing time from hours to minutes. For teams looking to automate beyond copy-paste, see our guide on Claude Code sales automation — which covers how to chain these prompts into full workflows.

How to Use These Prompts

Each prompt uses XML tags — <context>, <task>, <constraints> — that Claude is specifically designed to parse. This structure separates your prospect data from the instruction so Claude doesn't conflate them.

Three ways to run them:

1. Terminal (one-off): Paste the prompt into Claude Code, fill in brackets, hit Enter.
2. Skill file (repeatable): Save the prompt as a .md file in your project. Claude loads it on demand. Best for daily workflows like account research or follow-up drafts.
3. MCP-connected (automated): Connect your CRM via MCP and let Claude read deal data directly. No copy-paste. See Claude Code CRM integration for setup.

One rule: replace every bracket with real data. "[Company Name]" produces generic output. "Acme Corp (Series B SaaS, 140 employees, recently hired a VP of Sales)" produces targeted output.

Prospecting & Research Prompts

Use these before any outreach. The goal is a research brief Claude produces in under 60 seconds — the kind that used to take 20 minutes of manual tab-switching.

Prompt 1 — Account Research Brief

You are a B2B sales researcher. Your task is to create a pre-call research brief for a sales rep.

<context>
Company: [Company Name]
Website: [URL]
Recent news or trigger: [LinkedIn post / funding round / new hire / job posting]
My product: [Your product + one-line value prop]
</context>

<task>
1. Summarize what the company does in 2 sentences.
2. Identify the likely buyer title and their top 3 pain points based on the trigger.
3. List 2 relevant talking points that connect the trigger to my product.
4. Suggest the best opening line for a cold email based on this context.
</task>

<constraints>
- No filler phrases ("I hope this email finds you well", "I wanted to reach out")
- Be specific. Reference the company name and trigger directly.
- Output format: numbered list, under 150 words total.
</constraints>

Prompt 2 — ICP Fit Scoring

You are a B2B sales qualification specialist.

<context>
My ICP: [Industry / company size / tech stack / geography / signals]
Lead list:
- Company A: [description]
- Company B: [description]
- Company C: [description]
</context>

<task>
Score each company 1–10 against my ICP. For each, give:
- Score
- Top fit reason (1 sentence)
- Top disqualifier (1 sentence, or "none")
</task>

<constraints>
Output as a markdown table with columns: Company | Score | Fit Reason | Disqualifier
</constraints>

Prompt 3 — Tech Stack Intelligence

You are a B2B sales intelligence analyst.

<context>
Company: [Company Name]
Known tech stack or tools: [CRM / marketing automation / data tools visible on their site or job posts]
My product integrates with: [list your integrations]
</context>

<task>
1. Identify 2–3 workflow gaps the known tech stack suggests.
2. Map each gap to a specific feature of my product.
3. Write one sentence per gap as a talking point for outreach.
</task>

Output as a numbered list.

Prompt 4 — Buying Committee Map

You are a B2B sales strategist.

<context>
Target account: [Company Name]
Deal size: [estimated ACV]
Product category: [e.g., sales intelligence, CRM, ABM platform]
Known contacts at company: [list names and titles if any]
</context>

<task>
Map the likely buying committee:
1. Economic buyer (title + what they care about)
2. Champion (title + pain they own)
3. Technical evaluator (title + their veto criteria)
4. Blocker (most likely objection and who raises it)

For each, write one sentence on how to approach them.
</task>

Prompt 5 — Competitor Displacement Research

You are a competitive sales analyst.

<context>
Prospect currently uses: [competitor tool]
My product: [your product]
Key differentiation: [2–3 specific advantages — not generic]
</context>

<task>
1. List the top 3 frustrations users typically report about [competitor] on G2 or Reddit.
2. Map each frustration to a specific advantage of my product.
3. Write a one-paragraph "displacement" message for cold outreach.
</task>

<constraints>
Be fair. Don't fabricate competitor weaknesses. Only use known, verifiable pain points.
</constraints>

Prompt 6 — Job Posting Signal Analysis

You are a signal-based sales researcher.

<context>
Job posting text:
[Paste the full job description here]

My product: [product + value prop]
</context>

<task>
1. Identify the top 3 buying signals hidden in this job posting (tools mentioned, team size, urgency language, tech stack).
2. Infer the pain this hire is meant to solve.
3. Write a 3-sentence cold email opener that references this job posting without sounding like you read their JD.
</task>

For teams enriching accounts at scale and firing these prompts automatically, see Claude Code outbound sales.

Cold Email & Outreach Prompts

Generic context in, generic email out. Every prompt below forces specific input — which is what separates a reply from a delete. For deeper cold email strategy, see our guide to personalized cold email outreach.

Prompt 7 — First-Touch Cold Email

You are a B2B copywriter specializing in cold outbound.

<context>
Prospect: [Name], [Title] at [Company]
Trigger: [recent news / LinkedIn post / funding / hiring signal]
My product: [product name + one-line value prop]
One result a similar customer achieved: [specific metric — e.g., "cut research time by 3 hours/week"]
</context>

<task>
Write a cold email that:
- Opens with the trigger (no "I hope this finds you well")
- States the problem we solve in one sentence
- References the customer result
- Ends with one low-friction CTA (15-minute call, not "let me know if interested")
</task>

<constraints>
- Under 90 words
- No subject line provided by me — you write it (under 8 words, no question mark)
- No filler phrases, no "just checking in", no "I wanted to reach out"
- First person, plain language
</constraints>

Prompt 8 — Multi-Touch Email Sequence (5-Step)

You are a B2B outbound strategist.

<context>
Prospect: [Title] at [Company type]
Product: [product name + value prop]
Pain we solve: [specific problem]
</context>

<task>
Write a 5-email cold outreach sequence:
Email 1 (Day 1): Trigger-based opener + CTA
Email 2 (Day 3): Different angle — lead with social proof
Email 3 (Day 7): Teach something useful — no hard sell
Email 4 (Day 14): Direct ask — have you seen this?
Email 5 (Day 21): Breakup email

Each email: under 80 words. Subject line included. No email to repeat a point made in a previous email.
</task>

Prompt 9 — Email Subject Line Generator

You are a cold email subject line specialist.

<context>
Email body summary: [paste the email or describe the angle]
Prospect type: [title / industry]
Tone: [direct / curious / provocative]
</context>

<task>
Write 10 subject line options. For each:
- The subject line (under 8 words)
- Predicted open rate driver (curiosity / specificity / social proof / urgency)
- One-word risk (generic / spammy / too long / etc.)

Flag the top 3 with a recommendation.
</task>

Prompt 10 — Email Personalization at Scale

You are a B2B outbound personalization engine.

<context>
Email template:
[Paste your base email template with [PERSONALIZATION] placeholder]

Lead data:
Name: [Name]
Title: [Title]
Company: [Company]
Recent trigger: [LinkedIn activity / news / job change]
Industry: [Industry]
</context>

<task>
Replace [PERSONALIZATION] with a 1–2 sentence opening that:
- References the trigger directly
- Connects it to a pain point relevant to their title
- Sounds written by a human, not generated

Output only the completed email. No commentary.
</task>

Prompt 11 — Re-Engagement Email (Gone Dark)

You are a B2B sales rep trying to re-engage a prospect who went dark after showing interest.

<context>
Prospect: [Name], [Title] at [Company]
Last interaction: [date + what was discussed]
Stage they reached: [demo / proposal / trial / initial meeting]
Reason they likely went dark: [budget / timing / competitor / internal change]
</context>

<task>
Write a re-engagement email that:
- Acknowledges the gap without being apologetic
- Offers a new reason to reconnect (product update, new case study, changed market condition)
- Ends with a specific, low-effort ask

Under 70 words. Include subject line.
</task>

Prompt 12 — Inbound Lead Follow-Up

You are a B2B SDR following up with an inbound lead.

<context>
Lead source: [demo request / pricing page / content download]
Company: [Company Name]
Title: [Lead's title]
What they looked at: [specific page or content if known]
</context>

<task>
Write a follow-up email that:
- References exactly what they did (not "I saw you visited our site")
- Moves them toward a specific next step
- Is under 60 words
- Doesn't feel automated

Include subject line.
</task>

LinkedIn Outreach Prompts

LinkedIn connection requests have a 300-character limit. These prompts work within that constraint while maintaining specificity.

Prompt 13 — Connection Request Note

You are a B2B sales rep sending a LinkedIn connection request.

<context>
Prospect: [Name], [Title] at [Company]
Connection reason: [shared connection / their post / mutual interest / event]
</context>

<task>
Write a connection note under 280 characters that:
- States why I'm connecting (one specific reason)
- Does NOT pitch anything
- Ends with a non-question closing

Write 3 versions with different opening angles.
</task>

Prompt 14 — LinkedIn DM After Connection Accepts

You are a B2B sales rep sending a first message after a LinkedIn connection was accepted.

<context>
Prospect: [Name], [Title] at [Company]
Their recent activity: [post / comment / article they wrote]
My product: [product + value prop]
</context>

<task>
Write a first DM that:
- Acknowledges their content or activity specifically
- Asks one genuine question relevant to their work
- Does NOT include a pitch, a calendar link, or "I'd love to hop on a call"

Under 100 words.
</task>

Prompt 15 — LinkedIn Comment for Warm Engagement

You are a B2B sales rep using social selling to warm up a prospect before cold outreach.

<context>
Prospect's post: [paste the post text]
My perspective: [your genuine take on the topic]
</context>

<task>
Write a LinkedIn comment that:
- Adds a specific perspective or data point (not "great post!")
- Is 2–3 sentences max
- Makes me sound like a thoughtful peer, not a vendor

Write 2 versions.
</task>

Prompt 16 — LinkedIn Outreach Sequence (3 Messages)

You are a LinkedIn outreach strategist.

<context>
Prospect: [Title] at [Company type, size]
Product: [product + value prop]
Pain solved: [specific problem]
</context>

<task>
Write a 3-message LinkedIn DM sequence:
Message 1 (after connect): Value-add, no pitch
Message 2 (5 days later): Reference their work + soft ask
Message 3 (10 days later): Direct ask with easy opt-out

Each message under 120 words. No calendar links until Message 3.
</task>

Prompt 17 — LinkedIn Profile Research Snapshot

You are a B2B sales researcher.

<context>
LinkedIn profile text:
[Paste the prospect's About section, headline, and recent posts]
</context>

<task>
Summarize in bullet points:
1. Their primary professional focus (1 sentence)
2. Their likely top 2 pain points based on their role and posts
3. Best angle for outreach based on their content
4. One topic they've posted about that connects to my product: [product category]
</task>

Discovery Call Prompts

These prompts help before, during, and after discovery calls. Run them the night before to prepare, or paste call notes in immediately after to generate follow-up actions.

Prompt 18 — Pre-Call Research Brief

You are a B2B sales strategist preparing a rep for a discovery call.

<context>
Account: [Company Name]
Contact: [Name], [Title]
Deal source: [inbound / outbound / referral]
Known context: [what we know about their pain, stack, or company]
Call goal: [qualify / build relationship / drive to demo]
</context>

<task>
Produce a 1-page call prep brief with:
1. Top 3 discovery questions tailored to their role and company
2. Likely objections and one-line responses
3. Success metric: what does "good call" look like?
4. Suggested next step to propose at end of call

Under 200 words. Bullet format.
</task>

Prompt 19 — Discovery Question Generator (Role-Specific)

You are a B2B sales coach specializing in discovery.

<context>
Prospect title: [e.g., VP of Sales, Head of RevOps, CTO]
Company type: [industry, size, stage]
Product I sell: [product + category]
Pain hypothesis: [what I think their problem is]
</context>

<task>
Write 10 discovery questions for this persona. For each question:
- The question itself
- What it uncovers (1 sentence)
- Follow-up probe if they answer vaguely

Prioritize open-ended questions. No yes/no questions.
</task>

Prompt 20 — Call Notes to CRM Summary

You are a sales operations assistant converting raw call notes to structured CRM data.

<context>
Raw call notes:
[Paste your unstructured notes here]
</context>

<task>
Extract and format:
1. Pain points mentioned (bulleted)
2. Current solution / status quo
3. Decision criteria stated
4. Stakeholders involved (names + titles if mentioned)
5. Agreed next steps with owner and date
6. Deal risk flags (if any)
7. Suggested CRM stage (Qualified / Demo Scheduled / Proposal / Negotiation)

Output as a structured markdown summary ready to paste into a CRM note field.
</task>

Prompt 21 — Pain Quantification

You are a B2B value consultant helping a sales rep quantify a prospect's pain.

<context>
Pain described by prospect: [paste their exact words from the call]
Their team size: [number]
Estimated time spent on this problem per week per person: [hours]
Their industry average loaded salary for this role: [or use $80k/yr as default]
</context>

<task>
Calculate:
1. Annual cost of the problem (time × salary × team size)
2. A conservative ROI if my product solves 50% of the problem
3. A compelling "cost of inaction" statement under 30 words

Show your math. Present the final statement in quotable form.
</task>

Prompt 22 — Stakeholder Alignment Email Post-Call

You are a B2B account executive writing a post-discovery follow-up.

<context>
Call recap: [key pain points, agreed next steps, timeline discussed]
Prospect name: [Name], [Title]
Additional stakeholders to cc: [names if any]
Next meeting: [date / type]
</context>

<task>
Write a post-call follow-up email that:
- Recaps what we discussed (3 bullets max)
- Confirms agreed next steps with dates
- Sets expectations for what comes next
- Is under 100 words, conversational, not templated-sounding
</task>

Objection Handling Prompts

These prompts turn objections into structured responses. Paste the exact words the prospect used — Claude handles it better with verbatim quotes than summaries.

Prompt 23 — Respond to "Too Expensive"

You are a B2B sales rep handling a pricing objection.

<context>
Prospect said: "[paste exact words]"
Deal context: [company size, use case, competing solution they may use]
My pricing: [plan + price]
ROI we've delivered for similar customers: [specific example or metric]
</context>

<task>
Write a response that:
1. Acknowledges without caving
2. Reframes price as cost-per-outcome (not cost-per-seat)
3. References a customer ROI example
4. Moves toward a specific next step

Under 100 words. No "I understand your concern."
</task>

Prompt 24 — Respond to "Not the Right Time"

You are a B2B sales strategist.

<context>
Prospect said: "[paste exact words]"
Known context: [budget cycle / company initiative / recent change]
</context>

<task>
Write a response that:
1. Accepts the timing concern without closing the deal
2. Asks one question to understand the real reason
3. Proposes a specific future touchpoint (date or condition)

Under 80 words. No "I completely understand, let's reconnect in Q3."
</task>

Prompt 25 — Respond to "We're Already Using [Competitor]"

You are a competitive sales specialist.

<context>
Competitor they use: [competitor name]
Known weaknesses of that competitor (from G2 / user feedback): [list 2–3]
My product's specific advantage over that competitor: [list 2–3 specific differences]
</context>

<task>
Write a response that:
1. Validates their choice (fair, not sycophantic)
2. Asks one question that surfaces a known gap in the competitor
3. Plants a seed for a comparison without asking for a switch today

Under 90 words.
</task>

Prompt 26 — Respond to "We Need to Involve More Stakeholders"

You are a B2B enterprise sales coach.

<context>
Prospect said: "[paste exact words]"
Current champion: [Name], [Title]
Other stakeholders they mentioned: [names/titles if known]
Deal stage: [current stage]
</context>

<task>
Write a response that:
1. Encourages the multi-stakeholder process (don't fight it)
2. Offers to help the champion prepare for the internal conversation
3. Proposes a specific next step (e.g., a stakeholder demo, a business case template)

Under 90 words. Coach the champion, don't bypass them.
</task>

Prompt 27 — Objection to Full FAQ Matrix

You are a B2B sales enablement specialist.

<context>
Product: [product name + category]
Top 5 objections we hear: [list them]
</context>

<task>
For each objection, write:
1. The acknowledge line (1 sentence)
2. The reframe (1–2 sentences)
3. The proof point (customer example or stat)
4. The redirect question (move conversation forward)

Output as a markdown table with columns: Objection | Acknowledge | Reframe | Proof | Redirect
</task>

Follow-Up & Re-Engagement Prompts

The biggest waste in sales is a warm prospect who went cold because nobody followed up. These prompts solve that — fast.

Prompt 28 — Post-Demo Follow-Up

You are a B2B account executive following up after a product demo.

<context>
Demo date: [date]
Prospect: [Name], [Title] at [Company]
Pain points they highlighted during demo: [list]
Features that resonated: [list]
Agreed next step from the demo: [what was said]
</context>

<task>
Write a post-demo follow-up email that:
- Ties the features shown to their specific pain points
- Confirms the agreed next step with a specific date/action
- Attaches or links one relevant resource (case study, ROI template, or comparison guide)
- Is under 120 words, not a wall of text
</task>

Prompt 29 — "Just Checking In" Replacement

You are a B2B sales coach. The rep wants to follow up but has nothing new to say.

<context>
Last interaction: [date + what happened]
Time since last touch: [X days/weeks]
Any new information available: [product update / relevant news / customer win / industry stat]
</context>

<task>
Write a follow-up email that gives value before asking for anything.
Options to lead with:
1. A relevant industry stat they haven't seen
2. A short case study snippet from a similar company
3. A product update that addresses their stated pain
4. A question about a change at their company

Choose the best option given the context. Under 80 words. Include subject line.
</task>

Prompt 30 — Breakup Email

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

<context>
Prospect: [Name], [Title] at [Company]
Touchpoints sent so far: [number]
Last interaction: [describe briefly]
</context>

<task>
Write a breakup email that:
- Acknowledges the silence without guilt-tripping
- Leaves the door open (they can re-engage easily)
- Is honest and direct — under 50 words
- Ends with "no action needed" framing

Include subject line. Do not use "I'll take the hint."
</task>

Prompt 31 — Referral Request Email

You are a B2B sales rep requesting a referral from a happy customer.

<context>
Customer: [Name] at [Company]
Result they achieved: [specific outcome]
Ideal referral profile: [title / company type / pain]
</context>

<task>
Write an email requesting a referral that:
- Leads with their result (make them feel good first)
- Describes the ideal referral clearly (so they can picture someone)
- Makes the ask easy (a name, an intro, or a permission to use their name)
- Is under 80 words

No "if you know anyone" vagueness.
</task>

Prompt 32 — Event Follow-Up Email

You are a B2B sales rep following up after meeting a prospect at an event.

<context>
Event: [event name / date]
Prospect: [Name], [Title] at [Company]
What you discussed: [topic, problem mentioned, commitment made]
</context>

<task>
Write a follow-up within 24 hours that:
- References the specific conversation (not "great meeting you")
- Delivers on anything you promised (resource, intro, info)
- Proposes a clear next step
- Is under 80 words

Include subject line that references the event.
</task>

Proposal & Closing Prompts

Late-stage prompts that help you write compelling business cases, prepare negotiation strategies, and close with confidence.

Prompt 33 — Executive Business Case

You are a B2B sales strategist writing an executive summary for a business case.

<context>
Buyer company: [Company Name]
Decision makers: [titles]
Pain we solve: [specific problem with estimated cost]
Our solution: [product + key features used]
ROI evidence: [customer examples or metrics]
Our pricing: [plan / total cost]
</context>

<task>
Write a 1-page executive summary with:
1. Problem statement (2 sentences)
2. Proposed solution (2 sentences)
3. Expected outcomes (3 bullets with metrics)
4. Investment and expected payback period
5. Recommended next step

Professional tone. No buzzwords. Readable by a CFO in 90 seconds.
</task>

Prompt 34 — Mutual Action Plan (MAP)

You are a B2B account executive building a mutual action plan for a deal.

<context>
Prospect: [Company]
Decision maker: [Name], [Title]
Target close date: [date]
Procurement/security requirements: [if known]
Remaining steps to close: [what's left — legal, IT review, stakeholder sign-off, etc.]
</context>

<task>
Create a mutual action plan as a table with:
- Step
- Owner (Prospect or Us)
- Due date
- Status (Open / In Progress / Done)

Include 8–12 steps from today to signed contract. Start with what needs to happen today.
</task>

Prompt 35 — Pricing Justification Memo

You are a B2B sales specialist justifying a pricing decision to a procurement team.

<context>
Our price: [total contract value]
Competitor pricing (if known): [comparison]
Value delivered: [specific outcomes and ROI]
Customer references available: [yes/no + names if shared]
</context>

<task>
Write a 150-word pricing justification memo that:
1. Reframes price around total value delivered
2. Compares cost-per-outcome vs. cost-per-seat
3. References one customer result
4. Addresses the most likely procurement objection

Plain language. No buzzwords.
</task>

Prompt 36 — Contract Negotiation Preparation

You are a B2B deal desk advisor preparing a sales rep for contract negotiation.

<context>
Deal size: [ACV]
Prospect's likely asks: [discount / longer terms / extra seats / features / SLA changes]
Our floor: [minimum acceptable terms]
Concessions we can offer: [what we can trade without losing margin]
</context>

<task>
Prepare a negotiation playbook with:
1. Opening position (what to present first)
2. Trade-off matrix: for each expected ask, our response + counter-offer
3. Hard stops (what we won't concede)
4. Closing language for the final ask

Bullet format. Under 250 words.
</task>

Prompt 37 — Deal Risk Assessment

You are a B2B sales coach doing a deal review.

<context>
Deal: [Company Name]
Stage: [current CRM stage]
Last activity: [date + type]
Champion engagement: [high / medium / low]
Economic buyer engaged: [yes / no]
Competitive situation: [sole vendor / competitive eval / incumbent]
Timeline: [prospect's stated close date]
</context>

<task>
Score this deal's risk (Low / Medium / High) across:
1. Champion strength
2. Economic buyer access
3. Competitive threat
4. Timeline realism

For each High risk flag, suggest one specific action to mitigate it.
Output as a 5-row table.
</task>

CRM Cleanup Prompts

CRM data decays at roughly 30% per year. These prompts run against exported CRM data (paste it in or connect via MCP) and return clean, structured records. For teams doing this at scale, see Claude Code CRM integration for how to automate this without the paste step.

Prompt 38 — Deduplicate Lead Records

You are a CRM data hygiene specialist.

<context>
Lead records (CSV format or paste rows below):
[Paste records — Name, Email, Company, Title, Last Activity]
</context>

<task>
Identify duplicate records. For each duplicate set:
1. List both/all records
2. Recommend which to keep (most complete + most recent activity)
3. Note fields to merge from the duplicate into the master

Output as a table: Duplicate Set | Keep | Merge Fields | Reason
</task>

Prompt 39 — Contact Data Enrichment Gaps

You are a B2B data operations analyst.

<context>
CRM contacts (paste or describe):
[Company | Name | Email | Phone | Title | LinkedIn | Last Activity | Enriched Y/N]
</context>

<task>
For contacts marked Enriched=N or with missing fields:
1. Flag which fields are missing
2. Prioritize them by deal value or engagement score (if provided)
3. Suggest the most likely data source for each missing field (LinkedIn, company website, email signature, waterfall enrichment)

Output a prioritized enrichment queue as a table.
</task>

Prompt 40 — Stale Deal Triage

You are a sales operations analyst doing a pipeline hygiene audit.

<context>
Deals with no activity in 30+ days:
[Paste deal list: Company | Stage | ACV | Last Activity Date | Owner]
</context>

<task>
For each stale deal:
1. Recommend action: Revive / Disqualify / Nurture / Escalate
2. State the reason in one sentence
3. Suggest the next outreach touchpoint (channel + message angle)

Output as a table. Flag any deal over $20k ACV for immediate escalation.
</task>

Prompt 41 — CRM Activity Log from Meeting Notes

You are a CRM data entry specialist converting meeting notes to structured activity records.

<context>
Meeting notes:
[Paste raw notes]

CRM fields to populate: Contact | Date | Activity Type | Summary | Next Steps | Follow-Up Date
</context>

<task>
Extract and populate all fields. If a field can't be determined from the notes, write "Not mentioned."
Output as a single structured record, formatted to paste directly into a CRM note field.
Keep the Summary under 50 words. Next Steps as a bulleted action list.
</task>

Prompt 42 — Lead Scoring Model (Manual)

You are a RevOps analyst building a manual lead scoring model.

<context>
ICP criteria (with weights):
- Industry match: [weight, e.g., 20 points]
- Company size match: [weight]
- Title/seniority match: [weight]
- Tech stack match: [weight]
- Engagement signals: [weight]
- Intent signals: [weight]

Leads to score:
[Paste lead list with available data]
</context>

<task>
Score each lead against the criteria. Return:
- Total score (out of 100)
- Top fit reason
- Top gap

Output as a ranked table, highest score first.
</task>

Pipeline Analysis Prompts

Pipeline reviews are faster and more useful when Claude handles the pattern-recognition. Paste your pipeline export and get a structured analysis in seconds. These prompts complement the workflows covered in Claude Code RevOps workflows.

Prompt 43 — Pipeline Coverage Analysis

You are a revenue operations analyst.

<context>
Quota for period: [$X]
Pipeline data (paste or summarize):
[Stage | Company | ACV | Close Date | Probability | Last Activity]
</context>

<task>
Calculate:
1. Total weighted pipeline value
2. Coverage ratio (pipeline / quota)
3. Pipeline by stage (count + total ACV)
4. Deals likely to close this period (probability > 60% + close date within window)
5. Gap to quota and how many deals needed to fill it at average ACV

Output as a pipeline dashboard summary. Flag any coverage below 3x as a risk.
</task>

Prompt 44 — Win/Loss Pattern Analysis

You are a B2B sales analyst identifying win/loss patterns.

<context>
Closed deals (last 90 days):
[Paste: Company | Outcome (Won/Lost) | ACV | Competitor | Primary reason | Stage lost/won | Sales cycle length]
</context>

<task>
Analyze and return:
1. Win rate overall and by deal size (<$10k / $10k-50k / $50k+)
2. Top 3 win reasons (with frequency)
3. Top 3 loss reasons (with frequency)
4. Average sales cycle by outcome
5. Competitor win rate (which competitors are we losing to most)
6. One recommendation based on the patterns

Use tables where possible.
</task>

Prompt 45 — Forecast Call Prep

You are a sales manager preparing for a weekly forecast call.

<context>
This week's commit deals:
[Company | Rep | Stage | ACV | Close Date | Last Activity | Risk flags]
</context>

<task>
For each commit deal:
1. Validate the stage (does activity support it?)
2. Flag risks (no recent activity / no economic buyer engaged / close date unrealistic)
3. Suggest one question to ask the rep on the call

Output as a pre-call brief, one deal per block. Total projected commit at the top.
</task>

Prompt 46 — Rep Performance Scorecard

You are a sales operations analyst building a rep performance summary.

<context>
Rep data (current period):
[Rep Name | Quota | Pipeline | Closed Won | Closed Lost | Activities (calls/emails/meetings) | Avg deal size | Avg sales cycle]
</context>

<task>
For each rep, generate a scorecard with:
1. Quota attainment %
2. Pipeline coverage ratio
3. Win rate
4. Activity score (vs. team average)
5. One strength (highest performing metric)
6. One coaching opportunity (lowest performing metric)

Output as a table. Add a team summary row at the bottom.
</task>

Prompt 47 — Territory Planning

You are a sales strategy consultant designing territory assignments.

<context>
Total addressable accounts: [number + description]
Number of reps: [X]
Rep capacity per month (accounts touched): [Y]
Current territory breakdown: [describe or paste]
</context>

<task>
Recommend territory splits that:
1. Balance account load per rep
2. Group accounts by geography, vertical, or company size (whichever is most logical for this product)
3. Identify any coverage gaps (accounts not in any territory)
4. Flag any rep with territory misfit (too many / too few high-value accounts)

Output as a territory map table + recommendation summary.
</task>

Prompt 48 — Sales Cycle Compression Analysis

You are a B2B sales process analyst.

<context>
Average sales cycle: [X days]
Deals closed in under [target days]: [count + characteristics]
Deals that dragged past [max days]: [count + what they had in common]
Product type: [PLG / enterprise / mid-market transactional]
</context>

<task>
Identify:
1. The top 3 stages where deals slow down
2. What the fast-close deals had in common (actions taken, stakeholders engaged, deal size)
3. Three process changes that would likely compress the average cycle by 15%+

Output as a structured analysis with an action plan table at the end.
</task>

Prompt 49 — Churn Risk Signal Report

You are a customer success and sales analyst identifying churn risk.

<context>
Customer health data:
[Customer | ARR | Last Login | Support Tickets Open | NPS Score | Renewal Date | Usage Trend (up/flat/down)]
</context>

<task>
For each customer:
1. Score churn risk (Low / Medium / High)
2. Primary risk signal
3. Recommended intervention (expansion play / EBR / training / executive outreach)
4. Urgency (before renewal / immediate / monitor)

Sort by: High risk first, then by ARR descending.
Output as a table. Flag any High-risk customer with ARR > $25k for immediate escalation.
</task>

Prompt 50 — Monthly Sales Report Draft

You are a sales operations analyst writing a monthly performance report for leadership.

<context>
Month: [Month YYYY]
Team quota: [$X]
Closed won: [$Y — N deals]
New pipeline created: [$Z]
Pipeline from last month still open: [$W]
Top deal: [Company, $ACV, why it closed]
Miss or loss: [Company, $ACV, why it was lost]
Key activity metrics: [calls / emails / demos / meetings]
</context>

<task>
Write a monthly report executive summary (under 250 words) with:
1. Headline number (attainment %)
2. What drove the result (2–3 bullets)
3. Pipeline health for next month
4. One risk and one opportunity going into next period

Professional tone. Bullet-heavy. No filler.
</task>

Prompt Coverage at a Glance

Conclusion

A Claude Code prompt for sales is only as good as the context you give it. Every prompt in this list follows the same principle: role + task + output format + real data. Generic input produces generic output.

Pick the two prompts that match where you lose the most time — account research, post-call CRM logging, and objection prep are the most common starting points. Run them as one-offs first, then promote the best-performing ones to skill files that run automatically.

For teams ready to go beyond copy-paste, SyncGTM connects Claude Code to your contact enrichment data, CRM, and outbound stack. The prompts above become automated workflows — prospect research fires on every new lead, CRM cleanup runs nightly, pipeline analysis updates before every forecast call. Start free or read the complete Claude Code for sales guide to see the full workflow.