Why we don't sell teams (yet).

LADLE has a business page. It says: same $20/seat as consumer, no annual commitment, monthly impact reports on request. That's true, and companies do subscribe their teams that way today.

What we DON'T have yet is a proper team product. No shared workspace where colleagues can see each other's chats. No admin dashboard for a team lead to manage seats. No SSO integration with Okta or Google Workspace. No org-level data controls beyond what individual users already have.

Companies who subscribe today set up individual accounts for each teammate, expense the seats on a company card, and use LADLE as N-individuals-with-shared-billing rather than N-users-of-a-collaborative-product.

Here's why we haven't built more.

**Reason one: the collaboration features that matter are hard to get right.** Shared workspaces make sense when there's a workflow where two people naturally need to see each other's context. Most AI assistant usage isn't like that. Writing an email doesn't need collaboration. Reviewing code doesn't need collaboration. Research doesn't need collaboration until you're writing the report, at which point Google Docs is a better collaboration surface than a chat product would be. We haven't seen a compelling case for "our team needs to share this AI chat" that Slack + a shared doc doesn't solve better.

**Reason two: admin dashboards are surface area we'd have to maintain forever.** A proper team admin dashboard means seat management, invite flows, role permissions, per-user usage caps, org-level SSO, audit logs, data export controls at the org level. Every one of those features is a small forever-cost of maintenance and support. We'd want them to serve a real need, not to check a box for procurement.

**Reason three: LADLE's value prop is unusually simple, and team features can complicate the pitch.** "One AI subscription. $8 of every seat funds meals through the WFP. Same product for solo users and companies." Adding a team tier introduces "well but the team version has..." into every conversation. We're not in a hurry to complicate that.

**What would change our minds:**

If more than a small handful of businesses tell us their procurement or IT process actually needs SSO or an admin dashboard to say yes, we'll build the specific piece that unblocks them. Not the full team suite; just what's needed.

If we get repeated asks for a specific collaboration primitive (shared prompts library across a team, for example), that specific thing is probably a good build.

**What we already do that helps teams:**

The monthly impact report — PDF, CSV, or JSON — is available to any subscriber. If your team is subscribed and the CFO or CSR lead needs a report of what the team funded to WFP this month, we generate it on request. That's already built and available now.

The business page also has a procurement Q&A: DPA availability, subprocessor list, data flow diagram, security incident history. Everything a vendor-review team asks for in the first round.

So — no shared workspaces yet. If your team is buying seats, it works today. If your team needs specific team features and can't move without them, tell us which ones. The list of what we build next is driven by what you actually ask for.