Claude Projects for business: how to build your team an AI brain.
What to load into a Claude Project, how to set it up so the whole team works from it, and where it stops being the right tool. From the segment business owners ask us about most.
Kristian Njegovanovic, Director, Scalify · Updated 29 October 2026
What are Claude Projects?
Claude Projects are separate workspaces inside Claude, each with its own files, instructions and chat history. Everything you load into a project is available in every chat inside it, so Claude starts each conversation already knowing your prices, your processes and how you write. For a business, that makes a project a shared AI brain.
Without a project, every chat starts from zero. Staff paste in the same price list, explain the same rules and correct the same mistakes, every day. With a project, you do that work once. Anthropic's own description is that projects hold the background a body of work needs, and that project knowledge is always loaded in that project's chats (Anthropic, Skills explained).
In our workshop rooms this is the part people ask about most. We once gave it 25 minutes on the day and the room wanted more. It is not the flashiest thing Claude does. It is the thing that stops Claude giving generic answers about a business it knows nothing about.
What should a business put in a Claude Project?
Load the things a good new hire would need to read before they could do the job: your price list and rates, a set of recent quotes, your step-by-step procedures, a few emails written in your voice, and answers to the questions customers ask most. Keep it current, and keep one project per job rather than one for everything.
| What to load | Why it matters | Keep it useful by |
|---|---|---|
| Price list and rates | Claude prices from your numbers, not a guess from the internet. | Replacing the file every time prices change, with the date in the file name. |
| Recent past quotes | Shows how you actually bundle, mark up and word a job. | Picking 10 to 20 good ones across your job types, not every quote you have ever sent. |
| Procedures and checklists | Answers come back in your order of steps, with your sign-offs. | Writing them in plain language, one process per document. |
| Tone and email examples | Drafts sound like your business, not like a chatbot. | Including three or four real emails you were happy with, and a short list of words you never use. |
| Customer FAQs | Staff get the approved answer instead of making one up. | Adding the answer whenever a new question comes up twice. |
| Product or service catalogue | Claude can match a request to what you actually sell. | Exporting it from the system it lives in, not retyping it. |
The project instructions are where you tell Claude how to use all of that. Keep them short and specific: who it is helping, what it must always check, what it must never do. For a quoting project, that might be "always price from the current rate sheet, show the line items, flag anything not on the price list, and never send anything to a customer."
Two things to leave out. Anything you would not hand a new staff member on day one, like payroll or personal records, and anything out of date. An old price list in the knowledge base is worse than none, because Claude will use it with complete confidence.
Why does Claude get our prices wrong?
Because out of the box it has never seen your rates, your suppliers or your site conditions. It fills the gap with averages from the internet, which can be badly off. The fix is not a better prompt. It is loading your own price list and past quotes into a project and checking its first drafts against jobs you already know.
The same rule we give every room: reference data lives in one place, Claude drafts, a person reviews. Think of it as two employees, one who creates and one who checks.
How do you set up a Claude Project?
Open Projects in the left-hand panel of Claude, choose New Project, then add your files to the project knowledge and write the project instructions. The name and description are only for you; Claude reads the knowledge and instructions. It takes ten minutes to create and an afternoon to fill properly.
- Pick one job. Quoting, customer enquiries, or tender reviews. A project called "Company" that holds everything gives muddier answers than three focused ones.
- Gather the files. Use the table above. Clean them up first: remove old versions and duplicates.
- Write the instructions. Who Claude is helping, the steps it follows, what it always checks, and what it never does.
- Test it on jobs you already know. Ask it to price or answer five things you have done before and compare. Fix the files or instructions wherever it goes wrong.
- Name one owner. Someone has to update the price list when prices change. If nobody owns it, the brain goes stale within a quarter.
Projects are on every plan, with Free limited to five, according to Anthropic's help centre. On paid plans, when a project's knowledge gets close to Claude's working limit, it switches on retrieval automatically so the project can hold up to about ten times more (Anthropic). Which plan to pick is covered in our Claude pricing guide for Australia.
Want your team's first project built on your real price list and procedures, with everyone trained to use it? That is the core of our Claude training.
See Claude trainingHow does a team share a Claude Project?
Sharing projects needs a Claude Team or Enterprise account. The person who owns a project can share it with colleagues as view-only, where they can chat with it but not change it, or with edit access, where they can change the files and instructions. A project can also be made visible to the whole organisation.
The set-up we use with most small teams is simple. One or two people get edit access and own the knowledge. Everyone else gets view access and uses it. That way the price list cannot quietly drift because someone uploaded their own version.
Two details owners do not expect. First, chats inside a shared project stay private to the person who had them unless they choose to share them, so a shared project is not a window into everyone's conversations (Anthropic). Second, one chat does not learn from another. If someone works out a better answer, it only helps the rest of the team once it is added to the project's files or instructions.
That is why we teach this as part of how a business runs AI across a team, not as a personal trick. A shared brain is only as good as the habit of feeding it.
What does a business AI brain look like at full scale?
At full scale, the same idea becomes a tool built on your own history: every new job starts from what you have already done, priced by your own rules. A Claude Project is the cheap, fast first version of that. Many businesses find a project is enough; others outgrow it and build a proper system.
If quoting is your bottleneck, a project is the right place to start, and our page on automating quotes with AI covers what comes after it.
When is a Claude Project the wrong tool?
A project is the wrong tool when the job needs to run on its own, connect to live systems like Xero or your job software, or follow the same procedure across many different projects. Projects hold knowledge; they do not act on a schedule. Those jobs suit a Skill or a built automation instead.
| Option | What it is good at | Where it falls short |
|---|---|---|
| Claude Project | Background knowledge for one area of work: prices, procedures, tone. Quick to set up, easy to share. | Someone still has to open it and ask. It does not run by itself. |
| Claude Skill | A repeatable procedure Claude picks up whenever it is relevant, across any chat or project. | Takes more care to write and test than dropping files into a project. |
| Built tool or automation | Jobs that run on their own, connect to your systems and keep a record, like a quote register. | Needs building, checking and an owner. Worth it once the job is proven. |
Anthropic's own rule of thumb is a good one: if you keep copying the same instructions into several projects, that is a sign it should be a Skill. We go through the difference properly in Claude Skills explained.
Is it safe to put business data in a Claude Project?
On Claude Team and Enterprise, Anthropic does not train its models on your content by default. On the individual Free, Pro and Max plans, training is something you opt out of, so check the setting in every account. The bigger risk is staff loading client files into personal accounts the business cannot see or switch off.
Before you build a brain, decide what is allowed in it. Pricing, procedures and templates are usually fine. Client personal information, health records and anything under a contract or compliance regime need a clear answer first. How we handle data on every build and workshop is on our security page.
Load it with what you would hand a good new hire on day one, and keep it as current as your price list.
Common questions
Can you use Claude Projects on the free plan?
Yes, up to five projects. The automatic retrieval that lets a project hold much more material needs a paid plan, and sharing a project with colleagues needs Team or Enterprise.
Do Claude Projects cost extra?
No. Projects are included in every Claude plan, from Free with its five-project limit through to Enterprise. You pay for the plan, not per project.
Does Claude remember earlier chats inside a project?
Each project has its own memory, kept separate from your other projects. Chats do not share their content with each other, so anything the whole team needs should go into the project's files or instructions.
How many files can a Claude Project hold?
Anthropic does not publish a simple file count. Paid plans switch on retrieval when a project nears its limit, which expands capacity by up to about ten times. In practice, a focused set of clean files beats uploading everything.
What is the difference between a Claude Project and an AI agent?
A project is knowledge that a person chats with. An agent takes actions on its own, such as reading new emails or updating your job software on a schedule. Most businesses start with a project and build agents once they know which jobs are worth handing over.
Checked 29 October 2026. Claude's features and plan limits change often; Anthropic's help centre has the current detail.
Keep reading
Claude is only as smart as what you give it. Give it your business.
Bring your price list, your procedures and the job that eats your week. We will build your first project with you and show your team how to keep it current.