Claude for Sales Teams: Prospecting and Closing with AI

Prospect Research

Prospect research is the most time-consuming task — and the one where Claude delivers the most value.

Prospect Brief in 2 Minutes

Prepare a prospect brief for my sales meeting.

Company: TechStart Inc. (B2B fintech, 80 employees, New York)
Contact: Marie Johnson, VP Engineering
My offer: Cloud infrastructure monitoring platform

Produce:
1. Company summary (business, size, recent funding round)
2. Likely challenges for a VP Engineering at an 80-person fintech
3. Typical cloud infrastructure pain points in this context
4. 5 questions to ask during the meeting
5. 3 positioning angles for my offer vs. their challenges
6. Likely objections and prepared responses

Batch Research: 20 Prospects in 30 Minutes

Create a dedicated Claude Project for prospect research:

1. →Project instructions:

You are a research assistant for the sales team at [company].
Our offer: [short description].
Our target: [typical persona].
For each prospect, produce a structured 200-word max brief with:
company context, likely challenges, recommended approach angle.

2. →Usage: Paste each prospect's information (website, LinkedIn) → brief in 30 seconds

Personalized Prospecting Emails

The AIDA Framework with Claude

Write a prospecting email using the AIDA framework.

Prospect: [Name], [Title] at [Company]
Context: [recent news, identified pain point, or trigger event]
My offer: [1-sentence description]
Key benefit: [measurable outcome]

Constraints:
- Subject line: max 50 characters, no spam trigger words
- Body: max 120 words
- 1 single clear CTA
- Tone: professional but human (not corporate)
- Obvious personalization from the first sentence

Personalization Examples by Trigger Event

Multi-Touch Sequence

Create a 4-touch prospecting sequence for [persona].

Touch 1 (D0): Email — personalized with trigger event
Touch 2 (D+3): LinkedIn — connection request with contextual note
Touch 3 (D+7): Email — value-add (insight or case study)
Touch 4 (D+14): Email — breakup email with final proposition

For each touch: complete content, objective, and success criteria.
Tone: assertive but not pushy.

Sales Scripts

Discovery Call Script

Create a discovery call script (30 min) for an AE selling [product] to [persona].

Structure:
1. Introduction and rapport-building (2 min)
2. Prospect context — situational questions (5 min)
3. Pain point identification — impact questions (10 min)
4. Pain quantification (5 min)
5. Positioning presentation (5 min)
6. Next steps (3 min)

For each section: exact phrases, questions to ask, and natural transitions.
Include conditional branches: if the prospect says X → continue with Y.

Objection Handling

I sell [product] to [persona]. Here are the 10 most common objections:

1. "It's too expensive"
2. "We already use [competitor]"
3. "It's not a priority this year"
4. "I need to talk to my boss"
5. "Send me a presentation"
6. "We handle that in-house"
7. "We've had a bad experience with a similar product"
8. "The timing isn't right"
9. "We're in the middle of a reorg"
10. "Your company is too small/young"

For each objection, provide:
- Type (price, timing, authority, need, trust)
- Recommended response (50 words max)
- Follow-up question to regain control
- Concrete example of a successful response

Sales Proposals

Proposal Generation

Write a sales proposal for [prospect].

Context:
- Company: [name], [industry], [size]
- Contact: [name], [title]
- Pain points identified during discovery: [1, 2, 3]
- Budget discussed: [amount]
- Desired timeline: [date]

Proposal structure:
1. Executive summary (the problem and our solution in 100 words)
2. Understanding of challenges (use their words)
3. Proposed solution (features aligned with their pain points)
4. Projected ROI (calculation based on discovery figures)
5. Deployment plan (realistic timeline)
6. Investment (pricing with options)
7. Next steps

Tone: consultative selling — we solve their problem, we don't sell a product.

Competitive Battle Card

Create a battle card for my product [product] vs. [competitor].

For each category, provide our advantage and the repositioning script:

| Category | Our advantage | Their advantage | Script if prospect mentions [competitor] |
|----------|--------------|----------------|------------------------------------------|

Categories: price, features, UX, support, integrations, scalability, security.

Pipeline Analysis

Pipeline Diagnostics

Here is my quarterly sales pipeline (CSV):

[paste data: deal, amount, stage, creation date, last activity, probability]

Analyze:
1. At-risk deals (inactive >14 days, declining probability)
2. Velocity by stage (average time in each stage)
3. Stage-by-stage conversion rate
4. Forecast: revenue prediction based on weighted probabilities
5. Top 3 priority actions to improve close rate this quarter

Win/Loss Analysis

Here is the summary of our last 20 closed opportunities (10 won, 10 lost).

For each deal:
- Size: [small/medium/large]
- Industry: [industry]
- Sales cycle: [duration in days]
- Win/loss reason: [1-sentence summary]

Analyze:
1. Patterns of won deals (size, industry, duration)
2. Patterns of lost deals
3. Recurring success factors
4. Recommendations to improve win rate
5. ICP (Ideal Customer Profile) based on the data

CRM Enrichment

Enrichment Workflow

1. →Export: Export your contacts from Salesforce/HubSpot (CSV)
2. →Claude prompt:

Here is a list of 50 B2B contacts. For each contact, enrich with:
- Company summary (20 words)
- Likely role-specific challenges
- Recommended approach angle (1 sentence)

Format: CSV with added columns.
[paste the data]

3. →Import: Re-import the enriched CSV into your CRM

Qualitative Scoring

Here are 20 inbound leads from this week (source: landing page form).

For each lead, assign a qualitative score (A/B/C/D) based on:
- Title relevance vs. our target persona
- Company size (sweet spot: 50-500 employees)
- Message left (buying intent vs. curiosity)
- Perceived urgency

Justify each score in 1 sentence.

[paste the data]

Meeting Preparation

Pre-Meeting Brief

Post-Meeting Summary

Here are my notes from the meeting with [prospect]:
[paste raw notes]

Produce:
1. Structured summary (5 key points)
2. Action items with owner and deadline
3. Confirmed pain points (vs. pre-meeting hypotheses)
4. Buying signals detected
5. Recommended next steps
6. Ready-to-send follow-up email

Format: directly copyable into Salesforce/HubSpot.

Sales Coaching and Training

Sales Roleplay

Let's simulate a discovery call.
You play the role of the prospect: [persona, title, company, challenges].
I am the salesperson selling [product/service].

Prospect behavior:
- Start skeptical but open
- Mention 2-3 pain points when I ask the right questions
- Raise the price objection toward the end
- Ask for a demo if I handle the objection well

After the call, give me structured feedback:
- What I did well
- What I could improve
- Score out of 10 for: active listening, questioning, positioning, closing

Call Analysis

Here is the transcript of a 30-minute sales call.

Analyze the salesperson's performance:
1. Talk ratio salesperson vs. prospect (ideal: 30/70)
2. Question quality (open vs. closed)
3. Active listening (does the rep use the prospect's words?)
4. Objection handling (technique used, effectiveness)
5. Closing attempt (timing, technique, naturalness)
6. Overall score /10 and top 3 improvement areas

[paste the transcript]

The Daily Sales Workflow with Claude

Total: 75 minutes/day with Claude → 5-8 hours saved/week.

Mistakes to Avoid

1. →Sending emails without reviewing — Claude generates excellent drafts but always verify facts and tone
2. →Over-automating — The sales relationship stays human. Claude prepares, you execute
3. →Ignoring soft signals — Claude doesn't read body language. Your sales instinct remains essential
4. →Using the same templates — Vary your approaches. If all your emails look alike, prospects notice
5. →Forgetting CRM data — Keep your CRM updated. Claude can only analyze the data you provide

Read Next

• →Building a Customer Support Chatbot — Complete guide to building a support chatbot with Claude
• →Claude for Customer Support Teams — Integrate Claude into your support teams