Claude Team plan setup: a first-week checklist for small businesses

The Team plan is paid for, the invite list is ready, and the admin settings page has more toggles than anyone expected. The tempting move is to invite everyone on day one and sort out the settings later.

The first week decides whether Claude becomes part of how your team works or another login people forget. The order you set things up in matters more than any single setting.

Below is the sequence we use when we set up Claude Team, the warnings we give owners along the way, and the starter material we put in place so people open Claude to something useful on their first day. If you're an owner or manager rolling out Claude to your team, we'll walk you through the first week.

Day 1: lock in who can get in

Verify your domain. This proves to Anthropic that your company owns its email domain, and almost every other access setting depends on it. Anthropic's guide to getting started with the Team plan covers sign-up and the move from a personal account.

Turn on single sign-on (SSO) if you have an identity provider. SSO means people log in to Claude with the same company account they use for email, such as Google Workspace or Microsoft 365, instead of a separate password. It's the foundation for everything else, and it steers people away from running work through personal Claude accounts that the business can't see.

Turn on "Restrict organization creation." Once your domain is verified, this toggle appears under Organization settings > Organization and access > Security. It stops anyone with a company email address from creating a new Claude account or a separate workspace outside the one you manage.

Name at least two Owners. If the only Owner leaves or gets locked out, nobody can manage the account. A second Owner costs nothing and avoids that problem.

Day 2: start with connectors off

Connectors link Claude to your other tools, like Google Drive, Gmail, Calendar or Slack, so it can search and read from them without anyone uploading files. They're the easiest setting to over-grant and the hardest to audit afterward.

We start with every connector off and turn on only what the team needs, usually Drive, Gmail, Calendar and Slack, one at a time.

Day 3: set seats and spending limits

Team plans come with two seat types. Standard seats cover most people. Premium seats include the same features with much higher usage limits, at a higher price.

Start everyone on Standard and set spending caps at both the company and the individual level. Then watch usage for a few weeks.

When someone keeps hitting the Standard limit, find out what they're doing before you upgrade them. Sometimes the work is valuable enough that a Premium seat clearly pays for itself. Other times the person is spending their usage inefficiently, and a little coaching fixes that for far less money.

Day 4: publish a starter kit

People decide in their first few minutes whether a tool is worth coming back to. A blank chat box doesn't give them much to go on. Before anyone outside the pilot logs in, we set up three things.

Organization instructions

These are standing instructions Claude follows in every conversation across your company. Owners set them under Organization settings > Organization and access, with a limit of 3,000 characters.

Use the below template to get started. Fill in the brackets and trim anything that doesn't fit how you work.

About us
We're [Company], a [one-line description] serving [customer type]. Use plain, practical language. Skip hype and buzzwords.

How to respond
- Lead with the answer or recommendation, then the supporting detail.
- Keep it short unless I ask for depth. Use bullets for lists and prose for explanations.
- If a request is ambiguous, ask all your questions in one batch before starting.
- If you're unsure or missing information, say so. Never guess at facts, numbers, names, or quotes.
- Push back when an idea has a flaw. Don't just agree.

Writing
- Match our voice: [direct / friendly / formal]. Avoid corporate filler and AI-sounding phrasing.
- Drafts are for review. Mark any assumptions so I can check them.

Data handling
- Don't ask for or use passwords, payment details, Social Security numbers, or health records.
- Treat client and employee information as confidential. Use only what's needed for the task.
- Flag anything that looks like it needs legal, HR, or compliance review instead of advising on it.

Work product
- Cite sources when you use outside information.
- For anything going to a customer or the public, remind me that a person should review it first.
- When a task has more than a couple of steps, show a short plan before starting.

The data handling section sets a baseline for the whole company without anyone having to dig up a policy document.

One or two shared projects

A project is a workspace inside Claude with its own instructions and reference files, so every chat in it starts with the right background. Anthropic explains how to set them up in its article on creating and managing projects. For a services business, these two starter projects are the ones we set up first:

• Contact briefing. Ask about any prospect or customer and get a "state of the union" pulled from your CRM, email and web research: past conversations, open items, and what's changed since you last spoke. Nobody walks into a call missing context.
• Lead list builder. Upload a document describing your ideal customer, then set up an automation that searches for matches using tools like Google Maps, Clay or Apollo. Building lists by hand is manual busywork that crowds out the conversations those lists are supposed to lead to.

A few organization skills

Skills are saved, reusable instructions for a specific task, such as formatting a proposal or summarizing a call in your house style. Owners can publish them to the whole company, and they show up for everyone automatically. Start with two or three tasks your team repeats every week.

Day 5: run a small pilot

Don't switch everything on for everyone at once. Pick three to five people who do different kinds of work, give them access, and let them use Claude on real tasks for a week. A pilot that size beats a full rollout because problems show up while they're still small: a missing connector, a confusing instruction, a project nobody can find.

At the end of the pilot week, get the group together. Ask what they used Claude for, where it fell short, and what they'd want ready before everyone else joins. Adjust the starter kit, then open it up to the rest of the team.

Shared or personal: where projects should live

When an employee leaves and their account is removed, their private projects go with them. Projects shared with the company stay available to everyone else. We tell clients to make shared projects the default for anything the business relies on. A quick guide:

Know what the Team plan doesn't cover

Team handles access, billing and sharing well, but it leaves out some controls larger companies expect:

• No audit logs. There's no built-in record of who did what in Claude.
• No SCIM. SCIM automatically adds and removes people in Claude when you add or remove them in your company directory. Without it, offboarding is manual, so put "remove Claude access" on your offboarding checklist.
• No custom data retention. You can't set your own rules for how long chats are kept.

If your business needs audit trails for compliance, Team won't provide them. In that case we pair the Team plan with a written AI-use policy, or recommend Anthropic's Enterprise plan, which includes those controls.

After week one: keep the team talking

The setup gets people started. What keeps them going is talking to each other about how they use it.

When everyone works with AI on their own, good ideas stay with one person, mistakes get repeated, and a pile of one-off workarounds builds up that nobody else understands. A short regular meeting where people show what's working, and a shared place to collect the best prompts and projects, does more for adoption than any setting on this list.

How we help with Claude Team setup

We can set up your Claude workspace, organization instructions and starter projects before your team's first AI training session. Then the training uses your team's real work, so people leave with projects they'll keep using.

If people on your team already have personal Claude accounts, our guide to moving from a personal Claude account to Team covers what transfers.

Still choosing a tool? Our comparison of Copilot and Claude for teams covers which fits which kind of business. We work on-site around Rochester and Western New York and remotely with teams anywhere.