How to use Claude Projects for a small business

What you will be able to do

You will set up Claude Projects so each recurring shop job—quotes, SOPs, brand voice—has its own standing instructions and files, instead of re-explaining your business in every new chat.

What Projects are

Projects are workspaces inside Claude with their own chats, uploaded files, and project instructions. Free accounts can create a limited number of projects; paid plans expand capacity. Exact limits change—confirm in your account and on Anthropic’s pricing page.

In owner language: one folder per job, with the rules and reference files already loaded.

Why small shops need this

Without Projects, every chat starts empty. Someone pastes half a brand guide, forgets the cancel policy, and Claude invents a friendly discount. Projects reduce that hole by keeping the same instructions and source files next to the work.

Standing instructions worth writing once

Keep project instructions short and frozen:

• Who we are (one sentence) and who we are not
• Voice: clear, calm, local; no hype; no “as an AI”
• Never invent price, discount, timeline, or policy — mark gaps [NEED]
• Customer-facing drafts need a human send

Job-specific lines go in the matching project, not in a mega-prompt that tries to cover the whole company.

One project per job (start with three)

1. Quotes / proposals Upload: approved rate sheet or ranges you stand behind, scope boundaries, sample winning proposal (strip customer identifiers), cancel/deposit rules. Instruction: “Draft from these files only. Do not invent line items.”

2. SOPs / checklists Upload: current messy SOPs, safety stop-points you already enforce. Instruction: “Organize and tighten. Do not invent steps. Mark gaps [NEED].”

3. Brand voice / customer email Upload: three emails you actually sent that worked, a one-page voice note. Instruction: “Match length and directness of the examples. Facts come from the user message.”

Add more projects only when a fourth job keeps colliding with these three.

Files to put in — and leave out

Put in: approved policies, templates, anonymized examples, internal glossaries.

Leave out: card numbers, full charts, passwords, unrestricted employee folders, anything you would not put on a shared office drive. Projects are still Claude—see Is business data safe in Claude?.

Team sharing (Team / Enterprise)

On Team and Enterprise plans, projects can be shared with view or edit permissions so the floor uses the same knowledge base. Owners control org-wide sharing settings. Confirm current sharing options in Anthropic’s Projects help article before you roll this out.

Try this job: build the Quotes project in one sitting

1. Create a project named Quotes — [Your shop].
2. Provide standing instructions (voice + never invent price/policy).
3. Upload the smallest set of approved files that define scope and price.
4. Start a chat: “Draft a proposal section from these files for [job type]. Mark [NEED].”
5. Fill every [NEED], then ask for a tighten pass.
6. Save the final in your real proposal folder with a date—not only inside Claude.

Short close

Standing instructions plus the right files beat a clever one-off prompt—build one Project per recurring job.