Claude for Small Business: Setup, Workflows and Security

Claude for small business usually means the Claude Team plan: a company-owned workspace for 2 to 150 people at $20 per seat per month billed annually, or $25 billed monthly, as of October 2026, with single sign-on, admin controls, central billing, Claude Code and Claude Cowork included. The plan is the easy part. What decides whether the rollout works is ownership: who administers the workspace, which connectors may reach company data, and what staff may paste in. This guide covers the plan choice, the permissions to set before anyone joins, three role-based workflows, a 30-day pilot and the point at which buying implementation help is cheaper than learning it yourself.

Claude is Anthropic's AI assistant. It runs as a chat app on the web, desktop and mobile; as Claude Cowork, which works through multi-step tasks on files and connected tools without a terminal; and as Claude Code, the agentic coding tool for developers. If you are deciding between the two company plans, read Claude Team vs Enterprise; for the full budget picture, including usage billing, see Claude pricing for a business.

Which Claude plan should a small business buy?

Anthropic sells individual plans (Free, Pro and Max) and company plans (Team and Enterprise). The Claude pricing page lists these as of October 2026:

For most small businesses the answer is Team. Pro seats bought on the company card belong to the employee: no admin console, the chats and projects leave with the person, and the account runs under consumer rather than commercial terms. Enterprise earns its 20-seat minimum when a regulator, an auditor or a client contract asks for audit logs, SCIM deprovisioning or a HIPAA business associate agreement; Anthropic's HIPAA-ready Enterprise article says Team, Free, Pro and Max cannot enable HIPAA at all.

Who should own the Claude workspace?

Treat the Claude organization like the Microsoft 365 tenant: it needs a Primary Owner, at least one more Owner, and a written answer to who approves connectors. On Team, Anthropic's custom connectors article says only Owners and Primary Owners can add a custom connector, and the Microsoft 365 connector article says only owners can enable that connector for the organization. Whoever holds those roles is making data-access decisions for the whole company.

A workable split for a 10 to 50 person company: the business owner or operations lead is Primary Owner, the IT provider is an Owner who handles identity, connectors and offboarding, and one person per department tests for their role. Never run with a single Owner.

Which permissions should be set before staff join?

Do these in order, before the invitations go out:

1. Identity. Turn on SSO and domain capture, and use just-in-time provisioning so accounts are created from your identity provider rather than by hand. Both are included in Team standard seats per Anthropic's Team plan article.
2. Connectors. Decide which of the built-in connectors (Google Drive, Gmail, Google Calendar, GitHub, Microsoft 365 and Slack) are allowed. The Microsoft 365 connector requires a Microsoft Entra tenant on a Business plan and a one-time consent from a Global Administrator; its permissions are read-only by default, and write tools need separate consent and an owner to enable them.
3. Custom connectors. Keep them off until someone has reviewed who hosts each server, which scopes it requests and whether its tools can write or delete.
4. Claude Cowork. There is an organization-wide toggle under Organization settings > Cowork, and cloud sessions can be switched separately from the desktop experience. On Team, cloud Cowork is in beta, per Anthropic's Cowork getting started article. Start with the default Manual approval mode, where Claude asks before acting.
5. Feedback and training. Anthropic says it does not use inputs or outputs from commercial products for training by default. Thumbs-up and thumbs-down feedback is stored for up to five years, de-linked from the user, and Owners can turn the "Rate chats" option off under Organization settings > Data and Privacy if you prefer.
6. Sharing defaults. Skill sharing is on by default on Team, and projects can be shared with view or edit roles; Owners can turn either off. Decide whether staff may share organization-wide or only with named colleagues, and whether skills enter the library through "Requires review."
7. Spend caps. Set the organization and per-user caps on prepaid usage credits before anyone discovers the API credit pool.
8. A one-page usage policy. What may be pasted in (public and internal material), what may not (client identifiers, payroll, anything under a confidentiality agreement unless the connector path has been approved), and the rule that a person checks any output that leaves the building.

What do three role-based Claude workflows look like?

The scenarios below are illustrative patterns, not client stories. Each uses one Claude Project (a workspace with its own instructions, files and chat history) so the context is set once instead of pasted every time.

Operations and office management

Create a project called "Operations" with the employee handbook, vendor list, templates and standard operating procedures as knowledge files, and instructions that name the company, the tone and the formats you use. The office manager then drafts vendor emails, turns meeting notes into task lists, rewrites a procedure after a process change and answers "how do we handle this" questions from the handbook. With the Microsoft 365 connector enabled read-only, Claude can also find the current version of a document in SharePoint instead of working from an upload.

Sales and client service

A "Proposals" project holds the approved service descriptions, pricing rules, past proposals that won, and a style guide. Staff paste the discovery notes and get a first draft in the house format; the same project turns a long client email thread into a two-paragraph summary with the open questions listed. The rule that matters here is review: nothing goes to a client without a person reading it, and the project instructions should say so.

Finance and reporting

Claude Cowork is the tool for the monthly close pack: point it at a connected folder of exports, ask for the variance table and commentary, and it produces an Excel file with working formulas and a short deck. Approval mode stays on Manual so each file action is confirmed, and the controller checks every number against its source before anything goes to the owner. NetSys has built this kind of reporting roundup on Claude for a lean team; the case study describes the scope.

How should a small business pilot Claude?

Thirty days, five to ten people, two roles, with the measures set before day one:

1. Time. Each pilot user logs the minutes spent on two named recurring tasks in the week before the pilot and in its last week.
2. Adoption. How many of the pilot users are still using Claude in week four, and for which tasks. Anthropic's Team article points members to Settings > Usage for their weekly limit, which is a rough activity signal when you ask pilot users to report it.
3. Quality. A sample of outputs reviewed by the department lead: used as-is, used after edits, or discarded.
4. Policy incidents. Any paste of restricted data, any connector request outside the approved list, any output sent without review. Zero is the target, and the count tells you whether the policy is understood.
5. Cost. Seats plus any usage credits consumed, against the hours saved at loaded cost.

Keep the workflows that moved a measure, drop the rest, and expand with a second pilot rather than a company-wide announcement.

When should you buy implementation help?

A two-person company can set Team up in an afternoon. The signals that a consultant pays for themselves are concrete:

• You run Microsoft 365 and want the connector: the Global Administrator consent, the Conditional Access implications (the connector's server-side requests come from Anthropic's network range, so location-based policies block it) and the read versus write scopes need someone who administers Entra ID.
• You handle health, legal or financial client data and need to know whether Team is acceptable or Enterprise with a BAA is required.
• More than 15 or 20 people are joining, and nobody owns onboarding, offboarding and seat changes.
• Staff already use personal Claude accounts for work and their history needs to move into the workspace cleanly; see moving personal Claude work into a company workspace.
• You want Claude connected to a line-of-business system through a custom connector, which means an MCP security review before it goes live.

What does NetSys do for a Claude rollout?

NetSys's Claude consulting service covers the setup and consulting work above as a fixed-scope engagement quoted after a short scoping call: plan selection, workspace ownership and SSO with your identity provider, connector decisions and the Microsoft 365 consent, a usage policy your staff will follow, the first Projects for two or three roles, and the pilot measures. Ongoing administration (seats, offboarding, connector reviews, policy updates) runs under a month-to-month agreement with help desk support seven days a week, 4 a.m. to 11 p.m. Eastern. It sits inside our wider AI services, which stay vendor-neutral across Claude, ChatGPT business plans and Microsoft Copilot, so the recommendation is the tool that fits the data and the task.

Frequently asked questions

Is Claude a good fit for a small business?

Yes, for drafting, summarizing, research, reporting and multi-step document work, provided the company owns the workspace. The Team plan starts at two members, so even a very small company can have admin controls and commercial data terms rather than a personal account on a company card.

How much does Claude cost for a small business?

As of October 2026, Claude Team is $20 per standard seat per month billed annually or $25 billed monthly, and $100 or $125 for a premium seat with five times the usage. Enterprise is $20 per seat billed annually with a 20-seat minimum and usage billed on top at API rates.

Does Claude use our business data for training?

Not by default on Team and Enterprise. Anthropic's privacy article for commercial products says inputs and outputs are not used for training unless you opt in through feedback, bug reports or explicit permission. Personal Free, Pro and Max accounts follow a different, consumer policy, which is one more reason to put staff on the company plan.

Can a small business connect Claude to Microsoft 365?

Yes. The Microsoft 365 connector searches SharePoint, OneDrive, Outlook and Teams with the user's own delegated permissions. It needs an Entra tenant on a Microsoft Business plan, a one-time Global Administrator consent, and an owner to enable it for the organization; it is read-only until write scopes are consented and enabled separately.

Do we need Claude Enterprise?

Only if you need what Team lacks: SCIM for automatic deprovisioning, audit logs and the Compliance API, custom data retention, IP allowlisting, customer-managed keys or a HIPAA business associate agreement.

NetSys has run a Microsoft Copilot and Claude rollout for a 25-employee company with usage policies, connector access controls and staff training, and can scope the same for yours. Request a Claude rollout review.