⚪ A practical setup for small teams
Set up Claude CoWork properly before your team invents their own system
For small businesses with a team of five or fewer, where everyone handles a different part of the business, and you'd like Claude to work as a shared tool rather than five separate experiments.
01 — SOUND FAMILIAR?
If any of these sound familiar, you're in the right place
"
We've started using Claude, but it's all a bit random.
"
I can see the potential, but I don't want everyone doing their own thing.
"
One person gets great results. Another says it's useless. Nobody knows why.
"
We keep starting from scratch.
"
Our files are everywhere, and I wouldn't know what to give Claude first.
"
I want the team to use it confidently , but not carelessly.
"
We don't need a big AI rollout. We just need a sensible setup for a small team.
That last one is usually the clearest sign someone is ready for this.
They've moved past the question of whether Claude is useful and arrived at the more practical one:
How do we make it work for us, specifically?
02 — THE PREMISE
The
misunderstanding about Claude CoWork
Installing Claude Desktop takes about four minutes.
The actual setup, the part that makes it useful across a real team, is a different matter entirely.
Before Claude can genuinely help a team of people working on different parts of the same business, someone needs to decide ⇾ ⇾
⇾
What Claude can access, and what it absolutely should not touch yet
⇾
Where approved company files live
⇾
Which files Claude should read first
⇾
How much context is actually useful (more is not automatically better — it is often just more for Claude to wade through)
⇾
When to keep a conversation going, and when a new topic needs a fresh start
⇾
What each person can use Claude for in their role
⇾
Where human review is non-negotiable
Claude CoWork works from the computer it's set up on. That gives you real control over what it can access. It also means the setup matters.
Pointing Claude at the company junk drawer and hoping it figures out the business is not a strategy. It's how you get chaos with better branding.
03 — WHAT GOES WRONG
What happens without a shared setup.
A team can start using Claude quickly. That does not mean they're using it well.
Without shared rules, a few things tend to happen:
Pattern 01
One person uploads everything because more context feels safer.
Pattern 02
Another team member starts from scratch every time and wonders why the outputs are weak.
Pattern 03
Someone pastes in a giant document and gets a vague answer.
Pattern 04
Someone built a useful workflow; it's trapped in their private chat history; no-one else can see it, or reuse it.
Useful output exists, but the knowledge stays scattered.
Nobody quite knows what Claude can safely prepare versus what a human still needs to approve.
⇾
Someone uses it for a client email without checking whether that's okay.
⇾
Someone else avoids it entirely because they're not sure where the boundaries are.
⇾
And the founder ends up as the unofficial AI policy department, fielding questions they
didn't sign up for.
That is not AI adoption. That is AI-shaped chaos.
It happens not because the tool is useless, but because the working system around the tool was never built.
04 — THE SETUP
What this setup does
Claude CoWork Small Business Team Setup gives your team a shared, practical way to use Claude inside the business — with clear rules, clean context files, and workflows that actually match how each person works.
We build the workspace, the boundaries, the context files, and the review points before everyone runs off in different directions.
The aim is not to turn your team into AI experts.
The aim is to give them a clear way to use Claude for real work — without burning time, money, or confidence in the process.
05 — AN ORDINARY TUESDAY
What an ordinary Tuesday looks like after this.
BEFORE THE SETUP
Hunt, Paste, Hope
Before the setup, a team member opens Claude and starts from scratch. They hunt for the right document, paste in too much because they're not sure what matters, ask a vague question, and get a vague answer. Sometimes it's helpful. Mostly, it's inconsistent. And later, someone else on the team goes through the same process in their own chat.
AFTER THE SETUP
Same files. Same rules. Different outcome.
After
the setup, a team member knows where the approved files live. They know which context file Claude should read first. They know what their role-specific workflow covers and when a new conversation is the cleaner option.
MARKETING
The marketing person can turn notes into a campaign outline using approved offer context — without reinventing the brief every time.
OPERATIONS
The operations person can clean up a process without digging through five different versions of the same document.
ADMIN
The admin person can draft a client follow-up without wondering what tone or limits apply.
FOUNDER
The founder can ask for a useful summary of moving parts without rebuilding the business context from memory.
And everyone is working from the same basic rules: where the files live, which context matters, what Claude can help prepare, what needs human review, and when a conversation has done its job.
That is the difference between access to Claude and a working Claude setup.
Not impressive in a demo. Useful on an ordinary Tuesday.
06 — WHAT'S INCLUDED
What the setup includes
— THE WORKSPACE AND RULES
Claude Desktop and CoWork setup guidance, file access explanation, approved CoWork folder structure, usage and token rules, conversation length and topic-change rules, and file format guidelines.
— THE WORKFLOWS
One shared team workflow, one lightweight workflow per person, a Skills governance starter kit, and a built-in Claude for Small Business workflow relevance check — so you know what to turn on, what to leave off, and what needs clearer rules before Claude goes anywhere near it.
— THE CONTEXT LAYER
Clean, structured context files Claude can actually read, 01_READ_FIRST setup files, Global Instructions guidance, and a mini-context file for each person's area of the business. We handle the formatting — your team just needs to know where things live.
— THE ROLLOUT
A review checklist and a 30-day rollout plan that tells your team what to use first, what to test, and what not to automate yet.Smart non-developers who'd rather learn the practical split now than keep guessing, switching tools, and getting inconsistent results.
This is not a pile of prompt templates. It's the working structure
your team needs before prompts become useful.
07 — BUILT-IN WORKFLOWS
What about the built-in Claude for Small Business workflows?
Anthropic has added built-in workflows to CoWork for tools like PayPal, QuickBooks, HubSpot, Canva, DocuSign, Google Workspace, Microsoft 365, Slack, and others.
Some of those will be genuinely useful for your business. Some won't be relevant at all. And some will need a clearer process in place before it makes sense to connect them to anything.
Part of the setup is working out which category each one falls into, so you're not switching everything on because it exists, and not ignoring things that could genuinely save your team time.
08 — THE WORKING PRINCIPLES
5 rules
that shape the setup.
P / 01
Use the smallest useful amount of context.
More is not automatically better. It is often just more for Claude to wade through.
P / 02
A new topic deserves a new conversation.
Long chats can get expensive and less useful. Your team needs a simple rule for when to reset.
P / 03
Don't make Claude fight the file before it can do the work.
Messy files, buried instructions, and bloated documents slow everything down.
P / 04
Skills are for repeated, stable work, not experiments.
If a workflow is still changing, test it manually. Build a Skill once the process is settled.
P / 05
Claude can prepare. A human approves.
Especially for client communication, finances, publishing, legal, hiring, and anything with real consequences.
09 — HOW IT'S DELIVERED
How the setup is delivered
Three live sessions, two hours each.
01
SESSION ONE
2 hours · Live
Setup, access, and usage rules
The practical foundations. Claude Desktop and CoWork setup, what local file access means in practice, what Claude should and shouldn't access, approved workspace structure, usage and token planning, conversation rules, and file format decisions.
BY THE END
Your team has a clear picture of how Claude will be allowed to operate inside the business. Not a vague sense of possibility — a clear picture.
02
SESSION TWO
2 hours · Live
Workspace and safe delegation
The context layer. CoWork folder structure, 01_READ_FIRST files, Global Instructions, structured company context files, role-specific mini-context files, and a clear map of what Claude can draft, prepare, summarise, or analyse — and what stays with a human.
BY THE END
Your team has a shared workspace that Claude can actually use.
03
SESSION THREE
2 hours · Live
Workflows, Skills, and rollout
Turning the setup into working habits. One shared team workflow, one lightweight workflow per person, a built-in workflow relevance check, a Skills governance starter kit, a review checklist, and a 30-day rollout plan.
BY THE END
Your team has a practical plan — not a folder full of good intentions and a vague sense of what to try next.
10 — WHO THIS IS FOR
Who this is for
This works well if you run a small business with a team of five or fewer, where each person handles a different part of the business, whether that's marketing, operations, admin, client service, finance, delivery, or a combination of all of them rolled into two people.
It's especially useful when:
You've been using Claude yourself and now want the team involved without creating chaos
People are already using AI in the business, but there's no shared way of working
Your files and company knowledge are scattered, and you don't know what Claude should actually be looking at
You want your team to feel confident using Claude, but not careless
You know you need structure, not another tutorial
11 — WHO THIS IS NOT FOR
Who this is NOT for
If you want a general Claude tutorial, a prompt library, or a "switch everything on and see what happens" approach, this isn't the right fit.
If your team isn't ready to make clear decisions about file access, usage boundaries, and what belongs in a shared workspace — this isn't the right moment yet.
And if you're looking for a large-scale AI rollout with enterprise documentation, governance layers, and a six-month project timeline, you're looking at the wrong business. (No offence. Different problem.)
Claude CoWork can do a lot. But it works best when the business gives it a clean place to work from.
12 — NOT QUITE READY?
Not quite ready for the full team setup?
COMING SOON - WORKSHOP
Start with the workshop. Bring the team in once you're ready.
If you're earlier in the journey — still getting your own head around CoWork, or not sure whether your team is ready — there's a better starting point. A focused Claude CoWork setup workshop is coming soon. It's designed to help you understand how CoWork actually works before you bring the rest of the team in, so you arrive at the team setup with a clearer picture of what you want to build.
JOIN THE EARLY-BIRDERS
13 — INVESTMENT
One price. One team. One clean setup.
Claude CoWork Small Business Team Setup
Three live sessions, setup and access guidance, shared usage rules, approved workspace structure, Markdown context file guidance, role-specific mini-context files, workflow setup, Skills governance starter kit, review checklist, and 30-day rollout plan.
3 × 2-hour live sessions
Up to 5 people on your team
30-day rollout plan included
Total investment
$6,500.
For up to 5 people
14 — FREQUENTLY ASKED QUESTIONS
FAQ
Do I need to be "techy" to keep up?
No. You need to be willing to make clear decisions about files, access, and responsibilities. That's it. The setup is kept practical and business-friendly throughout.
Is this a Claude course?
No. It's a practical setup for a small team. We focus on workspace structure, context files, usage rules, workflows, and rollout — not general Claude training or prompt practice. If you want that, the workshop (coming soon) is a better starting point.
Are the sessions live or recorded?
Live. You can ask questions, push back, and watch real workflows happen. Replays are included, so if you miss one, you won’t lose your place in the series.
Do I need a paid Claude and ChatGPT account?
Yes. CoWork requires paid Claude access. Part of the setup includes helping you work out which plan makes sense for your team and what's worth using now versus later.
Will this include the built-in Claude for Small Business workflows?
We'll go through them together, but we won't switch everything on just because it exists. Built-in workflows are useful when they match how your business already works. We'll look at what's relevant, what needs a clearer process first, and what to leave alone for now.
What if our files are a mess?
That's probably the most common thing I hear. This setup does require willingness to create a clean approved workspace — we're not pointing Claude at years of scattered documents and hoping it figures out the business. But you don't need to sort everything before we start. Part of the process is working out what needs to be tidied, what needs to be written, and what Claude should simply not have access to yet.
What about confidential information?
This comes up on almost every fit call, and it's exactly the right question to be asking. A big part of the setup is deciding what goes into the workspace, what stays out, and where review must happen before anything leaves the building. You do not need to connect Claude to everything. You need to decide what belongs there.
Can this replace our existing systems?
No, and it shouldn't try to. Claude CoWork works alongside your existing tools and helps your team think, draft, prepare, summarise, and move through work more effectively. It is not a replacement for human judgment, client relationships, or proper business process.
How many people can attend the sessions?
Up to 5. That keeps the setup focused and practical — especially when each person handles a different part of the business and needs role-specific context.
What happens after the three sessions?
You'll have a 30-day rollout plan that tells your team what to use first, what to test, what to review, and what not to rush. The first month is about building useful habits — not trying to automate the entire business before lunch.
⚪ THE FIT CALL
The fit call is where we work out if this is right for you
It's not a sales call. It's a short conversation to look at how your team is currently using Claude, where your files and company knowledge live, what each person would actually use Claude for, and whether this setup is the right next step — or whether something else makes more sense first.
If your team needs a basic Claude introduction before a shared setup makes sense, I'll say so.
If your files and workflows need more preparation before CoWork will work properly, I'll say that too.
Pointing Claude at a messy business and calling it implementation is how you end up with chaos and a very tidy-looking folder structure.
$6500
FOR UP TO 5 TEAM MEMBERS