Claude Prompts for Sales Scripts That Don't Sound Like Sales
20 copy-paste Claude prompts for cold calls, discovery, objections, demos, and closing. Long-context Claude can ingest your call transcripts + spit out scripts that match your team's voice.
In short: This page contains 16 copy-paste ready prompts, organized into 4 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Cold + Outbound
4 promptsCold Call Script
1/16✨ What it does
Claude writes a cold-call script for [product] to [persona] with a 30-second opener, a problem line in their words, one line of proof, a 5-minute relevance ask (not a demo), and branches for yes and a respectful exit. Fill product and persona, then practice the opener out loud before you dial.
Cold call script for [product] to [persona]. Output: 30-second opener (pattern interrupt + permission), 1-line problem (in their words), 1-line proof, single ask (not "demo" — "5 minutes to see if it's relevant"). Branch: if interested → next step, if not → respectful exit + permission to follow up.
Pro tip: 5-minute meeting ask > demo ask = 3x conversion. Demo asks = "no, I'm busy." 5-min asks = "fine, what is it?" Lower friction; more meetings; demo earned through interest.
Cold Email Sequence
2/16✨ What it does
Claude writes a 5-email cold sequence for [product] to [persona]: problem-led, a case or insight, a specific question, a new angle, and a graceful breakup, each under 100 words and without a hollow hope-you-are-well opener. Fill both blanks, then send email 1 only after you cut it under 100 words.
Cold email sequence for [product] to [persona]. Output: email 1 (problem-led, not pitch), email 2 (case study or specific insight), email 3 (specific question), email 4 (different angle), email 5 (graceful break-up). Each under 100 words. No "Hope this finds you well."
Pro tip: Cold emails over 100 words = unread. Generic openers ("hope this finds you well") = filtered. Specific personal opener + 1 sentence problem + 1 ask = open + reply rates lift.
LinkedIn Outreach Variant
3/16✨ What it does
Claude writes a LinkedIn DM sequence for [product] to [persona] under 60 words, conversational, referencing their profile or content, with rapport, light context, and a specific ask only if they engage, and no pitch in message one. Fill both, then personalize DM 1 with something you actually saw on their profile.
LinkedIn DM for [product] to [persona]. Different from email: shorter (under 60 words), more conversational, reference their content/profile, no pitch in first message. Output: DM 1 (rapport), DM 2 (light context), DM 3 (specific ask if engaged).
Pro tip: LinkedIn DMs that feel like email pitches = ignored + worse, perceived as spam. Conversational DMs that respect platform = response rate 3-5x higher than email-pitch ports.
Voicemail Scripts
4/16✨ What it does
Claude writes 3 voicemails under 30 seconds for [product/persona]: intrigue, a mutual-connection reference, and a specific insight, each with a callback ask and an email follow-up you will send. Pick the variant that matches how you know them, then leave it and send the email the same day.
3 voicemail variants for [product/persona]: (A) intrigue-led (curiosity hook), (B) reference-led (mutual connection), (C) value-led (specific insight). Each under 30 seconds. Always include callback ask + email follow-up commitment.
Pro tip: Voicemail callback rate is brutal (~5%). Voicemail still triggers email open + LinkedIn check. Plays alongside email = compounds. Solo channel = ignored.
XML tags are just the start. Learn the full Claude workflow.
A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.
Discovery + Demo
4 promptsDiscovery Call Script
5/16✨ What it does
Claude writes a 30-minute discovery script for [product] with agenda, questions on current state, pain, impact, timeline, budget, and process, what you want to learn, what they should learn, and a demo or graceful exit. Name the product, then follow the question order instead of jumping to the demo.
Discovery call for [product]. Output: opener (set agenda), discovery questions in order (current state, pain, impact, timeline, budget, decision process), what I want to learn, what I want them to learn about us, transition to demo if qualified or graceful exit if not. 30 min.
Pro tip: Discovery call that pitches = bad discovery. Best AEs talk 30%; let prospect talk 70%. Question depth + active listening = qualified prospects + earned right to demo.
MEDDIC Discovery Mapping
6/16✨ What it does
Claude maps [Paste discovery call notes] to MEDDIC: Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, and Champion, and flags missing pieces for the next call. Paste the notes, then put every missing dimension on your next-call agenda.
[Paste discovery call notes]. Map to MEDDIC: Metrics (quantified pain), Economic buyer (named), Decision criteria (their evaluation framework), Decision process (steps + timeline), Identify pain (specific), Champion (internal advocate). Flag missing dimensions = next call focus.
Pro tip: MEDDIC gaps = forecast risk. Missing economic buyer = deal in jeopardy. Missing pain quantification = "nice to have" deal. Mapping discovery to MEDDIC = honest forecast.
Demo Script
7/16✨ What it does
Claude writes a 30-minute demo script for [product] aimed at [decision maker / user / champion] with a 5-minute recap, a 15-minute walk of their use cases only, outcomes and proof, and a next step, without a feature tour. Fill both, then cut any click that is not on your prospect's stated use case.
Demo script for [product]. Audience: [decision maker / user / champion]. Output: 5-min opener (recap their stated needs, demo agenda), 15-min product walk (focused on their use cases ONLY, not feature tour), 5-min outcomes/social proof, 5-min next step. Don't feature-dump.
Pro tip: Feature-tour demos = lost deal. Use-case-focused demo = "they get me + their product solves my problem." Same product, opposite reception. Discipline to NOT show all features = winning move.
Multi-Threaded Demo
8/16✨ What it does
Claude scripts a multi-stakeholder demo for [list of personas] with an opener that names each person, a flow that hits each priority, named transitions, and a Q&A that invites every seat. List the people in your room, then mark which minute belongs to each name.
Demo to multi-stakeholder room: [list of personas]. Each cares about different things. Output: opener acknowledges each persona, demo flow that hits each persona's priorities, individual transitions ("Sarah, this addresses your team's X"), Q&A frame inviting each persona. No persona left unaddressed.
Pro tip: Multi-stakeholder demo where one persona's needs ignored = they kill deal post-demo. Addressing each by name + need = each becomes champion or at least neutral. Inclusive demo = closeable deal.
Objections + Closing
4 promptsObjection Handling Library
9/16✨ What it does
Claude builds an objection library for [product] from [list] such as too expensive, not now, a competitor, no need, or an absent decision maker, with acknowledge, reframe, evidence, a next-step redirect, and 3 variants by relationship depth. Fill product and the list, then use the variant that matches how well you know them.
Build objection handling library for [product]. Common objections: [list — too expensive / not now / using competitor / no need / decision-maker absent]. Per objection: acknowledge, reframe (don't deny), evidence, redirect to next step. 3 variants per objection for different relationship depths.
Pro tip: Objection responses that sound canned = read as canned = lose trust. 3 variants in different tones = pick most natural for the moment. Authentic > scripted.
"It's Too Expensive" Reframe
10/16✨ What it does
Claude handles "It's too expensive" with 5 questions that surface the real objection, reframes on ROI, cost of inaction, and competitor cost, where to flex terms versus price, and where to walk, instead of discounting on reflex. Ask the questions first, then decide whether terms, not price, are what you give.
Prospect: "It's too expensive." Help me handle. Output: 5 questions to surface real objection (rarely actually price), reframe options (per ROI, per alternative cost of inaction, per competitor cost), where to flex on terms vs price, where to walk. Don't discount reflexively.
Pro tip: "Too expensive" = 80% something else (timing, authority, value-perception). Reflexive discount = leaves money on table + signals weakness. Question-discovery → real objection = better path.
Closing Move Scripts
11/16✨ What it does
Claude writes 5 closes for [product]: assumptive, alternative, real urgency, question, and social proof, with when to use each, exact words, and what not to do, matched to deal stage and relationship. Name your product, then pick the close that matches how warm this deal actually is.
5 closing moves for [product]. Output: assumptive close, alternative close, urgency close (real urgency, not manufactured), question close, social proof close. Per close: when appropriate, exact words, what NOT to do. Match move to deal stage + relationship temperature.
Pro tip: Wrong close at wrong moment = damages relationship. Right close at right moment = closes deal. Reading the room > having all moves memorized.
Stalled Deal Recovery
12/16✨ What it does
Claude writes a stall recovery for a deal stuck at [stage] last touched [days ago], with curiosity, value, and direct subject lines, a body that cites the last conversation, one ask, and a no-guilt, no-fake-urgency rule. Fill your stage and days, then send one ask; if they stay silent, disqualify the deal.
Deal stalled at [stage]. Last contact: [days ago]. Help me re-engage: subject line variations (curiosity / value / direct), email body referencing last conversation specifically, single ask, what NOT to do (don't guilt-trip, don't fake-urgency). Get response or move to disqualify.
Pro tip: Stalled deals waste pipeline focus. Re-engage with respect → response means re-active deal; no response after 3 attempts = disqualify + free up time. Both outcomes useful; lingering = neither.
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.
Specialty Scripts
4 promptsInbound Lead Response
13/16✨ What it does
Claude drafts a same-hour inbound reply to form [info] that references what they submitted, asks qualifying questions without sounding like a quiz, suggests a next step, and includes a CTA, because speed beats polish. Paste the form info, then send within 5 minutes rather than waiting to perfect your reply.
Inbound lead just submitted form: [info]. Help me respond fast (within 5 min). Output: opener referencing what they submitted, qualifying questions tactfully, suggested next step, CTA. Speed of response > polish; lead temperature drops 80% per hour.
Pro tip: Sub-5-minute response wins inbound leads. By 30 min, you're competing with everyone they also filled out. Speed + quality > perfection slowly.
Renewal/Expansion Conversation
14/16✨ What it does
Claude preps a renewal conversation from [account info] with usage review, ROI, expansion, risk signals, who to engage, and stage-by-stage scripts and timing. Drop the account facts in, then book the decision maker before you talk only to the user.
Customer up for renewal: [account info]. Help me prep: usage data review, ROI articulation, expansion opportunity, renewal risk signals, decision-maker engagement plan, timeline + scripts per stage. Renewals are easier than net new; treat with attention.
Pro tip: Renewals taken for granted = surprise churn. Renewals worked like sales (proper engagement, ROI articulation, decision-maker check) = 95%+ retention. Treat as new sale.
Win/Loss Interview Script
15/16✨ What it does
Claude scripts a win/loss interview with [former prospect/lost deal] that thanks them, stays non-defensive, asks about decision factors, what you did well and poorly, the competitor, and process lessons, as an interview rather than a last pitch. Name who you lost, then ask the questions and do not resell on that call.
Conducting win/loss interview with [former prospect/lost deal]. Help me script: thank them for time, no defensive tone, specific questions about decision factors, what we did well/poorly, competitor comparison, learnings for our process. Interview format, not pitch attempt.
Pro tip: Win/loss interviews that turn into pitches = you learn nothing. Pure-research framing = honest data. Most teams skip W/L interviews; the discipline is the edge.
Account Plan from Notes
16/16✨ What it does
Claude builds an account plan from [Paste 6 months of notes from major account] with a stakeholder map, relationship state, expansion, threats, a 90-day plan, and success metrics. Paste the notes, then put the 90-day plan on your next QBR agenda.
[Paste 6 months of notes from major account]. Build account plan. Output: stakeholder map with influence, current state of relationship, expansion opportunities, threats (competitors, project at risk, churn signals), 90-day plan, success metrics. Long context lets Claude see whole account.
Pro tip: Account plans built from memory = miss patterns. Account plans built from full notes via Claude long-context = uncover relationships + risks invisible day-to-day.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides