Most products are built behind closed doors and revealed with a launch post. We're trying something different: shipping early, sharing progress, and letting the work speak as it evolves.
The case for transparency
Building in public does three things well. First, it keeps you honest — when your progress is visible, you tend to make real progress instead of hiding behind planning. Second, it attracts early users who care about the process, not just the product. Third, it compounds learning across the whole portfolio, because each project's lessons feed into the next.
What "in public" actually means for us
We're not livestreaming every commit. Building in public, for us, means:
- Sharing what we're working on in this journal
- Publishing product updates before they're polished
- Being transparent about what's working and what isn't
- Inviting feedback from early users and builders
The trade-offs
Transparency has costs. You expose rough edges. Competitors can see your moves. Some ideas will be shared before they're ready. We think the benefits outweigh those risks at this stage — momentum and trust are worth more than secrecy when you're starting out.
If this resonates, follow along. If you disagree, we'd love to hear why — reach out at [email protected].