Three plans. All of them reserve meals.
Base at $20 with 10 meals/mo reserved. Max at $100 with 50. Max at $200 with 100. Same $0.80/meal peg via our future partner. Meals scale with plan; the monthly fund report is public. Ships as a real partner donation once the $50,000/year partnership threshold clears.
Ladle
The one plan most people should pick.
- ●Claude Sonnet · 200K context
- ●Generous daily use — hundreds of chats a month, most files, most workflows.
- ○Standard routing
- ●Chats never used for training
- ●10 meals/mo reserved · monthly fund report
Ladle Max 5x
Heavier use, longer files, priority at peak.
- ●Claude Sonnet · 200K context
- ●Five times the base usage. Priority routing at peak. For working days that lean on the model.
- ●Priority routing at peak
- ●Chats never used for training
- ●50 meals/mo reserved · monthly fund report
Ladle Max 20x
Rate limits become a thing you don't think about.
- ●Claude Sonnet · 200K context
- ●Twenty times the base. Effectively removes rate limits for individual power users. Same $0.80 working peg per meal.
- ●Priority routing at peak
- ●Chats never used for training
- ●100 meals/mo reserved · monthly fund report
Same price. One extra line.
How many meals over how long?
Every dollar has an itinerary.
No marketing spend. No acquisition budget. Here’s where every $20 goes — and here’s a slider so you can see what your commitment adds up to over the length of a year.
Math you can verify: $20 / seat / month, $8 of every subscription becomes 10 meals through the partner we select at $0.80 each. Nothing modelled — this is the same formula our webhook uses when we write to the ledger.
Every capability, every plan.
Multiples we can defend, not “unlimited”.
Base — a typical writer, developer, or knowledge worker doing 3-5 focused chats a day rarely hits the base plan's usage headroom. If you upload 200-page PDFs occasionally, still fine.
Max 5x — you code in the chat all day, you keep three long sessions open across projects, or your documents routinely fill the 200K window. 5x usage plus priority routing at peak keeps latency predictable when the base plan would start throttling.
Max 20x — you're using the model like a co-worker sitting next to you for 8+ hours. Rate limits stop being a thing you think about. This is the plan where the meal-fund earmark compounds — 100 meals/month reserved, 1,200/year.
None of these plans are unlimited. We say multiples because that's what's actually true. If you approach a plan's ceiling in normal use, we upgrade you at prorated cost rather than throttle you into a wall.
The split, plan by plan.
- $8 into the meal fund · 10 meals reserved
- $7 to Anthropic API
- $5 to ops (Stripe, infra, us)
- $40 into the meal fund · 50 meals reserved
- $40 to Anthropic API
- $20 to ops (Stripe, infra, us)
- $80 into the meal fund · 100 meals reserved
- $90 to Anthropic API
- $30 to ops (Stripe, infra, us)
Same tier prices as the incumbents. Different line item.
We hold price parity with the incumbent AI subscriptions on purpose. Being cheaper would let the meal-fund earmark be the discount that closes the sale; that framing turns the meals into a gimmick. Same price, published fund report, honest tradeoff. Full comparisons at /compare.
Give LADLE to someone. Meals reserved in their name.
Gift 1, 3, 6, or 12 months. Recipient creates their own account. Meals are reserved in their name in the same monthly fund report. No auto-conversion when the gift ends.
Ten questions.
Fixed. $8 of every Ladle subscription, $40 of every Max 5x, $80 of every Max 20x is earmarked into the meal fund the moment your Stripe charge clears. Not conditional on us being profitable. The pooled fund ships as a real partner donation once the $50,000/year partnership threshold clears; until then, the reserve accrues and is reported monthly. If we can't afford the earmark, we don't build the plan.
NOT ANSWERED HERE? EMAIL hello@ladle.chat — REAL PERSON, ONE DAY.
LADLE. Three plans. All of them reserve meals.
Cancel any time. Ten meals a month, minimum, reserved and reported.