Claude Projects.

Claude has no idea who you are.

Every time you open a new chat, it starts fresh. No memory of your business. No memory of what you're building. No memory of the conversation you had yesterday that took 45 minutes to get right.

Projects fix this.

Not in a complicated way. You create a workspace, upload a few documents about your business, write some instructions on how you want Claude to behave,1 and from that point on, every conversation inside that project starts with all of that context already loaded.

That's really it.

Simple: if you need Claude to show up differently for a specific type of work, create a project.

Asking for restaurant recommendations? No project needed. Strategizing about your business, creating content, analyzing data, managing client work, anything where you want Claude to actually know your context and produce specific, tailored results, that needs a project.

Think of each project as a dedicated room. One for business strategy. One for content creation. One for client work. One for data analysis. When you walk into each room, everything relevant is already there.

Before building anything, understand the hierarchy.

Files, the foundation. Everything Claude needs to know. SOPs, business documents, analytics, transcripts, legal documents, anything with information Claude should always have access to. Without files, Claude has nothing to work from. Everything else in the project sits on top of this.

Instructions, the behavior layer. How Claude should act, respond, and think inside this project. What format it should use. What it should always reference. What it should challenge versus accept. This goes on top of the files.

Memory + automations, the active layer. What Claude has learned about you over time within the project. Scheduled tasks. Prompts that run automatically. The intelligence that builds as you use it.

Build from the bottom up. Files first. Then instructions. Then automation.

In Claude, go to the Projects section. Click New Project.

Give it a name that describes the type of work, "Business Strategy," "Content Repurposing," "Client Research," whatever it is. Add a short description of what you're trying to achieve. This is just for your own organization, it doesn't affect how Claude behaves.

Create the project. You now have a dedicated workspace.

Quick tip: Star the projects you use most. They pin to the top of your sidebar. The ones you're in every day should be immediately accessible.

The single most valuable document you can give Claude is a business overview.

Not because it's complicated, because it's foundational. Every output Claude gives you is only as specific as the context it has about you. Generic context produces generic advice. Specific context produces advice that's actually useful.

Here's what a business overview should include:

Company identity: Who do you help? What do you do? One-sentence description. How long have you been in business?

Revenue model: What are your offers? What do you charge? What's your pricing structure?

Offer stack: Each offer explained in depth. What's included, what it costs, who it's for.

Team and operations: Who's on your team? What does each person do? How many hours? What are the key processes?

Market position: How are you different from competitors? Why do clients choose you?

Growth profile: How are you acquiring customers right now? What channels are working?

90-day priorities: This is the most important section. What are you trying to accomplish right now? Claude is best when it can see a specific target. Give it your actual goals, not vague ambitions.

Upload this to every project. Even if the project is about content creation or data analysis, having Claude understand your business context means it can flag when advice doesn't align with your actual goals.

Become a paying subscriber to get access to this post and all other premium content.