Building a Company Assistant With Claude Projects
Claude Projects is Anthropic’s feature that lets you upload company-specific information — documents, brand voice, FAQs, procedures — to Claude and build a persistent “company assistant.” You upload your brand guidelines, FAQ list, and product information into a Project once; from then on, Claude uses this information as ready-made context in every new conversation. In this piece I walk through the setup step by step, which tasks it’s genuinely useful for, and where I draw the line.
What Claude Projects Is, and How It Differs From Regular Claude
In a normal Claude chat, every new conversation starts from scratch. You’d have to re-paste your company’s tone guidelines, product list, or FAQs every single time — close the chat five minutes later and open a new one, and Claude won’t remember that context.
Claude Projects changes that. The documents you upload into a Project stay there permanently; every new conversation you open inside that Project automatically has access to them. You also define, once, how Claude should behave in that Project via “custom instructions” (tone, format, forbidden phrases) — you don’t rewrite it in every conversation.
Conceptually it resembles custom GPTs on the OpenAI side — if you want to look at it from that angle, see How to Build Your Own Custom GPT. For basic background on what Claude can do, reading What Is Claude AI first might help.
Step-by-Step Setup
Setup doesn’t require technical knowledge and takes 15-20 minutes:
- Create a Project. In claude.ai, click “Projects” > “Create project” from the left menu, enter a name and short description (e.g. “Customer Support Assistant”).
- Write custom instructions. Describe how you want Claude to behave inside that Project: which tone (formal/casual), what response format (short bullets/long paragraphs), which topics it should avoid. Example: “Always respond to customers formally and briefly. If asked about pricing, don’t give a number directly — direct them to the contact form.”
- Upload your documents. Drag your brand guidelines, FAQ document, product/service list, and past correspondence examples — as PDF, Word, or plain text — into the Project’s “Knowledge” section.
- Share with your team. On a Team or Enterprise plan, you can add members to the Project with “Add people”; everyone works from the same document base and the same instructions, keeping consistency managed from one place.
What It’s Used For
The three areas where it’s most useful in practice:
- Draft replies to customer emails. You paste in the incoming email, Claude produces a draft reply in your brand voice; you review and send it.
- Recurring content production. Blog posts, social media copy, product descriptions — all come out in the tone and format your company has set, without writing a brief from scratch.
- An internal FAQ assistant. HR policies, operating procedures, and common internal questions get uploaded to a Project; team members ask the assistant instead of asking a colleague. I cover this document-based Q&A approach in more depth in Building an AI That Answers From Your Documents.
What Its Limits Are
To be honest, Claude Projects doesn’t solve everything:
- Limited on the free plan. The number of projects and sharing options are limited on a free account; team sharing requires a Team or Enterprise plan.
- Limited document size and count. When you upload too many or too large files, Claude doesn’t “memorize” everything perfectly — it searches for and finds the relevant pieces. Keeping critical information in clear, short documents gives better results.
- Can’t pull real-time data. Live stock status, current pricing, or that moment’s campaign performance don’t live inside a Project — these need a separate integration (an API connection or automation). If your team needs group training on this, enterprise ChatGPT/Claude setup is a separate option.
A Real Example
In my own operation, I set up a Project for weekly performance summaries: I uploaded past report examples, the terminology I use, and the questions clients ask most often. Instead of writing a new account’s weekly summary from scratch, Claude produces the first draft in my voice, and I review the numbers and commentary before sending. For one client, this cut report preparation time in half — the real time savings isn’t in the writing itself, it’s in not having to rebuild the same tone and format every single time.
Claude Projects is a single tool on its own; if you want to treat it as part of a broader AI automation strategy, check out the AI Automation Guide.
You Can Ask Me for This Work
You can ask me for this work. Setting up a Claude Project custom to your company — compiling the right documents, writing custom instructions, and getting it ready for your team to use — is remote, hourly-billed work that typically takes 2 hours to 2 weeks. You can reach out to me to set up your own AI assistant.
Frequently Asked Questions
Is Claude Projects free?
You can create a Project on the free plan, but the number of projects and document capacity is limited. Sharing with a team requires a Team or Enterprise plan.
What’s the difference between Claude Projects and ChatGPT’s custom GPTs?
Both rest on the same idea: upload company-specific information once and have it ready in every conversation. The difference is in the platform and the details — the most practical way to decide which suits you better is to look at what your team already uses.
How many documents can I upload?
There’s no fixed number, but there’s a practical limit: upload too many or too large files and Claude can struggle to find the relevant part. A small number of clear, current documents gives better results.
Can Claude Projects see my live stock or pricing information?
No. Documents uploaded to a Project are static and don’t update in real time. Live data requires a separate API integration or automation.