Total Read: ~5,950 words | 25 min read
What's Inside This Guide:
What Cowork Actually Is — Why it's not a chatbot. The 5 core features. Why "context" beats "prompting."
Setting Up Cowork the Right Way — Copy-paste templates for context files, global instructions, and connector prompts.
What Plugins Actually Are — The 4-engine architecture most people miss.
S-Tier Plugins — Data Analysis, Productivity, Sales. 3 copy-paste prompts each.
A-Tier Plugins — Legal, Product Management, Marketing, Finance. 2 copy-paste prompts each.
B-Tier Plugins — Customer Support, HR, Engineering, Operations, Design, Financial Services, Brand Voice.
C-Tier Plugins — Enterprise Search, Bio Research, Plugin Management, Wealth Management.
The Connector Cheat Sheet — The 4-tier strategy for connecting your tools.
The Pattern Nobody's Seeing — The platform play behind the SaaSpocalypse.
Where Cowork Falls Short — Honest limitations + workarounds.
Your 30-Minute Setup Playbook — Minute-by-minute walkthrough.
Part 1: What Cowork Actually Is
Stop thinking about AI as a chat window.
If you are still copy-pasting text into a browser, you are doing it wrong. That is the "Tourist" model of AI. You visit the AI, ask a question, and leave.
Cowork is different. Cowork is a "Resident."
It lives on your desktop. It reads your files. It writes to your folders. It installs plugins. It connects to your Slack and Drive.
When Anthropic took Claude Code—a tool built for software engineers—and rebuilt it for operators, they didn't just make a better chatbot. They built a mechanical agent.
Here is the difference:
Chatbot: You paste a CSV. You ask for a chart. You download the chart.
Cowork: You point it to a folder. It reads 45 files. It builds a new spreadsheet with working formulas. It saves the file to your desktop.
I have spent hundreds of hours in this system since the beta launch. I have tested 47 different context configurations. I have broken the file permissions more times than I can count.
I suffered through the complexity so you get the cheat sheet.
This guide is the manual that should have come with the software.
The 5 Core Features
Cowork is built on five mechanical pillars. You need to understand these to operate the machine.
1. File System Access
This is the engine. Cowork reads and writes files directly on your hard drive. No more upload/download loops. It works in your environment, not a browser tab.
2. AskUserQuestion
Most AIs are confident liars. When they don't know something, they guess. Cowork is different. When it hits a knowledge gap, it stops. It generates a form. It asks you structured questions. It does not proceed until you align.
3. Plugins
These are not "GPTs." These are specialist packs. They give Cowork specific roles (Data Analyst, Sales Engineer, Chief of Staff). They come with their own slash commands and capabilities.
4. Instructions
Cowork has no long-term memory between sessions. Instructions are the "standing orders" that load every time you spin up a task. This is where you hard-code your preferences.
5. Connectors
These are the pipes. Connectors link Cowork to your live data—Slack, Google Drive, Notion, Jira. You link them once. Cowork references them forever.
The Shift: Prompting vs. Context
Here is the hard truth.
ChatGPT trained you to write better prompts. That is a depreciating skill. As models get smarter, prompt engineering matters less.
Cowork trains you to build better context.
That is a compounding skill.
When you write a perfect prompt, you solve one problem once. When you build a perfect Context File, you solve that class of problem forever.
I don't try to write perfect prompts anymore. I let Cowork figure out what it needs to know.
This guide covers the setup, the architecture, and the specific workflows I use to run my operations.
No theory. Just blueprints.
Part 2: Setting Up Cowork the Right Way
Most people install the app, ask a question, and get a generic answer. They churn in three days.
That is because they skipped the architecture phase.
You need to set the stage before you let the actor perform.
This setup takes 30 minutes. It will save you 10 hours a week.
A) File System Access: The Foundation
First, get the plumbing right.
The Setup:
Go to claude.com/download.
Install the desktop app.
Upgrade to the Pro plan ($20/month). You need the bandwidth.
Open the app → Click the "Cowork" tab.
Select a root folder.
The Context Files Strategy
Cowork can read. So give it something to read.
Do not rely on the "Custom Instructions" box in settings alone. It is too small.
Instead, create a folder on your computer named _Claude_Context.
Inside that folder, create three Markdown (.md) files. Cowork reads Markdown faster and more accurately than Word docs or PDFs.
Here are the templates. Copy these exactly.
File 1: about-me.md
This file creates the user profile. It tells Cowork who you are.
# USER PROFILE: [YOUR NAME]
## CORE ROLE
Current Title: [Job Title]
Company: [Company Name]
Key Objectives:
- [Objective 1]
- [Objective 2]
- [Objective 3]
## KNOWLEDGE BASE
I have deep expertise in:
- [Skill 1]
- [Skill 2]
I have blind spots in:
- [Weakness 1]
- [Weakness 2]
## STAKEHOLDERS
I report to: [Name/Title]
I manage: [Names/Titles]
Key Clients: [Client A, Client B]
## CONSTRAINTS
- I cannot approve budgets over $[Amount].
- I do not write code.
- I require legal review for [Topic].
File 2: brand-voice.md
This ensures you don't sound like a robot.
# BRAND VOICE GUIDELINES
## TONE SPECTRUM
- Professional but not corporate.
- Direct but not rude.
- Authoritative but not arrogant.
## FORMATTING RULES
- Use bullet points for lists.
- No paragraphs longer than 3 lines.
- Use Title Case for headers.
- Use bolding for **key concepts**.
## BANNED VOCABULARY
(Do not use these words under any circumstances)
- Delve
- Unlock
- Elevate
- Landscape
- Tapestry
- Game-changer
- Foster
- Utilize
## WRITING SAMPLES
[Paste 3-5 examples of your best writing here]
File 3: working-style.md
This defines the operational rhythm.
# OPERATIONAL PREFERENCES
## OUTPUT DEFAULTS
- Always prioritize brevity over politeness.
- If a response requires more than 3 steps, create a checklist.
- When analyzing data, always look for anomalies first.
## FEEDBACK LOOP
- If you are less than 90% sure, ask a clarifying question.
- Do not hallucinate URLs.
- Cite sources for all claims.
## FILE HANDLING
- When creating drafts, save as .md files in the /Drafts folder.
- When creating spreadsheets, use .csv format.
The Test:
Once these files are in your folder, run this prompt to verify the connection.
Read all the files in the _Claude_Context folder completely.
Then, give me a summary of what you know about me, how I require you to write, and what operational constraints you are working under.
Confirm you have indexed these files for future reference.
B) AskUserQuestion: The Anti-Hallucination Protocol
This is the single most important feature in Cowork.
Standard LLMs guess. They want to please you, so they make things up.
AskUserQuestion is a function that forces the AI to stop and interview you.
I never write detailed prompts anymore. I write a goal, and then I force Cowork to scope the project.
The Universal Task Opener:
Use this prompt to start every major project.
I want to [TASK] so that [WHAT GOOD LOOKS LIKE].
First, read all uploaded files completely before responding.
DO NOT start executing yet.
Use the AskUserQuestion tool to ask me clarifying questions to refine the approach. Ask as many questions as you need to ensure the output is perfect.
Only begin the actual work once we have aligned on the plan.
The Safety Suffix:
If you are in a rush, just append this to the end of any request.
... DO NOT start working yet. First, ask me clarifying questions so we can define the approach together. Only begin once we've aligned.
C) Instructions (Global & Folder)
Context files are for reference. Instructions are for behavior.
Global Instructions
These load for every session. Use this for your non-negotiables.
Path: Settings → Cowork → Edit → Global Instructions
Template:
You are an expert operator acting as my Chief of Staff.
YOUR PRIME DIRECTIVES:
1. Brevity is power. Omit preamble. Omit "I hope this finds you well."
2. You have file system access. Use it. Do not ask me for information you can find in the attached folders.
3. If a task involves risk (financial or legal), flag it immediately.
4. Use the AskUserQuestion tool if requirements are ambiguous.
OUTPUT STYLE:
- Use Markdown.
- Use arrows (→) for processes.
- Use bullets (•) for lists.
Folder Instructions
These are specific to a project. If you have a client folder, put a .clauderc file or a specific project-instructions.md file in the root.
Template (Client Work):
PROJECT: [Client Name] Website Redesign
ROLE: You are the Lead Project Manager for this account.
SPECIFIC CONTEXT:
- Brand colors are [Hex Codes].
- The main point of contact is [Name].
- Deadlines are strict: Fridays at 5 PM.
OUTPUT:
- All drafts must follow the [Client Name] Style Guide (see attached).
- All reports must be formatted as PDF-ready Markdown.
The Test:
Verify your instructions are active.
Before we start any work, tell me what you know about me, how I like to work, and any standing preferences you're aware of based on my Global Instructions.
D) Connectors: The Live Wire
Files are static. Connectors are live.
This is how you stop context-switching. You don't need to tab over to Slack to search for a message. You make Cowork do it.
Setup:Settings → Connectors → Browse directory → Add → Authenticate
Connect Slack, Google Drive, and Notion immediately. These are the "Big Three."
Slack Connector Prompt:
Run this on Monday mornings.
Search my Slack messages from the last 7 days.
Identify any messages where I was tagged or asked a question that I have not yet replied to.
Summarize them in a table:
| Sender | Topic | Urgency (1-5) | Suggested Action |
Google Drive Connector Prompt:
Run this before starting a new document.
Find the most recent document about [Project Name] in my Drive.
Read it.
Tell me the three most important things I need to know before I start drafting the new proposal.
Notion Connector Prompt:
Run this to update your team.
Read the [Project Name] page in Notion.
Extract all tasks assigned to me that are marked "In Progress."
Draft a status update email summarizing where each task stands.
Part 3: What Plugins Actually Are
Plugins are misunderstood.
People think they are just "wrappers" for prompts. They are not.
A Plugin in Cowork is a bundle of four distinct engines:
Skills: Specialized logic models (e.g., how to read a balance sheet).
Slash Commands: Shortcuts that trigger complex workflows (e.g.,
/data:explore).Sub-Agents: Mini-personas that handle specific domains.
Connectors: Pre-built pipes to specific tools (Snowflake, HubSpot, Linear).
The market does not understand this yet.
When Cowork launched, $285 billion was wiped off the market caps of SaaS companies. LegalZoom dropped 20%. Thomson Reuters dropped 18%.
Why?
Because a Cowork Plugin replaces the junior analyst using those tools.
How to Install:
Click "+" in the chat bar.
Select "Plugins."
Browse the library.
Click "Install."
How to Use:
Once installed, type / in the chat bar. You will see a list of commands specific to that plugin.
Do not ignore this. This is the difference between a generalist tool and a specialist weapon.
Before You Continue: Why We Verify Subscribers
Quick note.
We have had multiple instances of bots scraping this content and people republishing it without authorization.
This guide took 40+ hours to build. It is free. But it is not public domain.
To keep the full guide available for real humans (and out of the hands of content thieves), we require a valid email address to unlock the remaining 5 sections.
It takes 3 seconds. No spam. No upsells. Just proof you are a real person.
Enter your email below to prove you are a human to immediately unlock the full guide.
Part 4: S-Tier Plugins — Install These Immediately
I have tested every plugin in the directory. Most are noise.
These three are signal.
They are "S-Tier" because they provide immediate, hard ROI. If you are an operator, install these today.
A) Data Analysis — The ROI King
The Killer Feature: Anomaly Detection.
The Result: I found a $14K/month pricing error in 8 minutes.
I fed it a CSV with 45,000 rows across 3 product lines. I didn't know what I was looking for. I just told it to look.
It found a SKU that was pricing incorrectly in the EMEA region. That is pure profit.
Connectors: Snowflake, Databricks, BigQuery, Hex, Amplitude, Jira.
Prompt 1: The Blind Audit (/data:explore)
Use this when you have a dataset and no idea where to start.
/data:explore
I have attached the sales data for Q3.
I want you to act as a forensic accountant.
Scan the data structure. Identify the key columns. Then, propose 5 angles of analysis that would reveal the most about our profit margins.
Prompt 2: The SQL Writer (/data:write-query)
Stop writing SQL. Let the machine do it.
/data:write-query
Look at the connected BigQuery table sales_ledger.
Write a query to extract the top 10% of customers by lifetime value (LTV).
Then, cross-reference that with their support ticket volume. I want to know if our best customers are also our most complaining customers.
Prompt 3: The Money Finder (Anomaly Detection)
This is the prompt that found the $14K error.
Analyze the attached pricing sheet.
Look for anomalies. specifically:
1. Prices that are significantly lower than the category average.
2. SKUs with high volume but negative margin.
3. Inconsistencies between regions.
Flag anything that looks like a mistake.
B) Productivity — The Chief of Staff
The Killer Feature: Synthesis.
The Result: It replaced my morning triage routine.
This plugin compounds. The more you use it, the better it gets at mimicking your decision-making logic. It connects to everything—Slack, Notion, Asana, Jira.
Connectors: Slack, Notion, Asana, Linear, Jira, Monday, ClickUp, Microsoft 365.
Prompt 1: The Morning Brief (/productivity:start)
Run this while you drink your coffee.
/productivity:start
Review my Slack messages, unread emails, and Asana tasks for today.
Triaging them into three buckets:
1. FIRE: Needs immediate attention (explain why).
2. DELEGATE: Can be sent to [Team Member Name].
3. IGNORE: Low priority noise.
Give me the list.
Prompt 2: The Weekly Review
Friday afternoon ritual.
Look at my completed tasks in Notion and my sent emails from this week.
Draft a "Weekly Wins" email to my manager.
Highlight:
- Key milestones hit.
- Roadblocks removed.
- Focus areas for next week.
Keep it under 200 words. Punchy.
Prompt 3: The Meeting Prep
Never enter a meeting cold again.
I have a meeting with [Name] in 15 minutes.
Search my email and Slack history with them.
Give me a "Battle Sheet":
- Last 3 topics we discussed.
- Any outstanding promises I made to them.
- Their current sentiment (positive/negative).
C) Sales — The 90-Minute Time Saver
The Killer Feature: Non-generic Battlecards.
The Result: Pre-call prep went from 90 minutes to 5 minutes.
Most sales tools give you generic company info. This plugin reads your internal notes, your CRM history, and the prospect's latest news to build a strategy.
Connectors: Slack, HubSpot, Close, Clay, ZoomInfo, Notion, Jira, Fireflies, Microsoft 365.
Prompt 1: The Deep Dive (/sales:call-prep)
/sales:call-prep
Target: [Company Name]
Prospect: [Person's Name]
Scrape their recent news, their LinkedIn posts from the last 30 days, and our internal HubSpot history.
Tell me:
1. What is their biggest pain point right now?
2. How does our product specifically solve that pain?
3. What is a "hook" question I can ask to open the call?
Prompt 2: The Competitor Killer (/sales:battlecard)
/sales:battlecard
We are competing against [Competitor Name] for this deal.
Compare our feature set against theirs specifically for [Client's Industry].
Give me 3 "Kill Points"—features we have that they do not, which are critical for this client.
Prompt 3: The Cold Outreach
Draft a cold outreach sequence (3 emails) for [Prospect Name].
Base it on the fact that they just [Recent News Event].
Do not use generic sales fluff.
Tone: Peer-to-peer, helpful, low pressure.
Call to Action: "Worth a chat?"
Part 5: A-Tier Plugins — Role-Specific Powerhouses
S-Tier plugins are universal. Everyone needs productivity. Everyone needs data analysis.
A-Tier plugins are different. They are specialists.
If you work in these specific verticals, these plugins are not optional. They are the difference between a 60-hour week and a 40-hour week.
The only reason they aren't S-Tier? They require configuration. You cannot just "turn them on." You must tune them to your risk tolerance and organizational quirks.
But once tuned, they are lethal to the old way of working.
A) Legal — The Market Crasher
The Killer Feature: Risk Tolerance Triage.
The Result: Thomson Reuters stock dropped 18%. LegalZoom dropped 20%.
Why? Because Cowork automates the "Junior Associate" layer of legal work.
Reviewing NDAs. Flagging indemnity clauses. Checking compliance against a handbook. This is high-volume, low-leverage work. Cowork eats it alive.
Since the February 24 update, the Harvey connector allows Cowork to reference case law and firm-specific precedent. This moves it from "Drafting Tool" to "Legal Counsel."
Connectors: Slack, Box, Egnyte, Jira, Microsoft 365.
Why It's A-Tier:
Legal work has zero margin for error. You must spend time defining your "Risk Profile" in the plugin settings. If you skip this, it will either flag everything (paralysis) or nothing (liability).
Prompt 1: The Contract Review (/legal:review)
Use this to strip-mine a vendor contract for red flags.
/legal:review
I have attached the [Vendor Name] MSA.
Compare this against our standard Risk_Tolerance_Policy.md (attached).
Output a table with 3 columns:
1. Clause: The specific text in the contract.
2. Risk Level: High/Medium/Low.
3. Recommendation: Specific redline text to fix it.
Focus heavily on Indemnification and Termination for Convenience.
Prompt 2: The NDA Triage
Stop reading standard NDAs.
Read the attached NDA.
Does it deviate from "Market Standard" for a mutual NDA in the SaaS industry?
Specifically check:
- Duration (should not exceed 3 years).
- Jurisdiction (must be Delaware or New York).
- Non-solicitation (flag if present).
If it is standard, draft a "Looks good to sign" email. If not, list the deviations.
B) Product Management — The Spec Writer
The Killer Feature: The Clarification Loop.
The Result: Vague Slack messages turn into engineering-ready tickets.
Engineers hate vague requirements. PMs hate writing detailed specs.
The /product-management:write-spec command solves this standoff. You give it a rough idea. It asks you questions until it understands. Then it writes the ticket.
It is the most integrated plugin in the ecosystem. It talks to everything from design (Figma) to tracking (Amplitude) to execution (Jira).
Connectors: Slack, Linear, Asana, Monday, ClickUp, Jira, Notion, Figma, Amplitude, Pendo, Intercom, Fireflies.
Why It's A-Tier:
It requires you to have a product vision. It cannot invent a roadmap for you. It can only structure the one you have.
Prompt 1: The Spec Generator (/product-management:write-spec)
This is how you ship faster.
/product-management:write-spec
Feature: "Dark Mode" for the mobile app.
Context:
- Users are requesting this in Intercom (see attached CSV export).
- Needs to match the new design system in Figma.
First, ask me 3 clarifying questions about scope and edge cases.
Then, generate a PRD with:
- User Stories.
- Acceptance Criteria (Gherkin syntax).
- Technical Constraints.
Prompt 2: The Roadmap Synthesis
Turn noise into signal.
Ingest the following data sources:
1. The #feature-requests Slack channel (last 30 days).
2. The "High Priority" bugs in Jira.
3. The "Churn Reasons" report from Amplitude.
Propose a prioritized roadmap for Q3.
Rank initiatives by RICE score (Reach, Impact, Confidence, Effort).
Show your math for the RICE scoring.
C) Marketing — The Brand Clone
The Killer Feature: Voice Calibration.
The Result: Content that doesn't sound like ChatGPT.
Most AI copy sounds like plastic. It uses words like "tapestry" and "delve."
The Marketing plugin fixes this by anchoring to your brand-voice.md file (from Part 2). It doesn't just write; it mimics.
It connects the entire funnel: Research (Ahrefs/SimilarWeb) → Creation (Canva/Figma) → Distribution (HubSpot/Klaviyo).
Connectors: Slack, Canva, Figma, HubSpot, Amplitude, Notion, Ahrefs, SimilarWeb, Klaviyo.
Why It's A-Tier:
Garbage in, garbage out. If your brand-voice.md is weak, the output will be weak. You have to do the work to define who you are first.
Prompt 1: The Content Draft (/marketing:draft-content)
Never start from a blank page.
/marketing:draft-content
Topic: "Why traditional BI is dead."
Format: LinkedIn Long-form Post.
Target Audience: CTOs at Series B startups.
Constraints:
- Use the tone defined in brand-voice.md.
- Reference the "Competitor Analysis" file attached.
- Hook the reader in the first line. No fluff.
- End with a question to drive engagement.
Prompt 2: The Campaign Planner
Align your channels.
We are launching Feature X next month.
Review the "Feature X Product Spec" attached.
Build a 4-week launch calendar across:
1. Email (3 blasts).
2. LinkedIn (Organic + Paid).
3. Blog (SEO focus).
For each asset, define the "Key Message" and the "Call to Action."
D) Finance — The Excel-to-PowerPoint Bridge
The Killer Feature: Cross-App Workflow.
The Result: The "Monthly Business Review" deck takes 10 minutes, not 10 hours.
Finance teams spend 80% of their time moving data from Excel to PowerPoint. This is low-value labor.
The Finance plugin, built in partnership with PwC, automates this bridge. It reads your ledger, reconciles the accounts, and pushes the charts directly to slides.
Connectors: Snowflake, Databricks, BigQuery, Slack, Microsoft 365, FactSet, MSCI.
Why It's A-Tier:
Trust. You need to audit the first 10 runs heavily. But once you trust the logic, it changes your life.
Prompt 1: The Variance Analysis
Find out where the money went.
Compare the Q3_Actuals.xlsx against the Q3_Budget.xlsx.
Identify the top 5 variance lines (positive or negative).
For each variance, look at the transaction detail and hypothesize the root cause.
Draft a commentary blurb for the CFO explaining *why* we missed the forecast.
Prompt 2: The Board Deck Generator
The ultimate time saver.
Take the "Financial Highlights" table from the attached Excel.
Generate a slide outline for the Board Deck.
- Slide 1: Executive Summary (Bullet points).
- Slide 2: Revenue Bridge (Waterfall chart data).
- Slide 3: Opex Breakdown (Pie chart data).
Draft the "Speaker Notes" for the CFO for each slide, focusing on the "So What?" of the numbers.
Part 6: B-Tier Plugins — Solid but Needs Your Context
These plugins are engines without fuel.
They are well-built. The logic is sound. But out of the box, they are generic. To make them useful, you need to feed them your Standard Operating Procedures (SOPs).
If you are willing to spend 60 minutes configuring them, they become A-Tier. If not, they remain B-Tier.
The Operations Suite (Feb 24 Update)
1. Customer Support
Function: Ticket triage, "Resolved-to-Knowledge-Base" loop.
The Problem: It doesn't know your refund policy or your tone.
The Fix: Upload your
support-handbook.pdfandSLA-matrix.csv.Use Case: "Draft a response to this angry ticket using the 'Empathy-First' framework from our handbook."
2. HR
Function: Offer letters, onboarding checklists, performance reviews.
The Problem: Performance reviews are sensitive. Generic feedback destroys culture.
The Fix: Feed it your
competency-matrix.mdand specific examples of "Level 3 vs Level 4" behavior.Use Case: "Draft an offer letter for [Candidate] based on the 'Senior Engineer' band in our comp table."
3. Engineering
Function: Standup summaries, incident response, post-mortems.
The Problem: Every engineering team has a different ritual.
The Fix: Define your "Severity Levels" (SEV1 vs SEV3) in a text file.
Use Case: "Read the #incident-log channel. Draft a Post-Mortem using our standard template. Identify the root cause using the '5 Whys' method."
4. Operations
Function: Process documentation, vendor evaluation.
The Problem: Operations is too broad.
The Fix: Use it for decision matrices.
Use Case: "Compare these 3 vendor quotes. Build a decision matrix based on Price, Speed, and SLA."
5. Design
Function: Critique frameworks, UX copy, Accessibility audits.
The Problem: It can't "see" design intent perfectly yet.
The Fix: Use it for compliance, not creativity.
Use Case: "Audit this copy for WCAG accessibility compliance. Flag any language that is not inclusive."
The Financial Services WaveIncludes: Investment Banking, Equity Research, Private Equity, Wealth Management.
These launched in the "Vertical Wave" on Feb 24. They are powerful frameworks. They know how to calculate WACC. They know how to structure an LBO model.
But they do not have your firm's proprietary data or "House View."
You must upload your firm's investment-thesis.md and formatting-guide.pdf. Without them, you get generic Wall Street analysis. With them, you get a junior analyst.
Brand Voice by Tribe AI
This is a meta-plugin. You point it at 20 of your best documents. It analyzes them and writes a brand-voice.md file for you.
Use this once to set up your system. Then turn it off.
Part 7: C-Tier Plugins — Skip Unless You're the Target
Do not install these just to look busy. They add noise to your interface. Only install if you fit the exact profile.
1. Enterprise Search
The Promise: One search bar for Google Drive, Slack, Notion, and Jira.
The Reality: It is only as good as your file organization. If your Google Drive is a mess, this plugin just helps you find trash faster. Clean your house before you buy a robot vacuum.
2. Bio Research
Target: PhDs and Biotech operators.
Connectors: PubMed, BioRender, bioRxiv, ClinicalTrials.gov, ChEMBL.
Verdict: Incredible if you are doing drug discovery. Useless if you are selling software.
3. Plugin Management
Target: IT Admins.
Verdict: This is for the person managing 500 seats. It lets you whitelist/blacklist plugins for the org. If you are an individual user, ignore it.
4. Wealth Management
Target: Financial Advisors.
Verdict: Automates portfolio drift analysis and tax-loss harvesting proposals. Requires expensive subscriptions (FactSet/MSCI) to work properly.
Part 8: The Connector Cheat Sheet
You do not need to connect everything. That creates security risks and noise.
Follow this tiered strategy. Start with Tier 1. Only move to Tier 2 when you have a specific use case.
Tier 1: The Universal Stack (Activate Immediately)These activate 80% of the ecosystem's value.
Slack: The nervous system. Required for almost every plugin (Productivity, Sales, PM).
Microsoft 365 / Google Workspace: The file system. Cowork cannot work without reading your docs and emails.
Jira / Linear / Asana: The task layer. Required for the "Action" step of any workflow.
Tier 2: The Revenue Stack (Go-To-Market Teams)Activate if you touch money.
HubSpot / Salesforce: The source of truth for customer data.
Notion / Confluence: The company brain. Required for RAG (Retrieval-Augmented Generation) workflows.
Zoom / Fireflies: Meeting intelligence. Allows Cowork to "remember" what was said on calls.
Tier 3: The Data Stack (Analysts & Ops)Activate if you know SQL.
Snowflake / Databricks / BigQuery: Direct database access.
Warning: These incur costs. Ensure your query limits are set before you let an AI write SQL.
Tier 4: Niche Power-UpsSpecific roles only.
Figma: Product Managers & Designers.
GitHub / GitLab: Technical PMs & Engineers.
FactSet / MSCI: Finance professionals.
PubMed: Researchers.
The Strategy:
Start with Slack + Drive + Notion.
That combination covers communication, files, and knowledge.
It is the "Iron Triangle" of context.
Once those are stable, add your role-specific tool (e.g., Salesforce for Sales, Jira for Product).
Do not over-connect. Complexity is the enemy of execution.
Part 9: The Pattern Nobody's Seeing
Most people look at Cowork and see a "better ChatGPT."
They are missing the forest for the trees.
Cowork is not a chatbot. It is an operating system. And what we are witnessing is the rapid commoditization of the B2B software market.
Let's look at the timeline.
Wave 1 (Jan 30): The Horizontal Attack
Anthropic launched with the "Universal" stack.
Productivity
Sales
Marketing
Data Analysis
Legal
Finance
These are functions every company has. This was the shot across the bow. It proved that a generic agent, given the right context, could perform the work of a junior employee.
Wave 2 (Feb 24): The Vertical Siege
Less than 30 days later, they dropped the specialized warheads.
Investment Banking
Private Equity
HR
Engineering
Design
This is where the strategy reveals itself.
These plugins are not hard-coded software. They are text files.
If you look at the architecture, a Cowork Plugin is essentially a markdown file. It contains instructions, logic, and slash commands. That is it.
There is no compilation step. There is no cloud infrastructure to manage. There is no DevOps team required.
The Barrier to Entry is Zero.
I checked the GitHub repository. It has over 2,000 stars. I watched a 22-year-old analyst build a "Supply Chain Optimization" plugin in 15 minutes.
He defined the logic. He connected it to a spreadsheet. He shipped it.
In the old world, that is a $50,000 SaaS contract with a 6-month implementation cycle. In the new world, it is a text file you swap with your friends.
The SaaSpocalypse Explained
When the market wiped $285 billion off the valuation of SaaS incumbents, it wasn't a glitch. It was price discovery.
Investors realized that the "moat" around B2B software—complex workflows, proprietary data formats, sticky UIs—had evaporated.
If an agent can read your raw data (File System Access) and execute your logic (Plugins), you do not need the UI anymore. You do not need the app.
The Enterprise Response
The big players see this coming.
PwC is already building proprietary industry plugins for regulated sectors. They are creating "Audit Bots" that live inside Cowork, pre-trained on tax code.
JPMorgan analyst Toby Ogg put it bluntly: "We are seeing $20/month seats doing 40% of the work that $150/month enterprise seats used to do."
That is the math that kills legacy software.
The "Code" Shift
Kate Jensen, Anthropic's Head of Americas, said it best: "We expect every knowledge worker will feel about Cowork the way engineers feel about Claude Code."
Engineers stopped writing boilerplate code two years ago. They became architects. They direct the AI to write the syntax.
Now, that shift has hit the rest of us.
If you are a marketer, stop writing copy. Architect the campaign.
If you are an analyst, stop writing SQL. Architect the query.
If you are a manager, stop nagging for updates. Architect the reporting workflow.
We are moving from "Apps" (tools you use) to "Agents" (workers you manage).
Anthropic shipped 10 new major plugins in 25 days. Legacy SaaS takes 6 months to ship a dark mode update.
The velocity of innovation has shifted. You are either on the rocket ship, or you are watching it leave.
Part 10: Where Cowork Falls Short
I sell the dream, but I live in the reality.
Cowork is powerful, but it is raw. It is "Version 1.0" software. It breaks. It forgets. It gets expensive.
If you go in expecting magic, you will be disappointed. If you go in expecting a mechanical intern, you will be delighted.
Here are the friction points I deal with daily.
1. The Amnesia Problem (No Cross-Session Memory)
This is the biggest pain point.
When you close a Cowork session, the brain wipes. It does not remember that you prefer bullet points over paragraphs. It does not remember your project code names.
The Workaround:
This is why Part 2 of this guide is non-negotiable. You must use Context Files (about-me.md) and Global Instructions. You have to "re-inject" your personality at the start of every session. It takes 10 seconds, but you have to do it.
2. The Desktop Tether
Cowork lives on your machine. It is not in the cloud.
There is no mobile app. You cannot check the status of a task from your phone. If you close your laptop, the agent dies.
The Workaround:
Do not quit the app. Put your computer to sleep.
For files, use a cloud-synced folder (Dropbox, iCloud, OneDrive) as your "Claude Context" folder. This allows you to update your context files from another device, even if Cowork can only read them from the desktop.
3. The Credit Burn
Cowork is heavy.
Reading 50 files and generating a complex analysis eats compute credits like a furnace.
The standard Pro plan ($20/month) is not enough for a power user. I hit the cap by 2 PM on busy days.
The Reality:
If you use this for work, upgrade to the Max plan ($100-200/month). It sounds expensive until you realize it replaced a $5,000/month contractor.
4. No Image Generation
Cowork is a text and code engine. It cannot make logos. It cannot edit JPEGs.
The Workaround: Keep a tab open for Midjourney or Gemini Imagen. Do not try to force Cowork to do visual work. It will fail.
5. Safety Rails (The "Nanny" Factor)
Anthropic is obsessed with safety. Sometimes, too obsessed.
If you ask Cowork to "research competitors," it might refuse because it thinks you are asking for corporate espionage.
It also has "Deletion Protection" on by default. It will be terrified to delete a file, even if you tell it to.
The Workaround:
Be explicit. "I own these files. I authorize this deletion. This is for internal research purposes only." You have to speak like a lawyer to get it to act like a pirate.
6. Research Preview Status
This is beta software.
I have had it crash mid-task. I have had it hallucinate file paths.
The Rule: Never let it overwrite a source file. Always tell it to "Save as new" or "Create a copy." Protect your original data.
Part 11: Your 30-Minute Setup Playbook
You have read the theory. Now do the work.
Do not bookmark this guide. Do not save it for "later." Later never comes.
Open your laptop. Follow these steps. In 30 minutes, you will have an agent.
Minutes 0-5: Installation
Go to claude.com/download.
Download the Desktop App (Mac or Windows).
Sign in.
Upgrade to Pro ($20/month). Do not be cheap. The free tier is useless for this.
Open the app.
Click the "Cowork" tab at the top.
Minutes 5-10: Context Architecture
This is where you win.
Create a folder on your desktop named
_Claude_Context.Open a text editor (Notepad, TextEdit, VS Code).
Create
about-me.md. Paste the template from Part 2. Fill in your details.Create
brand-voice.md. Paste your writing samples.Create
working-style.md. Define your rules.Save all three into the folder.
Minutes 10-15: Global Instructions
In the Claude app, click your initials (bottom left) → Settings → Cowork.
Click "Edit" next to Global Instructions.
Paste the "Chief of Staff" template from Part 2.
Hit Save.
Minutes 15-20: The First Run
Go back to the chat.
Click "Select Folder." Choose
_Claude_Context.Type this prompt:
"Read all files in this folder. Tell me who I am, what my job is, and how I like my work delivered. Then ask me what our first mission is."Watch it analyze you.
Minutes 20-25: Weaponization (Plugins)
Click the "+" icon in the chat bar.
Select "Plugins."
Install Productivity (Universal).
Install Data Analysis (Universal).
Install ONE role-specific plugin (Sales, Marketing, or Engineering).
Type
/in the chat box to verify they are active.
Minutes 25-30: The Live Wire (Connectors)
Go to Settings → Connectors.
Connect Slack. (This is the highest value).
Connect Google Drive or Microsoft 365.
Go back to chat.
Type:
"Search my Slack for the last 3 messages from my boss. Summarize what they want."
Minutes 30: The Click
Watch the response.
It didn't just chat. It searched. It read. It synthesized.
That feeling? That is the feeling of leverage.
The Final Word
The SaaSpocalypse was just the beginning. The plugins are just getting started.
You have two choices.
You can keep doing the manual work, protecting a skillset that is rapidly depreciating.
You can build the context, set the instructions, and become the operator.
Stop accepting the old way of working.
Start delegating.
Written by John Peslar. Follow me on LinkedIn for more breakdowns like this.