Claude Cowork for sales

1. 0:00 – 0:05

   Intro

   1. SPSpeaker0:00

      [gentle music]

2. 0:05 – 0:36

   AE meeting prep pain: critical account context scattered across systems

   1. SPSpeaker0:05

      A mark. [upbeat music] Hi, I'm Brittany. I'm a growth account executive, and I manage a portfolio of our most strategic startup accounts. Before I meet with a customer for the first time, I need to get smart on them fast. Who are they? What are they building? How are they using Claude today? What's their spend look like today on us? And what are the risks and growth trends of this account? Now, all of this information exists today, but it's scattered across Salesforce, our data warehouse,

3. 0:36 – 0:51

   Using Claude Cowork to replace manual research with a reusable skill

   1. SPSpeaker0:36

      call recordings, Slack, email, on the web. Pulling this together used to mean hours of manual research, but with Claude Cowork, I have a skill that does it for me in minutes. To actually build the skill, I open up a Cowork session and describe what I'd want to know walking into that meeting.

4. 0:51 – 1:06

   Building the Account Strategy Builder skill from a conversation

   1. SPSpeaker0:51

      Claude drafted a skill file from that conversation, which is basically a text file that tells Claude how to approach the task, what data sources should it be looking at, what usage signals matter, and how

5. 1:06 – 1:36

   Connecting data sources and keeping the skill transparent via plain text

   1. SPSpeaker1:06

      to actually present the analysis. In my settings here, I've already connected to our data warehouse, Salesforce, the web, email, and Slack, and I picked a folder on my desktop where Claude can read, edit, or save the files. I ran it on a test account, refined it, and because the file is in plain text, I can always open it and verify what it's doing. So tomorrow I've got my first call with a customer. What I do to prep is head into Cowork, type slash, pick

6. 1:36 – 1:51

   Running the skill before a customer call with a simple slash command

   1. SPSpeaker1:36

      the account strategy builder skill, and name the account Acme Corp. [upbeat music] Once I enter, Claude will start running all the data pulls at the same time. Calls from the last ninety days, revenue trends, open opportunities that exist in

7. 1:51 – 2:06

   Parallel data gathering: calls, revenue, pipeline, comms, and external signals

   1. SPSpeaker1:51

      Salesforce, any relevant data in my email, calendar activity, Slack, and any funding trends or things on the web that are most relevant. Then it synthesizes everything into a strategy doc and saves it to my account folder. As you can see, the

8. 2:06 – 2:21

   Synthesizing into a saved strategy doc: brief, stakeholders, deals, and risks

   1. SPSpeaker2:06

      output will read like a full account brief, spend information, stakeholder mapping, what Claude models the user is building with, open deals, and risk signals.

9. 2:21 – 2:37

   Better first conversations: arrive with context instead of orientation questions

   1. SPSpeaker2:22

      Now I have the full landscape of the account before I've even talked to the customer, and it makes for a way more strategic first conversation. Instead of spending the meeting just getting oriented, I can show up with real context and make the first impression count. Now after

10. 2:37 – 2:52

    Post-meeting workflow: reusing retained context in the same Cowork session

    1. SPSpeaker2:37

       the meeting, I head back into the same Cowork session and Claude still has the account context loaded. I type slash, pick the call transcript processor, and Claude will pull the call transcript and generate three things:

11. 2:52 – 3:07

    Call Transcript Processor outputs: action items, internal recap, and customer follow-up

    1. SPSpeaker2:53

       my personal action items, an internal Slack message with key takeaways, next steps, and action owners, and a customer follow-up message. [upbeat music] You can see here that each one

12. 3:07 – 3:30

    Human-in-the-loop review: approvals before messages are sent

    1. SPSpeaker3:07

       comes up for my approval before it actually sends. Now, the whole post-meeting flow that used to take me thirty minutes is done in just a couple minutes, and it's way more thorough than what I'd write from memory. With Claude Cowork, I'm pulling insights from multiple different systems and turning them into real account strategy. The quality of every customer conversation is better for it. [upbeat music]

Episode duration: 3:31