TL;DR: Claude Cowork is not a chat interface with file access bolted on. It is a persistent agent that runs on your desktop, reads your files, connects to your tools via plugins, runs recurring scheduled workflows, and delivers finished work — while you get on with everything else.
For GTM teams, the question shifts from "how do I build this automation?" to "what do I tell the agent to do?" These 10 workflows, with copy-paste prompts, are where to start.
Cowork vs Claude Chat: the critical difference
Most people's experience of Claude is the chat interface: you ask a question, Claude answers, the session ends. Cowork is fundamentally different. It maintains context across sessions, runs tasks on a recurring schedule, connects to your GTM tools via plugins and MCP connectors, and delivers finished work rather than step-by-step instructions.
The simplest distinction: Claude Chat is like asking a brilliant colleague a question. Claude Cowork is like handing that colleague a project brief, leaving the room, and coming back to find it done.
| Feature | Claude Chat | Claude Cowork | Claude Code |
|---|---|---|---|
| Access local files | ✗ | ✓ | ✓ |
| Connect to external tools | Limited | ✓ via plugins | ✓ |
| Recurring scheduled tasks | ✗ | ✓ | ✗ |
| Works without terminal | ✓ | ✓ | ✗ |
| Best for | Q&A, drafting | GTM operators | Developers |
Three things to set up first
1. Turn on Cowork notifications. Go to Settings → Notifications → Cowork Delivery and enable "Notify me when a scheduled thread completes." If you have to remember to check for output, you will not use it.
2. Install your GTM plugins. From the Claude desktop app, browse the plugin marketplace and install the Sales plugin. Add connectors for Gmail, Slack, Google Calendar, and your CRM. On Team or Enterprise plans, your admin can provision these centrally so every team member starts with the same setup.
3. Create your brand and strategy context files. Create brand-voice.md and gtm-context.md on your desktop — your tone and messaging principles, your ICP, positioning, and key differentiators. Point Cowork at them at the start of your first session. Every workflow you run will draw on this context automatically.
Workflow 1: Weekly competitive intelligence brief
This is the single highest-ROI Cowork thread most marketing teams can set up. A recurring thread runs every Monday morning, researches your top three to five competitors across their website, blog, product announcements, job postings, and LinkedIn activity, and delivers a structured brief with a notification to your phone.
Prompt:
Every Monday at 8am, research [Competitor A], [Competitor B], and [Competitor C]. For each, cover: - New product or feature announcements - Blog posts or content published this week - LinkedIn posts from their founders or marketing team - Any press coverage or news mentions - Notable job postings (signals of investment areas) Format as a structured brief with a "So What" section for each competitor explaining what it means for our positioning. Our company: [one-line description]. We compete primarily on [key differentiator].Workflow 2: Content calendar management
Create a persistent Cowork thread that manages your content calendar: fed a quarterly theme and audience brief, it generates a monthly content plan, drafts briefs for each piece, tracks what is in progress versus published, and flags gaps or opportunities based on competitor activity.
Workflow 3: Campaign performance summaries
Export your campaign data as a CSV, point Cowork at the file, and ask it to produce a performance summary with your KPI definitions already baked in. Cowork reads the data, identifies top and bottom performers, flags anomalies, compares against targets, and writes a narrative summary structured for your weekly marketing review.
Prompt:
Read the file campaign_data_[month].csv in my Downloads folder. Our KPIs: CTR target >2.5%, CPA target <£[X], ROAS target >3x. Produce: 1. Top-line performance vs targets 2. Top 3 and bottom 3 ad sets with hypothesis for why 3. Any anomalies worth investigating 4. Three recommended actions for next week Format for a marketing leadership review. Use brand-voice.md for tone.Workflow 4: Pre-call meeting prep
Before every prospect meeting, trigger a Cowork pre-call thread. Give it the company name, contact role, and meeting objective. Cowork researches the account and formats everything into a one-page brief. With your CRM connected via MCP, it pulls in deal history, previous interactions, and open action items automatically.
Prompt:
Prepare me for a meeting with [Contact], [Title] at [Company]. Meeting objective: [discovery / demo / QBR]. Return: 1. Company background and recent news 2. Likely pain points based on their industry and growth stage 3. 5 tailored discovery questions 4. One relevant case study from ~/Documents/case-studies/ Keep it to one page. I have 10 minutes to read this before the call.Workflow 5: Post-call follow-up automation
Drop your raw notes into a Cowork thread. It structures them into a formal meeting summary, extracts action items with owners and deadlines, drafts a personalised follow-up email, and — with your CRM connected — updates the deal record directly. 30 minutes of post-call admin becomes under 3 minutes.
Workflow 6: Lead list enrichment and ICP scoring
Export a lead list from your CRM as a CSV. Point Cowork at the file and ask it to enrich each record against your ICP criteria, score each lead by fit, and return a prioritised list with a one-line rationale for each score. Run this weekly and your reps start each week with a ranked, ready-to-work list.
Prompt:
Read the file new_leads_[week].csv in my Downloads folder. Our ICP: 50–500 employees, [industries], recent funding or hiring for [roles]. Score each lead A/B/C for ICP fit, add a one-line rationale, flag buying signals. Return as a sorted CSV with score column added. A leads at the top.Workflow 7: Pipeline health audit
A weekly Cowork thread connects to your CRM, audits open deals against your pipeline health rules — deal age, last activity date, missing fields, stale stages — surfaces anomalies, identifies at-risk deals, and sends a structured pipeline health report to the sales manager before their Monday team meeting.
Prompt:
Connect to [CRM] and audit our open pipeline. Flag any deal where: - No activity in the last 14 days - Close date has passed without being updated - Missing required fields (contact, company size, use case) - Stage hasn't moved in 21+ days Summarise: total open pipeline value, at-risk value, % with data quality issues. Deliver to [Slack channel] by 8am Monday.Workflow 8: On-demand sales collateral
A Cowork thread acts as an on-demand sales enablement assistant: fed a deal context — company profile, stage, objections raised, competitor mentioned — it pulls the most relevant case study from your library, generates a tailored one-page summary, and drafts a covering note for the email.
Workflow 9: Launch GTM package
Product launches are where GTM coordination breaks down most visibly. A Cowork launch thread takes your product brief and generates the full launch package: press release draft, sales one-pager, email announcement, three LinkedIn posts, FAQ for customer-facing teams, and a launch checklist with owners and deadlines.
Workflow 10: Weekly GTM standup brief
A recurring Cowork thread that pulls data from your CRM, campaign dashboard, competitive intelligence thread, and content calendar — synthesises the week's highlights and lowlights into a structured brief — and posts it to Slack before your standup starts. The meeting becomes a decision-making session rather than a reporting session.
Prompt:
Every Friday at 4pm, generate this week's GTM standup brief. Pull from: - [CRM]: new deals created, deals closed, pipeline movement - [Campaign tool]: top campaign this week, any anomalies - This week's competitive intelligence thread - Content calendar: what published, what is coming next week Format: 3 wins, 3 things to watch, key metrics vs last week. Post to #gtm-team in Slack when complete.Deploying Cowork across your GTM team
Use plugins to standardise the stack. Plugins bundle your CRM connector, brand voice skill, ICP context, and core workflows into a single install. Any new team member installs it once and has the same setup as everyone else.
Provision organisation-wide on Team and Enterprise. Admins can push plugins, skills, and connectors to all users from the admin console. Skills update centrally — one change applies for everyone immediately.
Set group spend limits. Enterprise admins can set per-team budgets from the admin console — giving finance the predictable cost governance needed to approve deployment at scale.
Track adoption with usage analytics. Cowork activity appears in the admin dashboard. Track sessions, active users, skill invocations, and connector calls. Use this data to identify which workflows are landing and where to invest in training.
Frequently asked questions
What is Claude Cowork and how is it different from Claude Chat?
Claude Cowork is an agentic system built into the Claude desktop app. Unlike Claude Chat, Cowork can access files on your computer, connect to external tools via plugins, run tasks on a recurring schedule, and deliver finished work rather than step-by-step instructions. You define the goal; Cowork figures out how to get there and notifies you when it is done.
What plan do I need to use Claude Cowork?
Claude Cowork is available on all paid Claude plans — Pro, Max, Team, and Enterprise. For recurring scheduled workflows and organisation-wide deployment, Team or Enterprise is the appropriate tier.
Can the whole GTM team share the same Cowork setup?
Yes. On Team and Enterprise plans, admins can provision plugins, skills, and connectors across all users from the admin console. Update a skill or plugin centrally and the change applies for everyone immediately.
What is the best first Cowork workflow to set up for a GTM team?
Start with the weekly competitive intelligence brief. Set it to run every Monday morning, configure the notification, and let it deliver its first brief before your weekly marketing sync. Once your team sees a structured competitive summary arrive without anyone producing it manually, buy-in for broader Cowork deployment typically follows quickly.
How is Claude Cowork different from Claude Code?
Cowork is for GTM operators who want to describe a task in plain English and have it executed — no terminal, no coding required. Claude Code is for builders who want full programmatic control. In practice, many organisations use both: technical members build infrastructure in Claude Code, then package it as Cowork plugins that the rest of the team can run conversationally.
Next steps
- See the full Claude stack: The Complete Claude AI Stack
- Build the skills your Cowork workflows use: 15 Top Claude Skills for GTM Teams
- Connect Cowork to your CRM: How to Use Claude with HubSpot
- Connect Cowork to lifecycle marketing: How to Use Claude with Customer.io
About the author
Paul Sullivan is the Founder of ARISE GTM and creator of the ARISE GTM Methodology®. He is the author of Go To Market Uncovered (Wiley, 2025) and host of the GTM Uncovered podcast.
- HubSpot accreditations: HubSpot Platinum Solutions Partner
- Customer.io accreditation: Certified Implementation Partner
- Based: Here East, Queen Elizabeth Olympic Park, London E15 2GW
- Work with ARISE GTM: arisegtm.com/agency-services
- Speak to Paul: arisegtm.com/contact-us
- Podcast: GTM Uncovered on Spotify
- YouTube: @gtmuncovered
Based on ARISE GTM's Cowork deployment engagements (2024–2026). Current as of April 2026.
%20small.jpg)
