The changelog is the marketing.

Look at most SaaS marketing sites. There's a blog. There are pillar pages. There are customer stories. There's an SEO effort producing "10 best X" articles. Somewhere buried under "Resources" is a changelog, updated monthly at best, three paragraphs of "we shipped some things this quarter."

LADLE's marketing looks different. The blog exists (you're reading it) but the changelog is treated as a primary surface. Every ship — every real code change that a user might notice — gets a line. The receipt page is a monthly changelog for WFP donations. The founder-letter section reads like a public dev log.

This isn't a style preference. It's a specific choice, and here's the reasoning.

**Marketing that talks about features you don't have is a lie.**

The strongest marketing in tech (for products with actual users) has a specific texture: it describes what the product IS, right now, not what the pitch deck says it will be. When companies write blog posts about their "AI-first vision" without having shipped the AI feature, users can tell. It reads as ambient BS.

Changelog entries are the opposite of ambient BS. They're specific ("shipped X on date Y, replacing Z"), they're falsifiable (you can go check), and they're proof-of-work in a way marketing copy can't be.

**The receipts model needs it.**

LADLE's whole pitch is that we do a specific thing (send $8 to WFP each month per subscription) and prove it publicly. The receipts do the impact side. The changelog does the product side. Together they form the honest picture: here's what we did with your $20, in both directions.

If the product side of that picture went dark for months while the marketing site published "How AI is transforming the way we work" content, the receipts side would start feeling like an isolated stunt. Consistent public shipping evidence is part of the trust structure.

**It's easier than marketing.**

Real changelog entries write themselves — the work was done, the entry is the summary. Marketing content is invented from scratch, requires positioning, requires editorial judgment, requires promotion. A three-line changelog entry is 15 minutes of work; a "10 ways to use AI for productivity" post is a full afternoon of writing content most readers won't finish.

This isn't laziness. It's ROI. The changelog reaches users who already care (subscribers checking in, prospects doing due diligence, journalists writing about the space) with information they can act on. The generic marketing content reaches a broader audience with a shallower engagement, and most of that audience isn't converting anyway.

**It defends against feature drift.**

When the changelog is the marketing, you feel every quiet week. If nothing shipped in a week, the changelog for that week is empty, and the empty week is visible. That creates internal pressure to actually ship — small consistent progress rather than big splashy launches.

The alternative (long silent periods punctuated by marketing about "coming soon" features) is how most companies drift. LADLE trying to avoid that trap.

**What the changelog looks like:**

Short lines with dates. What shipped, why, and a link to the affected surface if it's user-visible. Occasional deeper writeup (a blog post) for changes that need explanation — but the changelog line comes first, and the blog is the followup.

Every entry corresponds to a real git commit or a real ops change. No entries invented to fill weeks; no backdated entries to make history look busier. If a week is empty, it's empty; if the changelog is quiet, the product is quiet, and that's information the reader deserves.

**Where the changelog lives:**

/changelog on the marketing site. Everything since launch. Public, no login. The RSS feed of it is where power users subscribe.

The bottom of every marketing page could link to it and probably will eventually. That's a minor design task.

**Rule of thumb.**

If your marketing describes features you have, it's a changelog with a different name. If it describes features you don't have, it's a pitch deck with a different name. LADLE tries to stay on the first side of that line.