Best Claude Prompts for Sales

Picture this: you just wrapped a 45-minute discovery call, you're back-to-back in the afternoon, and you still have to write the follow-up email, update the CRM notes, and build out the proposal framework before tomorrow. Each of those tasks individually takes 10-15 minutes. Together, they're the reason sales reps routinely work late on admin that isn't actually selling.

Claude prompts for sales teams work best when they're built around the specific, recurring tasks that eat non-selling time. Not generic "help me with sales" prompts -- focused prompts for follow-up emails, discovery frameworks, objection handling scripts, and call summaries, each calibrated to your actual sales process.

Quick-Start (Copy This Right Now)

Turn these discovery call notes into a structured follow-up email:

Notes: [paste rough notes or bullet points from the call]
Prospect: [name, company, role]
Key problem they described: [their words if possible]
What we discussed offering: [solution]
Next step agreed on the call: [specific next step]

Email should: open by reflecting their specific problem back to them (not a generic "great talking to you"), confirm the next step clearly, and stay under 120 words. Tone: direct and warm, not salesy.

Don't invent details not in my notes.

What this does: Anchoring the email to "their words if possible" for the problem statement is the single change that makes follow-up emails feel personalized rather than templated -- and capping at 120 words keeps it readable rather than a wall of text that gets skimmed.

Understanding the Variables

Swap

[key problem they described]

⚠️ Common mistake: Running the follow-up email prompt without filling in the "next step agreed on the call" field -- then wondering why the email generates a vague "looking forward to continuing the conversation" CTA. The prompt literally cannot produce a specific next step if you don't give it one.

Step-by-Step: Discovery Prep

I have a discovery call with [prospect name] at [company] on [date]. They're [role].

What I know so far: [paste any LinkedIn research, website notes, news, trigger events]
Our ICP: [describe your ideal customer profile in 2-3 sentences]
The problem we solve: [one sentence]

Generate:
1. Five discovery questions specific to this prospect that I couldn't Google -- based on what you can infer from their business model, growth stage, or industry
2. One hypothesis about their likely main pain point, with your reasoning
3. One thing about their business that I should ask to confirm or rule out early in the call

What this does: Asking for questions "you couldn't Google" explicitly filters out the obvious, generic discovery questions that waste call time -- the kind any rep could generate without any research. It pushes Claude toward questions that demonstrate you actually looked at their specific business.

⚡ Pro tip: Run the discovery prep prompt the evening before the call, not the morning of. It surfaces questions worth doing 15 minutes of additional research on, and that research compounds if you let it sit overnight before the call.

Pro-Level Variations

Objection handling script for a specific objection:

Our most common objection is: "[exact objection, in the prospect's typical words]"

Write 3 responses to this objection that each take a different approach: (1) acknowledge and reframe, (2) ask a clarifying question that reveals the real concern underneath, (3) use a customer proof point to address it directly.

For approach 3, here's a real example I can use: [paste a brief relevant customer story or result]

Don't use: "Great question", "I understand", "That's a common concern." These feel scripted.

What this does: Banning the three most overused sales openers ("Great question," "I understand," "That's a common concern") forces responses that actually address the objection instead of signaling that a script is being read from. Prospects notice these phrases more than reps realize.

CRM note from call recording or transcript:

Summarize this call transcript for CRM notes: [paste transcript or key exchanges]

Format:
- Pain points mentioned (direct quotes where possible)
- Stage: [discovery / demo / negotiation / closing]
- Objections raised and how they were handled
- Agreed next steps with dates
- Deal risk: [green / yellow / red] with one-line justification

Under 200 words total. Flag anything that's unclear from the transcript rather than guessing.

What this does: The deal-risk field is the insight most CRM notes skip, and it's often the most useful thing for a sales manager reviewing notes before a forecast call -- forcing a green/yellow/red with justification makes the rep name the actual risk level rather than defaulting to optimism.

Three Real Scenarios

A mid-market AE at a SaaS company used the discovery prep prompt for a strategic account call where the prospect was a direct competitor's existing customer -- the prompt surfaced three questions she wouldn't have thought to ask, including one about whether the competitor had hit any specific SLA issues in the past six months (they had, which became the most important topic of the call). The competitor-aware framing in the "what I know so far" field was what made those questions possible.

An SDR team of six at a revenue intelligence startup built a shared objection-handling library using this format -- running each of their top five objections through the three-approach prompt structure (acknowledge-and-reframe, clarifying question, proof point), reviewing the outputs in a team session, and choosing the best version of each approach collectively. The library became their training resource for new hires, encoding the team's best thinking rather than requiring each new hire to develop it through trial and error.

A sales manager used the CRM note prompt as a coaching tool: before 1:1s with reps, she'd run their most recent call transcript through the deal-risk prompt and compare her assessment to the rep's self-reported forecast. Discrepancies -- where the transcript suggested yellow or red risk that the rep had filed as green -- became specific, evidence-based coaching conversations rather than vague "how's the deal going" check-ins.

A Proposal Kickoff Prompt Worth Having

I have a verbal "yes" from [prospect] and now need to build the proposal. From our discovery and demo, here's what I know about what they care most about: [notes].

Help me structure a proposal outline that:
1. Opens with their specific problem in their language, not our product's capabilities
2. Sequences our solution to address their stated priorities in the order they stated them -- not our preferred feature sequence
3. Includes one section specifically acknowledging the risk they mentioned feeling hesitant about, with our mitigation
4. Ends with a clear, specific next step for signature -- not "let us know if you have questions"

Don't write the proposal yet -- just the outline and the suggested narrative logic.

What this does: Sequencing the proposal around the prospect's stated priority order -- rather than the vendor's preferred feature order -- is a structural change that experienced enterprise sales people know matters but most proposal templates don't accommodate. Having Claude explicitly order it this way forces the document to be prospect-centric rather than product-centric from the outline stage.

Your Turn

Sales teams that treat prompts as reusable assets -- maintaining a shared library of the tested versions that actually reflect their specific process, ICP, and objection patterns -- outperform teams where every rep reinvents from scratch. If you close a deal and the follow-up email sequence you used was the reason, that sequence is worth preserving. PromptABCD is useful specifically for this: keeping the best version of your most valuable claude prompts for sales in one place where the whole team can use and build on them.

One underused practice worth building into your workflow: after every deal that closes or goes dark, spend five minutes asking "which prompt or template contributed most to how this progressed?" Wins tell you what to encode more of. Losses tell you where a better-calibrated prompt might have changed the trajectory -- better discovery prep, sharper objection handling, a more specific follow-up that addressed the real hesitation rather than a generic one. That feedback loop, run consistently, is what turns a prompt library from a static reference into a genuinely improving system.