Most people are using Claude the same way they use a search engine — new tab, new question, repeat. They retype who they are and what they’re working on at the start of every conversation. They re-paste the brand guidelines every time they need copy reviewed. They re-explain their ICP every time they ask for help with a sales email. They’re treating a 200,000-token context window like a sticky note.
Projects fix this. One setup, persistent context, every conversation in that project starts informed. It’s the difference between having an assistant who knows your business and having a stranger who needs a full briefing every single time.
This guide is not about what to use Claude for — there are separate guides for that. This is about how to set up the infrastructure that makes Claude consistently useful instead of occasionally useful.
What You’ll Build
A working Project with custom instructions that shape every conversation without you having to set the stage
Uploaded files Claude can pull from every time — your brand guide, product docs, ICP definition, competitor intel
An organized conversation structure within the project so different workstreams don’t bleed into each other
By the end of this guide, four concrete Project setups for the highest-value use cases
Step 1: What Claude Projects Are (and What They’re Not)
Every new Claude conversation normally starts from zero. The model has no memory of what you discussed yesterday, last week, or five minutes ago in a different tab. That’s not a bug — it’s how the model works. But it creates friction when you’re doing recurring work and the same context needs to be present every time.
Projects solve this problem with three components:
Project Instructions — a custom system prompt that runs in every conversation inside the project. This is where you define who you are, what you’re working on, how you want Claude to behave, and what constraints apply. Every conversation in the project inherits this context automatically.
Uploaded files — documents, PDFs, and text files that Claude can reference in any conversation in the project. Brand guidelines, product documentation, competitor battlecards, pricing sheets, style guides, ICP definitions — upload them once and they’re always there.
Conversation history — all conversations within the project are stored together. Claude cannot automatically read a previous conversation while you’re in a new one, but the Project Instructions and uploaded files create an informed baseline that every conversation starts from.
Projects are available on Claude.ai Pro ($20/month) and Team plans. The free tier does not include Projects.
What Projects are not: they’re not magic memory that carries conversation context from one chat to the next automatically. They’re a persistent context layer — instructions and reference materials always present, not a conversation transcript Claude reads before responding.
The use case is simpler than the feature sounds. Instead of starting every conversation with “I’m a VP of Marketing at a B2B SaaS company focused on mid-market healthcare, here’s our ICP, here’s our messaging framework, here’s our style guide” — you write that once in Project Instructions and never type it again.
Step 2: Setting Up Your First Project
Go to claude.ai. In the left sidebar, you’ll see a “Projects” section with a “Create project” option. Click it, give it a name, and you’re in.
The two things to configure immediately:
Project Instructions. This is the highest-leverage thing you’ll do in this entire guide. Click “Set project instructions” (or “Edit project instructions” if you’ve been here before) and write your context. Be specific. A vague instruction produces vague improvement — or none at all.
Most people write something like: “You are a helpful assistant for my marketing work.” That’s not an instruction. That’s ambient noise.
A useful instruction looks like this:
You are a writing and strategy assistant for [Name], VP of Marketing at [Company].
[Company] is a B2B SaaS platform for mid-market healthcare operations. Our ICP is:
Operations directors and CMOs at independent physician groups (20-200 physicians),
$5M-$50M revenue, typically running Epic or athenahealth.
Core product: [product name]. Key outcomes we sell: [outcome 1], [outcome 2], [outcome 3].
Primary competitor: [Competitor]. Our main differentiators vs. them: [differentiator 1], [differentiator 2].
When helping with written content, match our brand voice: direct, clinical without being cold,
evidence-based. We do not use passive voice, we do not use jargon like "leverage" or "synergies,"
and we do not make claims we can't support with data.
When helping with strategy, push back on assumptions. Ask for the data before accepting a premise.That’s an instruction. It shapes every single conversation in the project without you having to re-establish context.
Uploaded files. Once instructions are set, upload your reference documents. Click the paperclip or file icon inside the project to add files. Start with the documents you re-paste most often.
Step 3: Your First Working Result
With instructions set and at least one file uploaded, open a new conversation inside the project. Notice that you don’t need to introduce yourself or explain what you’re working on. Claude has the context from your instructions.
Ask it something you’d normally spend two minutes front-loading with context. “Review this email against our brand voice guidelines” — paste the email, nothing else. Claude knows your voice guidelines from the instructions. “Does this positioning statement align with how we differentiate from [Competitor]?” — paste the statement. Claude has the competitor context.
This is the shift. The context is infrastructure now, not a prompt tax you pay every conversation.
If something comes back off, it means your instructions need to be more specific. Edit them. Add a constraint. Add an example of what you want. Instructions are a living document — the best Project Instructions are ones that have been refined through five conversations, not written once and never touched.
The rule: if you find yourself correcting Claude for the same thing in multiple conversations, that correction belongs in your Project Instructions.
Keep reading with a 7-day free trial
Subscribe to GTM AI Podcast & Newsletter to keep reading this post and get 7 days of free access to the full post archives.