Claude Projects: Your Persistent Brand Voice Assistant per Client

What This Builds

Instead of re-explaining your client's brand, audience, and style rules at the start of every Claude conversation, you'll build a Claude Project for each client that holds all of that context permanently. Every conversation you start inside that Project begins with Claude already knowing who the client is, who their audience is, what tone to use, and what to avoid — like having a dedicated AI assistant for each account.

Prerequisites

• Claude Pro account at claude.ai ($20/month) — Projects require Pro
• 30–45 minutes to set up each client Project
• Client's brand voice guide, style guide, or at least 3–5 examples of approved copy
• A list of 5–10 pieces of reference content (past blog posts, landing pages, brand guidelines)

The Concept

A Claude Project is a persistent workspace where you upload reference documents and write custom system instructions. Think of it like onboarding a new employee who has read your entire brand handbook before their first day of work. Every conversation you start in that Project, Claude has already "read" everything you uploaded and is operating from those instructions.

Without a Project, every conversation starts from zero — you have to re-explain the client, re-explain the voice, re-paste the brief, every single time. With a Project, that onboarding is done once and lasts indefinitely.

Build It Step by Step

Part 1: Create the Project and upload reference materials

Step 1: Log into claude.ai → click "Projects" in the left sidebar → "New Project"

Step 2: Name the Project: "[Client Name] — [Your Role/Focus]" (e.g., "TechFlow — Marketing Copy")

Step 3: Upload reference documents. Click "Add content" in the Project panel. Upload or paste:

• Brand voice guide (PDF or paste as text)
• Style guide (if separate from brand guide)
• 3–5 examples of the best approved copy (paste in as a doc titled "Approved Copy Examples")
• Audience persona document (if one exists)
• Product/service one-pager or overview

What you should see: Files and documents listed in the Project's knowledge panel on the left side.

Part 2: Write the Project Instructions

This is the most important step. Click "Edit Project Instructions" (or the settings icon for the Project). This is Claude's permanent system prompt for all conversations in this Project.

Use this template (fill in with your client's real details):

You are an AI writing assistant for [Client Name], a [brief company description].

YOUR ROLE: Help me write, edit, and improve marketing copy for this client. Everything you write should sound like it came from a human copywriter who deeply knows this brand — not from an AI.

ABOUT THE CLIENT:
[Client Name] is [1-2 sentence description]. They sell to [audience description]. Their positioning: [key differentiator in 1 sentence].

BRAND VOICE:
Tone: [3-5 adjectives]
Write like: [analogy, e.g., "a knowledgeable colleague explaining something clearly, not a salesperson"]
NEVER sound: [what to avoid, e.g., "corporate, hyped, jargon-heavy"]

VOCABULARY RULES:
Always use: [word A], [word B], [phrase]
Never use: [jargon word 1], [jargon word 2], [list banned words/phrases]
Preferred phrases: [examples of their actual phrasing]

TARGET AUDIENCE:
[2-3 sentence description of the reader — role, industry, what they care about, their skepticism level]

CONTENT STANDARDS:
- Sentence length: [e.g., "Short to medium — max 20 words. Break up long sentences."]
- Paragraphs: [e.g., "Short — 2-4 sentences. Never 7+ sentence paragraphs."]
- Active voice: [e.g., "Always. Flag any passive constructions."]
- CTA style: [e.g., "Specific and direct — 'Start your free trial' not 'Learn more'"]

THINGS TO FLAG:
If my draft has [specific issues], flag them before rewriting.

When I start a new task, confirm you're working in [Client Name]'s voice before proceeding.

Click Save.

Part 3: Test and Refine

Start a new conversation inside the Project (click "New Chat" while inside the Project). Give Claude a simple test task: "Write a 100-word product description for [product] in our brand voice."

Check the output against 3 criteria:

1. Does it sound like the approved copy examples you uploaded?
2. Does it avoid the banned words?
3. Does it feel like the right reading level for the audience?

If any criterion fails, return to the Project Instructions and be more specific. The most common fix: add more "Approved Copy Examples" content (the more real copy Claude has seen, the better it mimics the voice) and add more specific banned vocabulary.

Real Example: TechFlow B2B Brand Assistant

Setup: TechFlow is a workflow automation tool for operations teams at mid-size companies.

Project Instructions excerpt:

Brand voice: Direct, practical, collegial. Like a smart colleague, not a vendor.
Never sound: Hyped, buzzword-heavy, or like a features-first product sheet.
Always write to: An operations director who has seen 50 software demos and is skeptical of every claim.
Vocabulary: "connects" not "integrates," "your team" not "users," "simple" not "seamless."
Never use: leverage, synergize, robust, powerful solution, game-changing, cutting-edge.

Reference documents uploaded:

• TechFlow Brand Guidelines PDF
• 5 approved blog posts (pasted as text)
• Buyer persona document

Input: Starting a new chat inside the TechFlow Project → "Write a landing page hero section for the new Onboarding Module."

Output: "New hires, ready on Day 1. TechFlow automates the onboarding checklist so your HR team spends less time on paperwork and more time on people. Setup takes 20 minutes. No IT required."

Time saved: 25 minutes of re-explaining context on every session, multiplied by 3–4 sessions per week = 1–2 hours per week per active client.

What to Do When It Breaks

Problem: Claude sounds generic and ignores the voice instructions → Add more example content to the Project knowledge base (paste 3 more approved pieces) and make the vocabulary rules more explicit with examples

Problem: Claude keeps using banned words → Add to instructions: "CRITICAL VOCABULARY RULE: Never use [word]. If you catch yourself using it, stop and rewrite that sentence. This is non-negotiable."

Problem: The voice is right but the content structure is wrong → Add structural rules to the instructions: "Blog posts always start with a [question/statistic/pain point]. Never open with 'In today's world...' or 'As [role], you know...'"

Problem: Claude lost the context mid-conversation → Claude Projects maintain context better than regular conversations, but very long conversations (100,000+ tokens) can lose early context. Start a new conversation within the Project for each major project.

Variations

Simpler version: Use Claude's "Customize Claude" (non-Project memory feature) for a single primary client, avoiding the Project setup entirely. Less organized but faster to start.

Extended version: Create a Project subfolder structure per client: separate knowledge docs for "Blog voice," "Email voice," and "Ad copy voice" — each content type has slightly different rules.

What to Do Next

• This week: Set up one Claude Project for your highest-volume client and run all their work through it for a week
• This month: Set up Projects for your top 3 clients; measure reduction in revision requests
• Advanced: Add a "Content Critique" instruction: "Before writing anything, ask me: what's the target keyword and the single goal of this piece?" — builds better briefs automatically

Advanced guide for copywriter professionals. These techniques use more sophisticated AI features that may require paid subscriptions.