Example numbers are illustrative — we won’t pretend to know your budgets. The mechanism holds regardless of size: your AI budget can also reserve meals in your company’s name in the meal fund, one line at a time. Full framing on tax treatment is on /impact/tax.
Your team, in dollars and meals.
Slide to your headcount, pick a plan tier. Both numbers scale linearly — same $8 earmarked into the meal fund for every $20 seat, whether you buy 5 or 500.
Drag the sliders. Watch the meals.
Same math the webhook uses when it writes to your workspace ledger. No modelling, no marketing fluff — just seats × months × 10 meals.
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.
Chat. Kitchen. My Table. Scroll to see each one.
Same tool budget. Merged with a real social-impact line.
Your team is already paying for an AI assistant, or is about to. LADLE at $20/seat is a lower unit cost than the direct competitors, and every seat quietly reserves ten meals a month in the meal fund — pooling toward the $50,000/year partnership threshold — with a public fund report reference your ESG lead can verify. Real partner receipts post-partnership. The comparison, verified 2026-08-05 against published competitor pricing:
SOURCES · OPENAI.COM/CHATGPT/PRICING · ANTHROPIC.COM/PRICING · VERIFIED 2026-08-05. COMPETITOR SEAT-COUNT MINIMUMS AND ANNUAL COMMIT TERMS VARY; PRICES SHOWN ARE THE PUBLISHED PER-SEAT RATES A BUYING TEAM WOULD ENCOUNTER.
The document you get on the last day of every month.
Delivered by email to the billing contact plus every admin, and available as PDF/CSV from the dashboard. Attaches directly to a CSR/ESG report as evidence of a real meal-fund contribution — published fund reports (real partner receipts post-partnership), not marketing claims. Deep-dive on how each field reconciles to the public fund reports: see the impact reporting page.
Employees get the same LADLE they’d buy themselves.
A team seat is functionally identical to a consumer subscription — same model, same context window, same file handling, same Projects, same voice-guide behavior. The differences are administrative: their seat is billed centrally, an admin can add or revoke access, and the meals their subscription reserves in the meal fund are aggregated onto the organization’s statement.
Individual chats stay private to the seat holder. Admins do not have a "view all chats" surface, and there is no permission that enables it — see admin controls for the deliberate reasoning. What the admin can do: export a specific member’s data on request (member is notified), remove seats with three offboarding options for chat history, and switch plan tiers per seat where genuinely different usage patterns justify it.
Worth putting on your careers page.
“Every employee gets a LADLE subscription. Ten meals per seat per month are reserved in the meal fund in the company’s name — roughly 120 meals per employee per year — pooling toward the our future hunger-relief partner partnership threshold. Monthly fund reports are public.”
No HR-speak, no aspirational vagueness. A specific, verifiable fact about how the company’s tooling spend earmarks a meal fund pointed at food security. This is not "give back" language, and it is not purpose-washing — it is a line item on your invoice, and a fund report reference (partner ref populates once the partnership threshold clears).
One invoice. Meals per seat.
Four steps. No demos with a sales quota attached.
Onboarding is genuinely manual because we’re a small company and self-serve for business isn’t built yet. You email partners@ladle.chat with your headcount and preferred plan mix, we reply within one business day, run a 45-minute call to set up billing + invite the first seats, and after that the organization runs itself. First monthly impact statement lands on the last day of the calendar month you started in.
Answers to vendor-review questions, pre-answered.
The exact document your procurement team asks for — legal details, subprocessors, DPA, compliance honesty, insurance posture, standard vendor-form Q&A. Written for a vendor-review team, not a sales pitch.
See procurement page →SECURITYEncryption, retention, incident response, per-tenant isolation.
The technical posture your security team asks about, with what we have implemented and what we do not have (SOC 2 is not yet, and we say so). Real detail on data flow, subprocessor list, and how deletion works.
See security page →IMPACT REPORTINGThe monthly artifact, in full.
Every field on the impact statement explained, reconciliation to the published fund reports (real partner receipts post-partnership), CSR/ESG usage guidance, and what the document is and isn't (not a tax receipt).
See impact reporting →Eight questions procurement asks.
One invoice per organization, per month (or annually). Every active seat shows up as a line item, itemized by plan tier (Base/Max 5x/Max 20x). Payment via credit card is default; ACH and wire are available for orders above 25 seats — email partners@ladle.chat with your finance team's preferences and we handle the switch manually. Invoices are exportable as PDF for accounting and CSV for line-item reconciliation.
No fake logo bar. We’ll publish the first ten organizations here with their permission once they exist.
Most B2B pages open with a wall of customer logos to prove the product is real. We’re a small company and the business tier is new; the honest state is that we don’t yet have organizations to name here. When we do, we’ll list them with their permission and with the specific meals-per-year each is reserving in the meal fund — a substantive band, not a decorative one. If your organization would be an early one, email partners@ladle.chat and we’ll onboard you and, with your consent, cite you here when the section goes live.
SECTION UPDATED WHEN 10+ ORGANIZATIONS ARE LIVE · CONSENT-BASED · NO SPONSORED PLACEMENT
Bring the whole team. Send the impact statement to your CSR lead.
Email partners@ladle.chat with headcount + preferred plan. One business day reply. Every seat reserves 10 meals a month in the meal fund — pooling toward the partnership threshold — with a public monthly fund report.