The short version
- Start on a paid plan (Pro for one person, Team for several), install the Claude desktop app and use its Code tab. No terminal needed.
- Make one business folder with a simple structure, then write a CLAUDE.md brain file covering your services, prices, tone, clients and processes.
- Turn your most repeated job into a skill first, then connect one or two tools such as Gmail, Outlook or Google Drive.
- Keep permissions on Manual while you learn, and make sure anything that leaves the business needs a human yes.
- Roll out to a team only once one person has a setup that works, and share it through the folder rather than through habits.
Most owners who try Claude Code have the same first week. A couple of impressive moments, a few odd results, and a nagging feeling that it would be brilliant if only it knew how your business actually works. That feeling is right, and it's a setup problem rather than a Claude problem. To set up Claude Code for a business, pick a paid Claude plan, install the desktop app, give it one well organised folder, and write a CLAUDE.md file that tells it what you sell, how you work and how you sound.
This guide takes you through each step in order, with the choices we make when we set it up for clients. If you're not sure what Claude Code is yet, start with what is Claude Code and come back.
Step 1: Choose a plan and install Claude Code
Pick a paid plan, then install the Claude desktop app and use its Code tab. That covers most businesses.
Choose the right Claude plan
Claude Code is included on every paid Claude plan but not on the Free one, so the decision is really about how many people will use it and how heavily.
| Plan | Best for | Rough cost |
|---|---|---|
| Pro | One person trying it out or using it a few times a day | About $20 a month (roughly £18 before VAT) |
| Max | One person using it most of the day | From $100 a month |
| Team | Several people, with central billing and admin controls | Per seat, standard and premium seats |
| Enterprise | Larger organisations with stricter controls | On application |
Prices change and exclude VAT, so check claude.com/pricing before you buy. Our advice: start one person on Pro or Max, get a setup that works, then move to Team when others join. Team also matters for connectors, because on Team and Enterprise an admin controls which ones are switched on.
Install Claude Code
For most business users, the easiest route is the Claude desktop app. It includes Claude Code, so there's nothing else to install.
- Download the Claude app for Mac or Windows from claude.com.
- Install it, open it and sign in with your paid account.
- Click the Code tab.
- Choose the folder you want Claude to work in (we'll create that in the next step).
If you or someone on the team is comfortable with a terminal, the command line version is the most fully featured. Anthropic's recommended method is a one line native installer for Mac, Linux and Windows that keeps itself up to date. The exact command is on the official Claude Code overview page; copy it from there rather than from a blog post, as it does change. There are also extensions for VS Code and JetBrains, and a web version at claude.ai/code for running tasks in the cloud.
Everything you set up below works across all of these, because they share the same engine and read the same files.
Step 2: Create a project folder for the business
Claude Code works inside a folder, and it sees what's in that folder. So the folder is the foundation. Keep it simple and predictable. A structure that works for most service businesses:
- CLAUDE.md at the top level (the brain file, next step)
- clients, with one subfolder per client for notes, proposals and reports
- templates, for your proposal, report and email templates
- reference, for price lists, service descriptions, case studies and your tone of voice notes
- outputs, or a drafts folder, where finished work lands for you to check
Copy in a handful of your best real examples: two or three proposals you were proud of, a good client report, a few emails that sound like you. Claude learns your standard far faster from examples than from description.
Keep it clean. Don't point Claude Code at your whole drive or a shared folder with years of clutter. It'll read old price lists and outdated templates and use them. A smaller, tidy folder gives better work.
Step 3: Write your CLAUDE.md brain file
CLAUDE.md is a plain text file that Claude reads at the start of every session. It's the single biggest factor in how useful Claude Code is for your business. Write it the way you'd brief a sharp new starter on their first morning.
You can ask Claude to draft one for you from what's in your folder, and in the terminal version the /init command does exactly that. Treat that as a first draft. The parts that make the difference only you know.
Anthropic recommends keeping each CLAUDE.md under about 200 lines, because longer files are followed less reliably. Put detail in separate files in your reference folder and point to them. A good outline for a small business:
- About us. What the business does, who for, where, and how many people.
- Services and prices. Each service in a line or two, with the price or price range, and what's included.
- Ideal clients. Who you work with, who you turn away, and the problems you solve for them.
- Tone of voice. How you write: British English, formal or friendly, words you never use, sign off style. Point to example emails.
- Key clients. A short list of current clients with one line each, and where their folders are.
- Processes. How enquiries become quotes, how projects start, how you report. Name the skill for each.
- File rules. Where things are saved, how files are named, and which format you want finished documents in.
- Hard rules. The things it must never do, such as send anything without your approval, change prices, or contact a client directly.
Claude Code also keeps its own notes as it works, picking up your corrections and preferences. Those are useful, but your CLAUDE.md should hold anything that really matters, because that's the part you control.
Step 4: Add your first skills
A skill is a saved set of instructions for one repeatable job. It's a folder containing a SKILL.md file with a short description at the top and step by step instructions underneath. Claude reads the descriptions of all your skills, and loads the full instructions only when a request matches. You can also run one directly by typing a slash and its name, such as /quote.
Skills for a project live in a .claude/skills folder inside your business folder, so they travel with the folder and everyone who opens it gets them. Personal skills can live in your own user folder instead.
Start with the job you do most often. Good first candidates:
- Turning an enquiry into a quote or proposal
- Writing the monthly client report from exported figures
- Turning call notes into a follow up email and a task list
- Preparing a weekly summary of what's outstanding
The simplest way to write one is to ask Claude to help. Explain how you do the job, show it a good example, and ask it to save that as a skill. Then use it for a week and fix whatever it gets wrong. Our guide to Claude skills goes into more detail.
Step 5: Connect your tools
Connectors let Claude Code work with your other systems. They're built on MCP, the open standard for linking AI tools to data, which we explain in what is MCP. In the desktop app you add them with the plus button next to the prompt box, or through the Plugins section in the sidebar, and you manage or disconnect them under Customize.
The ones most small businesses connect first:
- Email. Gmail through the Google Workspace connectors, or Outlook through the Microsoft 365 connector. Useful for triage, finding past conversations and drafting replies.
- Files. Google Drive, or OneDrive and SharePoint through Microsoft 365, so Claude can find documents that don't live in your business folder.
- Calendar. For meeting prep and weekly planning.
- Slack or Teams, for summaries and messages.
- Your CRM. Many CRMs now offer a connector or an MCP server. Check the connector directory, or ask your CRM provider.
Add one at a time and test it before adding the next. The Microsoft 365 connector is read only by default and needs write tools switched on before it can send or change anything. On Team and Enterprise plans an organisation owner has to enable connectors first, and Microsoft 365 also needs a one time approval from your Microsoft administrator.
Step 6: Set permissions and safety rules
Claude Code asks before acting unless you tell it otherwise. In the desktop app the permission mode selector sits under the prompt box, and you can change it at any time.
- Manual asks before every file edit or command. Use this for the first few weeks.
- Accept edits lets file changes through without asking but still checks other commands. Fine once you trust a particular workflow.
- Plan has Claude explore and propose a plan without changing anything. Good for bigger jobs: agree the plan, then switch mode to carry it out.
- Auto, where available, runs without routine prompts while a background check reviews each action against your request.
Avoid the mode that bypasses permissions altogether. Anthropic suggests it only for isolated test setups, and on Team and Enterprise plans your organisation's policy controls it anyway.
Beyond modes, a few rules we always put in place:
- Anything that leaves the business (emails, posts, invoices, payments) needs a human yes, written as a hard rule in CLAUDE.md and backed by connector approvals.
- Sensitive material such as payroll, HR files and personal data you don't need stays outside the working folder.
- You check the data terms for your plan and follow the ICO's guidance on AI and personal data.
Remember. CLAUDE.md instructions are guidance Claude follows, not a lock. For something that must never happen, use permissions and connector settings too.
Step 7: Get finished work out as Word or PDF
Claude Code naturally writes in plain text and Markdown, which is fine for notes but not what a client expects. Add a rule to your CLAUDE.md saying which format finished documents should be in, and where they go. Claude can create Word documents and PDFs, usually by writing and running a small conversion script for you, and there are document skills and plugins that make it more reliable.
In our own setup, every proposal, report and plan is written as Markdown first, then converted automatically to a Word document in a named folder. Nobody copies and pastes anything. If you use a branded template, keep a copy in your templates folder and tell Claude to use it.
Step 8: Roll it out to your team
Get one person's setup working well before anyone else joins. Then share the folder, not the habits. Because CLAUDE.md, skills and project settings live in the business folder, everyone who works from it gets the same brain file and the same processes.
- Move to a Team plan so billing, seats and connector controls sit in one place.
- Keep the shared folder in a place everyone can sync, and agree who is allowed to edit CLAUDE.md and the skills.
- Let people add personal preferences in their own user level CLAUDE.md, so the shared one stays clean.
- Run a short session showing three or four real jobs end to end. People copy what they see work.
- Write a one page policy: what Claude Code is used for, what it must not touch, and who checks what.
Common mistakes to avoid
Most setups that disappoint fail in the same few ways.
- A vague brain file. "We're a friendly agency" tells Claude nothing. Prices, examples and rules do.
- A CLAUDE.md that grows forever. Past a couple of hundred lines it gets followed less well. Move detail into reference files and skills.
- Pointing it at a messy drive. Old templates and outdated prices end up in new work.
- Connecting everything on day one. Add tools one at a time and test each.
- Switching off permissions too early. Earn trust workflow by workflow.
- Not fixing skills. When an output is wrong, update the skill or the brain file, not just that one document. Otherwise you'll fix the same thing next week.
- Rolling out before it works. A team that sees a clumsy first version rarely comes back to it.
If you'd rather have it done for you, this is exactly what our Claude Workspace service does: we build the folder, the brain file, the first skills and the connectors around how your business already runs, then train your team on it. Either way, the steps above are the same ones we follow, and you can do them yourself with a bit of patience.
Questions people ask
How long does it take to set up Claude Code for a business?
You can install it and run a first task in under an hour. A properly useful setup, with a good brain file, a few skills and connected tools, usually takes a few days of part time work spread over a couple of weeks, because you refine it as you use it.
Which Claude plan do I need for Claude Code?
Any paid plan includes Claude Code: Pro, Max, Team or Enterprise. Pro suits one person trying it out, Max suits heavy daily use, and Team suits businesses with several users who want central billing and admin controls. The Free plan doesn't include it.
Do I need the terminal to use Claude Code?
No. The Claude desktop app for Mac and Windows includes Claude Code in its Code tab, and you don't need to install anything else. The terminal version suits people who are already comfortable with it.
What should go in a CLAUDE.md file for a business?
The things you'd tell a capable new starter on day one: what you sell and for how much, who your clients are, how you write, where files live and how your main processes run. Keep it short and specific, ideally under 200 lines, and move long detail into separate files or skills.
Can Claude Code send emails on its own?
With an email connector switched on it can draft, and depending on the connector and your settings it may be able to send. Connectors ask for approval before acting by default. We recommend keeping that approval in place for anything that goes to a client.