Why we build in public
We share our process, our stack, our failures, and our decisions openly. Not as a marketing strategy, but because we think it makes the work better.
Building in public is a term that has become entangled with growth hacking and audience building. We don't mean it that way.
For us, sharing our process openly is a design discipline. When you know you're going to write about a decision, you make that decision more carefully. When you articulate why you chose one approach over another, you often discover that your reasoning has gaps.
There's also a practical benefit: the people who reach out to work with us after reading a post about our process are better-fit clients. They understand how we think. The conversation starts from a more honest place.
We're not sharing everything. Client work stays private unless the client explicitly wants to be featured. Internal team conversations are internal. But our approach to craft, our stack decisions, our product philosophy: those are worth putting into the world.
If something we've written has been useful to you, that's the point.