May 5, 2026
Designing for the day this works
Why design decisions get pressure-tested against a hundred thousand users, not against the dozen we have today.
ForestLynk is small. Tens of users; all of them me. That’s the wrong baseline to optimise against.
The product thesis depends on reaching scale. A forest is more interesting with a few thousand people in it than with twelve. So the shape-of-the-thing decisions get pressure-tested against a hundred thousand users, not against today.
What that rules out
Anything priced per user, per message, or per device on a critical path. There are services that look free at our current size and look like a rewrite at a hundred thousand — the same product, two different bills, the difference paid in the period when switching is most expensive.
So the realtime layer is ours. The notification path is ours up to the point where the operating system takes over. Storage runs on infrastructure we operate.
What that doesn’t rule out
Spending money. The principle isn’t to be cheap. It’s to make sure the unit economics work at scale, not at demo size.
Why now
Because the day this works, it works fast. Network-effect products either reach an inflection point or they don’t. The infrastructure choices we make at twelve users need to still be right at a hundred thousand. Otherwise “this is going well” turns into “we need to rewrite the realtime layer”, and that’s a bad week to be having.