Why we build in private

If you came here looking for a roadmap, you will not find one. There are no teaser pages, no waitlists counting up, no rendered screenshots of software that does not exist yet. What we are building stays private until it is ready to be used — and that silence is a policy, not an oversight.

Announcements are loans

The moment you announce a product, you start paying interest on it. A public feature list becomes a contract with strangers. A launch window becomes a deadline that negotiates against quality, and it usually wins. Expectations compound quietly until the honest options — cut this, rethink that, walk away entirely — start to feel like defaults on a debt. For a small company, that is exactly the leverage that turns good judgment into sunk-cost reasoning.

Building in private keeps our decisions reversible. A prototype is allowed to fail and tell us so. A feature that does not earn its keep can be removed without a changelog apology. The product that finally ships is shaped by what we learned building it, and by nothing we once promised a landing page.

What the quiet costs

From the outside, private looks identical to idle. There is no drumbeat of announcements to signal momentum, nothing for an algorithm to amplify, and no way to tell the difference between a company working carefully and one doing nothing at all. We accept being underestimated in the meantime; it is cheaper than the alternative.

The product is the announcement.

When the first product is ready, it will simply appear here, working, with its trade-offs named the way we name them in these essays. If you would like a nudge when that happens, send us a short email — that is the entire mailing list, and the reply is the entire subscription.