Build in public: launch your SaaS out in the open

You're building your SaaS heads-down in your corner, telling yourself you'll start talking about it "when it's ready." The problem is that on launch day, nobody is waiting for you. You hit publish, and it's silence.

Building in public flips that logic. Instead of keeping the secret until release, you build out in the open: you share your progress, your numbers, your decisions and your mistakes as they happen. The result is that you don't launch to an empty room, you launch to people who have been following your story for weeks. And some of them become your first users.

What building in public actually means

Building in public isn't "posting once in a while." It's a stance: making the process of creating your product visible, continuously. A design you can't decide on, a bug that cost you two days, your first sale, your first refund. Everything that usually stays hidden behind the polished landing page.

The idea isn't new, but one founder made it famous. Pieter Levels spent about a decade building an audience of several hundred thousand followers by launching product after product out in the open, numbers included. When he shipped Photo AI, that stockpile of attention made all the difference: the product went from 0 to 132,000 dollars in monthly recurring revenue in eighteen months, solo, documented publicly step by step (Indie Hackers case study).

Note the mechanism carefully: it isn't transparency itself that sells. It's that by sharing, you build an audience of people who trust you before they ever reach for their card. You replace the ad budget with earned attention.

Nobody is waiting for you on launch day. Unless you told the story before.

Why it works when you're starting from zero

Building in public is one of the rare acquisition strategies that requires neither budget nor a starting audience. It requires consistency and a bit of nerve. Here's why it fits a founder looking for their first users so well.

These figures come from the same founder, and that's exactly the point: they show that the explosive launch (a product that hit one million dollars in annualized revenue in seventeen days) isn't luck. It rests on years of accumulated attention from building out in the open. You don't start from zero on the big day, you start from the capital you built before.

Three concrete reasons it works for you, now:

• You build your audience and your product at the same time. Every post is also a temperature check. Reactions tell you which feature actually interests people, before you code it.
• Transparency attracts. On indie maker platforms, posts that show real revenue numbers generate far more engagement than vague "making progress" updates (Indie Hackers analysis). Specifics stop the scroll.
• You document your credibility. When a prospect hesitates, your public track record of progress is worth a thousand sales arguments.

What to share (and what to keep to yourself)

The beginner's mistake is to share only the pretty feature announcements. But what creates the bond is the road: the doubts, the numbers, the decisions. Here's how to sort it out.

What you can keep to yourself: sensitive code, your users' data, and any number you couldn't stand behind publicly. Building in public doesn't force you to spill everything, it forces you to be truthful about what you show.

Which channels to build in public on

You don't need to be everywhere. You need one main channel where your audience already hangs out, and to be consistent there. Here's how to read the big three.

The right instinct isn't to pick "the" perfect channel, but the first one, the one that fits your audience. You go all in on it for a month, you measure, and you adjust. One channel taken seriously beats three lukewarm ones.

Your build-in-public routine, week by week

Building in public almost always fails for one reason: irregularity. Three enthusiastic posts, then nothing for a month. Here's a sustainable routine, even while building your product on the side.

The traps that make building in public useless

Plenty of founders build in public without ever landing a single customer. Almost always because of one of these three traps.

The second trap is number narcissism: sharing vanity metrics (likes, views) instead of what matters to your business. Your audience doesn't care about your impressions, it wants to see a product that solves a real problem move forward.

The third is believing that building in public replaces a strategy. It feeds your acquisition, it doesn't define it. You still need to know which channel to scale and exactly who you're talking to. Building in public without direction is regular noise, not growth.

Where to start this week

Building in public isn't a separate project, it's a habit to graft onto what you're already building. Pick a channel, open a notes file, and post your first number this week, even a small one. The first post is always the hardest, then it rolls.

To turn that audience into first users, combine it with the right levers: a waitlist to capture the people following you, the method to find your first 10 customers one conversation at a time, and a real content strategy so your building in public doesn't fizzle out. It's also the best way to spot your early adopters, the ones who buy before the product is perfect.