Individual seats, compounding earmarks.
There's no Teams plan yet. Here's how small teams use LADLE today — everyone on their own $20 subscription, shared Project context, and $8 per seat per month earmarked into the meal fund toward a real partnership with the hunger-relief charity we select.
How small teams actually collaborate today.
Everyone runs their own LADLE. One person maintains the team's 'context Project' (voice guide, key docs, shared standards) and exports it periodically for others to import. Not elegant, but it works and it's honest — we'd rather ship one product well than a broken Teams tier.
One voice guide, five seats using it.
The one thing that's actually worth standardizing across a team is voice. Publish a Project with your style rules and everyone imports it. Consistent house style without a Teams plan, without a Notion doc no one reads.
Ten meals reserved per seat. Every month. Publicly.
A 5-person team on LADLE reserves 50 meals every month. A 50-person team reserves 500. The math compounds — and every earmark shows up in the same public monthly fund report you can share with your team, on the road to a real partnership with the hunger-relief charity we select.
A team on individual LADLE subscriptions reserves N × 10 meals per month into the meal fund (pooled toward a real partnership with the hunger-relief charity we select), and every seat costs the same as an individual subscription — $20.
Questions.
A Teams tier would fracture the meal accounting, add compliance work (SOC 2, SSO integrations, admin controls) we can't sustain at our current size, and pull us into an enterprise sales motion we don't want to build. When it's genuinely worth it — a few thousand serious inbounds — we'll build it and price it so the meal-fund math still works.