How to set up Claude Cowork: a step-by-step guide for small business

Step 1 — Design your folders first

Cowork acts on real files in the folders you grant it, so the folder design is the safety model. What Claude can reach defines what can go wrong, which is why you design it before Claude touches anything.

• •One dedicated workspace folder. Never grant your whole Documents folder, your desktop, or a drive root.
• •Exclude by default. Payroll, HR records, customer identity documents and credentials never go inside the granted folder.
• •Mirror your business functions, not your file history. A clean structure beats ten years of accumulated folders.

cowork-workspace/
  0-inbox/        drop zone: things for Claude to process
  1-clients/      one folder per active client or job
  2-finance/      invoices out, bills in (NOT payroll)
  3-marketing/    content, social, website copy
  4-operations/   SOPs, templates, checklists
  9-archive/      completed work, read-mostly

When you grant the folder, Cowork offers two modes, "ask before acting" and "act without asking". Start with ask-first. Deletion always requires approval in both modes.

Step 2 — Write a business context file

Without context, every session starts from scratch. A short context file at the root of your workspace tells Claude who you are, what the business does, how you work and what the rules are: business name and what you sell, your customers, tone of voice, the tools you use, currency and date formats, and standing rules such as "draft, never send" for anything customer-facing.

Cowork’s memory currently persists within projects only and does not carry across standalone sessions, which is exactly why the written context file is the reliable backbone of the whole setup.

Step 3 — Connect your tools

Connectors give Cowork scoped access to the tools your business runs on: Gmail or Microsoft 365, Google Calendar, accounting software, your CRM and many more. Connect each from inside a conversation or via Settings, authorising through the provider’s own login.

• •Connect only what your first two workflows need. Taking trust back is harder than granting it.
• •Prefer the verified connector directory, because local integrations run with the same permissions as any program on your computer.
• •Scope to read-only where reading is enough. A workflow that summarises your inbox does not need permission to send.

Step 4 — Install plugins and skills

Plugins bundle skills, connectors and commands for a type of work. Anthropic publishes free first-party packs, including a small-business plugin (invoice chasing, cash-flow snapshots, customer pulse, month-end prep) plus marketing, sales and productivity packs, installable from the app via Customize then Browse plugins.

For a small business, start with the small-business pack, the productivity pack, and whichever of marketing or sales matches where your hours go. Skills are triggered with "/" in a conversation, or fire automatically when a task matches. Resist installing everything: an unused plugin is just configuration debt.

Step 5 — Build your first two workflows

Pick two jobs that are repetitive, document- or data-shaped, and genuinely annoying. Build them interactively first: delegate the task in a normal session, watch what Claude does, correct it, and fold what you learn back into your context file. Automate only once it works by hand. Two we run ourselves:

• •The Monday morning brief. "Read 1-clients/ and 2-finance/, check my calendar and inbox, and produce monday-brief.md in 0-inbox/: cash position, this week’s commitments, the top three things needing attention, and anything overdue."
• •Invoice follow-up drafts. "Check 2-finance/invoices-out/ against payments, and for anything 14 or more days overdue draft a reminder email matched to the customer’s history. Save drafts to 0-inbox/ for my approval. Never send."

Step 6 — Set up scheduled tasks

Scheduled tasks run your proven workflows automatically: hourly, daily, on weekdays, weekly, or manually. Each run happens in its own fresh session. Create them with /schedule or from the Scheduled page.

The detail most guides miss: tasks only run while the computer is awake with the app open. A missed run is skipped, then runs automatically once the machine wakes, with a notification. Design for "visible if missed" by having every scheduled task write a date-stamped output file, so a silent gap is obvious by its absence. Start with two scheduled tasks, not ten. Each run uses more of your allowance than a chat does.

Step 7 — Put your guardrails in writing

The difference between a safe setup and a mess is rarely the software. It is whether the operating rules exist in writing. A one-page policy a five-person business can adopt as-is should cover:

• •Draft, never send. Anything customer-facing is produced as a draft for a human to approve. Keep it for at least the first 90 days; most businesses keep it for good.
• •Folder boundaries. What is granted, what is excluded, and who may change that list.
• •Approval gates. What runs on its own (read-and-report tasks) versus what always asks first (anything that creates, sends, spends or deletes).
• •A review habit. Outputs of automated runs get human eyes within one business day.
• •What never enters the workspace: credentials, payroll, identity documents, anything you would not hand a new contractor on day one.

Anthropic’s own safety documentation is candid that prompt-injection risk is still non-zero and that you remain responsible for what Claude does. Written guardrails are how a small business carries that responsibility without an IT department.