What happens when Anthropic drops prices.

When Anthropic cuts Claude API prices, our operating cost drops. This post is the explicit accounting of what we do with the extra room — the answer is that price cuts flow into usage headroom, not into a lower subscription price.

**What we won't do:**

We won't drop the subscription price. $20/month is the price. Dropping to $18 would be a natural pass-through, but it would open a real design question about the meals ($8 becomes an awkward fraction of a smaller price, and the marketing anchor loses its round-number simplicity). We keep the price and pass the value differently.

We won't increase the meal-fund earmark. Raising to $9 per subscription would be the flashy move, but it changes the marketing (10 meals becomes 11-12), the fund reports have to explain the change, and if Anthropic ever RAISES prices we'd be caught having to lower the meal count publicly. The floor of 10 meals is a load-bearing constraint; we don't want to move it upward without confidence it can stay there.

**What we do:**

We increase the per-subscriber usage headroom. In practice: the monthly compute budget baked into each plan goes up. Users who regularly bump into their monthly compute cap get more room before they hit it. Users who never come close see no change.

**Why this way:**

The subscribers who most benefit from a price drop are heavy users. They're the ones for whom the compute budget was the constraint, not the meals. Giving them more headroom is a real product improvement for the people who feel the constraint, without touching the marketing narrative that everyone else counts on.

The subscribers who don't benefit — light users, casual users, users for whom the meals are the primary reason to subscribe — get the same product they were already using, at the same price, funding the same number of meals. Nothing worse for them; nothing better either.

**What we change in the pricing page copy:**

Barely anything. The plan pages say "Ladle base includes generous daily use" without pinning a specific token count, because pinning a specific count would create weekly-updated marketing every time the model changed. Internal budgets adjust; the external promise stays steady.

The "how we spend the $20" breakdown includes a line for this: "if inference costs drop, that flows through as usage headroom, not as a lower price." Honest, and it explains why the price is stable even as costs change.

**When would this reasoning change?**

If Anthropic dropped prices by 50%+ in a single move, the "pass-through as headroom" strategy would produce more headroom than any reasonable subscriber could use. At that point we'd revisit the meal donation floor — a $12 or $15 meal portion of the $20 might be feasible without breaking the marketing. But the change would be structural, announced deliberately, and permanent.

If Anthropic RAISED prices by 20%+, we'd absorb the first cut from margin ($3.50/subscriber has some room). Beyond that we'd have to raise the subscription price and be honest about why. Meals wouldn't drop — the meal floor is untouchable. Ops margin would compress first; price would rise second; meal count would never move down.

**The general principle:**

Price stability is a feature. Meal count stability is a feature. Both matter more to the LADLE story than optimizing every dollar. Passing cost savings through as capacity (rather than price) preserves both while still giving heavy users the win.

If Anthropic drops prices again — and they probably will as models get cheaper to serve — expect the same playbook. Same price, same meals, more room.