Claude Cowork for Sales Teams

Your AE gets a meeting notification at 8:47 AM. The call is at 11. She opens LinkedIn, pulls up the company website, checks recent news, looks up the buyer on LinkedIn, searches the CRM for any prior history, and tries to piece together a call brief that will take her 45 minutes to build and will look almost identical to the brief she built for the last call. And the call before that.

That’s not research. That’s a recurring task wearing a research costume. Claude Cowork is the answer to it — a persistent agent that lives across Desktop, iOS, and Android, remembers what you’ve built together, and keeps working when you switch devices. You start the brief on your laptop, check from your phone on the way to the call, and it’s done. That’s the shift.

This guide walks through setting up four persistent threads that run the most repetitive, pattern-heavy work in a sales workflow: pre-call research, pipeline review prep, follow-up drafting, and territory intelligence.

---

What You’ll Build

Four persistent threads, each with a job:

1. Pre-Call Research Thread — generates a call brief whenever you drop in a company name and context

2. Pipeline Review Thread — weekly deal summary with risk flags and next actions

3. Follow-Up Drafting Thread — drafts follow-up emails from your call notes

4. Territory Intelligence Thread — weekly brief on what’s happening at your key accounts

---

Step 1: Setup

Claude Cowork is in Claude.ai. On desktop, go to claude.ai and look for Projects in the left sidebar — that’s the persistent context layer Cowork is built on. On mobile, it’s the same app, same projects, same threads.

Name your threads like file folders. You’ll have four:

• Sales: Pre-Call Research

• Sales: Pipeline Review

• Sales: Follow-Up Drafts

• Sales: Territory Intel

The naming convention matters because you’ll be switching between these on your phone. Clear names save friction at the worst time — right before a call.

That’s it for setup. No API keys. No integrations. No ops ticket.

---

Step 2: Pre-Call Research Thread

Open your Sales: Pre-Call Research thread. Paste this as your first message to establish the context:

You are my pre-call research assistant. Every time I give you a company name, a contact name,and a meeting context, generate a call brief with the following structure:

1. Company Snapshot (3-4 sentences): What they do, their market position, recent news or
   announcements in the last 90 days, revenue/size if available.

2. Contact Context: Role, tenure, background, any public content they've written or posted
   recently, likely priorities based on their function.

3. Likely Objections: Based on company size, industry, and deal stage, what are the 2-3
   most likely objections I'll face on this call?

4. Suggested Opening Question: One question designed to surface their biggest current pain
   point in the first 5 minutes.

5. CRM Flag: Ask me if there's any prior history in our CRM I should factor in.

Keep each brief tight — I need to read it in under 3 minutes before a call.

To use it: drop in “Company: Acme Corp / Contact: Sarah Chen, VP Revenue / Context: discovery call, came in from paid social.” The brief comes back in under two minutes.

---

Step 3: Your First Result

Run it once before you read any further. Pick your next scheduled meeting and paste the company and contact. Review the brief.

What you’re looking at is the standard output: company snapshot, contact background, objections, opening question. Not perfect — you’ll refine with your CRM context and anything the rep already knows. But it’s 80% of the work, done before you’ve finished your coffee.

On mobile, the thread is right where you left it. On the way to the call, open the app, check the brief, add any CRM notes you pulled before you left the office. The thread holds all of it.

That’s the first win. The rest is below the line.

---