A team of one is not a boast — it's an operating decision that follows from the meal-donation math. This page shows why growth at the pace typical for AI companies would break the promise this company was built on.
The math
LADLE's meal-donation commitment is $8 per subscriber per month. At 16,000 subscribers, that's $128,000/month to WFP. Our other operating costs (inference at Anthropic, infrastructure, contractor pay) currently absorb the other $12/subscriber. There is no material buffer. Adding a $180K salaried engineer requires $15,000/month in new subscription revenue just to break even, which means the marginal engineer needs to enable that much sustained additional MRR to be net-positive.
Why this is different from other companies
A standard SaaS company with the same MRR could reasonably hire 8-12 employees at Series-A stage. It works because the marginal $12 of gross profit per subscriber can absorb hiring costs while investors fund growth. LADLE doesn't have that buffer — the $8 is contractually committed to WFP, not available to redirect to salaries. Same MRR, materially different hiring capacity.
What we sacrifice
- Feature velocity: shipping 2 large features a quarter, not 6. Some features that would be built in a month at a bigger company take three months here.
- Coverage: no dedicated CS org, no sales team, no marketing hire. Every founder-role is functional but not maximal.
- Enterprise readiness: no dedicated CSM per account. Business customers get direct founder access, which is arguably a feature — but doesn't scale.
- Speed of expansion: adding new geographies, connectors, or verticals is slow because there's no team to spin up per initiative.
What we get
- Coherent product decisions. Two people make every call; nothing is diluted by committee.
- The meal donation stays intact. This is the whole point.
- Long runway on a small revenue base. We don't need a Series B to survive.
- The ability to say no easily. Feature requests we don't build stay unbuilt without political cost.
- Every hire we do eventually make will be high-leverage. No middle-management layer to create.
When we'll grow
The first employee hire (beyond the current contractor) will happen when: (a) revenue supports it without cutting the meal-donation split, (b) the marginal work of that hire is clearly load-bearing on the product's trajectory, (c) we've done a written analysis showing the hire meets both bars. If revenue growth outpaces our ability to hire responsibly, we'll take the extra buffer and increase the meal split rather than force-hire — that's part of what being a PBC lets us do.
What this means for candidates
If you're joining LADLE, you're joining knowing that the team will grow slowly and every new hire has to justify a lot. That's a bug for candidates optimizing for “work at a company that will be 500 people in 3 years,” and a feature for candidates who want to have a real impact on a small, high-leverage team.