No, it doesn't cost Anthropic $5k per Claude Code user

Perception of the “$5k per user” Claim

• Some were surprised anyone believed Anthropic literally spends $5k/month in compute per Claude Code Max user; others point to Twitter/LinkedIn and a Forbes article as having popularized that idea.
• Several commenters say the Forbes framing is sloppy or sensationalized, mainly by conflating retail API prices with Anthropic’s internal compute costs.
• The blog’s estimate of ~$500/month real compute cost for a true “maxed out” power user is viewed as more plausible, though still a rough guess.

Inference Cost, Margins, and Training

• Many argue inference itself is profitable at current API prices; references to reported 30–70%+ gross margins for major labs are cited.
• Others remain skeptical, noting huge ongoing training, R&D, and capex costs; they argue “overall business” can still be losing money even if per-token inference is above marginal cost.
• Debate over whether you should count training and R&D into “cost per token” or treat that separately as long-term investment.

Comparisons to Chinese/Open Models

• Big argument over using Qwen/DeepSeek/Kimi prices as a proxy for Opus costs.
• One side: similar throughput (tokens/sec) on the same clouds implies similar active parameter counts and thus similar inference cost, maybe Opus 2–3× more expensive, not 10×.
• Other side: frontier models with better “taste” and planning may incur superlinear costs; quality gap vs Chinese models is seen as real in complex, ill-defined tasks.

Caching, Context, and Real Usage

• Multiple users report that Claude Code token logs dramatically overstate “real” compute because cache hits are much cheaper and heavily used.
• One comment claims that stripping cached tokens drops an apparent $5k API-equivalent month down to ≈$800 in actual compute, with Anthropic’s own infra likely cheaper still.
• Several heavy users report four- and five-figure equivalent API bills per month if billed at list price, but they pay low three figures in subscriptions.

Subscriptions vs API & Opportunity Cost

• Consensus that flat-rate plans are engineered assuming most users won’t max them out; they resemble “spot” or buffet pricing.
• Some argue that at saturated capacity, power users create high opportunity cost (foregone API revenue), even if direct compute cost is far below $5k.
• Others respond that opportunity cost ≠ actual cost; what matters is whether users would ever pay API prices without subscriptions.

Moats, Market Dynamics, and Behavior

• Several see a real moat in high-end models: Opus is considered meaningfully better for complex coding/agent work, despite cheaper near-competitors.
• Others emphasize rapid catch-up by competitors and note that many enterprises are already pushing usage towards cheaper models and imposing cost controls.
• There’s meta-discussion on AI-generated writing style (“LLM-isms”) spreading into human prose, and on platforms’ weak incentives to filter “AI slop.”