Claude for Sales

How to Use Claude AI for Sales
(7 Workflows That Actually Work)

Not generic AI tips. Seven specific Claude workflows — with real prompts — that B2B sales teams are using right now to do better research, write better outreach, and close more deals.

Why Claude

Why Claude beats ChatGPT
for sales use cases.

ChatGPT for Sales
  • Generic outputs unless you do heavy prompt engineering every time
  • No persistent company context — you re-explain your product on every session
  • Voice and tone drifts — outputs rarely sound like your brand
  • No native way to share a configured assistant with your whole team
  • Short context window limits for pasting full call transcripts
Claude for Sales
  • Claude Projects: your product docs, ICP, talk tracks, and voice live in the Project
  • 200K token context window — paste an entire earnings call or 10-page proposal
  • Instruction-following is precise: "write like a senior AE, not a marketer" actually sticks
  • Shared Projects — the whole sales team runs from the same configured assistant
  • Better at nuanced judgment calls: tone calibration, objection navigation, risk flags
7 Sales Workflows

The workflows. With the prompts.

Copy these prompts directly. Adjust the bracketed fields. The ones that work best are the ones you put into a Claude Project with your company context already loaded.

Workflow 01
Prospect Research
Before any outreach or call, Claude builds you a structured account brief — what they do, who the buyers are, what recent news or signals matter, and why your solution is relevant to them right now. Takes 90 seconds instead of 30 minutes.
Example Prompt
I'm preparing to reach out to [Company Name]. They're a [industry] company with about [headcount] employees. Research this company and give me: 1. What they actually do (in plain language, not their website copy) 2. Who likely owns the problem I solve ([describe your solution category]) 3. Any recent news, funding, leadership changes, or hiring signals from the last 6 months 4. 2–3 specific reasons why they'd care about [your product] right now 5. One risk or reason they might not be a fit Be specific and direct. Skip filler.
Workflow 02
Personalized Outreach
Claude writes outreach that doesn't sound like it came from a template — because it's built on real research. The key is feeding it the account brief from Workflow 1 and being specific about what "personalized" actually means.
Example Prompt
Write a cold email to [First Name] at [Company]. Here's what I know about them: [paste account brief from Workflow 1] My product: [1-2 sentence description] What we do for companies like them: [specific outcome] The one insight I want to lead with: [specific hook from research] Write a 5-sentence email. First line: specific to them, not generic. Don't start with "I" or "We." No "I hope this finds you well." End with a low-friction ask (15-min call or simple question). Sound like a peer, not a vendor.
Workflow 03
Objection Handling Prep
Before a big demo or follow-up call, Claude stress-tests your positioning by playing the skeptical buyer. This is more useful than any objection handling doc because it's specific to the account and the deal.
Example Prompt
I have a demo with [Company] tomorrow. They're a [type of company], currently using [competitor or current solution]. Their main concern going in is [known objection or hesitation]. Play the skeptical buyer. Give me the 5 hardest objections they're likely to raise, then help me craft a response to each one. Responses should be direct, not defensive. Don't over-explain. Acknowledge the concern before addressing it. After the objections, tell me the one thing most likely to kill this deal and how I'd handle it.
Workflow 04
Proposal Drafting
After a discovery call, Claude turns your notes into a structured proposal draft in 10 minutes. The output isn't polished enough to send immediately — but it's 80% there, and it's built from what you actually learned in the call, not a generic template.
Example Prompt
I just finished a discovery call with [Company]. Here are my notes: [paste raw call notes] Based on these notes, draft a proposal outline with: - Their situation as I understand it (2–3 sentences — they should read this and feel understood) - The specific problem we're solving - Our recommended approach / what we'd do - Expected outcomes (use their words from the call where possible) - Investment / pricing section placeholder - Next steps Write in a clear, direct tone. No buzzwords. Flag anything I said in the notes that's vague or that I should clarify before sending.
Workflow 05
Call Debrief Notes
Drop a call transcript into Claude and get structured CRM notes, key takeaways, and next steps — in 2 minutes. This workflow alone saves most AEs 20–30 minutes per day and dramatically improves CRM data quality.
Example Prompt
Here's the transcript from my call with [Name] at [Company]: [paste transcript] Give me: 1. A 3-sentence CRM note summary (past tense, third person, factual) 2. Key pain points they mentioned (direct quotes where possible) 3. Objections or concerns raised 4. What they said about timeline and decision process 5. Agreed next steps from the call 6. My assessment: hot/warm/cold and why Format this so I can paste it directly into Salesforce/HubSpot.
Workflow 06
Follow-Up Sequences
Claude writes multi-touch follow-up sequences that don't feel like automated drip campaigns — because each one is built around what actually happened in the conversation, not a generic template.
Example Prompt
Write a 4-email follow-up sequence for [Name] at [Company] after our discovery call. Context: - Main interest: [what they cared about most] - Main concern: [their biggest hesitation] - Their timeline: [when they're looking to decide] - Next formal step: [demo, proposal review, etc.] Email 1 (same-day): recap + one valuable insight from the call Email 2 (3 days later): address the main concern with proof or example Email 3 (7 days later): relevant resource or case study, no pressure Email 4 (14 days later): direct ask about status, easy out offered Each email: under 100 words, no fluff, clear subject line. Sound like a person, not a sequence.
Workflow 07
CRM Update Summaries
At the end of every week, Claude synthesizes your deal notes and tells you which deals need attention, which are stalling, and what to do about it. Better than any pipeline review meeting.
Example Prompt
Here are my active deals with their current notes: [paste deal names, stages, last activity, and notes] Give me: 1. Which 3 deals need my attention most urgently and why 2. Any deals that look like they're quietly going cold (and what the signal is) 3. The one deal I'm probably underestimating or underworking 4. Suggested next action for each deal (one sentence each) Be direct. If a deal looks dead, say so.
Setup Guide

How to set up Claude Projects
for your sales team.

The prompts above work better inside a properly configured Claude Project. Here's how to build one in an afternoon.

01
Create a "Sales" Project in Claude
Go to claude.ai → Projects → New Project. Name it something like "[Company] Sales" so the whole team knows where it lives. This becomes the single place your sales team runs all their AI workflows from.
02
Write a Project System Prompt
This is the most important step. Include: what your company does (in one paragraph), your ICP description, your product's key differentiators, your brand voice for written communication, and what you want Claude to always/never do. The better this is, the better every output will be.
03
Upload Your Context Documents
Add to the Project: your one-page pitch/deck, your top 2–3 case studies, your FAQ doc, your competitor comparison sheet, and your pricing structure. Claude will reference these in every conversation in this Project without you having to paste them every time.
04
Build a Prompt Library
Take the 7 prompts above and customize them with your company details. Save them in a shared doc that the team can reference. The goal is that any rep can start a Claude conversation and get a great output in under 2 minutes — without having to think about how to prompt.
05
Run a Team Training Session
One 60-minute session where you walk through each workflow live, run each prompt with a real account, and show the team how to edit and improve outputs. The goal is comfort and confidence — not just tool awareness.
Get Started

Want these workflows deployed
inside your sales team?

We build Claude Projects configured for your product, your ICP, and your team — and train everyone to use them. Usually done in 2–3 weeks.

We respond within one business day.

You're in good hands.

We'll be in touch within one business day.