CHAPTERS
- 0:05 – 0:36
AE meeting prep pain: critical account context scattered across systems
Brittany, a growth account executive, explains the challenge of preparing for first-time customer meetings quickly. The information she needs exists, but it’s fragmented across tools like Salesforce, a data warehouse, call recordings, Slack, email, and the web.
- •Needs fast understanding of who the customer is and what they’re building
- •Must assess current Claude usage, spend, risks, and growth trends
- •Relevant context is distributed across many internal and external sources
- •Manual research previously required hours of effort
- 0:36 – 0:51
Using Claude Cowork to replace manual research with a reusable skill
She introduces Claude Cowork as a way to automate account research in minutes. The key is creating a “skill” that standardizes what to pull, how to evaluate signals, and how to present results.
- •Claude Cowork consolidates multi-source research into a faster workflow
- •A skill encapsulates the research approach and output format
- •Moves from ad-hoc digging to repeatable, consistent account prep
- 0:51 – 1:06
Building the Account Strategy Builder skill from a conversation
Brittany describes creating the skill by starting a Cowork session and explaining what she wants to know before a meeting. Claude turns that into a skill file that guides data sourcing, signal selection, and analysis formatting.
- •Skill is generated from natural-language requirements
- •Skill file specifies task approach, sources to query, and usage signals
- •Defines how Claude should present a final analysis/brief
- 1:06 – 1:36
Connecting data sources and keeping the skill transparent via plain text
She shows the setup where Claude is connected to core systems and a local folder for file access. Because the skill is plain text, she can refine and verify what it does over time.
- •Connects data warehouse, Salesforce, web, email, and Slack
- •Selects a desktop folder Claude can read/edit/save to
- •Runs on a test account and iterates based on output quality
- •Plain-text skill file enables reviewability and control
- 1:36 – 1:51
Running the skill before a customer call with a simple slash command
Ahead of a scheduled call, Brittany invokes the Account Strategy Builder skill and specifies the account name. Claude then begins parallel data pulls to assemble a complete account picture.
- •Launches Cowork and selects the skill via “/” command
- •Inputs the target account (example: Acme Corp)
- •Claude executes multiple data pulls concurrently to save time
- 1:51 – 2:06
Parallel data gathering: calls, revenue, pipeline, comms, and external signals
Claude collects recent calls, revenue and spend trends, and Salesforce pipeline details, plus communication and scheduling signals. It also checks web-based indicators like funding and other relevant external context.
- •Analyzes call recordings/transcripts from the last 90 days
- •Pulls revenue trends and Salesforce open opportunities
- •Reviews relevant email, calendar activity, and Slack context
- •Adds web signals such as funding trends and notable updates
- 2:06 – 2:21
Synthesizing into a saved strategy doc: brief, stakeholders, deals, and risks
Claude compiles everything into a structured account strategy document and saves it into the account folder. The output reads like a full account brief designed for immediate pre-meeting readiness.
- •Produces a “full account brief” style deliverable
- •Includes spend information and stakeholder mapping
- •Summarizes what the customer is building with Claude models
- •Surfaces open deals and risk signals
- •Automatically saves the doc to the designated folder
- 2:21 – 2:37
Better first conversations: arrive with context instead of orientation questions
With the pre-read complete, Brittany can shift the first meeting from discovery basics to a more strategic conversation. This improves the customer experience and strengthens first impressions.
- •Shows up with real context before speaking to the customer
- •Reduces time spent getting oriented during the call
- •Enables more strategic questioning and positioning
- •Improves first impression and meeting quality
- 2:37 – 2:52
Post-meeting workflow: reusing retained context in the same Cowork session
After the call, she returns to the same Cowork session where the account context remains loaded. This continuity makes follow-up generation faster and more accurate.
- •Account context persists across the meeting lifecycle
- •No need to re-explain background for post-call tasks
- •Supports a seamless pre-to-post meeting workflow
- 2:52 – 3:07
Call Transcript Processor outputs: action items, internal recap, and customer follow-up
Brittany triggers a second skill to process the call transcript. Claude generates personal action items, a Slack-ready internal summary with owners, and a customer follow-up message.
- •Pulls the call transcript automatically
- •Creates a personal action item list
- •Drafts an internal Slack message with takeaways, next steps, and owners
- •Drafts a customer follow-up email/message
- 3:07
Human-in-the-loop review: approvals before messages are sent
She emphasizes that outputs appear for her approval before sending. This keeps the workflow fast while preserving control and accuracy.
- •Drafts are presented for review before sending
- •Maintains oversight on internal and external communications
- •Balances automation speed with quality control
Time savings and improved rigor: multi-system insights into real account strategy
The post-meeting process drops from about thirty minutes to a couple of minutes and is more thorough than relying on memory. Brittany closes by framing Claude Cowork as a way to turn scattered signals into consistently better customer conversations.
- •Reduces post-meeting admin from ~30 minutes to a few minutes
- •Produces more thorough follow-ups than manual recall
- •Combines insights from multiple systems into actionable strategy
- •Overall improvement in the quality of customer conversations
