How to use Claude Projects for marketing workflows

Projects that try to do everything do nothing well. The instructions get complex; outputs drift to generic.

Map your repeating workflows: long-form blog writing, ad copy generation, email sequence drafting, research synthesis, social post writing.

Build ONE Project per workflow. Each focused. Each great at one thing.

Example portfolio: "Blog Writing — [Brand Voice]," "Meta Ad Copy — [Brand Voice]," "Email Sequence Drafter — [Brand Voice]," "Research Synthesizer — [Industry]."

5-7 focused Projects > 1 mega-Project every time.

Log in at claude.ai.

In the left sidebar, click "Projects."

Click "+ New Project."

Name: specific and descriptive. "Blog Writing - EverestX Voice" not "Project 1."

Description (1-2 sentences): what this Project does. Helps you and your team identify quickly.

Choose default model: Sonnet 4.7 for most workflows, Opus 4.7 for complex reasoning tasks.

Click "Set custom instructions."

Write structured:

"You are a [role]. Your job is to [specific task].

Voice: [describe + reference examples in knowledge files]. Tone: [specific qualities].

Always: [list of rules]. Never: [list of banned patterns — generic AI words, marketing buzzwords, smooth transitions].

Workflow: When I ask for [X], do this exact process: [step 1, step 2, step 3]."

Example: "You are a Blog Writer for EverestX, a marketing agency placement platform. Voice: peer-to-peer, founder-honest, slightly contrarian, never marketing-speak. Always: write in first-person, include specific dollar examples, end with a clear next step. Never: use 'transform,' 'unlock,' 'leverage,' 'comprehensive,' 'innovative.' When I ask for a blog post, do: (1) generate outline first, (2) wait for my outline approval, (3) write section by section."

In the Project, click "Add to knowledge."

Upload 5-10 focused reference documents.

For content Projects: past best blog posts, style guide, persona research.

For ad copy Projects: top-performing ads, persona doc, competitive ads for tone reference.

For research Projects: industry reports, persona research, internal data.

Total knowledge: keep under 100MB. Smaller, focused files beat large catch-all files.

Update knowledge quarterly as your content/voice evolves.

In the Project, click "Start new chat."

Run a real prompt you would use in production. Example: "Write a 1,500-word blog post on [topic] for [audience]."

Audit the output: does the voice match? Does it follow the workflow you defined?

When it misses: iterate the Custom Instructions. "Add: 'Never use exclamation points.'" "Add: 'Always include 1-2 sentence fragments for rhythm.'"

Run 10-15 prompts before declaring the Project ready.

Outputs should be consistent — that is the whole point of Projects.

On Team/Enterprise: click "Share" on the Project.

Add team members by email or workspace.

Members can use the Project (read + send messages). Admins can edit instructions and knowledge.

Document the Project's purpose in a shared Notion/Confluence page so team knows which to use when.

For Pro plan: you cannot share Projects. Each user has their own.

Monthly review: open the Project, scan recent outputs. Where did voice drift? What instructions are being ignored?

Update Custom Instructions to address drift. "When asked for 'shorter,' default to 50% length, not 80%."

Refresh knowledge files quarterly. Add new best-performing content; remove outdated examples.

Track which Projects you use most. Build new Projects for emerging workflows; sunset Projects no longer needed.

Treat Projects as living infrastructure, not set-and-forget.