TL;DR

  • Claude Cowork works inside your real files and apps and runs tasks on a schedule. No terminal, no code.
  • Set it up in five steps: point it at a folder, write folder instructions (the brain), split work into projects, save skills, schedule the repetitive jobs.
  • The brief quality is the output quality, vague folder instructions give vague results.
  • Scheduled skills + connectors turn it into AI automation for small business without a platform like Zapier.

Most people open Claude Cowork, ask it one question like it’s ChatGPT, get a so-so answer, and quietly decide it’s overhyped. The tool was never the problem. The setup was. Cowork rewards a few minutes of structure with weeks of saved time, and punishes “just start typing” with mediocre output you’ll abandon by Friday.

I run my own consulting work through this kind of setup. No developer. No terminal. No automation platform with forty nodes. This is the version a non-technical small-business owner can stand up on a free Saturday morning.

What is Claude Cowork, and how is it different from chat or Code?

Claude Cowork is the part of Claude that works inside your real files and connected apps, and can run tasks on a schedule, without you ever touching a terminal. Anthropic is merging chat and Cowork into one conversation. It is rolling out now, so you may still see separate Chat and Cowork options. Code is still there as the developer version.

The distinction matters. Chat answers questions. Code is powerful, but the moment you hear “terminal” or “IDE”, most business owners are out. For a non-technical operator, Cowork gets you most of the way to what Code does, with almost none of the complexity. That’s the whole reason to start here.

Tool What it does Best for
Chat Answers questions in a box and can remember past chats Quick one-off questions
Cowork Works in your files + apps, runs scheduled tasks, no terminal Non-technical business owners
Code Same power, built for developers (terminal, editor, desktop app or web) Developers

Why most Cowork setups fail

The common story: someone spends hours wiring up Cowork, it spits back a generic, mediocre result, and they never open it again. It usually comes down to one thing: the context you gave it was thin. Claude takes you literally. Feed it a vague picture of your business and it gives you a vague answer back.

❌ Vague brief → generic output. ✅ Specific brief → output you’d actually send. The goal of the setup below isn’t to install features. It’s to get a good brief in front of Cowork, every time. The brief quality is the output quality.

Step 1, Give Cowork a workspace (this is the unlock)

Download the Claude desktop app and point Cowork at a real folder on your computer. For folder work, use the desktop app, not the browser. The folder is the thing that turns Cowork from a chat box into a tool. It can read and write actual files, which is most of its power.

1Download the desktop app

Get the Claude desktop app for Mac or Windows (Linux is in beta). Cowork needs a paid Claude plan (Pro or above). It also runs on the web and phone on some plans, but it can only work in folders on your computer while the desktop app is open.
2Create a project

Open it, click Projects in the left sidebar, click +, and choose Start from scratch to make a new folder. Call it something boring like cowork.
3Allow access

Allow it access to that folder. That’s your workspace. If you only ever chat in a browser tab, you’re missing most of what Cowork can do with your files.

Step 2, Write your folder instructions (the brain)

With your cowork folder selected in the desktop app, write its folder instructions. Anthropic’s help centre says these add project-specific context when you select a local folder on desktop. Tell Claude who you are, what your business does, who your customers are, and how you want it to work. It’s the brain of the whole system, the standing brief Cowork works from whenever you use that folder.

Let Claude draft them, and don’t try to perfect them on day one. Get a first version down fast, then refine them over time. Here’s the prompt to start:

Write folder instructions for this folder. I run [what your business does] for
[who you serve]. My goals this quarter are [X]. My tone is [direct / formal /
friendly]. When you produce work for me, always [house rules, e.g. Australian
English, no jargon, show your reasoning]. Ask me five questions first if
anything’s unclear, then write the instructions.

Then maintain them the lazy way, let Claude review its own brief:

Based on our recent work in this folder, suggest updates to my folder
instructions: what’s out of date or unnecessary, and what’s missing. Show me
the changes, then update them.

That self-pruning habit is the difference between a brief that gets sharper every week and one that rots. Don’t skip it.

Step 3, Split your work into projects

Cowork lets you create separate projects, each with its own memory and context. One for content, one for finances, one for client delivery. It’s housekeeping, but it’s the housekeeping that keeps outputs sharp, so a content request never gets answered with your bookkeeping context bleeding into it. Set up one project per distinct area, and Cowork stops making you re-explain yourself every session.

Step 4, Turn your best result into a skill

This is where it compounds. A skill is a saved workflow you trigger in one line (a client report, a content draft, a meeting prep doc) that comes out the same way every time.

The right way to build one is to show Claude a good result first, then save it, the same way you’d train a new hire by showing them a strong example before letting them run with it. ❌ “Make me a skill for reports.” ✅ “Here’s a report I like the format of [paste/screenshot], match this style, then save it as a skill called client-report.”

Two ways to get going fast:

On downloaded skills: only import skills from a source you actually trust. A random repo from someone with no name attached is a risk; Anthropic’s own plugins, or a creator you’ve followed for months, is a safer bet. Treat a skill like code you’re about to run, because it is.

Step 5, Put the repetitive jobs on a schedule

Cowork has scheduled tasks. It can run your skills on a cadence (every morning, every Friday) without an automation platform like Zapier or Make. Scheduled tasks run remotely, but a task that needs files on your computer still needs the computer on and the Claude desktop app open. This setup uses a local folder, so leave the computer on and the app open when a task is due. This is AI automation for small business that a non-technical owner can actually run. It’s what turns “a tool I open” into “a system that runs without me.”

Create a scheduled task: every weekday at 7am, scan my email and calendar and
give me the three things that actually move my business forward today. Output it
as a clean dashboard.

The sequence matters: get your folder instructions and workspace right first, refine a skill until its output is reliable, then schedule it. Automating a sloppy skill just gives you sloppy output on a timer.

Bonus, connectors and dashboards

Two more pieces tie the system together. Connectors plug Cowork into the apps you already use, Gmail, Google Calendar, Canva, Notion, accounting tools and many more. Go to Customize, then Connectors, then click + to browse. The list is long. On permissions, start with needs approval so Claude asks before it acts in your apps, and move to always allow only once you trust a given workflow. If an app you want isn’t natively listed, a bridge like the Zapier MCP can connect it.

Artifacts can be dashboards that read data from those connected apps. The single best first build for a small-business owner is a morning inbox dashboard: “Use the Gmail connector to show the ten emails I most need to reply to today, ordered by importance.” Now you get a 30-second read on your day instead of drowning in the inbox.

Steal these, the prompts to set the whole thing up

# 1. Build the brain
Write folder instructions for this folder. I run [business] for [audience]. Goals this
quarter: [X]. Tone: [direct, Australian English, no jargon]. Always [house rules].
Ask me 5 questions, then write it.
# 2. Keep the brain sharp (run weekly)
Suggest updates to my folder instructions based on our recent work. What’s
outdated, what’s missing? Show me the changes.
# 3. Build a skill from a good example
Here’s a [report/post] whose format I like: [paste]. Match this exactly, then
save it as a skill called [name].
# 4. Schedule the repetitive job
Scheduled task, weekdays 7am: scan my email + calendar, return today’s 3
highest-leverage tasks as a dashboard.
# 5. First dashboard
Use the Gmail connector to show the 10 emails I most need to reply to today,
ranked by importance.

Your Cowork checklist

The honest summary

Claude Cowork won’t make you more capable overnight, it makes your inputs repeatable, which is the part most people never get to. It won’t rescue a vague brief, and it won’t run a business you haven’t described to it. Scheduled tasks built on a sloppy skill will reliably produce sloppy work. But for the everyday reality of a small operation (the reports, the content, the morning triage, the follow-ups) a proper Cowork setup quietly takes hours off your week, with no developer and no code.

Start with the folder and its instructions. Add one skill. Schedule one job. That’s a system. Get your side of it right (the clear brief, the good example) and the output takes care of itself.

Straight answers (FAQ)

Claude Cowork is the part of Claude that works inside your real files and connected apps and can run tasks on a schedule, without using a terminal or writing code. It needs a paid Claude plan (Pro or above). Claude Code is the separate developer version.

No. Cowork is built for non-technical users and needs no terminal. You work in folders and plain-text files and trigger saved workflows in one line. For most small-business tasks it gets you most of the way to what the developer-focused Claude Code does, with far less complexity.

Folder instructions add project-specific context when you select a local folder in the Claude desktop app. Use them to tell Claude who you are, what your business does, and how you want it to work. They act as a standing brief, and Claude can also update them during a session. Write a first version fast, then refine it over time.

Both work with your files. Code is built for developers and runs in a terminal, code editor, desktop app or browser. Cowork suits non-technical users and runs in the desktop app, with web and phone access on some plans. For everyday business workflows, Cowork gets you most of the way Code would, with much less setup friction.

A skill is a saved workflow you trigger in one line so a task comes out the same way every time. A connector links Cowork to an app you already use, Gmail, Calendar, Canva, Notion, accounting tools, so it can read and act on real data. Anthropic also ships pre-built skill plugins (marketing, productivity, design) you can install as a starting point.

Treat a skill like code you’re about to run. Skills from a trusted source, Anthropic’s own plugins, or a creator you know, are reasonable. Skills from an anonymous repository are a risk worth avoiding. For connector permissions, start with needs approval and only switch to always allow once you trust the workflow.

Source: Anthropic: Get started with Claude Cowork (projects, skills, connectors, scheduled tasks).

Free · 10 Minutes

Find out where your marketing is leaking.

The free scorecard checks your traffic, website, lead capture, email and strategy, and tells you exactly what to fix first.

Take the Free Scorecard →

Get in touch

Prefer to talk it through? Call or text, email, or send a message.

Ty Pryor

Ty Pryor
Small business marketing & AI. I share the Claude and AI workflows I actually run, no hype, no fluff.