Claude Code pricing: what it really costs a business to build with it.

How much does Claude Code cost?

Claude Code is included in every paid Claude plan, so the cheapest way in is Claude Pro at about A$34 a month in Australia. Max costs about A$170 or A$340 a month for more usage. Team seats start at about A$43 a month. You can also skip the plan and pay per use through the API.

Anthropic sets its prices in US dollars and shows Australian accounts a local price at checkout, with GST included. The Australian figures below are approximate and match what Australian accounts were shown in October 2026; the US figures come from Anthropic's pricing page. The Free plan does not include Claude Code at all.

Enterprise also includes Claude Code, at US$20 a seat billed yearly plus usage at API rates, with a 20-seat minimum. For the full plan-by-plan picture beyond Claude Code, see our guide to Claude pricing in Australia.

What are the Claude Code usage limits?

Every plan's limits reset on a rolling five-hour window, and paid plans add a weekly limit on top. Claude Code and ordinary Claude chats draw from the same pool, so a long build session eats into the allowance you would otherwise use for email and documents. There is no fixed message count.

How fast you use the allowance depends on how long the session runs, how much of your project Claude has to read, and which model you pick. Anthropic's own guidance is that Pro gives at least five times the Free allowance per session, Max gives five or twenty times Pro, and a premium Team seat gives five times a standard one.

When you hit a limit you have three choices: wait for the window to reset, move up a plan, or switch on usage credits, which let you keep working and bill the extra at standard API rates. On Pro and Max you can set a monthly spend limit for those credits. On Team, the owner sets limits for the whole organisation, a group or one person, which is the control most businesses actually need.

Inside Claude Code, typing /usage shows where you stand against your plan, and what has been eating it.

Should you pay with a plan or through the API?

For a business owner, a plan is almost always the better deal. You pay a known amount each month and the worst case is a pause until the limit resets. API billing charges for every token, which suits automations and developers who want no ceiling, but it is easy to spend more than a Max plan without noticing.

When you connect Claude Code to a Claude Console account instead of a plan, it uses API tokens at Anthropic's standard rates. Tokens are the small chunks of text the model reads and writes, and Claude Code uses a lot of them because it reads your files and resends the whole conversation on every step.

For scale, Anthropic's Claude Code cost documentation puts the average across its enterprise customers at around US$13 per developer per active day, or US$150 to 250 per developer a month. Those are professional developers in code all day. A business owner building one tool around the edges of a working week is a very different job, and that is exactly why we put owners on a plan, where the bill cannot run away.

When should you step up from Pro to Max?

Start on Pro. Step up to Max only when you are hitting Pro's limit most days because you are actively building something, like a quoting tool or a dashboard. When the build is finished, drop back to Pro. Max is billed monthly, so there is no penalty for moving up and down.

Anthropic's own description of Pro is that it suits short coding sprints in small codebases. That is a fair summary of the first version of most owner-built tools. The pressure on the limit comes later, once you connect real data and start fixing the edge cases. That stretch is when Max earns its keep, and it is a stretch, not forever.

On a Team account the same rule applies at seat level. Keep everyone on standard seats and give a premium seat to the one or two people who build. You can mix seat types on one account.

What does a tool built with Claude Code cost to run?

Often very little. A tool built with Claude Code is usually a small app or script you own, and once it is finished it does not need Claude Code to keep running. The running cost is hosting, often a few dollars a month or nothing, plus a few cents per use if the tool calls AI to read documents.

This is the comparison that matters, because many owners are not weighing Claude Code against another AI tool. They are weighing it against software they rent every month.

• Scripts cost nothing to run. The director at KR Surveys had Claude write a script that turns a docket export and an invoice template into the monthly invoices. The owner runs it each month. A full day of work became about a minute.
• Reading documents costs cents. For a mining compliance team, we estimated pulling obligations out of each approval document at roughly 50 cents to a dollar per document, paid once when the document first arrives.
• Hosting is small. One client website we moved went from $218 a month in hosting to about $20 a year.

The honest maths: a couple of months on Max while you build, then Pro to maintain it, can cost less than a year of the software it replaces. But your time is the real cost, and a tool only you understand is a risk if you are the one who leaves. If that trade does not stack up, our team can build and maintain the tool for you instead. If you are not sure which jobs are worth automating at all, an AI audit ranks them before anyone spends a dollar on building.

How do you keep Claude Code costs under control?

Most runaway usage comes from a handful of habits: one long session that never gets cleared, the most expensive model left on for simple work, and jobs left running unattended. Fix those, put spend limits on, and costs stay predictable on any plan.

• Clear between jobs. Claude Code resends the whole conversation every step, so a session open all day costs more per question. Type /clear when you switch to something unrelated.
• Match the model to the work. Sonnet handles most building. Save Opus for the hard planning moments.
• Be specific. "Improve my app" makes Claude read everything. "Add a GST line to the quote total" does not.
• Set limits before you need them. On Team, set spend limits per person. On the API, set a workspace spend limit in the Claude Console.
• Check /usage weekly. It shows which skills, connectors and scheduled jobs are using your allowance, with suggestions to trim them.

If you have not used Claude Code yet and want to know what it can do before worrying about cost, start with our guide to Claude Code for business owners.