Claude Tag Pricing: Enterprise vs Team, and When Self-Hosting Wins

This is part of our Claude Tag field guide for agencies. Start with the overview: Claude Tag: A Builder’s Guide for Agencies.

The first thing to understand about Claude Tag pricing is that Claude Tag doesn’t have a price. There’s no separate line item, no per-feature fee. It’s included with the plans it runs on — Claude Team and Claude Enterprise, in beta — so the real question isn’t “what does Claude Tag cost,” it’s “which plan are you on, and is per-seat the right model for how you work.”

What you’re actually paying for

Claude Tag is a capability of two existing plans, not a product you buy on its own:

• Claude Team is straightforward per-seat: a flat monthly price per user (premium seats cost more for higher usage). Predictable, easy to budget, good for a defined internal team.

• Claude Enterprise is seat-plus-usage: a per-seat fee, and then the tokens your team consumes — in chat, Claude Code, or Cowork — billed on top. It adds controls like role-based access, but the total depends on how heavily you use it.

Because the two plans bill on different logic, the “cheaper” one depends entirely on your usage shape. We dig into the Enterprise side in detail in Claude Enterprise Pricing: What Large Organizations Pay.

The launch credit (worth knowing now)

At launch, Anthropic is subsidizing early adoption: as of June 2026, it’s offering $1,000 in Claude Code and Cowork credits for every Enterprise seat activated by July 2, 2026. For a team that was going to adopt anyway, that credit covers a meaningful chunk of early usage — it makes the “turn it on internally and try it” decision close to free. It’s time-boxed, so if Enterprise is on your radar, the math is best before that date.

When paying per seat is the right call

For a single internal team, the per-seat model is the obvious answer. You get a current-generation teammate (Claude Tag runs on Opus 4.8) with no infrastructure to build, the launch credit softens the ramp, and ambient mode is safe to use because all the data is yours. Buy the seats and move on.

When building your own loop wins

Per-seat pricing is built for one company’s team. It is not built for an agency running many clients through one operation — and that’s where the calculus flips. Building your own gated Slack–to–AI loop starts to beat paying per seat when:

• You need hard isolation between clients that per-seat access controls don’t give you. Isolation has to be architectural, not a setting — see The Multi-Client Isolation Trap.

• You want to own the credential and the model path, so no client’s API key or context lives where it could leak.

• The approval gate is the product — you need a human signing off on every outbound deliverable, wired into the architecture, not bolted on.

• Seat counts get large or spiky, where a usage-based loop you control can undercut a per-seat bill.

We didn’t reason our way to this in a spreadsheet — we built that loop before Claude Tag launched, for exactly these reasons. The story is in We Built a Slack AI Teammate Before Claude Tag.

The honest answer

For your internal team, adopt Claude Tag on a Team or Enterprise plan and take the launch credit — it’s the cheapest path to a real AI teammate. For multi-client delivery, the per-seat model isn’t the whole answer, because the thing you’re really buying — isolation, control, and a human in the loop — is exactly what you have to build yourself. That’s the part we build for clients at Tygart Media. Start at the pillar: Claude Tag: A Builder’s Guide for Agencies.