Getting started · 10 min read
Give Cowork its first safe job
Claude Cowork is designed for tasks, not just answers. It can work through several steps, read the material you permit, and return a finished file. Your best first job is familiar, reversible, and easy for you to check.
Pick the right Claude workspace
Claude Chat, Claude Cowork, and Claude Code use the same family of models, but they are built around different kinds of work. Choosing the right surface makes the task easier to explain and safer to run.
For most small-business owners, Cowork is the practical starting point. It does not require a terminal and is built for multi-step knowledge work across documents, spreadsheets, presentations, and connected business tools.
- Use Chat for a question, brainstorm, explanation, or quick draft.
- Use Cowork when you need a deliverable, several inputs, or several steps.
- Use Claude Code when the source of truth is a code repository or the result is software.
Create a narrow working area
Cowork is available on paid Claude plans. You can begin a task from Claude on supported surfaces, but access to folders on your computer requires the current Claude Desktop app to be open and connected.
Create a dedicated folder for the first task and place copies—not your only originals—of three to five nonsensitive files inside it. A good starter folder might contain meeting notes, an old checklist, and a blank document. Do not start with credentials, payroll, health records, customer identity documents, or unrestricted financial files.
Folder: Cowork / First SOP
01-old-checklist.pdf — a copy of the current process
02-team-notes.docx — approved notes with no sensitive data
03-output-template.docx — the format you want back
Ask for an outcome, not vague help
Open Claude, select Cowork, and describe the result you want. Name the source folder, audience, output format, and what Claude must not do. For a first task, use manual approval and keep every external action out of scope.
Ask Claude to repeat the job back and ask questions before starting. This catches assumptions while they are cheap to fix. Review the proposed approach, then let it work.
Turn the files in First SOP into a one-page opening checklist for a new employee.
Use only facts in those files. If two sources disagree, flag the conflict instead of choosing one.
Match the output template and save the result as opening-checklist-draft.docx in this folder.
Do not alter the source files, contact anyone, or use information outside this folder.
Before starting, repeat the task back to me and ask any clarifying questions you have.
Review the work like an owner
Watch for unexpected scope: a file, website, or application you did not mention. You can interrupt and steer Cowork while it works. Stop the task if it starts reaching beyond the job you assigned.
When the file is ready, compare names, dates, numbers, and process steps against the source material. Check that uncertainty is visible and that the original files are unchanged. The first success is not that Claude produced a file; it is that you can explain why the file is trustworthy enough to use.
Try it yourself
Build one useful SOP
Choose a routine you already know well, such as opening the shop, preparing a service visit, or onboarding a client.
- 1
Create a dedicated folder and add copies of three to five low-risk source files.
- 2
Open Cowork, select that folder, and use the task brief above with your real outcome and filename.
- 3
Review Claude's restatement and plan before allowing it to continue.
- 4
Check the finished file line by line against the sources and record every correction you make.
Keep thisStart by giving Cowork one bounded job you understand better than it does—and verify the finished work yourself.
Official Claude documentation
Check the source.
Claude changes quickly. This lesson was reviewed on August 17, 2026against the official Anthropic resources below. Confirm current plan, permission, and feature availability before using it in your business.