What are Claude Projects and how do you set them up?

Quick Answer: Claude Projects let you give Claude persistent memory, custom instructions, and uploaded knowledge so it behaves like a trained team member rather than a blank-slate chatbot. For B2B SaaS marketing teams, setting up a Project correctly means Claude understands your product, your audience, and your brand before you type a single prompt.

Marketing teams waste enormous time re-explaining context. Every new Claude conversation starts from zero: your positioning, your ICP, your tone of voice, your product's key differentiators. Claude Projects fix that. This guide walks you through exactly how to set up a Claude Project for marketing, what to put in the knowledge base, how to write a system prompt that actually works, and what custom instructions separate a useful Project from a generic one.

By the end, you will have a Project that functions as a context-aware marketing assistant for your B2B SaaS team.

What Are Claude Projects (and Why Should Marketers Care)?

Claude Projects is a feature inside Claude.ai that lets you create a persistent workspace for a specific purpose. Unlike a standard conversation, a Project retains:

• Custom instructions that shape how Claude responds every time
• A knowledge base of uploaded documents, files, and text Claude can reference
• Conversation history within the Project so context builds over time

For B2B SaaS marketing teams, this matters because your work is context-heavy. Claude needs to know what your product does, who buys it, why they buy it, and how you talk about it. Without that context loaded upfront, every prompt is a negotiation. With it, Claude produces on-brand, audience-aware output from the first message.

Step 1: Create Your Claude Project

Start at claude.ai and make sure you are on a Claude Pro or Team plan. Projects are not available on the free tier.

1. Click "Projects" in the left-hand sidebar
2. Select "Create Project"
3. Name it clearly, for example: "B2B SaaS Marketing" or "Content System - [Product Name]"
4. Add a short description so team members understand its purpose

The name and description are internal. They do not affect Claude's behaviour, but clear naming matters when you are managing multiple Projects across a team.

Step 2: Write Your Project System Prompt (Custom Instructions)

The system prompt is the most important part of your Project setup. This is the standing instruction Claude reads before every conversation inside the Project. Get this right and every output improves immediately.

What to Include in Your Marketing System Prompt

Your system prompt should cover four areas:

1. Role definition Tell Claude what it is. Be specific.

"You are a senior B2B SaaS marketing strategist working for [Company Name]. Your job is to help the marketing team produce copy, campaigns, and strategic content that converts mid-market SaaS buyers."

2. Audience and ICP Describe your ideal customer profile in concrete terms. Job title, company size, pain points, what they care about.

"Our primary ICP is a VP of Marketing or Head of Growth at a B2B SaaS company with 50-500 employees. They are responsible for pipeline generation and are measured on MQL-to-SQL conversion. Their biggest frustrations are inconsistent content output and poor alignment between marketing and sales."

3. Brand voice and tone List what your voice sounds like and what it does not sound like. Include a few examples if you have them.

"Our tone is direct, confident, and practical. We do not use jargon, we do not over-explain, and we never use buzzwords like 'synergy' or 'game-changer'. Think senior practitioner talking to a peer, not a vendor pitching a prospect."

4. Output rules Set formatting defaults, length preferences, and any standing constraints.

"Default to short paragraphs. Use headers for anything over 300 words. When writing copy, always lead with the customer problem before introducing the solution. Never write a headline that starts with 'How to' unless explicitly asked."

System Prompt Length

Keep your system prompt between 300-600 words. Long enough to be specific, short enough that Claude does not lose the thread of what matters most. If you find yourself writing more than 600 words, split the excess into knowledge base documents instead.

Step 3: Build Your Project Knowledge Base

The knowledge base is where you upload the documents Claude should treat as ground truth. This is what separates a generic AI assistant from one that knows your product.

What to Upload

Positioning and messaging documents Your core positioning statement, value proposition, key differentiators, and messaging hierarchy. If you have a messaging framework or brand guide, upload it here.

ICP and persona documentation Detailed buyer personas, jobs-to-be-done research, common objections, and the language your customers use. If you have recorded customer interviews or sales call summaries, extract the key quotes and upload them.

Product documentation Feature overviews, use case descriptions, and any technical context Claude needs to write accurately about your product. You do not need to upload everything. Focus on what marketing actually writes about.

Existing content examples Upload 5-10 pieces of your best-performing content. A mix of blog posts, email sequences, and landing page copy works well. This gives Claude a concrete reference for what good looks like in your context. If you want outside inspiration for how specialist teams structure repeatable content systems, it can also help to review how leading B2B SaaS content marketing agencies approach strategy and execution.

Competitive positioning notes How you are positioned against your top two or three competitors. What you win on, where you lose, and how you handle objections. Claude will use this when writing comparison content or competitive messaging.

How to Upload Files

Inside your Project, click "Add content" under the Project knowledge section. You can upload PDFs, Word documents, text files, and paste text directly. Claude can reference up to 200,000 tokens of knowledge per Project on the Pro plan.

Organise your uploads with clear file names. "ICP-VP-Marketing-2024.pdf" is more useful than "Persona doc final v3.pdf".

Step 4: Test Your Project Before Using It in Production

Before your team starts relying on the Project, run a set of test prompts that cover your most common use cases.

Test prompts to run:

• "Write a 150-word LinkedIn post announcing our new [feature]. Target a VP of Marketing at a mid-market SaaS company."
• "Draft a cold email subject line for a campaign targeting heads of growth. The offer is a free audit."
• "Summarise our positioning against [Competitor] in three bullet points."
• "What are the three biggest pain points our ICP faces, based on what you know about them?"

Read the outputs critically. Ask yourself:

• Does Claude understand who the audience is?
• Does the tone match your brand voice?
• Is the product described accurately?
• Are there any claims or framings you would never use?

Refine your system prompt and knowledge base based on what you find. This iteration step is where most teams skip ahead too fast. Spend 30 minutes here and save hours later.

Step 5: Set Up Task-Specific Projects for Different Marketing Functions

One Project per use case outperforms a single catch-all Project. The system prompt can only do so much when it is trying to serve a content writer, a demand gen manager, and a product marketer simultaneously.

Recommended Project structure for B2B SaaS marketing teams:

Each Project gets its own system prompt tuned to that function. A content writer's Project should have different defaults (longer form, SEO-aware) than a demand gen Project (short, conversion-focused, direct). If SEO is a major workflow inside your team, you may also want a dedicated Project informed by the processes used by specialist B2B SaaS SEO agencies. Likewise, teams running paid acquisition can benefit from a separate setup shaped around the practices of experienced B2B SaaS PPC agencies.

What Makes a Claude Project Actually Useful vs. Just Another Chatbot

The difference between a Project that teams use every day and one that gets abandoned comes down to three things:

Specificity in the system prompt. Vague instructions produce vague outputs. "Write in a friendly tone" tells Claude nothing. "Write like a senior practitioner explaining a concept to a peer, no jargon, no hedging, no filler sentences" tells Claude something it can act on.

A knowledge base that reflects how you actually talk about your product. If your uploaded documents use formal corporate language but your brand voice is conversational, Claude will default to the documents. Make sure what you upload matches how you want to sound.

Regular updates. A Project set up once and never touched will drift out of date. When your positioning changes, update the knowledge base. When you launch a new product line, add the documentation. Treat the Project like a living brief, not a one-time setup.

FAQs

What is a Claude Project and how is it different from a regular Claude conversation? A Claude Project is a persistent workspace that stores custom instructions, uploaded knowledge documents, and conversation history. A regular Claude conversation resets every time. Projects let Claude retain context about your brand, product, and audience across every session, which means you get relevant, on-brand output without re-explaining your context each time.

How many documents can I upload to a Claude Project knowledge base? Claude Pro supports up to approximately 200,000 tokens of Project knowledge, which is roughly 150,000 words of text. In practice, that covers a full messaging framework, several persona documents, a competitive overview, and 10-15 content examples with room to spare.

Do I need technical skills to set up a Claude Project for marketing? No. Setting up a Claude Project requires no coding or technical configuration. The setup is entirely text-based: you write a system prompt, upload documents, and test outputs. Any marketer comfortable writing a creative brief can set up and manage a Project.

How often should I update my Claude Project knowledge base? Update your Project whenever your positioning, ICP, or product changes meaningfully. For most B2B SaaS teams, a quarterly review is sufficient. If you run a major rebrand or launch a new product tier, update immediately. Outdated knowledge produces outdated outputs.

Can multiple team members use the same Claude Project? Yes. On Claude's Team plan, Projects can be shared across a workspace so every team member works from the same context. This is one of the strongest arguments for Teams over individual Pro accounts: consistency across every piece of content your team produces.