Claude CoWork for Sales Reps

What is Claude CoWork?

Claude CoWork is the practice of using Claude as a persistent, knowledgeable co-worker embedded in your daily sales workflow. This is not about asking a chatbot to write a generic follow-up email. It is about configuring Claude with your product knowledge, deal context, and communication style so that every interaction produces output that moves pipeline forward.

Claude-native prompts. The prompts in this guide use Claude's native XML tag structure (<context>, <instructions>, <avoid>) for more precise, consistent output. These tags help Claude parse your intent with less ambiguity.

Think of Claude as the most diligent sales analyst on your team, one who has read every case study and can prep you for a call or draft a proposal in seconds. This guide covers setup, the five highest-impact workflows, and the prompting techniques that separate generic output from production-ready content.

Install the Sales Representative Plugin

This guide works on three Claude surfaces. The plugin is the fastest path on two of them. Pick whichever you use:

If you're on Cowork (desktop or mobile app)

Claude Cowork is Anthropic's agentic workspace — Claude completes work autonomously and returns finished deliverables. The Sales Representative plugin packages the workflows below as native skills and slash commands.

Open the Cowork plugin directory in your desktop app.
Filter by Cowork, search for "Sales Representative", and click Install.
The plugin's slash commands and ambient skills are now available in any Cowork task.

If you don't see the plugin in the directory yet, install via custom marketplace: paste https://github.com/alexclowe/awesome-claude-cowork-plugins in your Cowork plugin settings.

If you're on Claude Code (CLI)

Install from your terminal:

claude plugin add alexclowe/awesome-claude-cowork-plugins/sales-rep

The plugin's slash commands and skills load on next session.

If you're on Claude.ai (web chat only)

Plugins aren't directly installable on the web chat surface. You have two options:

Use the prompts in this guide directly in a Claude Project (covered in the next section). Same outputs, more typing.
Upload the plugin's skills as a zip via Settings → Features → Custom Skills (Pro/Max/Team/Enterprise plans). Higher friction; only worth it if you want the auto-activating skills, not the slash commands.

What the plugin gives you (any surface)

Slash command	What it does
`/prospect-brief`	Generate research summaries for upcoming calls with company background, news, and pain points
`/follow-up`	Draft email sequences for post-meeting, post-demo, and nurture scenarios
`/sales-proposal`	Create proposals with value proposition, pricing, ROI analysis, and competitive positioning
`/call-prep`	Build pre-call research briefs with talking points, discovery questions, and objection handling

Auto-activating skills (no command needed — Claude applies them when relevant):

Sales Strategy — Consultative selling, value-based positioning, objection handling, and deal strategy
Sales Communication — Professional persuasive writing, personalization at scale, and buyer-centric messaging

The plugin works standalone for one-off tasks. Pair it with the surface-specific setup below for persistent context across every task — that combination is the full Claude CoWork setup.

Setting Up Claude for Sales Work

Surface note: The Project setup below is for claude.ai web users. Cowork users have their own task-context mechanism (set context once when starting a Cowork task). Claude Code users get the plugin's ambient skills automatically — no Project setup needed. The workflows themselves are surface-agnostic — paste the prompts wherever you're working. The key to getting consistently useful output is using Claude Projects. A Project lets you set custom instructions that persist across every conversation.

Step 1: Create a Sales Project. In Claude, click "Projects" and create one called something like "My Sales Desk."

Step 2: Set your custom instructions. In the Project settings, add:

You are my sales assistant. Here is my context:

<business-profile>
- Name: [Your Name], [Your Company]
- Product/Service: [What you sell, in one sentence]
- Target market: [Industry / company size / buyer persona]
- Average deal size: $[X] | Sales cycle: [X weeks/months]
- Key competitors: [Competitor A, Competitor B, Competitor C]
- Communication tone: [Consultative / Direct and data-driven / Friendly and solution-oriented]
</business-profile>

<rules>
- Never fabricate competitor claims, pricing, or product capabilities.
- All outbound emails must comply with CAN-SPAM requirements.
- Focus on value and outcomes, not feature dumps.
- Match my voice: [paste a sample email].
</rules>

Step 3: Upload reference documents. Add your product one-pagers, case studies, pricing guides, and battle cards to the Project knowledge base.

Step 4: Start every session inside this Project.

Your Top 5 Workflows with Claude

1. Call Prep Briefs

Walking into a call without preparation is walking into a negotiation unarmed. Claude can build a research brief in minutes.

<task>Create a call prep brief for my upcoming discovery call.</task>

<context>
- Prospect: DataFlow Inc., mid-market data analytics company, ~250 employees
- Contact: Sarah Chen, VP of Operations (inbound demo request)
- Their website mentions: rapid growth, Series B, expanding into healthcare
- Our product: workflow automation platform
</context>

<instructions>
- Summarize what we know about the company
- List 5 discovery questions tailored to their likely pain points
- Identify 2-3 relevant case studies, note potential objections
- Include a suggested 30-minute call agenda
</instructions>

<avoid>Generic questions or assumptions about budget and timeline.</avoid>

Before Claude: 20-30 minutes researching and building notes. After Claude: 3 minutes to paste context, 5 minutes to review.

2. Follow-Up Emails

Speed and relevance win deals. Claude drafts follow-ups while the details are fresh.

<task>Draft a follow-up email after my discovery call with Sarah Chen at DataFlow.</task>

<context>
- Pain points: manual data reconciliation (15+ hrs/week), no process visibility, scaling 12 to 30 people
- Most interested in: automation templates and reporting dashboard
- Next steps: I send a custom demo link, she loops in CTO
- Objection: concerned about Snowflake integration (we have a native connector)
</context>

<instructions>
- Recap 3 key pain points in her language, confirm next steps
- Address Snowflake concern briefly, include demo link placeholder
- Under 150 words, professional but warm
</instructions>

<avoid>"Just checking in" language or rehashing features she did not ask about.</avoid>

Before Claude: 15-20 minutes drafting a thoughtful follow-up. After Claude: 2 minutes to paste call notes, 2 minutes to review.

3. Proposals

Claude can draft the narrative sections while you focus on pricing and terms.

<task>Draft the executive summary and solution overview for a proposal.</task>

<context>
- Prospect: DataFlow Inc., 250 employees, data analytics
- Problem: manual reconciliation (15+ hrs/week), no visibility, scaling team
- Solution: workflow automation, Snowflake integration, Professional tier, 30 seats
- ROI: estimated 60% reduction in manual time, ~$180K/year savings
- Competitor in play: CompetitorX (they prefer our UI and support)
</context>

<instructions>
- 2-paragraph executive summary framing problem and solution
- 3-4 paragraph solution overview mapping capabilities to pain points
- Quantify ROI, reference growth plans, confident tone
</instructions>

<avoid>Generic superlatives, naming competitors, unsubstantiated ROI claims.</avoid>

Before Claude: 60-90 minutes writing proposal narratives. After Claude: 5 minutes to input context, 10 minutes to refine.

4. Prospect Research Briefs

Before reaching out cold, Claude can synthesize what you know into actionable intelligence.

<task>Build a prospect research brief based on my gathered information.</task>

<context>
- Company: Meridian Health Systems, regional healthcare provider, 1,200 employees
- Recent news: expanding into telehealth, hired new CIO from Amazon
- Contact: David Park, Director of IT Infrastructure (posts about cloud migration)
- Our angle: compliance workflow automation for healthcare orgs
</context>

<instructions>
- 3-4 bullet company summary, top 3 pain points we address
- Personalized outreach angle based on David's background
- Draft a 75-word cold email, list 2 relevant case studies
</instructions>

<avoid>Fabricating information or making claims about their vendor stack.</avoid>

Before Claude: 25-35 minutes researching before outreach. After Claude: 5 minutes to compile, 3 minutes to review.

5. Objection Handling Scripts

Claude can build objection-handling playbooks tailored to your product and market.

<task>Create objection handling scripts for our healthcare vertical.</task>

<context>
- Product: workflow automation for healthcare compliance
- Objections: (1) "We already have a system," (2) "HIPAA concerns with cloud tools," (3) "No budget until next FY," (4) "IT team too busy for implementation"
- Differentiators: SOC 2 Type II, HIPAA BAA included, 3-week avg implementation
</context>

<instructions>
- For each: the objection, a reframe, a 3-4 sentence response, a follow-up question
- Ground responses in actual differentiators, consultative tone
</instructions>

<avoid>Dismissing objections, overpromising, or badmouthing competitors.</avoid>

Before Claude: 45-60 minutes building a new objection playbook. After Claude: 5 minutes to list objections, 5 minutes to refine.

Prompt Engineering Tips for Sales Reps

1. Always specify the deal stage. "Write a follow-up after discovery" produces very different output than "write after a pricing objection." Tell Claude exactly where you are in the cycle.

2. Use the prospect's language. Include the exact words your prospect used in calls. Claude mirrors this language back, which builds trust.

3. Set strict word limits. Prospects do not read long emails. Keep outreach under 100 words, follow-ups under 150, proposals tight.

4. Provide your competitive positioning. Upload battle cards to the Project. Claude weaves differentiators naturally into proposals and objection responses.

5. Ask for multiple angles. "Give me 3 versions with different value prop leads" for outreach. Testing hooks is how you find what resonates.

6. Use Claude to pressure-test your pitch. Ask: "What objections would a skeptical CTO raise after reading this?"

Privacy & Compliance

CAN-SPAM compliance for emails. All commercial emails must include an opt-out mechanism, your physical business address, and accurate subject lines. Never draft emails that disguise their commercial intent.

No fabricating competitor claims. Never generate false statements about competitors' products, pricing, or limitations. Stick to factual, verifiable differentiators.

Verify all pricing and terms. Claude cannot check your current price book. Always verify every number in a proposal against approved pricing before sending.

Prospect data privacy. Do not paste financial statements or confidential documents. Use summaries: "250-person analytics company, Series B" rather than uploading confidential materials.

Going Further

Ready to build on this foundation? Check out these resources:

Browse our full collection of sales prompt packs and cheat sheets for ready-to-use templates
Run an AI readiness audit for your sales practice to identify your biggest opportunities
Explore AI-powered tools built specifically for sales reps to automate even more of your workflow