Projects
Also: Claude Projects
Projects are dedicated workspaces inside Claude.ai — each with its own instructions, uploaded files, and conversation history. Where a regular chat starts from scratch, a project carries everything forward: your context, your documents, your rules for how Claude should behave. When the files you upload grow large, Projects automatically switch to RAG mode, pulling only what's relevant rather than loading everything at once — which means the knowledge base can scale well beyond the context window without slowing down. On Team and Enterprise plans, projects can be shared with teammates, so a whole team works from the same foundation instead of each person rebuilding it individually.
In practice
You create a Project in Claude.ai called "Marketing." You upload your brand guidelines, style guide, and product docs. Every time you open that Project, Claude has all that context already loaded — you don't re-paste your guidelines every session. Projects are persistent workspaces where Claude remembers your files and instructions.
Where Projects shows up
17 articlesThe two ways to give Claude context about your organisation — shared Projects and individual personalisation — and how to decide which fits your rollout.
One Project per team function is the right starting point. Here is the architecture that works at scale — naming, ownership, system prompt governance, and what to avoid.
Most meetings fail before they start — not from bad intentions but bad preparation. A structured 10-minute routine that works for 1:1s, client calls, difficult conversations, and investor meetings.
Capture, connect, and retrieve your thinking. How to use Claude Projects, custom instructions, and conversational recall to build a system that works.
Skeptical colleagues aren't anti-AI — they've usually had a bad experience, heard about one, or watched a tool get mandated without explanation. Here's how to address all three without being annoying about it.
The way you configure Claude Code at the start of a project determines how useful it is six months in. Here's how to set it up so it stays useful — not just for you, but for anyone who touches the repo later.
Most people's first week with Claude follows the same pattern: one good result, one confusing result, and a vague sense it's not as useful as advertised. Here's how to break that pattern in the first three days.
If every person on your team sets up Claude from scratch, they will each get different results and most will give up. Here is how to give your team a consistent starting point — whether you have admin access or not.
Approval is not adoption. What to do in the window between 'we can use this' and 'we actually use this' — before momentum stalls and inertia wins.
Projects are the most underused feature in Claude. Here's how to configure them so your whole team gets consistent outputs — not whatever each person happens to type.
Finance teams deal with high-stakes, high-precision work. Here is where Claude genuinely helps — and where it has no place.
Product managers spend a disproportionate amount of time writing. Here is where Claude changes that — and how to set it up so it actually fits how product work gets done.
Legal has real limits with AI — and real opportunities. Here is where Claude fits in a legal context, and what should stay out of scope.
QBR prep used to take half a day per account. Here is the workflow that gets it to 45 minutes — without cutting corners on the things that actually matter.
A weekly review sounds like a productivity cliché — until you do one with Claude. Here's the version that takes 20 minutes and actually changes what you do the following week.
Operations work is mostly translation: turning messy reality into clear documentation, turning vendor conversations into decisions, turning incidents into processes. Here is where Claude actually fits.
The founders who use AI well don't use it for everything — they use it for the three tasks that used to eat half their week. Here's what those tasks are and exactly how the workflow runs.