What comes next — and what doesn't.

This post is a public roadmap. Not the "here's our vision for 2028" version — the "here's what we're actually working on for the next few months" version. And, importantly, the list of what we're deliberately NOT building.

**Coming in the next few months (in rough order):**

**Mobile apps.** LADLE works well in mobile browsers today, but a native iOS and Android app would improve the daily-use case for a lot of subscribers. iOS first. No timeline commitment; when it ships, the changelog gets a line.

**Better projects.** Projects work today (chats grouped, shared instructions, knowledge files at the project level) but the UI is under-considered. A rework is queued.

**Team seats with light admin.** Not a full "team product" — just: buy multiple seats on one card, one billing contact, one impact report. No shared workspace. This unblocks the small-business use case without committing to the full team-product roadmap.

**Referral / affiliate.** The /creators page describes a program that doesn't exist yet. Building it — flat rate per referral, honest math, publicly documented.

**Live model updates.** When Anthropic ships a new Sonnet or Haiku version, we need a smoother update path than "we redeploy and users find out from the changelog." Model updates deserve their own release notes.

**Impact API.** Some business customers have asked if they can pull their organization's monthly impact numbers via API for their own dashboards. Low-effort to build; queued.

**Not building (for now):**

**Image generation.** Diffusion models are outside our stack and outside our value prop. If you need image gen, dedicated tools do it better.

**Voice mode.** The audio chat pattern is nice for some users. It's a lot of surface area to build well — audio streaming, voice selection, mobile audio state management — and we don't currently see it as our core. Might change if enough subscribers ask.

**Custom GPTs / agent builder.** OpenAI has GPTs; Anthropic has Projects (which we support). A custom-agent-builder inside LADLE is a big product that would distract from the core. Not on the list.

**Enterprise SSO / SCIM.** No demand from subscribers yet. If a big-enough deal shows up requiring it, we build it for that deal.

**A public API for LADLE itself** (letting developers hit LADLE's chat endpoint from their own apps). Interesting but not core; Anthropic's API is the answer for developers who want to build with Claude directly.

**A LADLE-branded model, fine-tuned or otherwise.** We use Claude Sonnet as-is. No LADLE-specific training data, no proprietary fine-tune. The model is Anthropic's; the product is ours. This is deliberate.

**What would move something from the "not building" list to the "building" list:**

Repeated specific asks. Not "would be cool if" — actual "we would sign up / stay subscribed / recommend if" requests. When we see the same request from a few different people who match the customer we're building for, that's signal.

A specific unlocked use case. If enterprise SSO would unblock a 200-seat customer, we build it for that customer.

A material shift in the underlying tech. If open-source models close the gap to Sonnet at meaningfully lower cost, the economics could support things that don't fit today.

**How we prioritize:**

The order isn't "biggest feature first" or "loudest request first." It's roughly: (1) things that fix specific broken user experiences, (2) things that unblock specific stuck subscribers, (3) things that expand the reachable-users set materially, (4) new capabilities.

Meal-donation infrastructure doesn't compete with other work; it always ships first when it needs attention. That's baked into how we run.

**What NOT to expect:**

Big splashy quarterly launches. We ship small and often. If we shipped a big feature quietly, it made it into the changelog with a line — the changelog is the announcement.

A roadmap document that's revised quarterly with dates. Our roadmap is the changelog looking backward and this post looking forward. The dates are "when it ships."

Pre-announcements of features six months out. If we're not going to ship it in the next quarter, we're not going to pre-announce it.

**Rule of thumb.**

If you want to know what LADLE is doing, read the changelog for the last two months and this post for the next two. That's the whole picture, and the picture updates as we go.