How to use Claude for sales: the complete workflow

Four ways to run outbound: the honest comparison

Before the workflow, it helps to see where this approach actually fits. Here is the honest version against the alternatives most small businesses and solo operators weigh up.

An SDR is still the right call if you have the budget and want a human carrying the relationship from the first reply. A sales-engagement suite is fine if you enjoy the dashboards and already have your list and your copy sorted. But if you want the sourcing, the enrichment, the scoring, the personalisation, and the follow-up to happen in one place, on your own data, at near-zero monthly cost, Claude connected to your stack is now a real option. This guide walks the whole loop.

What "Claude for sales" actually means

The phrase gets used two ways. The shallow version is "ask Claude to write a cold email," which is useful but is maybe a fifth of the job. The version that actually fills a pipeline is Claude with tools connected: it pulls a list of companies that fit your ideal customer, enriches each row with the contact and firmographic detail you need, scores the list so you work the strongest leads first, writes a specific opener for every one, drafts the follow-ups, and writes each touch back to your CRM. That is a sales operation, not a chat.

The honest framing: Claude does not replace the part of sales that is relationship and judgement. It removes the manual labour around it. You still decide who is worth pursuing, you still read every draft before it sends, and you still carry the conversation once someone replies. Claude does the sourcing, the enrichment, the scoring, the first-draft personalisation, and the CRM bookkeeping that used to eat your whole week.

The five jobs Claude can actually do for sales

Outbound is not one task. It is five, and Claude handles each one differently. The loop below is the same one we run on this business every week.

The rest of this guide takes each of those five and shows the actual setup and the prompt patterns that work.

Step 1: Connect Claude to a real lead source and your CRM

This is the step that separates a real sales engine from a clever copywriter, and it is a one-time setup. Claude talks to outside tools through MCP servers, small connectors that give it a specific capability. For sales, the two that matter most are a lead source (a scraper like Apify, or an enrichment provider like Apollo) and a connection to your CRM database.

Once those are wired in, you stop describing your prospects to Claude and start asking it to go find them and remember them. The difference in output is night and day. Instead of "write a cold email to a marketing agency," you can say "pull 50 marketing agency owners in Sydney with 2 to 15 staff, enrich them with role and email, and skip anyone already in my CRM." That is a real instruction against real data, and the result is a list you can work, not a paragraph you have to find people for.

Step 2: Enrich and score, so you work the right leads first

A raw list of names is not a pipeline. Two jobs turn it into one: enrichment, filling in the role, company size, location, and verified contact detail you need to reach someone, and scoring, ranking the list so your limited outreach hours go to the strongest fits. Done by hand, both are tedious enough that most solo operators skip them and just blast the whole list. That is exactly why most cold outreach gets ignored.

Connected to an enrichment provider, Claude fills the gaps automatically, then scores every lead against your own ideal-customer criteria, demoting the mismatches and surfacing the 20 or 30 people most worth your time. You pick from evidence instead of working the file top to bottom. The criteria live in your stack, so the scoring reflects your judgement, not a generic vendor formula.

Step 3: Write outreach that is genuinely written for one person

This is where most "AI sales" goes wrong. A lazy prompt produces a message that reads like every other automated email and converts like none of them. The openers that get replies share a quality: they prove you actually know something specific about the person, they name a real problem that person has, and they ask for one small thing. A name slotted into a template is not personalisation, and prospects can tell instantly.

Claude is good at producing real personalisation on demand, because it can read what it just enriched, the company, the role, a recent signal, and write a specific first line for each lead. But you have to ask for it properly, which is what the weak-versus-strong example above shows. The skill below encodes that structure so you are not re-explaining it every time. And the judgement of whether a finished message is worth sending, whether it actually respects the person's time, stays with you. That review is the part that keeps your domain reputable and your brand intact.

Step 4: Run the follow-up nobody else does

You can write the best opener in your niche and earn nothing if you never follow up, and most people do not. The majority of replies come after the first message, yet the first message is usually where outbound stops. On top of that, the manual bookkeeping of "who replied, who went quiet, who am I about to accidentally double-message" is exactly the kind of admin a solo operator drops first.

With your CRM and a LinkedIn or email connection in place, Claude carries the follow-up for you. It drafts the timed second and third touches, checks the conversation history so it never messages someone who already replied, and builds you a daily "who is waiting on me" view: hot replies to answer, prospects who went silent, connections that accepted but never got a first message. The asset is the same as in step three, real drafts you approve, but now applied to the part of the funnel where deals are actually won or lost.

Then there is the reactivation work: the accepted connections and old conversations that just need one good nudge. Claude pulls them straight from your CRM and tells you which are worth a fresh touch. That is some of the highest-return time in outbound, and it is sitting in data most people never open.

Step 5: Keep the CRM honest, automatically

The reason most pipelines are a fiction is that logging is manual and manual logging never happens. You send a message, you mean to log it, you forget, and a week later you have no idea who you have already contacted or who is mid-conversation. The dark funnel is not a strategy problem, it is a bookkeeping problem.

When Claude runs the outreach, it writes the event back the same moment it acts. Connection sent gets logged. A reply comes in, the contact moves stage. A proposal goes out, it is recorded with the file and the version. Because the CRM is the same database the outreach runs on, there is no integration tax and no second system to keep in sync. The payoff is that you can finally answer the question that matters: what actually brought this customer from a cold name to a closed deal, and which step of the loop is worth doing more of.

The honest limits

A few things Claude will not do for you. It will not build the relationship: once a prospect replies with real interest, the conversation is yours to carry, and no workflow shortcuts the trust that gets built in a back-and-forth or a call. It will not override deliverability and compliance for you: a cold domain still needs warming, volume still needs caps, and people still need an easy way to opt out, none of which a clever message fixes. And it will not send anything to a real prospect on its own. Every external touch goes through your review first, on purpose. Autonomous sending is how accounts get burned and reputations get damaged.

What it does remove is the labour. The sourcing that took an afternoon, the enrichment nobody finishes, the scoring everyone skips, the follow-up that never gets sent, the CRM that is always out of date. Hand those to Claude and the part that is left is the part that was always the actual work: deciding who is worth your time, reading every message before it ships, and being genuinely useful to the person who replies.

SoloStack runs its entire sales operation this way, in one repo, on the same database as the CRM and the rest of the business. We build that setup with you, live, in the workshop.

Skills referenced in this article

Every skill linked above, in one table. Each is a free, downloadable Claude Code prompt.