A blank Claude chat is a poor place to do marketing. The company belongs in a project: files on one side, rules for every chat on the other. The model reads those. It does not read the project name or the description. The help page on creating projects says Claude will not have access to those details. I opened that page on November 16, 2026.
The next question starts without your prices, your bans, and your voice, unless you put them in files. That base is where an AI marketing system: what it is and where to start begins. The same idea in another product, without the Claude screen, is in ChatGPT for business: system instead of an empty chat.
You can hand a project to a colleague on Team and Enterprise plans. Can view lets them read the files and chat, and not edit. Can edit lets them change the instructions and the files. I have spent 19 years in Google Ads, since 2006, and the gap is the same every time: the role sits in the title, and the files are empty.
What to create: one project per role
One project is one job Claude will repeat. It is not the whole company in a single folder, and it is not a new project for every post. Keep the role narrow, or the instructions will argue with themselves.
For an HVAC company I would make three projects. The first answers homeowners who ask about a repair and flinch at the price. The second holds a short map of nearby firms and does not invent their terms. The third drafts ads you read before anything goes live in the account. A dental practice uses the same shape. One social post does not deserve its own project.
You can create a project on a free account. The help page caps that at five projects. The buttons below are from the help page I checked on November 16, 2026. If the label on your screen differs, follow the label.
- Click Projects on the left, or open claude.ai/projects.
- Click + New Project in the upper right.
- Give it a name you will still understand next month. Do not hide the role in the name.
- On a Team or Enterprise plan, choose Keep it private until you decide who should see it.
- Click Set project instructions. Write the role, the language of the reply, and the bans. Save with Save instructions.
- On the right, click + and add files. Start the next chat inside the project.
Test it with a question whose answer lives in one file only. If Claude answers in generalities, the file is missing or the filename says nothing.
Which files go in the project knowledge base
The knowledge base is the set of facts the model is not allowed to leave. I keep the files short. I do not upload the whole drive. The help page asks for clear filenames, because Claude uses them to find the right passage once the base is large.
| File | What it holds | What to leave out |
|---|---|---|
| Who we are | One or two pages: what you sell, to whom, and what you refuse | A long history and slogans |
| Services | What is included and on what terms. Put the price in its own file and the date in the filename | A price list with no date |
| Customer | Objections and phrases from real emails and calls | A portrait you invented in five minutes |
| Competitors | Who is nearby and how you differ | Copies of other people’s sites |
| Voice | Three to five emails or posts you actually sent | Text the chat just invented as an example |
| Bans | Address, guarantee, and timelines the model must not invent | Passwords and customer records |
Build the competitor map before you drop it into the project. A map is not a guess, and that difference is the point of AI Competitor Analysis: A Map, Not Guesses. The project gets your map, not a dump of someone else’s pages.
A file in the project knowledge base can be up to 30 MB. The upload help page is dated July 23, 2026, and I checked it on November 16, 2026. The page does not cap the number of files, but the text has to fit the context window, which is what the model can read at once. An ordinary file yields text only. A PDF of up to 100 pages also yields images. From page 101 to page 1000, Claude reads text only. A longer PDF will not upload. Save a price list as CSV or plain text.
When the base nears the context window, a paid plan turns on search across the files by itself. Anthropic calls this RAG. The RAG help page says capacity grows by up to 10 times. That is a ceiling on how much the base can hold, and answer quality stays the same. You do not switch it on, and the plans are Pro, Max, Ultra, Team, and Enterprise. The model pulls passages. It does not hold every file in view. Name the file in your question. A free account does not get that expansion in the help page. The base has to fit the window.
How instructions differ from files
Instructions tell Claude how to behave in every chat in this project. A file tells Claude what is true about the company. The name does neither. If the role “office coordinator” lives only in the Name field, the reply will be generic and confident.
| Place on the screen | What you put there | Does Claude read it |
|---|---|---|
| Name and description | A label for you and your colleagues | No. The help page says there is no access |
| Instructions | Role, language, shape of the reply, bans | Yes, in every chat in the project |
| Knowledge base on the right | Company files | Yes, in all chats in this project |
| A single chat | The question in this conversation | This chat only, until you save the conclusion in the base |
Here is an instruction I would put on the HVAC replies project. Swap in your own trade. You write short replies as the person who answers the phone. You take prices only from the services file. If the price is not there, you say so. You do not promise a repair result. You do not name a competitor who is not in the map file.
The text of one chat does not become the next chat. The help page shares that text only after you add it to the knowledge base. The raw window does not load into the next chat. A project also has its own memory. On Free, Pro, Max, and Ultra it is on by default, and it does not pull memory from other projects. Claude saves separate topics on its own, not the whole dialogue, until you turn Memory off. To keep it from mixing with account memory, turn off Use account memory on the project page. A conclusion that must survive belongs in a file.
Once the role, the files, and the instructions are in place, the project is yours to assemble on your own material. If you also run Google Ads, the step-by-step version for business owners is in my book.
My e-book “19 Google Ads Secrets”: how to get the most out of Google Ads without draining your budget, drawn from real campaigns and tests.
See the book →Who can open the project
The Share project button is on Team and Enterprise plans. The help page does not describe sharing for Free, Pro, Max, or Ultra. You cannot hand this project to a freelancer on a separate Pro account through that button. They are in your Team organization, or you keep the files yourself.
Open the project, click Share project to the right of the name, add the person by name or email, and pick a level. Can view sees the files, the instructions, and the chats, and changes nothing. Can edit changes the instructions and the knowledge base. The project overview also says Can edit can add and remove members. In the steps, the project creator removes access with Remove access. Then click Share.
When you create the project, choose Keep it private or Share with your broader organization. The second option opens the project to everyone, if an admin allows it. An owner can turn sharing off. New people cannot be added, and existing access stays. Do not put passwords or customer records in a project the whole company can open.
What not to mix with Claude Code
Claude Code is for code and repositories. You do not need it for offers, emails, or a competitor map. Do not make it a step before the knowledge base in ordinary chat.
On September 17, 2026, Anthropic described a different project: threads that do the work, and a coordinator that directs them. That is a beta in Claude Code, not the screen where you write marketing copy. The What are projects page, which I opened on November 16, 2026, carries the label Updated over 2 weeks ago and the date October 30, 2026. It says the new version is rolling out from Claude Code, some Pro, Max, and Ultra users are already having existing projects moved, and chat and Cowork come later. The rest of that page describes the current version. You are on it if chats sit on the left and the knowledge base sits on the right.
If you already see threads in the Code tab or at claude.ai/code, do not carry these clicks over. If you are on Pro, Max, or Ultra and do not have access yet, the help page offers a waitlist. A ChatGPT agent is a different workplace too, and it does not replace the files in Claude. The boundary is in How to Create a ChatGPT Agent for Marketing.
When this does not apply
A project does not repair a stale price list, and it does not turn ads on. I would not build it this way under four conditions.
- The Set project instructions button is missing. The create page shows it with no paid label, while the personalization page still says in one line that project instructions are for paid plans. Do not hunt for the button in another menu. Look at your plan.
- The role lives only in the project name. Claude does not read that field, and the replies stay generic.
- The services file is older than the price you actually charge. The reply will sound calm and be wrong. The date in the filename is there for this.
- You ask Claude to change a live Google Ads account. A draft in chat is not a change in the account. The same check, on another product, is in ChatGPT for Google Ads Setup: What Holds Up in Your Account.
Two more limits. A colleague on Pro will not become a co-editor: the help page describes sharing on Team and Enterprise. A base larger than the context window does not get the expansion of up to 10 times on a free account.
Questions and answers
Claude does not read the project name
No. It does not read the name or the description. The help page says there is no access to those details. Anything the model must always respect goes in the instructions or in a file.
Instructions set behavior, and files hold facts
Instructions apply to every chat in the project: the role, the language, and what not to invent. A file on the right holds company facts for those same chats. A sentence in one chat does not enter the next chat on its own.
Colleagues get access on Team and Enterprise
Yes, and only there. Can view reads and chats. Can edit changes the base and the instructions. The help page does not show a share button for Pro. If an admin has turned sharing off, you cannot add new people.
Claude Code is not required for a marketing base
No. The files, the instructions, and the chats live in an ordinary project. Threads and a coordinator are the Claude Code beta, not a step for offers. If your screen already shows threads, this page is about a different interface.