You've been chatting with Claude for a couple of months. You like it, you use it for emails and the occasional rewrite, and then every single time you open a new chat you have to explain who you are, what your business does, who you sell to, and what your voice sounds like all over again. And then halfway through the conversation Claude forgets and starts writing like a HubSpot intern. I know. I did the same thing for almost a full year before I figured out what a Claude Project actually is, and once I did my whole AI life changed.
So I want to walk you through setting up your first one. Not the influencer version with 47 screenshots and a paid template. The version a normal business owner can do in about 90 minutes one Saturday morning.
What a Claude Project actually is (in plain English)
A Project is a dedicated workspace inside Claude where you upload reference files once, write a set of standing instructions once, and then every conversation you start inside that workspace already knows who you are. Think of it like hiring a new assistant and giving them a binder on day one instead of explaining the business from scratch every Monday.
Three things make a Project different from a regular chat:
You upload files that Claude can reference across every conversation inside that Project. You write custom instructions that load at the start of every conversation. And the conversations you have inside the Project stay grouped together, so you can come back to that one rewrite you did three weeks ago without scrolling through 400 random chats.
That last part sounds boring and it's actually the thing that saves the most time once you get used to it.
Why Projects beat just chatting
When you chat with Claude in a fresh window, you're talking to a brilliant generalist who knows nothing about you. You spend the first ten messages getting Claude up to speed on your business, your tone, and what you actually want, and by the time the answer starts coming back, you're already tired.
A Project skips that whole opening act. You walk in, Claude already has your brand brain, your ideal client doc, and your voice rules loaded, and you start with the actual work. I'd estimate a good Project saves me 15 to 20 minutes per session because I'm not re-explaining anything. Across a week that's hours.
The other thing nobody mentions: Claude tends to write better when it has context. Not slightly better. A lot better. A Claude with no context will hedge, generalize, and use the corporate words you hate. A Claude with your brand brain loaded sounds closer to you, because it has examples to pattern-match against.
The 3 files to upload first
Don't try to load 50 documents on day one. Pick three, get them right, and add more later as you find gaps.
File 1: The Brand Brain
This is one document, ideally 4 to 8 pages, that captures the spine of your business. Who you are, who you serve, what you sell, what you charge, your top three offers, your most common objections, your origin story in 3 paragraphs, and the words you use for the things in your world. If you call your audience "agents and lenders" don't let Claude default to "real estate professionals." That's what the brand brain is for.
Build this in Google Docs first. Save it as a PDF. Upload it.
File 2: The Ideal Client Doc
A separate document because it gets edited more often. Who is the person you want to attract. Their pain points in their own words, not yours. The phrases they use when they describe their problem to a friend at dinner. The objections they have before they buy. The transformation they want. The transformation they actually need (sometimes different). What they've tried before and why it didn't work.
I keep mine to 3 pages. Anything longer and Claude starts averaging across too many archetypes.
File 3: The Voice Rules
This is the file most people skip and it's the one that does the heaviest lifting. A voice rules doc lists the words you will never use, the words you do use, the sentence patterns you avoid, the formatting tics you have, and 4 to 6 paragraphs of writing you've personally written that you're happy with. Claude uses those samples to triangulate your voice. Without them, you get the default Claude voice with a polite hat on.
If you want to skip ahead, I've got a full piece coming on building a brand voice Skill, which is the next step after a voice rules file. Same idea, more portable.
The custom instructions to write
Inside the Project you'll see a field for custom instructions. This is where most people leave it blank. Don't.
Write something like this in plain English:
"You are working inside the [Your Business] Project. Your job is to help me write, plan, and think out loud about my business. Always reference the brand brain, ideal client doc, and voice rules when generating any client-facing copy. Match my voice, not yours. When in doubt, ask before generating. Use contractions, vary sentence lengths, and no em-dashes. If you're about to use a corporate word like 'use' or 'use,' rewrite it before showing me. Default to specific examples and named clients, not generic advice."
Adjust to taste. The whole instruction block should be maybe 200 to 400 words. Long enough to be useful, short enough that Claude can actually hold it all in working context.
The "this is for my business" scaffold
Once the files are in and the instructions are written, start your first conversation with what I call the scaffold prompt. Something like, "Read the brand brain and the ideal client doc. Summarize back to me in 5 bullets who this business is, who it serves, and what kind of voice I want. I want to confirm you've understood before I ask you to write anything."
Claude will summarize. You'll find things that are wrong or weak. Fix the source docs, re-upload, summarize again. Two rounds of this and your Project is calibrated. I cannot stress this enough: spending an extra 20 minutes on calibration day saves you weeks of fixing bad output later.
Pattern interrupt. The number one mistake I see people make at this stage is going straight from setup into "write me 10 LinkedIn posts." Don't. Have one conversation about your business with Claude where you don't ask for output. Just talk. See if the responses sound like someone who knows you. If yes, you're calibrated. If no, the docs need work.
What to do once the first Project is humming
You're going to want to make more. Resist for two weeks. Use this one Project for everything, and watch where it breaks. Maybe it's bad at writing emails specifically, maybe it loses voice on long-form, maybe it doesn't know your podcast guests. Those gaps tell you what your second Project should be (for me it was a content Project separate from a sales Project), and what additional files to add to your knowledge base.
If you want the bigger system this Project sits inside, including the Skills layer that makes your voice portable across every Project, that's what I teach inside Level Up. Same setup we use internally on my team, end to end, no fluff.