How Do I Build My First Claude Project That Actually Knows My Business?

I spent about six months using Claude as a smart notepad. Every new chat, I'd paste my company description, my voice guide, my current offer, my latest case studies. Every. Single. Chat. Then I discovered Claude Projects and felt like an idiot. One afternoon of setup replaced roughly a hundred copy-paste rituals and — more importantly — gave me a Claude that sounds like my business, not like a well-meaning intern who just walked in.

This is the walkthrough I wish I'd had. Twenty-five minutes, start to finish, and you come out with a Claude that actually knows what you do, who you talk to, and how you want to sound.

Why this matters

Claude Projects are persistent workspaces inside Claude.ai. Each Project gets its own custom instructions (what Claude should always know about you), its own knowledge base (files it can reference in every chat), and its own chat history (separate from your other work).

Without Projects, Claude is a brilliant contractor you hire fresh every morning. With Projects, Claude is a staffer who already knows the playbook.

For consultants, solopreneurs, and small teams, the ROI shows up inside a week. You stop re-briefing. You stop drifting off-voice. You stop explaining the offer. Good Claude work becomes the default instead of the exception.

Before you start

You need:

• A Claude.ai account. Free works; Pro is better because Projects on the free plan cap knowledge-base size tight. Pro is $20/month.
• About 25 minutes. Ten of that is gathering files you already have.
• Three things to have in front of you: your brand voice guide (or a sample of writing in your voice), your current offer or services list, and two or three of your best case studies or testimonials.

If you don't have a brand voice guide, that's fine. I'll show you how to generate one from sample writing in Step 2.

Step 1: Create the Project

Sign into claude.ai. In the left sidebar, click Projects. Top right, click Create Project.

Name it something you'll use daily — Elite AI Advantage or Acme Marketing — not Test or Claude Project 1. The name shows up in your sidebar and the URL.

Add a short description. One line. "Brand content, client work, and SEO for Acme Marketing." This isn't just UI cosmetics — Claude reads this description when it picks up context in a new chat.

Step 2: Write custom instructions that survive model updates

Click Edit system prompt (sometimes labeled Custom instructions depending on the Claude UI version). This is the single most important field in the whole Project.

Don't paste a marketing bio. Write instructions for Claude. Here's the template I use, with my own values swapped in:

Three things to notice. First, this is written TO Claude, not ABOUT my business. Second, it's rules and examples, not adjectives. Third, that last line — "push back if I'm wrong" — is the single most valuable sentence in there. Claude's default mode is agreement. You have to explicitly permit disagreement.

Hit save.

Step 3: Upload the knowledge base

Scroll to the Knowledge or Project files section. This is where you park reference material Claude can cite in any chat.

Upload three things to start:

1. Your voice guide — a one-page doc with your tone rules, five example paragraphs of your best writing, and five phrases you'd never use.
2. Your current offer / services sheet — a plain-language summary of what you sell, who it's for, what it costs, and what's in vs. out of scope.
3. Two or three case studies — the actual write-ups, not the one-line bullet versions.

That's it for v1. Resist the urge to upload every file you've ever written. A tight, well-curated knowledge base beats a dump. Claude's retrieval degrades on bloat — 10 surgical files outperform 100 dumped files, every time.

Don't have a voice guide? Upload a folder of your best emails, blog posts, or sales pages and ask Claude (inside the Project, once it's saved):

Save what it produces as VOICE.md and upload it back to the knowledge base. Now Claude has a formal voice reference instead of having to re-learn from raw samples every time.

Step 4: Test the Project with a real task

New chat inside the Project. Ask something that would have gotten a generic answer before:

Read the output. Does it sound like you? Does it cite the audience size you defined? Does it avoid hype words?

If anything's off, fix it in the custom instructions — don't fix it in the chat and move on. That drift is exactly what you set up the Project to prevent.

Good first edit signals:

• Voice too formal? Add "Write like you're talking to a single person at a bar, not a room of 100" to instructions.
• Too agreeable? Strengthen the "push back" rule with "If my premise is wrong, say so in the first sentence."
• Ignoring your offer? Add "Every content draft should tie back to one of our three services (AI tools, SEO, automation) when it naturally fits."

Iterate on the instructions. Re-test. Two or three rounds and it's locked in.

Step 5: Share it with your team (if you have one)

If you're on Claude Team or Enterprise, the Share button lets you invite teammates into the Project. Their chats are separate, but the custom instructions and knowledge base are shared.

This is the single best onboarding artifact you can hand a new hire. "Here's the Project. Run your work through it. Ask Claude any business question before you ask me."

Verify it worked

Three quick tests:

1. Voice test. Ask Claude to rewrite a generic paragraph "in our voice." Does it match?
2. Offer test. Ask "what do we sell?" and check the answer matches your offer sheet exactly.
3. Knowledge test. Ask "which of our case studies is most relevant for a SaaS client doing SEO?" — does it reference the actual case studies you uploaded, or does it hallucinate?

If all three pass, the Project is working.

Where this breaks

• Uploading a 50MB PDF. Projects have a knowledge-base size cap. A big PDF can eat the whole budget and push out the files that actually matter. Convert PDFs to Markdown first (or upload the Markdown source if you have it), and split long files into focused chunks.
• Custom instructions that are biography, not rules. "We're a leading agency founded in 2018 specializing in…" is useless. Claude already has your website. Rules that are actionable — "always cite sources, never use the word 'leverage'" — are what move the needle.
• Treating the Project as read-only. Revisit it monthly. Offers change, voice evolves, case studies get added. If your Project matches the business you ran a year ago, it's drifting you backwards.
• Using one giant Project for everything. One per distinct client or domain. Mixing "my SaaS product" and "my freelance copywriting" into one Project produces schizophrenic output. Split them.
• Relying on Projects alone for security. Project chats aren't private from Anthropic under the default data-retention settings. Flip on the "do not train on this data" toggle in Settings → Privacy if you handle anything sensitive.

What to try next

• Read How Do I Set Up Claude Code on macOS Without Breaking My Shell Config? — Projects live in the browser; Claude Code lives in your terminal, and the two together are where the real productivity lives.
• Browse the blog for specific ways to use Projects (content ops, sales enablement, research workflows).
• Want this set up for you, tuned to your voice, with knowledge-base files generated from your existing content? Let's talk.