Claude Team Plan: Seats, Price and How to Share Project Progress

The Claude Team plan gives a group of people their own Claude seats under one admin console, with shared billing, shared Projects and team controls. It is the step up from everyone paying for Claude Pro on their own. What it does not give you is a shared record of the work itself: each person's chats and memory stay with that person, so "where is this client at?" still depends on who you ask. This guide covers what the Team plan includes, who it suits, and how to give the whole team one project history that every seat's Claude can update.

Interest is growing fast. In Google Keyword Planner data we pulled in October 2026, searches for "claude team plan" were around 5,000 a month and up sharply on the year before. We make one of the tools mentioned below, the KissMySkills AI CRM. We say where it fits and where Claude on its own is enough.

What the Claude Team plan includes

Plans and prices change, so check Anthropic's pricing page before you buy. At the time of writing (October 2026), the Team plan works like this:

• Seats. A minimum of 2 seats (lowered from 5 in July 2026), up to 150. Above that, you are in Enterprise territory.
• Two seat types. Standard seats give roughly Pro-level usage. Premium seats give much higher usage for heavy users. You can mix them on one team.
• Price. Standard seats start at about $25 per person a month, less when billed yearly. Premium seats cost several times more.
• Admin and billing. One invoice, an admin console to add and remove people, and single sign-on.
• Shared Projects. A Project with its files and instructions can be shared with teammates, so everyone starts from the same brief.
• Data handling. By default, Team conversations are not used to train Anthropic's models.
• Tools. Claude Code and connectors to other apps, which the admin can turn on or off for the organization.

Claude Team vs Claude Pro: who needs which

The gap: shared Projects are not shared progress

A shared Project holds the starting point: files, instructions, a brief. It does not hold what happened after. On a typical team:

• Anna asks Claude to draft a proposal for a client. That chat lives in Anna's history.
• Ben follows up with the client the next day in his own chat. His Claude has no idea Anna's proposal exists unless he pastes it in.
• The manager asks "what is open with this client?" and has to ask Anna and Ben, not Claude.

Each person's memory and chat history stay personal, which is right for privacy but leaves the team without one picture of the work. Teams usually patch this with a shared doc, a Slack channel or a project tool that someone has to update by hand.

Give every seat's Claude one board to update

The fix is a shared place outside Claude that every teammate's Claude can read and write. Claude connects to outside tools through connectors that use the Model Context Protocol (MCP). Connect the same CRM or task board on every seat, and the team's work ends up in one place, no matter whose chat it started in.

With the KissMySkills AI CRM it looks like this:

1. Anna, in her Claude: "Add Northwind as a deal, proposal drafted, follow-up Friday." The deal appears on the team board.
2. Ben, in his Claude, next day: "What is open with Northwind?" His Claude reads the same deal, the note and the follow-up date.
3. Ben: "Client wants a call, move it to Negotiation and set a reminder for Tuesday." The board updates for everyone.
4. The manager, in any assistant: "What is stuck for more than a week?" One answer for the whole team.

It works for more than sales. The default template is a plain task board (To do, In progress, Done), and you can ask Claude to add stages like Review, or fields like owner and budget. Every change to the setup is saved in History with a rollback, which matters when several people's agents edit the same board.

If some of your team use ChatGPT, they connect the same way and see the same board. More on that in how to switch between ChatGPT and Claude without losing your projects.

How to set it up for a Claude team

1. Check connectors are allowed. On Team plans, the owner or admin controls which connectors members can add. Ask them to allow the KissMySkills connector.
2. Create the CRM. Sign in at crm.kissmyskills.com, pick a template or start blank.
3. Connect Claude on each seat. Each person adds the KissMySkills connector in Claude (claude.ai, the desktop app or Claude Code).
4. Agree on two habits. Start work with "What is mine today?" and finish with "Update the board with what I did."

The free plan covers one user and up to 300 deals, which is enough to try it yourself first. For a shared team workspace, write to hello@kissmyskills.com and we will set it up.

When you do not need anything extra

• Your team already lives in a project tool that has its own Claude connector. Use that and skip a new tool.
• The work is one-off. If each task starts and ends in one chat, shared Projects are enough.
• Two people, one project. A shared doc with a weekly handover note may be all you need.

Frequently asked questions

How many seats does the Claude Team plan need?

At least 2 seats since July 2026 (it used to be 5), and up to 150. Check Anthropic's pricing page for the current rules.

Can teammates see each other's Claude chats?

No. Chats and memory stay with each person. Shared Projects share files and instructions, not conversations.

Does the Claude Team plan include Claude Code?

Yes, Team seats include Claude Code, with usage limits depending on the seat type.

Can a Claude team use one CRM together?

Yes. Connect the same CRM through an MCP connector on every seat, and each person's Claude reads and updates the same board.

Can ChatGPT users on the team use the same CRM?

Yes. The KissMySkills connector works in both Claude and ChatGPT, so mixed teams share one board.

Try the AI CRM free and connect your team's Claude →