Why we publish reports.

The most important thing on this website is the ledger page. Not the landing page, not the demo, not the comparison tables. The ledger — dates, amounts, meal counts, and the cumulative pooled fund growing toward the $50,000/year partnership threshold. Every month, on the day the batch posts.

Framing note: today the monthly artifact is a **LADLE-issued fund report**. Once we cross the $50,000/year threshold that unlocks the corporate partnership with the hunger-relief charity we select, real partner receipts publish alongside every fund report — same discipline, additional line item. Full context in [the-fifty-thousand-threshold](/blog/the-fifty-thousand-threshold).

Everything else on the site is downstream of that decision.

We could operate LADLE without publishing anything. Pick a nice-sounding fraction ("a portion of every subscription goes to good causes"), route the money quietly, and never have to prove it. The competitive set does this, mostly. A public commitment that isn't tied to an artifact is really just a mood.

We didn't want to run that company. The whole point of LADLE is that you're already paying $20 a month for a general assistant, and if some of that money is going to do a second job on the way out, you should be able to verify it. Not eventually, not with a login, not with a "sustainability report" published quarterly at PDF page 34 — verify it, on a URL, with a monthly fund report today and a partner reference number alongside it the moment the partnership activates.

That commitment has three second-order effects that shape the rest of the business.

First: it caps how creative we can get with the price. The moment we start experimenting with a Pro tier at $30 or a Team tier at $50/seat, the meal math gets more complicated to publish honestly. So we don't. One product, one price.

Second: it kills the retention team playbook. Every SaaS company has some version of "cancel? Are you sure? Here's 50% off." Ours can't. If the pitch was "you're paying for meals to be reserved and eventually shipped through the partner we select", offering a discount on cancel means saying "you're reserving fewer meals now, but still paying us" — which is worse than just letting you go. So the cancel screen is one button.

Third: it makes marketing straightforward. We don't have to invent a story about impact. We just link to the ledger. The reports do the work that a testimonial section would do at another company. If we ever can't show you the report, cancel us. That's the deal.

This is also why we don't have a Series A pitch deck. What we have is a spreadsheet: subscribers × $8, minus API cost, minus ops, minus $0 for growth marketing because we don't run any. It either works at scale or it doesn't. If it does, we grow, we cross the partnership threshold, and the receipts side lights up. If it doesn't, we don't get to reinvent ourselves into a different company that's better at fundraising.

The reports, and the fact that the reports are the whole trust mechanism, are the operating decision. Everything else is a consequence.