Source: ai-research (web research, 2026-04-11); raw/Claude_Cowork_-_8_Use_Cases_Every_Marketer_Should_Know_Full_Tutorial.md; 2026-10-28: raw/Build_Agent_Teams_within_Claude_Cowork_in_17_min.md and raw/Claude_Cowork_Just_Changed_How_You_Do_Marketing.md (Ben AI); Anthropic’s Cowork help article and docs, and Claude Code’s parallel-agents and Desktop docs (ai-research/, 2026-10-28); 2026-10-30: raw/Claude_Cowork_Just_Changed_How_You_Do_Marketing-l_Iy4ZCK1lY.md (Grace Leung, https://www.youtube.com/watch?v=l_Iy4ZCK1lY) Type: Product Feature / Use Case Product: Claude Cowork (Desktop)

Cowork is Claude’s agentic AI mode for knowledge work on desktop — the same architecture as Claude Code, but for non-engineering tasks. It has direct local file access, sub-agent coordination, long-running task support, and scheduled automation. For marketing teams, this means strategy decks, ad creatives, campaign performance analysis, and competitor reports can be produced by agents working in parallel.

What Cowork does for marketing

  • Strategy decks: Agent reads your brand guidelines, market research, and brief, then produces a complete strategy deck
  • Ad creatives: Parallel agents create ad images and product copy simultaneously
  • Campaign performance analysis: Feed in raw data (CSVs, exports), agent produces analysis with recommendations
  • Competitor analysis: Automated site audits, content tracking, positioning comparisons
  • Direct local file access: Works with files on your machine — no uploading to a web interface

Parallel agents

Cowork uses “the same agentic architecture that powers Claude Code” and runs sub-agents, not agent teams. Anthropic’s help center: “Claude breaks complex work into smaller tasks and coordinates parallel workstreams to complete them”, and “for complex tasks, Claude may coordinate multiple sub-agents working simultaneously.”

  • Multiple sub-agents work on different parts of a deliverable simultaneously
  • Example: one agent generates ad images while another writes product copy — both finish faster than sequential work
  • Each sub-agent reports back to the main Claude, which combines the results; the sub-agents do not message each other ^[inferred: from Claude Code’s documented sub-agent behaviour, which Cowork’s docs say it shares]
  • If parallel pieces depend on each other (copy that must match the image), run them in sequence or have the main Claude hand one result to the next step

Topic: do Cowork's parallel agents communicate with each other?

Existing claim: (from cowork-for-marketing.md, 2026-04-11 web research, no saved source) — “Agents share context when needed (built on Agent Teams architecture)” and “Built on the same agent teams architecture as Claude Code — peer-to-peer agent communication” New source says: (from raw/Build_Agent_Teams_within_Claude_Cowork_in_17_min.md, Ben AI, 2026-03-04) — “In Claude Code, we can now even run multi-agent teams that can communicate between each other. While Claude Co-work, they’re all isolated sub-agents.” Each sub-agent returns only a summary to the main agent. Ben’s later primer (Every Cowork Feature Explained) says the same. Resolution: Anthropic’s Cowork help article and Cowork docs (ai-research/claude-help-get-started-with-claude-cowork-2026-10-28.md, ai-research/claude-docs-cowork-overview-2026-10-28.md) describe only “sub-agent coordination”: Claude breaks the work into subtasks and coordinates parallel workstreams. Neither mentions agent teams or agents messaging each other. Claude Code’s docs (ai-research/claude-code-docs-run-agents-in-parallel-2026-10-28.md) define the difference: “Subagents report results back to the conversation that spawned them”, while “teammates in an agent team message each other directly”; agent teams are “experimental and disabled by default”. The Claude Code Desktop docs (ai-research/claude-code-docs-desktop-2026-10-28.md) add that agent teams “are available in the CLI, not in Desktop” (said of the Desktop app’s Code tab). Ben AI’s description matches the first-party docs; the April claim had no saved source and is withdrawn. Status: resolved (2026-10-28)

Reusable plugins and workflows

  • Create team-wide Cowork plugins for repeating tasks: competitor analysis, keyword tracking, content creation
  • Workflows can be shared across the marketing team for consistency
  • Once built, anyone on the team can trigger the workflow without understanding the underlying prompts

Scheduled automation

  • Set up tasks to run on a schedule (e.g., monthly reports)
  • Example workflow: raw Excel data arrives -> agent analyzes -> produces PowerPoint -> runs unattended
  • No manual intervention required once configured

Key Takeaways

  • Cowork brings Claude Code’s agentic architecture to non-engineering knowledge work
  • Marketing teams get parallel agents, local file access, and scheduled automation
  • Reusable workflows mean you build the process once and the whole team benefits
  • Scheduled reports (Excel -> analysis -> PowerPoint) run without human intervention
  • Built on the same agentic architecture as Claude Code, using sub-agents that report to the main Claude; agent teams with peer-to-peer messaging are a Claude Code CLI feature, not part of Cowork
  • Direct local file access avoids the upload/download friction of web-based tools

Try It

  1. Identify a repeating marketing task that takes 2+ hours (monthly competitor report, campaign analysis, content calendar)
  2. Use Cowork to prototype the workflow: feed it the raw inputs and describe the desired output
  3. Iterate on the agent’s approach until the output quality matches your standards
  4. Save as a reusable workflow/plugin for the team
  5. Set up scheduling for tasks that recur on a fixed cadence (weekly, monthly)

Eight concrete use cases (Grace Leung tutorial, 2026-05-16)

Source: Claude Cowork - 8 Use Cases Every Marketer Should Know (Full Tutorial) — Grace Leung (YouTube @graceleungyl; channel confirmed 2026-10-30, the section was previously mislabelled as an Anthropic tutorial) — step-by-step Cowork-for-marketing walkthrough using a fictional brand (“Pet Pure”) as the running example. Each use case below corresponds to a concrete demo in the tutorial.

1. Marketing workspace setup (foundation)

The setup that makes every later use case work. Create a project folder with three subfolders: context/ (brand knowledge), template/ (reusable assets like brand decks), projects/ (campaign-specific outputs).

  • Configure global instructions under Cowork settings (e.g., “always scan for context folders before starting the task”) — one or two lines, intentionally short to avoid over-restricting.
  • Use the Ask User Question tool to have Claude interview you for brand context. Prompt: “create three context files — brand context, brand voice, ideal customer profile — and ask me the questions you need to fill them. Save inside context/.” Within minutes the brand baseline lives on disk.
  • Every subsequent Cowork session in this folder auto-reads the context — no re-explanation of brand, audience, voice.

2. Strategy deck generation from brand context + template + photos

Load multiple folders at once (marketing folder + brand-photos folder) and prompt: “research the latest marketing trends, and based on our growth priorities, create a 12-slide strategy deck using our brand photos.”

  • Claude reads context first (knows brand, audience, priorities), then loads photos, then builds the outline, then generates the full deck.
  • Output: on-brand strategy deck saved to projects/. First draft is not perfect (some photo repositioning needed), but the structure + content are tailored, not generic.
  • Loss prevented: the “build a strategy deck from scratch” task that historically took hours collapses to one prompt against the existing workspace.

3. Cowork Projects for recurring workflows

For repeating tasks (weekly carousels, recurring reports) create a Cowork Project, not a one-shot chat. Each project has:

  • Its own project instructions (system prompt scoped to this project — how Claude should navigate the folder, what rules to follow).
  • Its own context files (auto-loaded from context/).
  • Its own persistent memory (separate from other projects).

Walkthrough example: a Carousel Design System project. Reference folder of carousel layouts you like, brand context auto-attached, project asked Claude to “analyze references + brand context, generate a brand style guide and a carousel design system file.” Once saved, every future “design a 7-slide carousel about X” prompt produces on-brand output.

The tutorial highlights this as the most underused Cowork feature: “the project instruction is the system prompt just for this project. I highly recommend doing this for every project that you create.”

4. Connectors — pull live external data into the workflow

Cowork’s Connectors panel (under Customize) wires Claude to external tools. Built-ins: Google Drive, Gmail, plus a marketplace of additional connectors.

Walkthrough example with Apify (web-scraping):

  • Install Apify connector via API token.
  • Prompt: “scrape the last 25 social posts from each of our competitors, prepare a spreadsheet with analyzed data, and build an interactive dashboard to inform our content strategy.”
  • Claude loads brand context, calls Apify per competitor, returns a spreadsheet with summary + post detail (color-coded performance) and a filterable dashboard with engagement metrics + top-performing content types.

The pattern unlocks any external-data workflow where the data lives behind an API that has a Cowork connector.

5. Gamma integration via connectors

Multi-connector chain: connect both Gamma and Gmail under Connectors. Then prompt:

“Read my Gmail, find the Adobe AI traffic trends report the team sent over, pull out the key insights, generate a 10-slide presentation on Gamma with a professional theme.”

Output: a polished Gamma deck (images, charts, callout boxes) ready to edit one-click in the Gamma editor. The deck inherits Gamma’s design system (much more polished than Claude’s native presentation outputs).

Pattern is generalizable: any time the “rough draft” lives in one tool and the “polished output” lives in another, connector chaining is the bridge.

6. Live Artifacts for persistent marketing dashboards

Live Artifacts are interactive pages with live data that refresh on demand. Build it once, pin it, click refresh anytime to pull updated data.

Walkthrough example: an AI Search Visibility Radar using connected Ahrefs + Google Search Console.

  • Prompt: “build a live artifact using both data sources with sections for weekly priority brief, keyword opportunities, and new queries in my niche.” Important: use the literal phrase “live artifacts” in the prompt — without it Claude defaults to a static output.
  • Output: branded radar page (brand colors) with weekly priorities, sortable long-tail keyword opportunities, new queries. One-click CSV export, one-click PDF download.
  • Pin to sidebar. Refresh button at top-right re-runs the connectors and updates the data. No re-prompting required.

Prerequisites: under Settings → Capabilities, enable Artifacts + AI-powered artifacts + Code Execution. The tutorial calls these out explicitly because Live Artifacts won’t render without all three.

7. Skills — package a one-off workflow into a reusable skill

Once a workflow is dialed in, package it. Walkthrough example: a one-time lead magnet PDF build (sourced from a research folder of competitive comparisons, FAQs, surveys, best-practices docs) — Claude proposes the outline, builds the 8-page PDF on confirmation, saves to projects/.

Then: “extract this workflow and package it into a reusable skill called Lead Magnet PDF Builder. Make this skill brand-agnostic so it works for any brand.”

Claude uses the skill-creator skill (from the Skills library) to build it. One-click Save Skill installs it. Next time you need a lead magnet for any brand, drop the materials in, run the skill — same quality, same structure, no re-explanation.

Pre-built alternative: Anthropic’s official Marketing plugin ships 8 pre-built marketing skills (brand review, campaign plan, competitive brief, etc). Install via Connectors → Browse Plugin → search “marketing.” Use via slash command. Plugins are bundles of skills, commands, or agents.

8. Browser Use (Claude in Chrome) — capture data the API doesn’t expose

For marketing tasks that require navigating a real website (AI search visibility tracking, competitor monitoring, manual checks), Claude in Chrome lets Cowork drive an actual browser session.

Walkthrough example: AI search visibility across Perplexity / ChatGPT / Google AI mode.

  • Install Claude in Chrome extension from the official Anthropic listing.
  • Prompt: “read this prompt list, search them on Google AI mode, ChatGPT, and Perplexity, indicate the things we want to capture, then synthesize the findings into an Excel tracker.”
  • Claude asks permission, opens a Chrome session, walks each platform, captures rankings + cited URLs, builds the Excel tracker (raw data tab + insights tab with visibility-by-platform, top competing brands, gap opportunities, color-coded charts).
  • Runs in the background — ~15-20 minutes for a moderate prompt list. No manual monitoring needed.

Scheduled task pattern. Under the project’s Schedule section, click Add → create scheduled task with the same prompt → set frequency (e.g., every Sunday at 9 AM). Next week’s run creates a new tab for the data, Claude updates the insights tab with week-over-week trend.

The tutorial frames this as the marketing control center pattern: combine Live Artifacts (always-fresh dashboards) with Scheduled Tasks (recurring captures) → a self-updating marketing analytics surface.

Building marketing skills step by step (added 2026-10-28)

Ben AI’s marketing walkthrough (raw/Claude_Cowork_Just_Changed_How_You_Do_Marketing.md, https://www.youtube.com/watch?v=FAEKF-nr3D0, 2026-03-14) covers the skill-building layer this article’s use case 7 only touches: the six or seven reference files his copywriting skills read, a newsletter-writer build with exact prompts, a Nano Banana infographic skill, a scheduled ideation skill with a CSV log of sources already checked, a YouTube-analytics dashboard and an SEO-audit skill. Full write-up: Cowork Marketing Skills Playbook (Ben AI).

2026-10-30 field note (Grace Leung)

Source: raw/Claude_Cowork_Just_Changed_How_You_Do_Marketing-l_Iy4ZCK1lY.md (Grace Leung, YouTube, https://www.youtube.com/watch?v=l_Iy4ZCK1lY, 17:17, published 2026-02-06). Recorded before the 2026-09-16 chat/Cowork merge, so the three-mode framing below describes the February desktop app, not the current one (see Claude Cowork).

  • Her February split. The desktop app had three modes: chat for thinking and brainstorming, Cowork for getting work done, Claude Code for building. She called Claude Code Desktop “95% of the same Claude Code power” as the terminal; that is her estimate.
  • Move a Claude project into Cowork. A chat project could be added to Cowork, which brings its instructions and files into the conversation. Pick a working folder (Claude only reads and saves there) and put source files in it rather than uploading them. Her strategy-deck demo followed the project’s workflow and loaded the official PowerPoint skill.
  • Batch ad creative from a master spreadsheet. Folder: raw product images, an output folder for ads, a master plan spreadsheet (product names, image paths), the Nano Banana prompting guide and a product-description guideline. With the Nano Banana MCP enabled, she asked for two parallel tasks (three image variations per product; research plus a description) and a spreadsheet update at the end. About 10 minutes.
  • Analyse a large local corpus. She pointed Cowork at Lenny’s Podcast transcripts plus brand context and asked for three parallel outputs: a framework analysis spreadsheet, an interactive dashboard and a growth-playbook deck. She asked Claude to keep a progress tracker so it would not lose its place. It launched eight parallel sub-agents, missed some episodes, and finished after she asked it to double-check.
  • Build skills in Claude Code. She found skill-building most reliable there. Her “Landing Page Audit” skill uses Claude in Chrome (connector plus extension) to compare a target and competitor page against a conversion framework. Install by uploading the zip under Settings → Capabilities, then ask Claude to list its skills to confirm. She says this turned a two-hour task into under 30 minutes.
  • Turn a manual workflow into a skill. Her Google AI Mode tracker: describe the steps, give 10 queries, capture the top five cited URLs and domains per query and domain frequency, then ask Claude to package the workflow as a reusable skill.
  • Plugins bundle the set. Commands run when you trigger them; skills trigger when Claude judges they fit. She suggests cloning an official plugin’s skill rather than editing it in place, and built her own “marketing team” plugin in Claude Code by pointing it at the official plugin docs, then uploaded it to Cowork. Chained example: an AI-search check command, then keyword research, then an AI-search-friendly blog in brand voice. See Cowork Plugins.
  • Her March follow-up, a full content system run from one folder and a spreadsheet, is in Cowork + Skills Content System (Grace Leung).

Use-case combinations to steal

The eight use cases compose:

  • Workspace + Project + Live Artifact = always-fresh on-brand dashboard.
  • Workspace + Skill + Scheduled Task = repeatable on-brand deliverable, no human in loop.
  • Workspace + Connectors + Browser Use + Scheduled Task = competitive-intelligence radar that runs itself.
  • Workspace + Project + Skill-Creator + Plugin install = team-shareable marketing playbook.

The compounding insight: most of the marketing value isn’t in any single use case — it’s in the workspace foundation (#1) that all the others build on. Skip the foundation and every later use case has to re-explain brand context every run.

Open Questions

  • Is Cowork available on all Claude plans or only Pro/Team/Enterprise?
  • What file formats can Cowork output natively (PPTX, DOCX, PDF)?
  • How does scheduled automation handle failures — is there alerting?
  • Can Cowork workflows call MCP servers for external data (analytics APIs, ad platforms)?