· readers
How to Set Up Claude for Your Small Business in One Afternoon

If you want Claude to actually help your small business, don't start by typing random questions into a blank chat. Set it up once: one project for each job you repeat, a short set of instructions that sounds like a first-day briefing, and a few real files it can work from. Then test it on last week's work before you trust it with this week's.
That's the whole method. Below I'll walk you through it step by step, in plain words, so you can get it done in an afternoon.
Why setup matters more than the tool
On Monday I wrote about ChatGPT vs Claude for small business. My answer there was simple: test both on your own work and keep the one that wins. If Claude won for you, this is the next step.
Here's what I see with owners all the time. They try an AI tool, ask it something vague, get a generic answer, and decide it isn't for them. The tool wasn't the problem. It just didn't know anything about their business.
Think of it like a new hire. If you hand a new front desk person a phone and say "be helpful," you'll get polite guesses. If you sit down for twenty minutes and explain your services, your rules and how you talk to customers, you get someone useful by lunch. Claude works the same way.
What you need before you start
You don't need anything technical. Grab these:
- A Claude account. Anthropic's help pages say Projects are available on free accounts too, with a limit of five projects on the free plan. That's plenty to start.
- One job you repeat every week. Customer emails, review replies, quote follow-ups or appointment reminders are good first picks.
- Three or four documents you already have: a list of your services, your most common customer questions with your usual answers, any policies (cancellations, warranties, refunds) and a few replies you've sent that you were happy with.
- An hour or two without the phone ringing.
If you don't have those documents written down, that's fine. Part of this afternoon is writing them, and honestly that alone is worth doing even if you never touch AI.
Step 1: Tell Claude about yourself once
Claude has a setting for instructions that apply to every conversation, not just one project. In Anthropic's current help pages it's under your initials in the lower left, then Settings. Menus move around, so if it looks different, look for "Instructions."
Keep this short. A few lines is enough:
- Who you are and what your business does
- Where you're located and who your customers usually are
- How you like answers (short, plain English, no jargon)
- One rule for everything: if you're not sure, ask me instead of guessing
That last line matters most. It's the difference between a tool that makes things up and one that checks with you first.
Step 2: Create one project per job
A project is a workspace inside Claude that keeps its own instructions and files. Every chat you start inside it uses that same setup, so you're not explaining your business from scratch every time.
The mistake I see is one giant project called "Business" with everything thrown in. Don't do that. Make one project per job instead:
- Customer emails
- Review replies
- Quote follow-ups
- Social posts
Name each one after the job. One thing to know: Anthropic says Claude can't see the project name or description. Those are labels for you. Anything Claude needs to know goes in the instructions or the files.
Start with just one project. Get it working, then add the next.
Step 3: Write project instructions like a first-day briefing
Inside the project, there's an option to set project instructions. These only apply to chats in that project. Write them the way you'd brief a new employee on day one. Not "be professional." Real details.
Here's a simple template you can copy and fill in:
- Who we are: "You help [business name], a [type of business] in [town], reply to customer emails."
- Who our customers are: "Mostly [homeowners, parents, local businesses]. Many are busy and reading on their phone."
- How we sound: "Friendly, short and direct. Plain English. Sign off as [your name]."
- What you never do: "Never confirm a date, time or price that isn't in our files. Never promise a refund. Never make up a policy."
- When you're unsure: "If the files don't answer it, say so and flag it for me."
That's it. Five short sections. You can always add more later when you see what it gets wrong.
Step 4: Add the files Claude should work from
Each project has a knowledge area where you upload documents. Claude uses those files across every chat in the project. This is how it answers from your real information instead of guessing.
A good starter set for most small businesses:
- Services list. What you offer, in plain words. Current info only, so delete old versions.
- Common questions. The ten questions customers ask most, with the answers you usually give.
- Policies. Cancellations, warranties, refunds, service area, hours.
- Good examples. Three to five real replies you've sent that you liked. Take out names, phone numbers and addresses first.
One detail that trips people up: Anthropic's help page on projects says chats inside a project don't share memory with each other. If you explain something once in a chat and want Claude to remember it next time, add it to the project files or instructions.
Step 5: Test it on last week's work
Before you use it on anything live, test it on work you've already done. Open a new chat inside the project and paste in five real customer messages from last week, with personal details removed.
Then check every answer:
- Is every fact right? Hours, services, policies.
- Did it stay inside your rules, or did it promise something it shouldn't?
- Does it sound like you, or like a brochure?
- Would you send it with a quick edit, or would you rewrite it?
When an answer is off, don't just fix that one reply. Fix the instructions or the file that caused it. That's how the setup gets better every week instead of making the same mistake over and over.
Step 6: Make it part of your week
Once it passes the test, use it on real work, but keep yourself in the loop:
- Claude drafts, you read, you send. Nothing goes to a customer without your eyes on it.
- Keep a short note of anything it gets wrong. Once a week, spend ten minutes updating the files.
- After the first project feels easy, add the second job.
If your team needs to use it too, Anthropic's help page says Team and Enterprise plans can share projects inside the organization. Keep one person in charge of the files so your price list or policies don't drift.
Mistakes to avoid
A few things I'd steer you away from:
- Pasting sensitive information. Don't paste customer card numbers, health details or anything you wouldn't want stored somewhere outside your business. Check your industry's rules before you share client data with any AI tool.
- Vague instructions. "Be helpful" gives you generic answers. Specific rules give you useful drafts.
- Old files. If last year's service list is still in there, Claude may use it. Keep one current version.
- Skipping the test. Ten minutes of testing saves you from an awkward email to a customer.
- Trying to set up everything at once. One job, done well, beats five half-built projects.
If you want more ideas for that first job, my post on how to start using AI in a small business walks through picking one, and using AI for customer emails goes deeper on that job specifically.
FAQ
Do I need a paid plan to set up Claude for my business?
Not to start. Anthropic's help pages say Projects work on free accounts, with up to five projects. Try it free on one job before deciding if you need more.
How long does setup take?
For one job, an afternoon is realistic if you already have your services list and common questions written down. If you're writing those from scratch, give yourself a little longer.
Will Claude remember things between chats?
Inside a project, it uses the instructions and files you added every time. Anthropic says chats don't share context with each other unless the information is in the project knowledge, so put anything important in the files.
Is it safe to upload my business documents?
Upload what you'd be comfortable sharing with an outside service: services, policies, FAQs, sample replies with personal details removed. Leave out payment info, health details and anything your industry restricts.
What's the best first job to set up?
The one you repeat most and dread the most. For a lot of owners that's customer emails or review replies.
Want help setting it up?
If you'd rather walk through this with someone, that's what Mugen Solutions does. I run a free workshop for small business owners on putting AI to work in practical ways, and I'm always happy to just chat about where it fits in your business. Reach out here.
Bookmark this, you'll want to come back to it the next time you add a new job.