How much does Claude cost for a business?

The four parts of the cost

Almost every Claude budget we build breaks down into the same four lines:

1. Seats: a monthly or annual fee per person on a business plan such as Claude Team or Enterprise.
2. Usage: if you build tools on the Claude API, you pay for what you use, measured in tokens.
3. Setup: the time to configure the plan, connect your tools and build Projects and Skills.
4. Adoption: training, playbooks and the time your team spends learning new habits.

Many businesses budget only for the first line and then wonder why nothing changed. The last two lines are where the value is decided.

Seats on a business plan

Claude's business plans are priced per seat. Team plans are designed for smaller organisations and are bought online; Enterprise is priced through Anthropic's sales team. Some plans offer different seat types, for example premium seats with higher usage limits for heavy users such as engineers, so you do not have to pay the higher rate for everyone.¹²

A useful rule: buy seats for the people who will use Claude every week, not for everyone on day one. It is easy to add seats once a team has proved the value.

API costs, if you build custom tools

When you build your own tools on the Claude API, such as a document assistant or an automated workflow, you are billed for usage rather than seats. Usage is measured in tokens, which are small chunks of text. You pay for the text you send to Claude and the text it sends back, and the rate depends on which Claude model you choose.³⁴

• Larger, more capable models cost more per token and suit harder reasoning tasks.
• Smaller, faster models cost much less and suit simple, high-volume jobs such as sorting or tagging.
• Techniques such as prompt caching and batch processing can reduce costs considerably for repeated or non-urgent work.⁵⁶

For most small business tools, API costs are modest compared with the time saved. The way to know for sure is to run a short pilot on real work and measure the usage.

Setup and training

This is the part most budgets miss. A proper rollout includes choosing and configuring the plan, setting access and data policies, connecting your tools, building Projects for each team, writing Skills for your standard processes and training people on their real work.

You can do this in-house if you have someone with the time and the knowledge, or bring in a specialist to do it faster. Either way, budget for it explicitly. A rollout with no setup budget usually becomes a pile of unused licences.

How to build your budget

1. List the teams and the specific tasks Claude will help with first.
2. Count the people who will use it weekly. That is your seat number.
3. Decide whether any task needs a custom tool on the API, and pilot it to measure usage.
4. Add setup and training time, in-house or external.
5. Estimate the hours saved per person per week, and compare that with the total.

If the hours saved are worth more than the total cost within a few months, you have a business case. If they are not, start smaller, with the one team where the gain is clearest.