How to Use Claude Projects for Marketing Teams: The Complete Setup Guide (With Templates)

Every new Claude conversation starts from zero. You re-explain your brand, your audience, your tone, and your goals. That context tax adds up fast when your team runs dozens of chats a week across SEO, email, paid, and social.

Claude Projects remove the repetition by storing instructions and documents that persist across every conversation. But most marketers either skip Projects entirely or build one overloaded "Marketing" Project that tries to handle everything and handles nothing well. This guide covers a five-Project system for marketing teams, with copy-paste instructions, document recommendations, and an organization method that scales.

Claude Project Instructions Explained in 90 Seconds

A Claude Project has three components: custom instructions, uploaded files, and conversations. Custom instructions act as a persistent system prompt that every conversation in the Project inherits. Uploaded files, such as brand guidelines, personas, and campaign data, are available in every chat. Conversations are individual chats that start with the instructions and files already loaded.

Projects do not automatically carry chat history between conversations. Each new chat begins fresh, but it always includes the Project's instructions and files. This distinction matters because it means your instructions need to be thorough enough to stand on their own.

Projects are available on all plans. Free accounts can create up to five Projects. Pro and Team plans allow unlimited Projects. Team and Enterprise plans support sharing Projects across an organization, which is where the system described below becomes especially useful.

The Three-Layer Customization Stack for Marketers

Claude offers three layers of customization, and understanding how they divide the work prevents duplication and conflicting instructions.

Layer 1: User Preferences

These are global settings in your profile that apply to every conversation across every Project. They cover your identity and communication style. A marketing director might set preferences like their role, their company, and a preference for concise responses with specific examples.

Layer 2: Project Instructions

These are settings specific to one Project. They define the function-specific context and constraints that shape every conversation in that Project. An SEO Project's instructions would cover content standards, keyword rules, and formatting requirements that do not apply to an email or paid media Project.

Layer 3: Skills

Skills are reusable task-format packages that can be invoked in any conversation. They work across Projects and handle specific execution patterns, such as a brand voice skill or a content brief template.

The guiding principle is to avoid duplicating information across layers. Preferences cover who you are and how you communicate. Project instructions cover what you are working on. Skills cover how to execute a particular task format.

Five Claude Projects Every Marketing Team Needs (With Instruction Templates)

Each marketing function gets its own Project with its own context, documents, and instructions. This avoids the one-Project problem where competing instructions across SEO, email, paid, and social confuse the output. For a broader overview of ​how to use Claude for marketing, the companion guide covers the full range of capabilities.

Project 1: Brand HQ (Your Central Intelligence Hub)

Brand HQ is the foundational Project. It holds your core brand context and serves as the single source of truth that every other Project references.

Custom instructions template:

• Company context: what you do, who you serve, your market position, and your differentiators
• Audience: primary and secondary personas with their goals, pain points, and language patterns
• Brand voice: specific tone descriptors with examples of what that voice sounds like in practice
• Positioning: how you frame your product against alternatives, what claims you can and cannot make
• Constraints: what to avoid, such as unsupported "#1" claims, competitor disparagement, and specific terminology that does not fit your brand

Documents to upload:

• Brand style guide
• Annotated examples of your three to five best-performing content pieces
• Competitor analysis
• Customer research or survey data
• Product one-pager
• Audience persona documents

Use Brand HQ for: Strategy, messaging, positioning, competitive analysis, and campaign briefs.

Project 2: SEO and Content Production

This Project handles blog posts, landing pages, content optimization, and everything related to organic discovery.

Custom instructions template:

• Content standards: problem-first openings, short paragraphs, active voice, target reading level, word count ranges by content type
• SEO requirements: keyword placement rules, meta title and description length limits, internal linking minimums, FAQ section formatting
• AI search optimization: direct answers under headings, data density, structured formats that improve citation likelihood

Documents to upload:

• Top-performing blog posts with traffic data
• Keyword research exports
• Editorial calendar
• Internal linking map
• Competitor content examples
• SEO playbook or content guidelines

Use this Project for: Blog posts, content briefs, on-page optimization, topic clusters, and meta tag generation.

Project 3: Email Marketing

This Project covers campaigns, nurture sequences, newsletters, and outreach.

Custom instructions template:

• Email voice: how your brand sounds in inboxes, which may differ from blog or social tone
• Audience segments: key segments with their context, pain points, and stage in the funnel
• Performance benchmarks: current open rates, click rates, and conversion rates by email type
• Email types: campaigns, nurture sequences, newsletters, transactional, and re-engagement
• Constraints: maximum word counts, subject line character limits, one CTA per email, A/B subject line suggestions with every draft

Documents to upload:

• Best-performing emails with open and click metrics
• Email style guide
• Segmentation definitions
• Nurture sequence outlines
• Competitor email examples

Use this Project for: Drafting emails, building nurture sequences, writing subject lines, and analyzing email performance.

Project 4: Paid Media and Advertising

This Project handles ad copy, landing pages, campaign strategy, and performance analysis.

Custom instructions template:

• Channels: which platforms you run ads on, with platform-specific character limits
• Budget and objectives: monthly spend range and primary campaign objectives
• Ad copy standards: variant counts per request, a rule against unproven superlatives, headline and description formats
• Audience targeting: key targeting parameters and audience definitions
• Landing page rules: headline formulas, proof elements, CTA placement, mobile-first formatting
• Campaign types: awareness, consideration, conversion, and retargeting

Documents to upload:

• Top-performing creative with click and conversion data
• Current landing page copy
• Targeting documentation
• Platform performance exports (CSV)
• Competitor ads from ad transparency libraries

Use this Project for: Ad copy, landing pages, campaign structure, performance analysis, and A/B test hypotheses.

Project 5: Social Media and Community

This Project handles social content, engagement, and platform-specific copy.

Custom instructions template:

• Platform priorities: which channels matter most and the voice for each
• Content pillars: three to five pillars with target posting percentages
• Post formats: carousels, threads, short video scripts, discussion prompts, and polls
• Constraints: three-hashtag limit on LinkedIn, avoid stock corporate phrasing, strong opening hooks, and a CTA in every post

Documents to upload:

• Top-performing posts with engagement data
• Social style guide
• Content pillar definitions
• Executive profile briefs for thought leadership
• Competitor social examples
• Platform best practices documents

Use this Project for: Post drafts, content calendars, repurposing long-form content, executive thought leadership, and community responses.

How to Organize Five Projects Without Overlap

The most common mistake is repeating brand voice, audience personas, and product details across every Project. This makes updates painful and causes conflicts when the same information is worded differently in each place.

The core rule: Brand HQ holds the truth. Function Projects reference it.

Keep Documents in the Right Place

Upload shared documents to Brand HQ. Upload function-specific files to their own Projects. Any document relevant to two or more Projects belongs in Brand HQ, so it only needs updating once.

Name Projects Clearly

Use a consistent naming convention like "[Function] + [Company]." For example: "SEO + Content | Acme Corp" or "Email Marketing | Acme Corp." This makes Projects easy to scan and keeps the workspace organized as the system grows.

Copy-Paste Claude Project Instructions Templates by Marketing Function

The templates above give each Project its structure. Here is how to adapt them for your team in practice.

Start by copying the relevant template into your Project's custom instructions field. Replace every placeholder with your actual brand details, audience segments, and performance benchmarks. Generic placeholders like "[your brand voice]" produce generic output.

Customizing Templates for Your Stack

Every marketing team runs a different tool stack, and your ​Claude MCP connector setup determines what data Claude can access directly. Reference your connected tools in the Project instructions so Claude knows what data sources are available.

Add platform-specific rules that match your actual campaigns. If your LinkedIn posts never exceed 1,300 characters or your email subject lines stay under 50 characters, those constraints belong in the function Project's instructions, not in Brand HQ.

What to Include vs. What to Leave Out

Include anything that stays consistent across conversations: voice rules, formatting standards, audience context, and performance benchmarks. Leave out anything that changes per task, such as specific campaign briefs, individual keyword targets, or one-off creative directions. Those belong in the conversation prompt, not the Project instructions.

How to Write Claude Project Instructions That Actually Work

The quality gap between mediocre and strong Claude output almost always traces back to the instructions. A prompt like "You are a helpful marketing assistant" gives Claude almost nothing to work with. Specific instructions produce output you can publish with light edits. Generic instructions produce drafts you have to rewrite.

Show, Do Not Tell

Describe your tone concretely. "Write like a knowledgeable colleague explaining something over coffee" is more useful than "be friendly." Include a paragraph-length example of what your brand voice sounds like in practice, so Claude has a reference point beyond abstract adjectives.

Include Constraints, Not Just Goals

Specify limits: character counts, formatting rules, variant counts, word count ranges, and structural requirements. Constraints narrow the output space and reduce the amount of editing required. An instruction that says "write a blog post" will always produce worse output than one that specifies length, structure, keyword rules, and audience context.

Add Negative Examples

Name the clichés, openings, and patterns to avoid. Never open a blog post with a dictionary definition. Never use "in today's fast-paced digital landscape." Never starting an email with "I hope this email finds you well." Negative examples are often more instructive than positive ones because they eliminate the most common failure modes. For more on how ​Claude's latest models handle marketing tasks, the capabilities guide covers what is new.

Claude Project Instructions vs. Custom Instructions: What’s the Difference?

The terminology can be confusing because Claude uses "custom instructions" in two different places. Understanding the distinction prevents misconfiguration and duplicated context.

Custom Instructions (User Preferences)

Custom instructions in your user profile are global. They apply to every conversation across every Project and every standalone chat. They cover who you are, your role, your communication preferences, and any universal rules you want Claude to follow. These are set once and rarely change.

Project Instructions

Project instructions are scoped to a single Project. They apply only to conversations started within that Project. They cover function-specific context, constraints, formatting rules, and task-specific guidance. These change when your strategy, tools, or team structure changes.

When to Use Which

Put information in user preferences when it applies everywhere: your name, your role, your company, and your general communication style. Put information in Project instructions when it applies only to one function: SEO formatting rules belong in the SEO Project, email benchmarks belong in the Email Project, and brand positioning belongs in Brand HQ. The ​Claude for AEO guide covers how Project instructions specifically support AI engine optimization workflows.

Why Claude Project Instructions Make or Break Your Marketing Output

The difference between a Claude draft you can publish and one you have to rewrite comes down to what the Project knows before you start typing. Instructions are the highest-leverage input in the entire system because they shape every conversation, every draft, and every analysis that happens inside the Project.

Teams that invest 30 minutes writing precise instructions save hours of editing across every subsequent task. Teams that skip instructions or paste in vague guidance end up doing the same correction work in every chat, which defeats the purpose of the system entirely.

The pattern is consistent: the more specific your instructions, the less editing your output requires. The templates above give you the starting structure. Your brand details, audience context, and performance data give them teeth.

Your Next Move

Start with Brand HQ. Adapt the template, upload your brand style guide and three of your best-performing content pieces, and give it ten minutes. Test it by asking Claude to produce something that normally takes you 30 minutes, and compare the result with a context-free chat.

After Brand HQ works, build the SEO and Content Project and the Email Project. Within a week, you will have a system covering your three highest-volume marketing tasks, with instructions and documents that compound across every conversation.

A well-configured Project does not make Claude smarter. It makes Claude informed. That is the difference between a tool that generates content and a system that produces work your team can actually use. For teams running ​SEO and ​GEO at scale, the Project system is the operational layer that connects AI capability to marketing execution. ​Talk to an expert.

Frequently Asked Questions

What Are Claude Projects, and How Can Marketing Teams Use Them?

Claude Projects are persistent workspaces that store custom instructions, documents, and conversations. Marketing teams use them to organize work by function, keeping SEO, content, email, paid media, and social media contexts separate so Claude produces more relevant output.

How Many Claude Projects Should a Marketing Team Create?

Five is the recommended starting point: Brand HQ, SEO and Content Production, Email Marketing, Paid Media and Advertising, and Social Media and Community. Separating functions prevents conflicting instructions from diluting output quality.

What Files Should Marketers Upload to Claude Projects?

Useful uploads include brand guidelines, audience personas, competitor research, top-performing content with metrics, keyword research, campaign performance data, email reports, and social media examples. Upload shared files to Brand HQ and function-specific files to their own Projects.

Do Claude Projects Remember Previous Conversations?

Not automatically. A Project keeps its custom instructions and uploaded files across every conversation, but a new chat does not include the history of earlier chats. This is why thorough Project instructions matter.

How Can Teams Prevent Overlap Between Projects?

Keep core brand information in a central Brand HQ Project and give each functional Project focused instructions and its own resources. Reference Brand HQ rather than duplicating brand voice, audience, and positioning details across every Project.

How Long Should Claude Project Instructions Be?

There is no strict limit, but effective Project instructions typically run between 300 and 800 words. Long enough to cover voice, constraints, formats, and audience context. Short enough that every line earns its place. Instructions that exceed 1,000 words often contain duplicated context that belongs in uploaded documents instead.

What Is the Difference Between Claude Project Instructions and Custom Instructions?

Custom instructions in your user profile are global and apply to every conversation. Project instructions are scoped to a single Project and apply only to conversations within it. Put universal preferences in your profile and function-specific rules in Project instructions.

How Do I Set Up a Claude.md File for a Content Marketing Team?

A claude.md file is a local configuration file used in Claude Code that functions similarly to Project instructions. For a content marketing team, structure it with sections for brand voice, content standards, SEO requirements, formatting rules, and constraints. Include your style guide rules, keyword placement standards, internal linking requirements, and any patterns to avoid. The same principles that make Project instructions effective apply to Claude.md files.