Claude for Sales: 7 Workflows With Prompts & Examples

“We’d like to move quickly.” That’s the last line in your notes from a call with Northstar Logistics. You’re meeting them again tomorrow, and you still don’t know who signs off or whether they have a deadline in mind.

Give Claude the call notes and ask it to pull out what the buyer actually agreed to, what’s still open, and the one question worth asking first. In this case, that might be “What needs to happen on your side before you can pick a start date?” Now you have a way to find out what quickly means to the buyer.

That’s a good starting point for using Claude for sales. In this guide, we’ll follow the same fictional account from the first prospecting decision to the forecast review. Each of the seven workflows includes the inputs to give Claude, a prompt you can copy, and a sample output you can use as a reference.

Quick take

• Use Claude across the sales cycle. Research accounts, draft outreach around a verified signal, prepare for discovery, turn call notes into follow-ups, revisit stalled deals, review pipeline, and stress-test your forecast.
• Start with the data you already have. Paste call notes or upload a pipeline CSV. Connect Claude to folk when you want it to work with the CRM records your account can access.
• Ask for a deliverable you can check. Try a one-page call brief, a follow-up email, or a list of proposed CRM updates. For each proposed change, ask Claude to show the current value, the new value, and the evidence behind it.

What Is Claude for Sales?

👉 Claude is Anthropic’s AI assistant. Sales teams can use it to research accounts, draft outreach, prepare for calls, and review their pipeline. How you set it up depends on the task and where the information lives.

Say you need a brief for tomorrow’s discovery call. You can paste your notes into Claude, use the Sales plugin’s call prep workflow in Claude Cowork, or connect your CRM so Claude can pull up the relevant records. You can also use the Sales plugin with a CRM connector.

The plugin gives Claude sales workflows. The connector gives Claude access to records. With folk connected, Claude can look up contacts and deals and make supported updates within your account’s permissions. For your first run, ask it to show the note or field behind each finding so you can check the result against the CRM.

How to Set Up Claude for Your Sales Team in 4 Steps

Start with one deal you know well. You’ll be able to tell whether Claude found the detail that matters or just wrote a convincing summary.

1. Pick One Account and One Deliverable

Choose a deal with a recent conversation and an upcoming next step. For Northstar Logistics, the first task is a pre-call brief that answers three questions.

👉 What did the buyer agree to last time?

👉 What’s still open on their side?

👉 What should the rep ask first?

2. Give Claude Your Team’s Sales Rules

Share the rules Claude needs for this task. For call prep, that might be your stage definitions, qualification criteria, and one example of a brief your team would actually use.

Be specific about what counts as evidence.

For example, “Count a next step as confirmed only when the buyer has agreed to the action. If the owner or date is missing, mark it as unconfirmed.” That keeps a rep’s note like “Aim to start in June” from turning into a buyer commitment.

3. Add Your Notes or Connect Your CRM

Start with notes or a CSV. Paste the relevant call notes and email excerpts for one account. For a pipeline review, upload a CSV with the deal name, stage, next step, and last buyer activity.

Connect folk for CRM context. In Claude Desktop, open Customize in the sidebar, browse connectors, search for folk, and add it. Sign in and authorize your workspace. Claude’s access follows the permissions of the folk account you connect.

4. Run a Read-Only Test Before Updating Records

Use an account where you already know the difference between what the buyer said and what the rep inferred.

Copy-ready prompt :

Find the open deal for [account] in [folk group]. Use the latest available deal notes to list the last buyer-confirmed action, who owns it, and any agreed date. Give the note date and a short supporting excerpt for each finding. Mark missing details as “unconfirmed.” Suggest one question for the next call. Leave all CRM records untouched.

Sample output from the fictional Northstar deal

Check the output against the original note. When you’re ready to update the CRM, ask Claude to show the record, field, current value, proposed value, and supporting evidence first. Apply the changes after you’ve reviewed them.

7 Claude for Sales Workflows With Prompts and Sample Outputs

These workflows follow Northstar Logistics, a fictional account evaluating a tool for managing shift handoffs across warehouses. Each example shows what to give Claude, what to ask for, and what to check before using the result. You can start with notes or a CSV and use connected CRM records where available.

1. Turn Account Research Into a Prospecting Decision

A company opening a warehouse gives you a reason to look closer. The research should tell you who to contact, why now, and what might make the account a poor fit.

Give Claude your ideal customer profile, a company announcement, and any relevant job postings. Include publication dates and links when you have them.

Copy-ready prompt:

Compare [account] with [ICP]. Return the strongest verified signal with its source and date, one problem it might create for [persona], and one finding that would weaken that hypothesis. Then choose REACH OUT, RESEARCH MORE, or SKIP. If the evidence is thin, give me one specific thing to verify before I contact anyone.

Sample output:

⚠️ Before you act: Open the original source and check that the signal is still current. Keep the hypothesis as a question when you write to the prospect.

2. Write Cold Outreach Around a Verified Trigger

The best detail to personalize around is the one that changes what you ask. Here, the third warehouse gives the rep a reason to ask about a specific operational decision.

✔️ Give Claude the verified signal, the prospect’s role, your offer, and one useful resource you can actually share.

Copy-ready prompt:

Write a first-touch email under 80 words for [persona] using [verified signal]. Ask one question about the decision they may be facing. Then write a follow-up under 60 words that offers [resource]. Keep any unverified assumptions in question form. If you can’t connect the signal to the offer in one sentence, tell me what to research next.

Sample output:

Subject: Shift handoffs at the new site

Hi Maya, I saw Northstar is opening a third warehouse. Are you planning to use the same shift handoff process at all three sites, or will the new team set up its own?

We help warehouse teams keep track of what’s still open when shifts change. If you’re revisiting the process for the new site, I’d be happy to share the checklist we use to map it.

Follow-up:

Maya, one item from the checklist is who owns an exception when it’s still open at shift change. That’s often the first decision worth writing down. Happy to send the full checklist if it would help with the new site.

⚠️ Before you send: Make sure the resource exists and the recipient is close enough to the problem to answer the question. If you’re adding more touchpoints, give each one a distinct purpose. See: Multichannel outreach guide

3. Prep for a Discovery Call Around What’s Still Unknown

A useful call brief gives the rep a question that could change the next step. If Maya says Northstar wants to move quickly, the next call needs to establish what’s driving that timing.

✔️ Give Claude the latest email thread, call notes, meeting attendees, and your qualification criteria.

Copy-ready prompt:

Use [notes and emails] to identify the three unknowns most likely to change the next step on this deal. For each one, show what the buyer has already said, what we still need to learn, and one question to ask. Finish with one outcome the rep should aim for by the end of the call. Mark any inference as an inference.

Sample output:

Target outcome: Agree on who owns the security review and what that person needs to get started.

⚠️ Before the call: Check the latest reply. If the buyer has already answered one of these questions, use the time to resolve the next unknown.

4. Turn a Sales Call Into a Follow-Up and CRM Updates

A call recap should separate what you owe the buyer, what the buyer agreed to do, and what’s still open. That distinction also tells you what belongs in the CRM.

✔️ Give Claude the transcript or notes, the current deal fields, and your rules for moving a deal to the next stage.

Copy-ready prompt:

Extract seller commitments, buyer commitments, and open questions from [transcript]. Draft a follow-up email that reflects what each side agreed to. Then list proposed CRM changes with the field, current value, proposed value, and a short supporting excerpt. Preserve the stage and close date unless the evidence meets our rules for changing them. Preview only.

Sample output:

Hi Maya, thanks for walking me through the pilot. I’ll send the security overview today. You mentioned you’d introduce the reviewer by Thursday. Once they’ve had a look, we can work out what a pilot date would depend on.

⚠️ Before you apply changes: Check the transcript and resolve relative dates such as Thursday to calendar dates. Verify the record and group, then approve the specific fields you want updated.

5. Reopen a Stalled Deal With a Reason to Reply

Before drafting another follow-up, find the moment the deal stopped moving. A missed introduction calls for a different message than a buyer who explicitly asked you to wait.

✔️ Give Claude the last few interactions, today’s date, any agreed follow-up date, and a resource or next step you can offer.

Copy-ready prompt:

Identify the last buyer commitment and the issue still blocking progress. Choose SEND, WAIT, or CLOSE THE LOOP. If you choose SEND, draft a message under 65 words that offers one practical way to move the deal forward. If you choose WAIT, give me the date or event that should trigger the next touch.

Sample output:

Decision: SEND. The agreed introduction date passed. Maya still owns the introduction, and the rep can make it easier to forward the relevant materials.

Hi Maya, is it still useful to loop in your security reviewer for the pilot? I can send a short, forwardable note with the overview and the two questions we need their input on. If the review has moved behind the warehouse launch, when would be a better time to pick it up?

⚠️ Before you send: Check for a newer reply or a request to pause. If Maya asked you to wait until after the launch, use that date for the follow-up.

6. Run a Pipeline Review Based on Buyer Activity

A deal can have several recent emails and still have no buyer action scheduled. Ask Claude to surface that gap before the weekly pipeline meeting.

✔️ Give Claude a pipeline export or the relevant CRM group, plus available interaction notes and your criteria for each stage.

Copy-ready prompt:

Review open deals in [group or CSV]. For each deal, list the current stage, most recent buyer action, next buyer commitment and date, and any missing evidence required for the stage. Separate rep activity from buyer activity. Return the three deals that need attention this week with a recommended action, owner, and deadline. Mark unavailable evidence as “unknown.” Keep this read-only.

Sample output:

⚠️ Before the review: Spot-check the latest interaction on flagged deals. If an account has limited activity data, ask the owner what happened before treating it as stalled. See: Sales activity tracking guide

7. Stress-Test Your Sales Forecast Before the Review

A useful forecast tells you which deal changes the number and what needs to happen for it to stay in the quarter. Start with your team’s existing forecast rules.

✔️ Give Claude deal amounts, close dates, current forecast categories, recent buyer activity, and your rules for including deals in each scenario.

Copy-ready prompt:

Build downside, expected, and upside scenarios for [quarter] using [deal list] and [forecast rules]. Show the deals included in each total and the buyer milestone required for any deal that moves between scenarios. Use the amounts in the input. If a deal has an amount but no evidence for its projected close date, flag the missing evidence.

Sample output:

In this fictional example, two deals totaling $82,000 meet the team’s expected-case criteria. One of those, worth $22,000, drops out of the downside case because procurement timing is still open. Northstar is worth $24,000.

⚠️ Before sharing the forecast: Recalculate each total from the deal list. Check that every condition describes something observable, such as a booked review or a confirmed approval date.

How to Check Claude’s Sales Output Before You Use It

Review the parts of the output that could change what you send, what you log, or what you report. Start with any claim about the buyer’s plans, any proposed CRM update, and any deal that moves into or out of the forecast.

→ Outreach. Open the source behind the first line. Northstar’s warehouse announcement gives you a reason to ask about shift handoffs. Check for a direct quote or another source before saying the team is struggling with them.

→ Call recap. Read each commitment alongside the original quote. “I’ll check who owns the security review” belongs in the recap as a task for Maya. Keep the reviewer and review date marked as unconfirmed until she provides them.

→ CRM update. Confirm the workspace, group, and deal record. Compare the current and proposed values. If a teammate edited the field after Claude prepared the preview, review the latest value before applying the change.

→ Forecast. Recalculate the totals and check the deal that drives each change. If Northstar adds $24,000 to the upside case, write down which buyer milestone would justify moving it into the expected case.

Use a Second Pass to Find Claims That Go Beyond the Evidence

Paste the draft and source material into Claude and ask it to flag specific lines. Check those flags against the original notes before you send the draft or update a record.

Copy-ready prompt:

Compare [draft] with [source notes]. Flag any claim where the draft adds certainty, changes who owns an action, or turns a proposed date into an agreed one. For each flag, return the draft line, the closest supporting quote, and a suggested revision. If there’s no supporting quote, mark the claim “unverified.”

💡 folk tip: Ask Claude to compare the Next Step field in folk with the latest documented buyer commitment for each open deal. “Send security overview” is Alex’s task. “Maya will introduce the reviewer by Thursday” tells the team what to look for on the buyer’s side. Ask for a short list of deals where the CRM records a rep task and the buyer’s next action is still unclear. That gives you a list of questions for your next pipeline review.

Give Claude the Sales Context It Needs With folk!

When a buyer asks you to pick up a conversation next quarter, the details might be spread across an email thread, a call recap, and a deal note. folk brings that history together so your team can pick up where the conversation left off. As a CRM for AI agents, it also gives Claude access to that context through folk MCP, within the permissions of your connected account.

What You Can Do With folk and Claude?

✅ Bring prospecting into your CRM. Save contacts from LinkedIn and Sales Navigator with folkX, then organize them by account, territory, or campaign.

✅ Keep conversations tied to the relationship. Sync email and WhatsApp interactions in folk so your team can see who last spoke to the buyer and what they discussed.

✅ Prepare for calls with CRM context. Ask Claude to pull together the latest deal notes, buyer commitments, and open questions before a meeting.

✅ Review pipeline across deals. Use Claude to flag deals with an overdue buyer action or an unclear next step, then check the underlying records in folk.

✅ Update records after a conversation. Use Claude to draft a deal note or propose changes to fields and stages. Review the proposed edits before applying them through the connector.

👉 Try folk CRM for free(14 days, no credit needed)

よくある質問

What Can Sales Teams Use Claude For?

Sales teams can use Claude to research accounts, draft outreach, prepare for discovery calls, turn call notes into follow-ups, and review their pipeline. A good first task is to give Claude the notes from your last call and ask for a brief that separates what the buyer agreed to from what’s still open.

Can You Use Claude for Sales Without Connecting a CRM?

Yes. Paste a call transcript to draft a follow-up, or upload a pipeline CSV to identify deals that need attention. For a pipeline review, include each deal’s stage, next step, and latest buyer activity so Claude can distinguish a quiet deal from one with a scheduled next step.

What’s the Difference Between Claude’s Sales Plugin and a CRM Connector?

Anthropic’s Sales plugin adds workflows for tasks like account research, call prep, and forecasting in Claude Cowork. A CRM connector gives Claude access to the records those workflows can use. You can run the plugin with notes or a CSV, or pair it with a connector to work with CRM data.

Can Claude Update Contacts and Deals in folk CRM?

Yes. Through folk MCP, Claude can make supported updates to contacts, notes, custom fields, and deal stages within the connected account’s permissions. Ask Claude to preview the record, current value, proposed value, and supporting evidence before you approve any changes.

How Do You Make Claude’s Sales Outreach Sound Less Generic?

Give Claude one verified fact that changes what you’d ask the prospect. A warehouse opening, for example, gives you a reason to ask whether the new site will use the same shift handoff process as the others. Include one example of an email you’d actually send so Claude can match its length and tone.

Can Claude Build a Sales Forecast From a CSV?

Yes. Include deal names, amounts, expected close dates, forecast categories, and any buyer milestones that affect timing. Give Claude your rules for the downside, expected, and upside cases, then ask it to list the deals behind each total. That makes it easier to check the math and see which buyer decision could move the forecast.