To create a Claude Project, open Claude on a paid Pro or Team plan, click Projects, name your project, write custom instructions once, and upload your reference documents. Every chat inside that project then remembers your context, so Claude gives consistent, on-brand answers without you re-explaining anything. Want it set up for your business? Book a free call with The Crunch.
If you use Claude for work, you have probably noticed the same small frustration over and over: every new chat starts from zero. You paste in your company details, remind it of your tone, explain who your customers are, then finally ask your question. Tomorrow you do it all again. Learning how to create a Claude Project is the fix for exactly that problem, and it is one of the first things we set up for the business owners we work with.
Think of a normal Claude chat as talking to a brilliant temp who forgets everything the moment they clock off. A Claude Project is the opposite: a dedicated workspace where your instructions and reference documents live permanently, so Claude walks in already knowing your business. This guide shows you how to create a Claude Project step by step, in plain English, with three ready-to-copy examples for a small business. We are The Crunch, a Malaysian AI Automation Agency, and this is how we get owners past copy-paste and into real leverage.
What a Claude Project Actually Is
Picture your office. You do not brief a new stranger from scratch every time a task lands. Your finance person already knows your suppliers. Your sales person already knows your prices. They have context, so they get straight to the work. A Claude Project gives Claude that same standing context.
In practical terms, a Claude Project is a dedicated workspace inside Claude built around one job. It has two things a normal chat does not. First, custom instructions you write once — who you are, your tone, your rules — that apply to every conversation in that project. Second, project knowledge: reference files you upload, such as your price list, brand guide, or standard replies, that Claude can read every time. Every chat you start inside the project inherits both automatically.
So instead of one clever assistant with amnesia, you get a set of specialist workspaces, each one already trained on a single corner of your business. That is the whole idea behind how to create a Claude Project — you set the context once and reuse it forever.
Why a Claude Project Helps a Business
The value is not that Claude becomes smarter. It is that Claude becomes consistent, and consistency is what turns a clever tool into a reliable member of the team.
(1) Reusable context. You stop re-explaining your business at the start of every chat. The instructions and documents are already there, so you skip straight to the task.
(2) Consistent, on-brand output. Because every conversation reads the same instructions, your WhatsApp replies, proposals, and captions all sound like the same company — not like ten different people had a go.
(3) Team sharing. On a Team plan, a project can be shared with staff. A new hire opens the “Customer Replies” project and instantly writes in your house style, without a week of training.
(4) Fewer mistakes. If your real price list and policies live in the project knowledge, Claude quotes from them instead of guessing. That alone removes a whole category of embarrassing errors.
Normal Chat Versus a Claude Project
If you are weighing up whether this is worth the effort, the difference is easiest to see side by side. The same request, handled two ways.
| What you experience | Normal Claude chat | Claude Project |
|---|---|---|
| Context each time | Re-typed or pasted every chat | Set once, always on |
| Reference documents | Re-uploaded per chat | Uploaded once as project knowledge |
| Consistency of tone | Drifts between chats | Same voice every time |
| Team use | Everyone starts from scratch | Shared workspace (Team plan) |
| Best for | Quick one-off questions | Repeating tasks with fixed context |
What You Need Before You Start
One honest caveat up front: Projects is a paid feature. You cannot do this on the free tier. Here is exactly what is required.
(1) A paid Claude plan. Projects live on Claude Pro or Claude Team. Pro is around USD 20 per month (about RM 90) for one person; Team is around USD 30 per user per month and adds shared projects for staff. If you are on the free plan, you will not see the Projects option at all.
(2) The documents you keep repeating. Your price list, brand or tone guide, a few example replies you are proud of, your FAQs, or a standard operating procedure. Anything you find yourself pasting into Claude more than once belongs in a project.
(3) Ten minutes. That is genuinely all it takes to set the first one up. Learning how to create a Claude Project is far quicker than the time it saves you in the first week.
How to Create a Claude Project, Step by Step
The whole process is five short moves. Follow them in order and you will have a working project before your coffee goes cold.
1Open Claude and click Projects
Sign in at claude.ai on your Pro or Team plan. In the left-hand sidebar you will see “Projects”. Click it, then click the button to create a new project. If you cannot see Projects at all, you are still on the free plan and will need to upgrade first.
2Name the project after one job
Give it a clear, single-purpose name — “Customer WhatsApp Replies”, not “Marketing”. The tighter the job, the better Claude performs, because the instructions and documents all point the same way. One project equals one recurring task.
3Write the project instructions
This is the most important step. In the instructions box, tell Claude who it is working for and how you want it to behave, in plain English. Cover four things: who your business is, who your customers are, the tone you want, and any hard rules (for example, always reply in the customer’s language, never promise discounts). You are writing a job description once, so every future chat obeys it.
4Upload your knowledge files
Add your reference documents to the project knowledge — price list, brand guide, sample replies, FAQs. Drag them in, the same way you would attach a file to an email. Claude now reads these every time, so it answers from your real information instead of guessing.
5Start chatting inside the project
Open a new chat from within the project and make your request as normal — “Reply to this customer” or “Draft a proposal for this enquiry”. Claude already has your instructions and documents loaded, so it responds in your voice, from your facts, with no set-up. Every chat you start here keeps that context.
Write your instructions like a job description, not a wish
The single thing that separates a project that works from one that disappoints is the quality of the instructions. Do not write “be helpful and professional” — that tells Claude nothing. Write the way you would brief a new employee on their first day.
Name the business and what it sells. Describe the typical customer. State the tone in real words (“warm, direct, no corporate jargon”). List the rules that must never be broken. Then add: “When you are unsure, ask me rather than guess.” That last line alone prevents most of the confident-but-wrong answers people complain about.
Three Claude Projects Worth Building This Week
Theory is fine, but the fastest way to understand how to create a Claude Project is to build one you will actually use. Here are three that earn their keep for almost any small business.
The “Customer WhatsApp Replies” project
Instructions: reply to customer messages in a warm, human tone, always in the language the customer used, never promise a discount without approval. Knowledge: your price list, delivery terms, and ten of your best past replies.
The “Proposal Writer” project
Instructions: write client proposals in our house style, structured as problem, solution, price, next step. Knowledge: your service list, pricing, two winning past proposals, and your terms.
The “SOP Assistant” project
Instructions: answer staff questions about how we do things, using only our documented procedures, and say so if the answer is not in the documents. Knowledge: your standard operating procedures, staff handbook, and process checklists.
Notice the pattern: each project does one job, has instructions written like a brief, and carries the exact documents that job needs. If you would like these built and connected to your real systems, our AI agent development team does exactly that. Or just tell us the task and we will suggest the project.
Tips to Get More From Your Claude Project
Once your first project is running, a few small habits make a big difference to the quality you get back.
(1) Keep the knowledge current. When your prices change, update the file in the project. Claude is only as accurate as the documents you give it, so a stale price list means stale quotes.
(2) One project per job. Resist the urge to build one giant “everything” project. Separate workspaces stay sharper because their instructions do not have to serve five conflicting purposes.
(3) Refine the instructions over time. When Claude gets something wrong, do not just fix that one reply — add a line to the instructions so it never repeats. The project quietly gets better the more you use it.
(4) Remove sensitive personal data first. Upload your policies and price lists, but strip out customer names, phone numbers, and identity details you do not need. For anything confidential, talk to us about a private setup.
Common Mistakes to Avoid
Vague instructions. “Be professional” gives Claude nothing to work with. Spell out the tone, the rules, and the customer, exactly as you would for a new hire.
Forgetting to upload the documents. Great instructions with no price list still leaves Claude guessing your numbers. The knowledge files are half the point of learning how to create a Claude Project in the first place.
Expecting the free plan to work. Projects is a Pro and Team feature. If the option is missing, that is why — check your plan at claude.com/pricing rather than assuming something is broken.
One project for everything. A workspace trying to write proposals, answer staff, and reply to customers all at once does none of them well. Split them.
Final Word: Set It Up Once, Benefit Every Day
Knowing how to create a Claude Project is a small, one-off effort that quietly pays you back on every task afterwards. You write the instructions once, upload your documents once, and from then on Claude turns up already knowing your business — consistent, on-brand, and fast. Start tonight with a single project for your most repetitive task, and expand from there.
When you are ready to go further — projects wired into your live systems, or AI agents that act on what they find — that is where an agency saves you weeks. The Crunch helps Malaysian, Singaporean, and Hong Kong (MY/SG/HK) SMEs adopt AI tools and build automations that genuinely save time, with trilingual delivery across English, Bahasa Malaysia, and Chinese (Mandarin and Cantonese). Book a free strategy call with The Crunch today and we will help you turn your best documents into workspaces that do the repeating for you.
01How do I create a Claude Project?+
Open Claude on a paid Pro or Team plan, click Projects in the sidebar, and create a new project. Name it after one job, write custom instructions describing your business and tone, then upload your reference documents as project knowledge.
Every chat you start inside that project then uses those instructions and files automatically, so you never re-explain your context again.
02Do I need a paid plan to use Claude Projects?+
Yes. Projects is a paid feature available on Claude Pro (around USD 20 per month) and Claude Team (around USD 30 per user per month). It is not available on the free plan.
If you cannot see the Projects option in your sidebar, you are still on the free tier and will need to upgrade first.
03What is the difference between a Claude Project and a normal chat?+
A normal chat forgets everything once you close it, so you re-explain your business each time. A Claude Project keeps your custom instructions and uploaded documents permanently, and applies them to every conversation inside it.
Think of a chat as a helpful stranger and a project as a colleague who already knows your business.
04What should I put in the project instructions?+
Write it like a job description for a new employee. Name your business and what it sells, describe your typical customer, state the tone you want in plain words, and list any rules that must never be broken.
Adding a line like “when you are unsure, ask me rather than guess” prevents most confident but wrong answers.
05What documents can I upload to a Claude Project?+
Anything you keep repeating: your price list, brand or tone guide, sample replies, FAQs, and standard operating procedures. Claude reads these every time, so it answers from your real information instead of guessing.
Remove sensitive personal data such as customer names and phone numbers before uploading anything you do not strictly need.
06Can my team share a Claude Project?+
Yes, on the Claude Team plan. A shared project lets staff open the same workspace and work from the same instructions and documents.
This is how a new hire can write in your house style on day one, without a week of training.
07How many Claude Projects should I create?+
One project per recurring job. Keep a separate project for customer replies, another for proposals, another for staff questions, and so on.
A single project trying to do everything performs worse than several focused ones, because its instructions cannot serve conflicting purposes at once.
08Is my business data safe inside a Claude Project?+
For ordinary business documents such as price lists and procedures, it is generally fine, but always strip out customer names, phone numbers, and identity details you do not need. Check the current data-use settings in your Claude account.
For confidential or regulated data, The Crunch can set up a private, self-contained system for you.
