Six months in.
AUGUST 2026 · RETROSPECTIVEMarch to August. What worked, what didn't, and the two things I got embarrassingly wrong. Not a growth post — a lessons post.
Six months since the March launch. This is the retrospective. Not a growth-numbers post — we'll write those at year-end if we're still growing enough for the numbers to be interesting. This is a lessons post.
**What worked:**
**The receipts.** The single strongest signal that the whole approach works has been the reception to the monthly WFP receipt. Users share screenshots of them, prospects mention them as the reason they subscribed, journalists writing about consumer AI have referenced them. The receipt turned out to be the marketing, exactly as we'd hoped.
**Not chasing free.** Every month of not launching a free tier has been a month of not having to defend the meal donation math against "but why don't the free users get meals too." The demo (three messages on marketing, no signup) has been enough. Zero regret on this call.
**Being specific in copy.** The marketing copy says "$8 buys ten meals through WFP's ShareTheMeal partner at $0.80 each." Not "we donate a portion." Not "we give back." Specific numbers, specific partner, specific per-unit cost. This has been our biggest differentiator against generic-impact marketing from every other consumer subscription trying to look ethical.
**Kitchen panel and model transparency.** We shipped this without knowing if users would care. They do — the most engaged subscribers use it, mention it to friends, and treat it as one of the reasons LADLE feels different from the black-box competitors.
**What didn't work:**
**The first onboarding.** The three-step "get to value fast" version we launched with produced worse retention than the ten-step "Setting the Table" we shipped later. Should have started with the longer version and let it prove itself, rather than shipping the industry-default shortest one first and rebuilding.
**Design mode's first version.** Before the canvas-first rebuild in August, design mode was just chat with a different system prompt. Nobody used it meaningfully. The lesson: system-prompt-only features don't feel like features to users — they need distinct surfaces. Should have done the canvas from the start.
**The billing hesitation.** We spent longer than we should have without shipping Stripe. The market for "consumer AI subscription with meals attached" was ready in June; we didn't have real checkout until August. Two months of coasting on a placeholder page is two months of lost momentum. Lesson: ship billing early even when it's ugly, then polish.
**Two things I got embarrassingly wrong:**
**One: I assumed users would want fewer settings, not more.** The original composer had four toggles hidden behind a menu. Users kept asking where the toggles were. Turns out for a $20/month product, users want visible controls, not "we've hidden the complexity for you." Every toggle got promoted to the composer surface after month two. Should have started that way.
**Two: I underestimated how much the community would care about the specific WFP partnership.** I picked WFP for the operational reasons (scale, receipt clarity, per-meal math). What surprised me was how often subscribers wrote in with a personal story about a family connection to food insecurity, or a professional connection to humanitarian work. This wasn't in the market research. It should have been.
**What I'm watching for the next six months:**
Whether the receipts model scales past a certain subscriber count without losing its intimacy. At 500 subscribers, every one is close-to-personal; at 50,000 the receipts become anonymous line items. The lesson from month one publishing carefully has to hold at 100× scale.
Whether the "no free tier" position gets tested by cheap-model competitors. DeepSeek's essentially-free tier is real competition on price. So far the value prop has held, but the market is dynamic.
Whether we can keep the changelog cadence tight enough to matter. Silent weeks would be visible in a way most companies don't have to worry about, because we've committed to the changelog being the marketing.
**One thing I want to say explicitly:**
The subscribers who joined in the first three months when the product was rougher — thank you. That's the group that took the promise at face value before there was much of a track record. Every month since has been building the track record. The receipts page is the ongoing thank-you.
If you're reading this having just subscribed: hello, thanks, and if something feels wrong please write. If you're reading this after canceling: also thanks, and honestly, no hard feelings — the refund policy exists for exactly the "not for me" case.
Six months. Onward.