Claude for sales: prompts, workflows and what it cannot do

Claude is useful in sales for reading, writing and thinking: summarising an account, drafting and editing messages, preparing a call, planning a campaign and reviewing results. It cannot send safely at volume, remember your leads by itself or know your numbers unless you give it access. Connected to Sellinger through the hosted MCP connector with 43 tools, it can read your leads, campaigns and replies, and writes ask first.

This post is practical. It gives five prompts worth saving, four workflows, the limits, and the point at which a connector is better than pasting text into a chat. For the bigger question of whether an assistant can run outreach, read ChatGPT or Claude: can an assistant run your outreach.

What is Claude good at in a sales job?

Four things stand out.

• Reading. A long thread, a website, a transcript, a job ad. It summarises quickly and finds what matters.
• Writing and editing. First drafts, shorter versions, a different tone, a message in another language.
• Preparing. A one page brief before a call: who the person is, what they said before, three questions to ask.
• Thinking. Comparing two plans, finding the weak point in a pitch, listing objections you will hear.

It is weaker at being right about facts it was not given. It will fill gaps with plausible text, so every prompt should carry the facts and a rule not to invent more.

Which five prompts are worth saving?

Write them once, save them, and edit the details each time.

1. The account brief. "Here is the website text and the person's LinkedIn profile. Write a five line brief: what the company does, what the person is responsible for, one recent event, one question worth asking. Quote the line you used for each fact. If something is not in the text, write 'not found'."

2. The first message. "Write a LinkedIn message of under 60 words to this person. Open with one observation about their work from the text below. Say in one sentence why I am writing. End with one easy question. Do not flatter, do not pitch, do not invent facts."

On our own LinkedIn outbound, openers that state an observation out-replied openers that ask a question by 10 to 15 points, so prompt 2 asks for an observation. See observation openers beat questions.

3. The reply drafter. "Here is the conversation so far. Draft a reply in the same language as the last message. Answer only what was asked. If they asked about price, give only prices I have listed below. If you cannot answer from what I gave you, say so."

4. The objection handler. "The prospect wrote: 'we already have a vendor'. Give me three replies that respect that, each under 40 words, none of which argue. One should ask what they would change if they could."

5. The call prep. "Here are the notes and the thread. List the three things the prospect cares about, the two they have not said, and five questions I should ask in the first ten minutes."

What are four workflows?

Research a list. Paste 20 companies, get a brief for each, read them, mark each as use, edit or skip. Our post on Claude Code for outbound builds this as a small agent.

Draft and review a campaign. Give Claude your ICP and offer, ask for three message angles and three subject lines, then pick one. Do not send them yet. Read them aloud.

Prepare calls. Before each meeting, run prompt 5 on the thread. Five minutes.

Review the week. Give Claude the numbers and ask what stands out. Be careful, because without real data it can only talk in generalities. This is where a connector helps.

What does a connector add?

Pasting is slow and risky. A connector lets Claude read the real thing. Sellinger's hosted MCP connector has 43 tools and 4 saved workflows across leads, prospecting, conversations, campaigns, approvals, meetings, analytics and search. Connecting takes four clicks: Settings, Connectors, add the custom connector, sign in and pick Full access or Read only. Read tools run freely and writes ask first.

With it, the prompts above become short. Ask "which replies need me today?" and Claude reads the inbox. The MCP recipes give ready prompts:

• Prep my day
• Weekly pipeline review
• Audit stale leads
• Approval queue triage
• Daily reply digest

If you want to know what MCP is, the post on what MCP is for sales explains it in plain words.

What can Claude not do?

• Send safely on its own. Limits per account, quiet hours, a suppression check before every send and account safety belong to the platform. On Sellinger, LinkedIn defaults are 20 invitations a day and 150 a week.
• Know what it was not shown. Without a connector or pasted data, it has no idea what happened last week.
• Remember across chats. Each conversation starts from what you give it, unless you use a feature that stores memory, and then you should check what is stored.
• Take responsibility. A message that goes out in your name is yours. Read it.
• Choose your audience. On our account the audience changed meetings per person tenfold. Claude can help you think about it, but your data decides.

For the comparison of Claude with an AI SDR, see Claude against an AI SDR.

How do you start safely?

1. Use approval for anything that writes. Writes should ask first.
2. Begin read only. Let Claude read for a week before it writes.
3. Keep facts in the knowledge base, not in chat history.
4. Review ten outputs a day at the start, and note what it gets wrong.
5. Decide what is private. Do not paste what you would not put in an email to a supplier.

What does a good week with Claude look like?

Monday: ask for the pipeline review and the list of replies that need you. Tuesday to Thursday: prepare each call with prompt 5 and draft replies with prompt 3, reading each before it goes. Friday: ask Claude to compare this week with the last and to propose one rule change for the agent, then decide yourself.

The habit that matters most is the last one. A rule change proposed by an assistant and approved by you is how the agent improves without surprises. Sellinger has a recipe for exactly this, update agent rules from replies, and writes still ask first. Over a few months the rules reflect what your buyers actually say, which is worth more than any prompt library.

A checklist

• [ ] Every prompt carries the facts and forbids invention.
• [ ] I saved five prompts and edit only the details.
• [ ] I use a connector, not pasting, for real data.
• [ ] I started with Read only access.
• [ ] A person reads every message before it goes out.
• [ ] I know what Claude cannot do: send safely, remember, choose the audience.