Claude for
sales work
The repetitive parts of a pipeline, translated into things Claude can help with. Research, outreach that still sounds like you, call summaries, and the etiquette of keeping it human.
Sales is one of the places where Claude gets misused the most often. Generic LinkedIn-bot outreach, obvious AI-written follow-ups, the whole thing. The people who use it well do something different: they use it to amplify the human work, not replace it. This page is about that version.
Three places to start
Three workflows where Claude genuinely helps you sell more and sound less like every other rep in the inbox.
1. Research brief before a call
Ten minutes before a call, you want one page on the company and the person: what they do, what's happening in their market right now, what their job probably looks like, and two or three things you could open with that aren't generic. Claude will write this in about thirty seconds from public information plus whatever context you already have.
Pre-call brief prompt, annotated
The shape of a good "read before you dial" prompt.
Where this falls over
It will occasionally confuse companies with similar names or invent a fact that sounds plausible. Always ask for a citation or source for anything specific, and flag the bits you haven't verified.
2. First-draft outreach that sounds like you
This is the one everyone gets wrong. The fix is to show Claude three of your own emails that got replies, so it has your voice to copy. Then give it a specific reason to reach out (not "I noticed you recently..."), a real piece of context, and a word limit. The output is something you'll edit for two minutes rather than rewrite.
Outreach that sounds like a human
The difference between a LinkedIn-bot template and something worth sending.
Subject: Quick question about Acme's operations
Hi Priya, I hope this finds you well. I noticed Acme is scaling quickly and wanted to reach out. We help teams like yours achieve operational excellence through innovative solutions. Would love to set up a quick chat to explore synergies.
The email everyone deletes.
Subject: Measuring the impact of the warehouse rollout
Hi Priya,
Your blog post this week mentioned that measuring the operational impact of the automation rollout has been harder than expected. We've seen exactly that with two logistics teams in the last year, and in both cases the hard bit was not the data, it was agreeing on what "working" looked like before the rollout started.
Worth 20 minutes to compare notes? No pitch, just a conversation. I can come to you or do it by video.
Tom
Where this falls over
If you don't give it a real reason to reach out, it will manufacture one and sound like everybody else. The prompt should explicitly tell it to say so if the reason is thin.
3. Turning raw call notes into a CRM-ready summary
After a call, you have a mess of notes, action items, quotes, and half-finished thoughts. Paste the lot into Claude, ask for a structured summary (who was there, deal stage, what the customer actually said they wanted, objections, next step with owner and date), and you have CRM content in under a minute.
A call summary, as a conversation
A rough reconstruction. Notice the clarifying questions before Claude writes anything.
Where this falls over
If your notes are contradictory or ambiguous, Claude will smooth it over into something that reads well but isn't quite right. The fix is the escape hatch: "flag anything in my notes that's ambiguous rather than smoothing it over".
Worked examples
Before and after, on tasks from sales work.
Prompts to steal
Copy any of these, fill in the square brackets, run.
Try this week
Pick one. All of these are under an hour.
Sales is one of the clearest places to measure whether Claude is helping: are you having more real conversations, or just sending more polished templates? The first is the point. The second is the trap.
If you want to go broader, the Beginner guide covers the habits that apply everywhere. The prompt library has the full set of role-tagged prompts in one place.