Build in public
I think building in public is one of the most underrated shifts in how products get made and marketed. It's been around for a while, but it's hitting different now, and I want to talk about why.
The core idea
Building in public means sharing the process of creating your product with the world as it happens. Not after launch. Not in a polished case study. While you're in the thick of it. That includes things like product updates, lessons learned, decisions you're wrestling with, metrics, and even failures. The goal isn't to show off. It's to bring people along for the ride. Done well, it turns your build process into an interactive narrative that educates, inspires, and invites engagement. It's less of a tactic and more of a philosophy about how you relate to the people you're building for.
Why it actually works
The genius part about building in public is that you're marketing while you're building from day zero. You don't wait until the product is ready to start finding your audience. You build your audience while you build the product. Everything happens simultaneously. This is why you see something as basic as an expense tracker doing well. The product itself isn't revolutionary, but the creator built an audience around the journey of making it. By the time it launched, people already cared. There are a few reasons this works so well:
- Distribution from day one. Sharing progress gives people a reason to follow along before you even have a finished product. Over time, that audience turns into early users, partners, or advocates.
- Real-time validation. When you build in public, you're getting live feedback on what you're making. You learn what resonates, what doesn't, and what features people actually want, all before you've over-invested in the wrong direction.
- Trust and credibility. Transparency builds trust. People who watch you work through problems and make decisions are far more likely to believe in what you're selling than people who only see the polished end result.
- Community as a moat. The audience you build becomes genuinely invested in your success. They're not just customers, they're supporters who feel like part of the story.
The storytelling angle
Here's the thing that I think a lot of people miss: building in public is storytelling. You're not dumping every detail at once. You reveal things piece by piece, like a TV show rolling out its season arc. Each update is an episode. Each milestone is a plot point. Think about how Fortnite handles its seasons. They drip-feed the narrative over weeks, keeping people engaged and guessing about what comes next. Building in public works the same way. The slow reveal keeps people hooked. This is also why the early "build in public" trend of just posting revenue screenshots eventually lost its punch. People would share how much money they were making, and it would get attention, sure. But it didn't really capture what the movement was about. It was a flex, not a story. The people who do this well focus on the how and the why, not just the how much.
The old objection (and why it doesn't hold up anymore)
The classic pushback used to be: "Why would you tell everyone what you're building? Someone will just copy you." I get why people thought that. But it turns out, the risk of being copied is massively overblown compared to the advantage of having an audience that's watching you execute. Ideas have always been cheap. What matters is the execution, and that's exactly what building in public puts on display. And then AI came along and made this even more true.
How AI changed the equation
AI has reduced the friction of building software to almost zero. Writing code is cheap now. Someone with no technical background can describe what they want in plain English and get a working prototype. The barrier to entry for making apps has essentially disappeared. So if anyone can build the thing, what actually matters? Two things: the idea and the execution. The idea gives you direction. But execution is where building in public becomes your superpower. When dozens of people can ship a similar product in a weekend, the person who's been sharing their journey, building an audience, and earning trust for months has a massive head start. The product might be replicable. The relationship with the audience is not. This is why building in public is more relevant now than ever. It's not just a marketing strategy anymore. It's a survival strategy in a world where the technical moat has collapsed.
Who should build in public
Building in public isn't for everyone, and that's fine. It tends to work best for:
- Indie hackers and solo founders who rely on founder-led distribution
- Developer tools and creator products where the audience values transparency
- Community-driven products where early adopter feedback shapes the roadmap
- Anyone doing product-led growth where the product sells itself once people discover it
If you're running an enterprise sales motion or building something highly regulated, a more private approach might make more sense. The key is matching your transparency level to your audience and your go-to-market strategy.
Getting started
If you're thinking about building in public, here are some practical starting points:
- Start before you're ready. You don't need a finished product to start sharing. Share the problem you're trying to solve. Share your first sketches. Share the moment you write your first line of code.
- Pick your platform. X (formerly Twitter) and LinkedIn are the most common, but Reddit, Indie Hackers, and even YouTube work too. Go where your audience already hangs out.
- Be consistent, not perfect. Post regularly. It doesn't have to be groundbreaking every time. Small updates compound over time.
- Share the lows, not just the highs. People connect with honesty. A post about a mistake you made or a feature that flopped will often get more engagement than a win.
- Engage with your audience. Building in public is a two-way conversation. Respond to comments, ask questions, and genuinely listen to the feedback you get.
The bottom line
The way the scene has changed is so much different from what it used to be. In the past, the default was to build in secret and reveal with a big launch. Now, the smart move is often the opposite: start sharing from day zero, build your audience alongside your product, and let the journey itself become the marketing. Building in public isn't about giving away your secrets. It's about showing people you're worth paying attention to, one update at a time.
References
- "Building in public: Is this the right approach for your startup?" Mercury Blog. https://mercury.com/blog/build-in-public-or-private
- "The Case for Building in Public." Bubble Blog. https://bubble.io/blog/case-for-building-in-public/
- "A complete guide to building in public." Cobalt Blog. https://joincobalt.com/blog/the-power-of-building-in-public
- "Build in Public." Tyler Stupart, Blueprint DAO, Medium. https://medium.com/blueprint-dao/build-in-public-7e0c7b8880bf
- "Build-in-public strategy: Benefits + 10 examples." Paddle Blog. https://www.paddle.com/blog/build-in-public-boost-your-engagement
- "The Building in Public How-To Guide." Gaby Goldberg, Medium. https://gabygoldberg.medium.com/the-building-in-public-how-to-guide-219d417f00c1
- "Building in Public: Complete Strategy for Startups in 2026." Athenic Blog. https://getathenic.com/blog/building-in-public-complete-strategy-startups