ChatGPT Projects and Claude Workspaces: Team AI Done Properly

The graveyard of one-off chats

Most companies did not adopt AI; individuals did. The result, a year or two on, is a sprawl of personal ChatGPT and Claude accounts where the same prompts get rewritten weekly, good outputs vanish into private history, and nobody knows what the agreed marketing tone actually is because it lives in Dave's chat from March. When Dave leaves, it leaves with him.

ChatGPT Projects and Claude's Projects, inside a shared team workspace, exist to fix this: persistent spaces that hold instructions, reference files and related conversations together, shared across the people who need them. Set up well, a new starter can produce on-brand work on day one. Set up badly, they become a second graveyard with better folders.

Start with the business tier, not personal accounts

Before structure, sort the account model. Move the team onto a business plan: ChatGPT's team or business tier, or Claude's Team plan, typically in the £20–£30 per user per month bracket.

• Business tiers exclude your conversations from model training by default; on consumer accounts this needs a manual opt-out per person, which someone will forget.
• You get an admin console: central billing, user management and the ability to remove a leaver's access in one click.
• Shared projects only work properly when everyone sits inside the same workspace.
• Expensing personal subscriptions scatters your company's working knowledge across accounts you do not control, and recovering it later sits somewhere between painful and impossible.

Structure projects around how work actually flows

Resist the single 'Company AI' project. Create one project per stable stream of work, each with its own instructions and a small set of knowledge files.

• By function: Marketing Content, Sales Proposals, Customer Support Replies, Finance Admin.
• By client, if you are an agency: one project per major account, holding tone, history and constraints.
• Use a naming convention with a team prefix, such as 'MKT – Blog production', so search and the sidebar stay usable once you reach 40 projects.
• Upload only load-bearing documents to each project: the style guide, the price list, the standard terms. Five current documents beat fifty stale ones.
• Name one owner per project in the instructions themselves, responsible for keeping files and instructions current.

Custom instructions by department

Project-level instructions are where the compounding value lives, because everyone inherits them on every chat without thinking about it. Write them the way you would brief a capable freelancer.

• Marketing: 'UK English. House tone: plain, confident, no exclamation marks. Audience: UK small-business owners. Never invent statistics; flag any claim that needs a source.'
• Sales: 'Use the attached price list only; never guess pricing or discounts. Proposals follow the attached template structure. Flag anything outside our standard terms for human review.'
• Support: 'Match the attached tone guide. Never promise refunds or delivery dates; draft options for a human to approve. If a customer mentions legal action or the ICO, stop and escalate.'
• Finance: 'Formats: DD/MM/YYYY and GBP. Verify any figure against the uploaded sheet, and say when a number is absent rather than estimating it.'

Review instructions monthly at first. The gap between what you wrote and what people keep correcting by hand is your edit list.

Permission hygiene and what never goes in

Treat the workspace like any other system that holds company data, because that is exactly what it is.

• Least privilege: client projects visible to that account team only; HR and finance projects locked to those roles.
• Offboarding: removing workspace access goes on the leaver checklist next to email and the CRM.
• Write a one-page acceptable-use note: no customer personal data beyond what a task strictly needs, no passwords or API keys ever, and anything sensitive belongs in an approved project, not a personal chat.
• UK GDPR still applies: pasting customer records into any processor needs the same lawful basis and care as any other data transfer, so keep your privacy notice and processor list current.
• Check where connectors reach: linking Drive, SharePoint or email into a shared workspace can surface documents to people who could not open the originals. Verify before enabling, not after.

Keeping it alive past week three

Workspaces die of neglect, not misuse. The teams that get compounding value run a light ritual: a monthly half hour where each project owner prunes dead conversations, updates one instruction based on the month's corrections, and shares the single best prompt or output in a team channel. Keep a pinned prompt-library document in each project so good patterns get reused instead of reinvented.

• Month one: pilot with one team and two projects; publish what worked and what flopped.
• Month two: roll out by function, with owners named and the acceptable-use note signed off.
• Month three: prune anything unused, merge overlapping projects, and review permissions once.

If usage flattens, the cause is nearly always stale instructions or missing reference files rather than the model. Our team helps UK businesses design these workspace structures and the automation around them, so the tools you already pay for start behaving like infrastructure.