How to Use Claude Cowork for Business: Setup, Workflows, Skills

I install Cowork into small businesses as a fractional CTO. The wiring takes an hour. The Business Brain takes the rest. Here's the exact sequence I use, in the order that actually works.

What Claude Cowork is (in one paragraph)

Cowork is the agentic layer on top of Claude. Instead of you copy-pasting between Claude and your tools, Cowork connects Claude directly to the tools (Gmail, Slack, HubSpot, QuickBooks, etc.) and lets it take action — draft an email in your inbox, post a Slack message, update a HubSpot deal, pull a QuickBooks report. Everything runs on approval gates you set. For the full definitional explainer, see what is Claude Cowork.

Before you start

Three things you need lined up before the first click:

• A Claude Team plan. Cowork is Team-and-above only. Team is $25/seat with a 5-seat minimum, so the practical floor is $125/month. There is no Cowork-only plan and no Pro tier with Cowork. The full breakdown is in Claude Cowork pricing.
• OAuth admin access to the tools you plan to connect. If you're the owner, you're fine. If you're not, get the owner on a screen-share for 20 minutes — connecting QuickBooks or Google Workspace as a restricted user inherits restricted permissions, which is the most common reason setups feel broken.
• Roughly 6 hours of uninterrupted time. One hour to wire connectors and workflows. Five hours to build the Business Brain (brand voice, offers, ICP, sales motion). The Brain is where the actual value lives.

Step 1: Enable the Cowork toggle

In your Claude Team admin settings, find the Cowork section and turn it on for your workspace. This unlocks the connector library, the workflow library, and the skills system. On a fresh Team plan, this is one click. If you don't see the toggle, your seat doesn't have admin permissions — go ask the workspace owner.

Once enabled, Cowork shows up as a new section in the Claude sidebar. You'll see three tabs: Connectors, Workflows, and Skills. That's the whole product surface. Everything you do in Cowork happens through one of those three.

Step 2: Connect your first 3 tools

Cowork ships with 8 native connectors at launch. Don't wire all 8 on day one. Pick 3.

The right first 3 for almost every business:

1. Google Workspace OR Microsoft 365 (whichever runs your email and docs — never both)
2. Slack (or whatever your team uses for internal comms)
3. QuickBooks (or Xero — financial visibility unlocks the highest-ROI workflows)

Wire those. Skip HubSpot, PayPal, Canva, and DocuSign for now. You'll add them in week 2 once you know which workflows you actually run.

The permission inheritance gotcha: Cowork inherits whatever permissions the OAuth user has. If you connect QuickBooks as a read-only accountant user, Cowork can only read. If you connect Google Workspace as a user who can't see the shared drive, Cowork can't see it either. Connect as the owner or as a user with full access. You can always tighten permissions later via the Cowork trust rules in step 8.

For the full connector-by-connector walkthrough with permission specifics, see the 8 connectors explained.

Step 3: Run a built-in workflow

Cowork ships with 15 built-in workflows. Don't try them all. Pick one easy first win to prove the wiring works.

My go-to first workflow: /business-pulse. It pulls from your connected tools and generates a Monday-morning snapshot — last week's revenue, top deals moving in the pipeline, open invoices, calendar load this week. Five minutes to run. Output is immediately useful.

Run it once. Read the output. Notice what it gets right and what it misses. The gaps are where the Business Brain comes in.

If /business-pulse doesn't fit your business (you're pre-revenue, or you don't use QuickBooks), the other easy first wins are /meeting-prep and /lead-triage. Pick one. Run it. Move on.

Step 4: Build a skill

Skills are reusable prompts that act like slash commands. Cowork ships with 15 built-in skills, but the real power is building your own. The skill I install for almost every client first: a customer service draft skill.

Here's the recipe:

1. In Cowork, go to Skills → New Skill.
2. Name it /cs-draft.
3. Description: "Draft a customer service reply in our brand voice. Match tone, reference past context if available, end with a clear next step."
4. Add 3-5 examples of real customer service emails you've sent (paste the customer message + your reply). This is the part most people skip. Without examples, the skill outputs generic AI customer service voice.
5. Add an escape valve: "If the question involves a refund, billing dispute, or anything you're not sure about, flag for human review instead of replying."
6. Save. Test it on a real incoming email.

That's the pattern for every custom skill — name, description, examples, escape valve. The examples matter more than the description. Cowork learns voice from examples, not adjectives.

For more skill recipes and the full breakdown of the 15 built-in ones, see Claude Cowork skills explained.

Step 5: Build the Business Brain

This is the step that separates a Cowork setup that's "kind of useful" from one that pays for itself in week one.

The Business Brain is a 4-layer context capture I install for every fractional CTO client: brand voice (with real writing samples), offers and pricing, ICP and positioning, and sales motion. You load it into Cowork as a persistent Project, and every workflow and skill inherits that context.

Without the Brain, Cowork drafts emails that say "I hope this email finds you well." With the Brain, it drafts emails that sound like you wrote them.

The capture takes about 5 of the 6 setup hours. It's the work. The full framework lives at /business-brain, and the step-by-step setup walkthrough is in the Claude for small business setup guide.

Step 6: Set trust rules

Cowork has three trust levels for every action: auto-run, approve-then-run, and draft-only. Default everything to draft-only for the first two weeks. You want to see what Cowork does before you let it do anything autonomously.

After two weeks, look at the actions Cowork has drafted. The ones you approved every single time without edits — promote those to auto-run. The ones you edited heavily — keep at draft-only or rewrite the skill. The ones in the middle — approve-then-run.

The actions worth auto-running for most businesses: pulling reports, generating internal summaries, creating draft documents. The actions to never auto-run: sending external emails, posting to client Slack channels, charging payments. Even when you trust the output, send actions are where a single mistake costs real money.

Common first-week mistakes

I've watched the same three mistakes happen across dozens of installs:

• Connecting all 8 tools on day one. Now every workflow has too much surface area, permissions get confused, and you can't tell which connector caused a weird output. Wire 3. Add the rest later.
• Skipping the Brain. Cowork without a Brain is autocomplete with extra steps. The first time you run a customer email workflow and the output sounds like a generic SaaS welcome message, you'll think Cowork is overrated. It's not. You skipped the work.
• Expecting Cowork to auto-send emails on day one. Cowork can, but you shouldn't let it until you've watched its drafts for two weeks. Treat the trust rules as a graduation system, not a setting.

What to do after week 1

By the end of week 1, you should have: 3 connectors wired, 2-3 workflows running, 1-2 custom skills built, and a working Business Brain. That's enough to deliver real value.

Week 2 and beyond:

• Add 2-3 more custom skills based on tasks you found yourself doing manually that week
• Add the 4th and 5th connector (probably HubSpot and DocuSign for B2B services, or Canva and PayPal for DTC)
• Promote your most-trusted draft actions to auto-run
• Update the Business Brain with new offers, new pricing, new positioning as your business evolves

The Brain is the only part of the setup that needs ongoing attention. Connectors and workflows are set-and-forget. Skills are set-and-occasionally-refine. The Brain is a living document.

For a comparison of Cowork against the developer-focused Claude Code (different product, often confused), see Claude Cowork vs Claude Code.

Frequently asked questions

Once Cowork is working, the next move

You'll know Cowork is set up right when you stop opening it. The workflows run on their schedule, the skills get used by your team without you watching, and the Business Brain quietly makes every output sound like you. That's the goal.

If you'd rather not spend the 6 hours yourself, that's exactly the work I do — my productized Cowork install wires the connectors, builds the first 5 skills, captures the Brain, and hands you a working system at the end of week one. There's also a done-by-you path with the full playbook if you'd rather build it.

Either way: don't skip the Brain. The Brain is what turns a $125/month tool into a system that runs your operations.