20 Claude Prompts for Sales That Actually Close Deals

<context> I'm a [role, e.g. Account Executive] selling [product/service] to [target market, e.g. mid-market SaaS companies]. I'm preparing to reach out to [company name], a [brief description of prospect company]. Their website is [URL]. </context> <task> Build a pre-call research brief for this account covering: 1. Company overview (what they do, who they serve, business model) 2. Recent news, funding rounds, executive hires, or product launches from the last 6 months 3. Likely pain points based on their industry, size, and stage 4. How our product ([describe product]) maps to those pain points 5. 3 personalized conversation starters I could use in outreach 6. Key decision-makers and their likely priorities (based on typical org structures at this company size) </task> <constraints> - Be specific — don't give me generic industry observations I could find on any blog - Flag anything you're uncertain about with "[VERIFY]" so I know what to fact-check - Focus on insights that would make the prospect think "this person actually understands my business" - Keep the brief under 500 words — I need to scan it before a call, not read a report </constraints> <format> Use clear headers for each section. Bullet points, not paragraphs. </format>

<context> I sell [product/service] at [company]. Our best customers include [list 3-5 current customer names and what they have in common]. Our average deal size is [amount] and sales cycle is [length]. We win most often against [competitor] and lose most often against [competitor]. </context> <task> Build a detailed Ideal Customer Profile (ICP) document that includes: 1. Firmographic criteria (industry, company size, revenue range, geography, tech stack signals) 2. Trigger events that indicate buying readiness (hiring patterns, funding, tech migration, leadership changes) 3. Pain indicators — specific symptoms a prospect experiences before they need our solution 4. Anti-patterns — characteristics of companies that look like a fit but consistently churn or stall in pipeline 5. A qualification scoring rubric (1-5 scale across 5 dimensions) I can use to rank new leads </task> <constraints> - Ground everything in the patterns from my actual customer examples — don't just list generic B2B criteria - The scoring rubric should be practical enough for an SDR to use in under 60 seconds - Include specific phrases to listen for on discovery calls that signal high ICP fit </constraints> <format> Structure as a reference document with sections I can share with my sales team. </format>

<context> I'm a [sales ops / rev ops / sales manager] at [company]. We sell [product] to [target buyer persona] at [target company type]. Our CRM is [Salesforce/HubSpot/etc.]. Right now we don't have a structured lead scoring model — reps prioritize leads based on gut feel. </context> <task> Design a lead scoring framework with: 1. Demographic/firmographic scoring criteria (title, company size, industry) with point values 2. Behavioral scoring criteria (website visits, content downloads, email engagement, demo requests) with point values 3. Negative scoring signals (competitor employee, student email, unsubscribed, etc.) 4. Score thresholds: MQL, SQL, and "fast-track to AE" with specific point ranges 5. A recommended handoff process from marketing to SDR to AE based on score </task> <constraints> - Total possible score should be 100 points - Weight behavioral signals more heavily than demographic — intent matters more than fit alone - Include at least 3 "fast-track" triggers that bypass normal scoring (e.g., pricing page visit + demo request in same session) - Make it implementable in [CRM name] without custom development </constraints> <format> Return as a structured document with tables for each scoring category. </format>

<context> I sell [product/service] and I'm competing against [competitor name] on a deal with [prospect company]. The prospect is evaluating both solutions for [use case]. My champion at the prospect has told me the competitor is [any intel you have — pricing, demo feedback, features mentioned]. </context> <task> Create a competitive battle card for this specific deal: 1. Likely positioning the competitor will use (based on their public messaging and typical sales plays) 2. Their strengths I should NOT try to argue against — acknowledge and redirect 3. Our differentiators that matter most for this specific use case 4. Landmine questions I can plant in the prospect's mind before they see the competitor demo 5. If the prospect says "Competitor X can do that too," give me 3 responses that reframe the conversation around outcomes, not features 6. Trap topics to avoid — areas where engaging would work in the competitor's favor </task> <constraints> - Be strategic, not petty — never trash the competitor directly - Frame everything around the prospect's outcomes, not our features - Landmine questions should sound like genuine curiosity, not attacks - If you don't have enough information about the competitor, flag what I should research </constraints>

<context> I'm a [role] at [company]. We help [target persona] solve [core problem] by [how product works in one sentence]. I'm reaching out to [prospect name], [prospect title] at [prospect company]. Here's what I know about them: - Company: [what they do, size, recent news] - Prospect: [background, LinkedIn summary, recent posts or activity] - Trigger: [why now — hiring, funding, product launch, job change, etc.] </context> <task> Write a cold email that: 1. Opens with a specific observation about their company or role (NOT a compliment — an insight) 2. Connects that observation to a problem they likely face 3. Positions our solution in one sentence without jargon 4. Includes a low-friction CTA (not "Let me know if you'd like a 30-minute demo") 5. Is under 120 words total </task> <constraints> - No "I hope this finds you well" or any filler opening - No bullet lists of features — this is a first touch, not a pitch deck - The email should make the prospect think "this person did their homework" - Subject line should be under 6 words, lowercase, and curiosity-driven - Write 3 variations with different angles so I can A/B test </constraints> <format> For each variation, provide: Subject line, Email body, and a one-line note explaining the angle. </format>

<context> I'm a [role] at [company] targeting [buyer persona] at [company type]. I want to connect with [prospect name], [title] at [prospect company] on LinkedIn. What I know about them: [any context — mutual connections, shared content, company news]. </context> <task> Write a 3-touch LinkedIn sequence: 1. Connection request note (under 300 characters) — no selling, just a relevant reason to connect 2. First message after they accept (sent 2 days later) — share a relevant insight or resource, plant a seed about the problem we solve 3. Follow-up message (sent 5 days after message 1) — soft ask for a conversation, reference something specific For each message, also write an alternative version if the prospect has NOT engaged at all (cold follow-up path). </task> <constraints> - Connection request must NOT mention my product or ask for a meeting - Messages should feel like peer-to-peer conversation, not sales outreach - Each message must be under 500 characters (LinkedIn truncates longer messages) - Reference specific, real-sounding content or insights — not "I came across an interesting article" - No "pick your brain" or "I'd love to learn more about your role" filler </constraints>

<context> I sent a cold email to [prospect name], [title] at [company] about [topic/solution] on [date]. They haven't responded. Here's the original email I sent: [paste original email] I know the following about this prospect: [any additional context — industry, company size, recent activity]. </context> <task> Write a 4-email follow-up sequence spaced over 3 weeks: 1. Follow-up 1 (Day 3): Brief bump with a new angle or piece of value — NOT "just following up" 2. Follow-up 2 (Day 7): Share a relevant insight, case study reference, or data point that reframes the problem 3. Follow-up 3 (Day 14): Pattern interrupt — different format, tone, or approach entirely 4. Follow-up 4 (Day 21): Breakup email — respectful close that leaves the door open Each email should be under 80 words. Include subject lines for each. </task> <constraints> - Never reference that they haven't replied — no guilt-tripping - Each email must stand alone as valuable even if they didn't read the previous ones - Follow-up 3 should be the most creative — try humor, a counterintuitive question, or a bold claim - The breakup email should make them want to respond, not feel relieved you stopped - No "just circling back" or "wanted to bump this to the top of your inbox" </constraints>

<context> I'm a [role] at [company]. I have a good relationship with [referrer name], who is [their role/relationship to me — customer, former colleague, partner, etc.]. I want to ask them for an introduction to [target prospect name], [title] at [target company]. The connection between referrer and target: [how they know each other — LinkedIn connection, former colleagues, same industry group, etc.]. </context> <task> Write three things: 1. A message to my referrer asking for the intro — make it easy for them to say yes by explaining exactly why I want the intro and what I'll say (no "I promise I won't be salesy") 2. A suggested "forwardable blurb" my referrer can copy-paste when making the intro — written from their perspective, under 100 words 3. My response to the introduction email/message once the referrer connects us — acknowledge the referrer, establish relevance, and propose a specific next step </task> <constraints> - The referral request should take under 30 seconds for my referrer to act on — minimize their effort - The forwardable blurb should position me as a peer, not a vendor - Don't oversell — the referral itself is the credibility, not the pitch - Keep each piece under 100 words </constraints>

<context> I'm a [role] selling [product/service] to [buyer persona] at [company type]. I have a discovery call scheduled with [prospect name], [title] at [prospect company]. What I know so far: [any intel — how they found us, what they said when booking, their company situation]. Our typical sales process is [describe: e.g., discovery → demo → proposal → close]. </context> <task> Build a discovery call framework with: 1. 3 rapport-building openers tied to something specific about the prospect (not weather or sports) 2. 5 situation questions to understand their current state (without sounding like a survey) 3. 5 pain questions that dig into consequences and costs of the status quo 4. 3 implication questions that help the prospect realize the problem is bigger than they thought 5. 2 need-payoff questions that get the prospect to articulate why solving this matters 6. A recommended "next step" close for different scenarios (interested, uncertain, or not ready) </task> <constraints> - Questions should feel conversational, not interrogative — suggest natural transitions between them - Include follow-up probes for when a prospect gives a surface-level answer - Flag which questions to skip if the call is running short (mark as "skip if under 20 min") - Never ask a question whose answer is easily found on their website </constraints> <format> Organize by call phase with estimated time for each section. </format>

<context> I'm selling [product/service] to [buyer persona]. During a recent discovery call with [prospect name] at [prospect company], they mentioned these pain points: 1. [Pain point 1 — in the prospect's own words] 2. [Pain point 2 — in the prospect's own words] 3. [Pain point 3 — in the prospect's own words] Their company has [X employees], approximately [revenue/size context], and operates in [industry]. </context> <task> For each pain point, help me quantify the business impact: 1. Calculate the estimated annual cost of inaction using reasonable assumptions (time wasted, revenue leaked, productivity lost, employee turnover cost) 2. Show your math — break down each assumption so I can validate or adjust the numbers 3. Suggest 2 follow-up questions I can ask the prospect to get their real numbers (instead of my estimates) 4. Write a one-sentence "cost of inaction" statement I can use in my proposal or follow-up email </task> <constraints> - Use conservative estimates — a prospect will dismiss inflated numbers instantly - Label every assumption clearly so the prospect can swap in their actual data - The "cost of inaction" statements should be specific enough to cite in an executive email, not vague ROI claims - If a pain point can't be reasonably quantified, say so and suggest a qualitative framing instead </constraints>

<context> I'm working a deal at [prospect company] for [product/service]. The deal size is approximately [amount] and involves [department/team affected]. Here's everyone I've interacted with or heard about so far: - [Name 1]: [Title], [what they've said or how they've engaged] - [Name 2]: [Title], [what they've said or how they've engaged] - [Name 3]: [Title], [what they've said or how they've engaged] The buying process at this company seems to involve [any intel on how they buy]. </context> <task> Create a stakeholder map for this deal: 1. Classify each person's role: Champion, Economic Buyer, Technical Evaluator, End User, Blocker, or Coach 2. Assess their current disposition: Supportive, Neutral, or Resistant — with reasoning 3. Identify gaps — roles that should be involved but aren't in my map yet (and suggest titles to look for) 4. For each stakeholder, recommend: what they care about most, the message that resonates with their role, and one action I should take to advance their support 5. Flag the single biggest risk in this deal based on the stakeholder landscape </task> <constraints> - Don't assume everyone is supportive just because they took a meeting - If someone's role is unclear from my notes, mark them as "ambiguous" and suggest questions to clarify - Be direct about political dynamics — if two stakeholders likely have competing priorities, call it out </constraints> <format> Return as a visual-friendly table plus a narrative risk summary. </format>

<context> I just finished a discovery call with [prospect name], [title] at [prospect company]. Here are my raw call notes: [Paste your call notes, transcription, or bullet points from the call] We sell [product/service] and our key capabilities are [list 3-5 main features/capabilities]. </context> <task> Synthesize these call notes into a structured needs analysis: 1. Current State: What the prospect is doing today and what tools/processes they use 2. Desired State: Where they want to be and what success looks like to them 3. Gap Analysis: The specific gaps between current and desired state 4. Fit Assessment: Which of our capabilities map to each gap (and which gaps we DON'T address — be honest) 5. Priority Ranking: Rank their needs by urgency based on what they emphasized most 6. Recommended Next Steps: What I should propose as the logical next action and why 7. Red Flags: Anything from the call that suggests this deal might stall or not close </task> <constraints> - Use the prospect's actual words wherever possible — don't paraphrase into sales jargon - Be honest about fit gaps — it's better to know now than after a failed implementation - The next step recommendation should match their buying urgency — don't push a proposal if they're still exploring </constraints>

<context> I'm preparing a proposal for [prospect company]. The deal: - Buyer: [economic buyer name and title] - Problem: [core problem they need solved] - Solution: [what we're proposing] - Investment: [price/pricing model] - Timeline: [implementation timeline] - Competition: [who else they're evaluating, if known] Key things the buyer has said during the sales process: [List 3-5 direct quotes or paraphrased statements from the prospect] </context> <task> Write a one-page executive summary for the proposal that: 1. Opens with the prospect's problem in their own language (not our marketing language) 2. Quantifies the cost of the status quo using data from our conversations 3. Presents our solution as the bridge from their current state to desired outcome 4. Addresses the top concern or objection they've raised, without being defensive 5. Closes with a clear recommendation and specific next step with a date </task> <constraints> - Write for the economic buyer who has 2 minutes to read this — lead with business impact, not product features - Use the prospect's terminology, not ours - The entire summary must fit on one page (under 400 words) - No superlatives ("best-in-class," "cutting-edge," "world-class") — those words mean nothing - Include exactly one proof point (customer result, metric, or case study reference) </constraints>

<context> I need to build a business case for [prospect company] to justify purchasing [our product/service]. Here's what I know: - Annual contract value: [price] - Their current solution/process: [what they do today and what it costs] - Pain points quantified: [list with dollar amounts or time costs if available] - Implementation effort: [timeline and resource requirements] - Expected outcomes: [what we've promised or what similar customers achieved] - The decision-maker who needs to approve this: [title, e.g., CFO, VP Ops] </context> <task> Build a ROI business case document that includes: 1. Investment Summary: Total cost including implementation, training, and Year 1 subscription 2. Cost of Status Quo: What they're losing annually by doing nothing (break down by category) 3. Expected Returns: Conservative, moderate, and aggressive scenarios with specific dollar amounts 4. Payback Period: Months to break even under each scenario 5. Risk Mitigation: What happens if results come in below the conservative estimate 6. Comparable Results: Framework for a "Customer X achieved Y" proof point (I'll fill in the real case study) 7. Decision Framework: A simple table the CFO can use to compare "buy vs. don't buy" </task> <constraints> - Use the conservative scenario as the headline number — overestimating ROI destroys credibility - Show your math for every calculation so the CFO's team can verify - Include soft benefits (employee satisfaction, competitive advantage) separately from hard ROI — don't mix them - The payback period is the most important number — make it prominent - Account for implementation costs and the productivity dip during transition </constraints> <format> Structure as a professional document with an executive summary at the top, followed by detailed sections. </format>

<context> I've sent a proposal to [prospect name], [title] at [prospect company] for [product/service] at [price]. They've come back and said our pricing is [too high / above their budget / more than the competitor]. Specifically, they said: "[exact quote or paraphrased feedback on pricing]." Our actual cost vs. competitor: [any pricing intel]. The value we've demonstrated so far: [key outcomes or proof points from the sales process]. </context> <task> Write an email response that justifies our pricing: 1. Acknowledge their concern without being defensive or dismissive 2. Reframe the conversation from cost to value — tie the price back to the specific outcomes they told me they need 3. Break down the investment in a way that makes the number feel smaller (per user/month, per transaction, percentage of the problem cost) 4. Address the competitive price gap honestly without trashing the competitor 5. Offer a creative path forward that protects our price integrity (phased rollout, pilot program, success-based milestone) — NOT a discount 6. Close with confidence and a specific next step </task> <constraints> - Never apologize for the price — frame it as an investment - Do NOT offer a discount unless I specifically tell you to — protect margin - The reframe must use numbers and outcomes from our actual conversations, not generic ROI claims - Keep the email under 200 words — long justification emails signal desperation - If the competitor is genuinely cheaper for equivalent value, acknowledge it and pivot to what's different </constraints>