Claude for sales:
what it does, and where it stops.

Ask Claude to research a prospect, turn a discovery call into action items, or write a cold email, and it is genuinely excellent. Ask it to actually connect with that prospect on LinkedIn, and it stops, because there is no button for it to press. Claude can read public information, reason over your CRM through a connector, and draft a message that sounds like you wrote it on a good day. What it cannot do on its own is take an action on LinkedIn: find a real person, send a connection request, deliver a message. That is not really a Claude limitation. It is a LinkedIn one. There is no official LinkedIn API for people search or messaging, and Anthropic ships no first-party LinkedIn connector, so the phrase "Claude for sales" ends one step before the send.

This guide covers what Claude does well for sales right now, names the exact wall it hits, and shows how to complete the sentence: Claude drafts, you approve, and an MCP connector does the sending.

What can Claude do for sales on its own?

Claude handles the thinking half of selling. On its own it researches accounts and people from public information, summarizes call transcripts into owners and next steps, drafts follow-ups and cold emails, preps objection handling from your notes, and writes a personalized first line per prospect. With a connector it reads your CRM live. The one job it cannot do alone is take any action on LinkedIn.

The clean way to see this is a single table. The left column is Claude by itself with no integrations. The right column is Claude once you add the relevant connector. The two rows at the bottom are the gap this whole article is about.

The connector column is real and worth knowing. Apollo ships a native Claude connector, launched in beta in February 2026, that brings its contact database into Claude, so you can search people and organizations, enrich records, and add prospects to its email sequences from one conversation. It works on any Claude subscription, free accounts included, needs a sign-in with a work email, and "Everything runs on your existing Apollo permissions, plan limits, and credit balance" (Apollo help, updated 1 October 2026). The database itself holds more than 240 million contacts, by Apollo's pricing page checked October 2026. HubSpot is a first-party connector in Anthropic's directory with read and write access to your CRM, so Claude can create and update contacts and deals and log activity (HubSpot, 2026). Salesforce exposes your org through its own hosted MCP server, which you add as a custom connector (Salesforce, 2026).

Sequencing platforms are more cautious about writes: Outreach's MCP server exposes read tools plus create and delete, including adding prospects to a sequence, but deliberately ships no tools that update existing records, citing unpredictable model behavior when editing live data (Outreach, 2026).

Notice what is not in that list. There is no first-party LinkedIn connector in Anthropic's directory, and the two connectors that do execute anything outbound, Apollo and Outreach, both execute into email sequences rather than LinkedIn invites or direct messages (on Apollo, LinkedIn steps stay manual tasks: see the Apollo alternative for LinkedIn outreach). The LinkedIn action lane is the one every native sales connector leaves empty.

The Claude for sales prompts that already work

Use what works before you worry about the gap. Claude is strongest at research, synthesis and drafting, the jobs that need reasoning over text rather than access to a live account. A handful of prompt patterns pay off the day you start, and none of them need anything connected beyond, optionally, your CRM.

1. Account research brief. Paste a company's public site copy, recent posts and a prospect's profile text, then ask for a one-page brief: what they do, likely priorities this quarter, and two angles worth opening on. Claude is good at reading the room from public text.
2. Transcript to action items. Drop in a call transcript and ask for a summary, a list of action items with owners, and a follow-up email under 150 words that references the two things that actually mattered. This is the single most reliable sales use of Claude today.
3. Personalized first lines at volume. Give Claude a list of prospects with one real detail each, and ask for a specific opener per person. This is where warmth shows up in the numbers: Belkins' 2026 benchmark, built on more than 15 million outreach touchpoints, found messages to already-connected prospects replying at 12.2% against 7.9% for cold connector requests (Belkins, 2026). A merge-field template like "Hi {name}, I saw you work at {company}" reads as automated no matter how many fields you add; a real reference does not.
4. Objection scripts from real calls. Feed Claude the objections your team actually hears and ask for a short, non-defensive response to each. Because it drafts from your material, the output sounds like your team rather than a generic playbook.
5. Pipeline triage. With a CRM connector attached, ask Claude to review open deals and flag the five most likely to slip based on stage, close date and last activity, with a suggested next step for each.

The productivity case is real and measured. The Prospecting 2025 report from Outreach found that 100% of AI-powered SDR users reported time savings, with nearly 40% saving four to seven hours a week (Outreach, 2025). Those hours come from the research, drafting and triage jobs above, not from taking the human out of the loop.

Put the idea to work

Less searching.
More conversations.

Tell Vera who you want to reach. Review the first message. Take it from there.

Ask Vera to find leads

Where Claude hits a wall: it cannot act on LinkedIn

Claude cannot search LinkedIn, send a connection request, or message a prospect on its own. There is no official LinkedIn API that exposes people search or messaging to outside developers, and Anthropic ships no first-party LinkedIn connector. So Claude drafts the perfect connection note and then hands it back to you to paste into LinkedIn by hand, one prospect at a time.

This is structural, not a feature Anthropic forgot. LinkedIn keeps its API locked down, and there is no partnership that would let Claude message members through a sanctioned channel. The connector directory reflects it: plenty of sales and CRM connectors, no LinkedIn outreach one. The only way to give Claude LinkedIn reach is a third-party MCP connector, and those are not interchangeable: setup, tool coverage, and what each one can actually do all vary. The full comparison of what is out there is in the guide to a LinkedIn MCP server for Claude.

The distinction that matters is between finding people and deciding what goes out to them. Finding prospects is a research problem: reading profiles and posts, matching them against a brief, and writing an opener that references something real about the person. A well-built connector treats that as its job: it builds the list and drafts a first message per person, then puts a human in front of every send before anything reaches a prospect.

Complete the sentence: Claude drafts, you approve, BeReach sends

The fix is an MCP connector that gives Claude a LinkedIn action layer. BeReach's hosted connector at mcp.bereach.ai loads 32 tools into Claude: it builds the prospect list, drafts a first message per person, and a human approves every one before it sends. In Claude, you decide how much to automate.

Setup is the part that usually goes wrong, and this connector removes most of it. It runs over Streamable HTTP with OAuth 2.1, so you approve it in a browser rather than pasting a key into a JSON file, and it runs on one included model, BeReach 3.0 Flash, so there is no key to bring and no model picker to misconfigure. It also works in ChatGPT and other MCP clients. How to add it is in the docs: Claude and the API, and the current plans are on the pricing page.

If you want to see the finding half in action, the posts reader runs on the same public lane the connector uses, free, right in your browser.

A worked transcript: research to sent, in one conversation

Here is the full loop as an actual Claude conversation, with every send waiting on your review before it goes out. The prompts are yours. The bracketed notes describe what BeReach does when Claude calls the tool.

You: Find heads of data and analytics leads at mid-market ecommerce companies who commented on that post about dashboard fatigue in the last two weeks.

Claude: [calls find posts and post engagers on public data] I found 63 people who commented on that thread. Filtering to data and analytics titles at ecommerce companies brings it to 22. Want me to draft a first message for each?

You: Draft a first-touch connection note for each of the 22. Open on the specific thing they said in the comment, keep it under 200 characters so it stays inside LinkedIn's 300-character note ceiling with room to spare, and do not pitch in the note itself.

Claude: [calls draft dm for each contact] Drafted 22 notes. Each one opens on that person's own comment and asks a question rather than selling. They are sitting in drafts for your review, not sent to anyone yet.

You: Show me the first five.

Claude: [returns the drafts] Here are five. Edit any of them inline, cut the ones you do not like, or tell me to approve the batch.

You: Approve 20, cut two. Send them.

Claude: Connect your LinkedIn account to send these.

Notice where you stayed in the loop. Every draft sat in review before anything reached a prospect, and you cut two before they ever went out. Those two are the ones an unsupervised sender would have delivered without you seeing them first. If you want the finding and drafting to run on a schedule in the background instead of inside a live chat, the same engine does that too, with the same approval gate in front of every send, and it is the subject of the guide to an AI agent for LinkedIn outreach.

Pacing sends within LinkedIn's own limits

The send still has to be paced. LinkedIn throttles connection invitations hardest. LinkedIn does not publish the ceiling, but outreach tooling documentation and support threads converge on roughly 100 invitations per week for a standard account, with higher allowances reported for older accounts and Sales Navigator seats. Spreading approved invites across days instead of firing a batch keeps volume well under that line rather than testing where it sits, since the number LinkedIn actually enforces is undisclosed and shifts with account age and standing. The full picture on caps is in LinkedIn connection request limits, and the current pacing rules are on the usage limits page.

Claude for sales: frequently asked questions