Enterprise seats

Per-developer math, times the team.

Multiply the per-developer cost by your seat count. See whether team seats beat buying hardware to run open models yourself. Every number cites a source, and the caveats stay with the answer.

Pick a seat count and workload mix. The three routes recompute as you change the inputs.

Team inputs

Set the seats and how the team works.

The three routes recompute as you change these inputs.

Seat count

Accepted range is 2 to 500. Values outside that clamp on blur.

Workloads

Data stance

Volume per developer

Three team routes

The lowest bill at this headcount.

Monthly totals scale with 20 seats at regular volume per developer. The lowest mid-range total gets the accent treatment.

Seat plans

Team seat plan

Standard seats include the current Claude family and Claude Code.

Monthly total: $400
Per seat: $20

What this is

Claude Team Standard is the lowest public team rate that covers 20 seats.
The estimate uses the published per-seat rate for every developer.

Claude Team plan ↗

Reality check

The $20 monthly equivalent requires annual billing. Weekly per-member limits apply, and extra usage uses prepaid credits. Claude Enterprise pricing is contract based.
Negotiated enterprise pricing usually lands below public list rates at larger seat counts.

Cheapest

Metered API

Monthly total: $300–$480
Per seat: $15–$24

What this is

Metered APIs route each selected workload through the lowest-cost covering models in the catalog.
The estimate applies 100 million tokens to every developer, so each seat adds the same usage range.

Reality check

The range assumes 70 percent input tokens and 30 percent output tokens. Prompt caching discounts are excluded.

On prem

On-prem serving

Monthly total: $878
Per seat: $44
Capex: ~$31,600

Machines4 × DGX Spark + RTX 5090128 GB unified + 32 GB VRAM

Route large models to Spark and latency-sensitive work to the desktop GPU.

What this is

Capacity + speed local lab is the highest-capacity catalog option that covers the selected workloads locally.
One box serves about 6 developers under an interactive coding load. Hardware cost is spread over 36 months.

Reality check

Serving and operations labor are excluded from the math. Electricity is also excluded.
Capacity assumptions need validation against your real workloads.

Need the one-person version? Open the solo planner for individual stack math.