Tutorial

12 min read Beginner

In This Guide

What is a Claude Project?

Most people use Claude the same way they use Google. They open it up, type a question, get an answer, and move on. Maybe they come back later and ask something else. But here's the problem: every time they come back, Claude has no idea who they are. It doesn't know about their business. It doesn't remember the pricing discussion from last Tuesday. It doesn't know they have two employees and a 90-day goal to hit $50k in monthly revenue.

So they get generic advice. The kind of thing you could find in any business blog. "Consider diversifying your revenue streams." Thanks. Very helpful.

A Claude project fixes this. Think of it as a room in your house. Your kitchen is set up for cooking. Your office is set up for work. You don't bring your filing cabinet into the kitchen. Each room has its own tools, its own purpose, and its own context.

A project is a container where you store three things:

Claude also builds up project memory automatically as you chat. Little things it picks up about your preferences, your business details, your working style. These get stored in the project and inform future conversations without you needing to repeat yourself.

Setting Up Your First Project

Creating a project takes about 30 seconds. Here's the process:

1. Open Claude and go to Projects
2. Click "New Project" in the upper right corner
3. Give it a name (e.g., "Business Strategy Room")
4. Add a short description of what you're trying to achieve
5. Click Create and you're in

The name and description are mostly for your own organization, but they do help Claude understand the context. Something like "Business Strategy Room" with a description of "Ongoing business strategy discussions to hit goals faster and maintain context around ideas" is plenty. Don't overthink it.

Once you create the project, you'll land in a workspace that looks similar to a regular Claude chat but with some important differences. On the right side, you'll see sections for Memory, Instructions, and Files. These are the three pillars that make projects powerful.

The Foundation: Your Business Overview Document

Before you write a single instruction or start chatting, upload a business overview document. This is the single most impactful thing you can do to improve Claude's output. Without it, Claude is guessing. With it, Claude is working from your actual data.

A good business overview covers seven sections. You don't need to write a novel for each one. A few bullet points per section is fine. What matters is that the information is specific and current.

That seventh section is the most important one. Claude is best when it's looking at a target it can actually see, not a target it can't see. "Increase monthly recurring revenue from $12,000 to $18,000 by adding 4 new group coaching clients" is a goal Claude can help you work toward. "Grow revenue" is not.

And here's something that might surprise you: Claude projects have a lot of storage capacity. You can upload up to 30MB per file, and the total project knowledge base is generous. In testing, 15 full YouTube video transcripts (each around 30 minutes of talking) only used about 10% of the available capacity. So don't hold back. SOPs, P&L statements, client onboarding procedures, content guidelines, legal documents, past strategies. If it's relevant, put it in.

Writing Project Instructions That Actually Work

Here's where most people either skip a step or do it badly. Project instructions are the single biggest factor in how Claude responds within a project. And yet, a lot of people leave them blank or write something vague like "Be helpful and professional."

That's not an instruction. That's a wish.

Good project instructions are usually 200 to 500 words. Much shorter and they're too vague. Much longer and Claude can start losing track of specifics during long conversations.

Two Layers of Instructions

You actually have two layers available:

• Personal instructions (in your account settings) that apply everywhere, across every conversation and project. Your name, general preferences, broad context about who you are.
• Project instructions that only apply within a specific project. This is where you customize Claude's behavior for a particular type of work.

Both layers work together. Personal instructions provide the baseline. Project instructions layer on top for specific contexts. So you don't need to repeat your name and preferences in every project.

Example: Business Strategy Room

Here's what good project instructions actually look like:

Notice what this does. It puts Claude in a specific role. It tells Claude to reference a specific uploaded file. It sets the tone: direct, challenging, data-driven. And it defines specific behaviors that change how every response in this project sounds.

The result? When you say "I think I want to completely do away with my one-on-one consulting today," Claude won't just nod along and agree. It'll come back with something like: "That's a $23,000 per month decision. Let me poke some holes in that. Your one-on-one consulting is 55% of your revenue. Those clients have a $6,000 lifetime value and the highest referral rate across your offers."

That's not generic advice. That's a strategic analysis based on your actual business data. And it happened because of a simple business overview document and a few lines of instructions.

Think of Your Project Like a Pyramid

Here's a mental model that makes everything click. A well-built Claude project has layers, and each one depends on the ones below it.

At the base, you have your files. This is the foundation. Your business overview, your SOPs, your analytics data, transcripts, whatever gives Claude raw material to work with. Without this layer, everything above it is weaker.

Next up is instructions. These tell Claude how to use those files, what role to play, and how to communicate. Instructions shape the behavior. Files provide the substance.

Above that, conversations and memory build over time. The more you use a project, the more Claude learns about your preferences, your decisions, and the context behind them. This layer grows organically.

At the top, outputs: the strategies, the content, the analyses, the decisions that come from having all of those lower layers working together. The quality of what comes out the top is directly proportional to how solid the layers beneath it are.

This is why the business overview document goes in nearly every project you create. Whether you're doing data analysis, creating content, or strategizing about your next quarter, Claude benefits from knowing who you are and what you're working toward.

Claude Desktop and Cowork: The Next Level

Everything we've covered so far works in Claude on the web. But there's a whole other level available through the Claude desktop app, specifically through a feature called Cowork.

The difference is this: Claude on the web is great for back-and-forth conversations. You talk, Claude responds, you refine. Claude Cowork, on the desktop app, is more task-focused. You tell Claude to do something, and it goes and does it. It can create files, save them to your computer, run research, and produce finished deliverables without you babysitting every step.

Setting Up a Cowork Project

On the desktop app, switch to the Cowork tab at the top. Click "New Project" and you'll get three options:

• Start from scratch, just like on the web
• Import a project from Claude web
• Use a folder on your computer as the project base

That third option is the interesting one. Since Cowork runs on your machine, it can read and write files directly to a folder on your computer. Choose where it lives: your Desktop, iCloud Drive, Google Drive, anywhere. Claude works from that folder, and anything it creates gets saved right there.

⏰ Scheduled Tasks

This is probably the most powerful Cowork feature. You can set up tasks that Claude runs automatically on a schedule. Have Claude check your email every morning and draft responses. Compile a weekly metrics report every Friday. Pull industry news daily at 8 AM. As long as your computer is on, the task runs in the background within your project, using all the context and instructions you've set up.

To set one up, type /schedule in any Cowork task, or use the "Scheduled" section in the sidebar. You can set tasks to run daily, weekly, biweekly, monthly, or on a custom cadence.

Connectors

Cowork supports connectors that let Claude interact with other apps and services. Gmail, Google Calendar, Slack, Notion, and dozens more. This means your scheduled tasks can pull data from and push data to the tools you already use.

Imagine a project called "Content Repurposing System" where you upload a YouTube transcript, tell Claude to create seven LinkedIn posts based on it, and walk away. Claude researches what makes a LinkedIn post perform well, extracts key themes from your transcript, writes the posts, checks them against your content guidelines, and saves everything to your computer. All in about 90 seconds.

That's not hypothetical. That's a real use case. And it's the kind of thing that takes 30-45 minutes manually.

Practical Project Ideas

You don't need to build all of these. Pick the one that would save you the most time this week and start there.

Common Mistakes to Avoid

After watching hundreds of people set up Claude projects, a few mistakes show up over and over again.

Getting Started Today

That first conversation will sell you on projects more than anything in this article. When Claude comes back with specific analysis based on your real numbers instead of "consider evaluating your pricing strategy," you'll understand why this matters.

The people getting the most out of AI right now aren't the ones using the fanciest prompts. They're the ones who set up the right context and let the tool do what it's built to do.