Claude Max Price Hike Tested: How to Lock in Your Current Rate

What Changed — A/B Testing Higher Prices

Multiple user reports, including side-by-side screenshots, confirm Anthropic is running an A/B test on Claude Max subscription pricing. For the same service limits in the same region on the same day, different accounts are seeing different prices:

• Claude Max 5: Some accounts show $100/month, others show $150/month.
• Claude Max 20: Some accounts show $200/month, others show $300/month.

The test appears linked to account creation details (like verification phone number country) rather than IP address. This is a classic market test to gauge price sensitivity before a potential permanent increase.

What It Means For Your Claude Code Workflow

This isn't just a billing footnote. For developers using claude code daily, a 50% price increase on a Max 20 plan ($200 to $300) directly impacts your operational budget and tool selection calculus. The Max 20 tier, with its higher message limits, is often the choice for power users handling large refactors, complex debugging sessions, or multi-file project analysis throughout the day.

If the test results in a permanent hike, the cost-benefit analysis for staying on a Max plan versus optimizing usage on a cheaper tier (or exploring alternatives) changes significantly.

Actionable Steps to Take Right Now

1. Check Your Account's Pricing: Log into your Anthropic account and navigate to the subscription or plan upgrade page. Do you see the original price ($100/$200) or the test price ($150/$300)? This tells you which cohort you're in.
2. Consider Locking in Your Rate: If you are on a monthly Max plan and see the original, lower price, switch to annual billing immediately. Annual subscriptions typically lock in your current rate for the billing cycle, protecting you from any mid-term price increases. The upfront cost is higher, but it could save you hundreds if a hike is imminent.
3. Audit Your Claude Code Usage: Use this as a trigger to review your claude code efficiency. Are you using the /compact flag for large outputs? Is your CLAUDE.md file optimized to reduce redundant context? Are you using MCP servers to offload tasks like file search? Reducing token waste makes every message count more, which is crucial if message limits become more expensive.
4. Evaluate the Tiers: If you're on Max 5 but often hit the limit, a price hike might make the jump to Max 20 less palatable. Conversely, if you're on Max 20 but use only a fraction of the messages, downgrading before a potential price change could be a smart cost-saving move.

Stay informed. Monitor official Anthropic channels for announcements, as A/B tests often precede official policy changes.