How to set up a Claude Project for a client or brand
The short answer
Create one Claude Project for each client or brand. Give it short instructions that say who the brand talks to, how it sounds and what Claude’s job is, then upload the brand’s own files as project knowledge. Every chat in that project starts with that context, and Claude keeps its memory separate from your other projects.

The basics
What is a Claude Project?
A Claude Project is a workspace inside Claude with three parts: instructions, files and chats. Anthropic’s Help Center calls it self-contained, with its own chat history and its own knowledge base. What you set up in a project applies to the chats in that project and nowhere else.
Instructions. Read at the start of every chat in the project.
- Who the brand talks to
- How the brand sounds
- What Claude’s job is here
- What to do when a fact is missing
Keep it short. Anthropic’s own advice is to put the task in the chat and only the standing rules here.
Knowledge. Files Claude can draw on in every chat.
- Brand voice guide.pdf
- Services and prices.docx
- Past campaigns.xlsx
- Customer FAQs.txt
Up to 30 MB a file. Claude reads the text in a file, and the images too in a PDF.
Chats. Each piece of work gets its own chat.
- November newsletter
- Loft conversion landing page
- Reply to the Hendry review
- Spring offer ideas
A project keeps its own memory. Claude never carries memory across from another project.
Without a project, every new chat starts from nothing. You paste the brand guide again, explain the audience again and correct the tone again. A project does that once.
Step 1
Why make one project per client?
Because the walls between projects are real. Anthropic says each project has its own memory, and that inside a project Claude never uses memory from a different project. One client’s prices and plans cannot turn up in another client’s draft.
We work the same way with our own clients: each one has a separate store of context, and nothing is shared between them. It is the simplest rule we know for keeping client work apart.
One detail is easy to miss. Anthropic notes that Claude cannot see a project’s name or description. Calling the project “Halden Homes” tells Claude nothing. The brand has to be named in the instructions.
Step 2
What should the instructions say?
Four things: who the brand talks to, how it sounds, what Claude’s job is, and what to do when a fact is missing. Anthropic’s advice is to keep project instructions short and general, and to put the task itself in the chat.
You are the marketing writer for [BRAND].
Who we talk to: homeowners planning work on their own home. Most are doing this for the first time, so explain anything a builder would take for granted.
How we sound: plain and direct. Short sentences and everyday words, because our readers are busy and skim.
Your job in this project: write first drafts for me to edit. Give me one version, not three, and tell me which parts you were unsure about.
Use the files in this project for facts about our services, prices and past work. If a fact is not in the files, say so and ask me, because anything you guess could end up in front of a customer.The wording in that template follows three habits from Anthropic’s own prompting guide:
- Give the reason. “Short sentences, because our readers are busy and skim” works better than “short sentences”. With the reason, Claude can handle cases you did not list.
- Say what to do. “Write in plain words” gets a better result than “do not use jargon”. The guide’s own line is to tell Claude what to do, not what to avoid.
- Drop the capitals. Anthropic says newer models over-react to forceful words such as CRITICAL and MUST. Plain wording is enough.
Anthropic also suggests a test. Show the instructions to a colleague who knows nothing about the client. If they would be confused, Claude will be too.
Step 3
Which files should go in the project?
The ones a new hire would be given in their first week. Start with four and add more only when a chat shows that something is missing.
- The brand voice guide, or three pieces of writing the client is proud of if there is no guide.
- Services and prices, as they stand today.
- Past work that performed, with the numbers next to it.
- Questions customers ask, with the answers the client gives.
Anthropic allows files up to 30 MB each and sets no limit on how many. Claude reads the text in a file, and the images as well in a PDF. On paid plans, when the files outgrow what the model can read at once, Claude starts searching them for the relevant parts, which Anthropic says expands capacity by up to ten times.
Keep the files current. A price list from last year is worse than no price list, because Claude will quote it with confidence.
Plans
Which Claude plan do you need for this?
The free plan is enough to try it, and you need a Team plan to share a project with colleagues. Projects exist on every plan, with different limits.
| Plan | Listed price | Projects | Sharing |
|---|---|---|---|
| Free | $0 | Up to five | No |
| Pro | $20 a month, or $17 on annual billing | Yes, with larger project knowledge | No |
| Max | $100 a month | Yes, with five times Pro’s usage | No |
| Team | $25 a seat each month, or $20 on annual billing | Yes | Yes, with view or edit access |
If you work alone, Pro covers it. If three people write for the same client, a shared project on Team means all three get the same voice and the same facts.
Avoid
What are the common mistakes?
Five come up again and again, and each has a quick fix.
- One project for everything. Mixed clients mean mixed voices. Split them.
- Instructions that try to cover every task. Long instructions use up your allowance in every chat. Keep the standing rules and move the rest into the chat.
- Relying on the project name. Claude cannot see it. Name the brand in the instructions.
- Old files. Replace the price list and the offer sheet when they change.
- One endless chat. Start a new chat for each piece of work. The project carries the context, so the chat does not have to.
Anthropic is testing a new version of projects that runs work in parallel in the background. It is in beta for some subscribers, and the setup above carries across: instructions, files and chat history all move with the project.
A project is the first step towards a system your whole team can use. When you want the same context to feed reports, drafts and approvals across a team, that is what we set up in anAI enablement build. Our guide tobuilding a personal AI OS shows the next step up from a project.
Questions
Questions people ask
- What is a Claude Project?
- A workspace inside Claude with its own instructions, its own files and its own chats. Anthropic describes it as self-contained: everything you upload and every instruction you set applies to the chats in that project and nowhere else.
- Are Claude Projects free?
- Yes, with a cap. Anthropic’s Help Center says projects are available on every plan and that free accounts can create up to five. Paid plans hold more project knowledge, and sharing a project with colleagues needs a Team or Enterprise plan.
- How many files can I add to a Claude Project?
- As many as fit. Anthropic sets no limit on the number of files, only 30 MB for each one, and the total has to fit what the model can read at once. On paid plans Claude switches to searching the files when they get too large, which Anthropic says expands capacity by up to ten times.
- Does Claude remember things between projects?
- No. Each project keeps its own memory. Inside a project Claude can use that project’s memory and your general account memory, and Anthropic says it never uses memory from another project. You can switch off account memory for a project as well.
- What should I put in project instructions?
- The rules that hold for every chat: who the brand talks to, how it sounds, what Claude’s job is, and what to do when a fact is missing. Anthropic advises keeping them short and general and putting the task itself in the chat.
- Can my team use the same Claude Project?
- On Team and Enterprise plans, yes. You can share a project with named people or the whole organisation, with “Can view” or “Can edit” access. On Free, Pro, Max and Ultra a project belongs to one person.
- What is the difference between a Claude Project and a Skill?
- A project holds the context for one client or subject. A skill holds the steps for one kind of task, and Claude loads it only when a request matches. Use a project for “everything about this brand” and a skill for “how we write a newsletter”.
Free audit
Want this worked out for your team?
We look at how your marketing work runs today and show you what to build first, what it would cost and what to leave alone. The audit is free.


