Building in public is one of the most misunderstood growth strategies for indie hackers. Most people think it means tweeting your MRR dashboard. It doesn't. After two years of doing this across DocAPI and FarmPosts — and getting multiple viral posts on LinkedIn — I can tell you the actual system. This is the building in public guide I wish existed when I started.
What building in public actually means
Building in public is not a highlight reel. It's not "we hit $1k MRR." It's sharing the messy middle — the failed launches, the features you built that nobody wanted, the pivots you made at 11pm when the metrics came back wrong.
The people who do this well share the question they couldn't answer, not just the answer they found. They share the month revenue went down, not just the month it went up. They post the launch that got 4 upvotes, not just the one that hit the front page.
This matters because the value of building in public comes from authenticity, not from optics. When you share real struggle, you attract people who are in that struggle. Those are your users. Those are your collaborators. Those are the people who reply with "I built something similar — want to talk?"
Most people stay quiet during the hard parts and then show up with a polished win. That's not building in public. That's a press release.
Why building in public works
The mechanism is an accountability loop backed by a distribution engine. When you write "I'm shipping X by Friday," you ship X by Friday — not because anyone is watching, but because the act of writing it down makes it real. I've shipped things I would have let drift for weeks simply because I'd announced them publicly.
Beyond accountability, the compounding distribution effect is real. Every post you publish is a searchable artifact that says "this person ships things." Over 18 months, that artifact trail is worth more than any cold outreach campaign. People who find your post from 14 months ago don't know you were unknown then — they see someone with a consistent history of shipping.
The other underrated mechanic: early users before launch. When I launched DocAPI, I already had 200+ people who'd watched me build it for months. The launch worked because the audience existed. That audience came from building in public. It's a self-reinforcing loop once you have enough reps.
I wrote more about the distribution side of shipping early in my post on shipping before you're ready — the two strategies compound together.
The content calendar system for building in public
Here's my actual cadence. Not aspirational — actual.
Every Tuesday morning: ship update. What launched, what changed, what's next. If nothing shipped, why not. This is short — 3 to 5 sentences on LinkedIn, slightly longer thread on X. The discipline is the consistency. I do not skip Tuesdays.
Every first Monday of the month: transparency post. Numbers, lessons, one thing that surprised me. Revenue, user counts, notable wins and losses. I've published months where the numbers were embarrassing. Those posts consistently outperform the good-news months in engagement because they're honest.
Whenever something interesting happens: the viral take. A failed launch, a weird metric pattern, a counterintuitive lesson. These are not scheduled — they happen when something worth saying has happened. These are the posts that get 50k impressions.
The mistake most people make is skipping the cadence posts (Tuesdays and monthlies) and only posting the viral takes. That means you go dark for weeks. Consistency is what builds trust. The viral posts are what accelerate it.
What to share — and what to skip
Share:
- Revenue numbers, even if they're small. "$340 MRR after 3 months" is more useful to your audience than silence.
- Specific mistakes with a specific lesson. "I built a feature for 3 weeks that 0 users have touched" is better than "I've been learning a lot."
- Pivots with the actual reasoning. Not "we're evolving the product" — "we killed the API tier because 100% of revenue came from the dashboard tier."
- Metrics with context. Not "up 40%" (from what?) — "from $230 to $322, mostly from one LinkedIn post hitting on March 3rd."
- The question you couldn't answer. "I have no idea why retention is 40% for users who find us through Google and 80% for users who come from HN" is a post that attracts exactly the people who can help.
Skip:
- Vendor specifics that could backfire. Don't name the payment processor that failed you.
- Customer details. Never, ever.
- Percentage gains from a tiny base without the absolute number. "300% growth" when you went from 1 to 4 users is noise.
- Anything that embarrasses someone else. Ex-employees, investors you pitched, co-founders you split from.
The filter I use: would a founder 6 months behind me find this useful? If yes, post it. If it's purely ego management — either polishing a win or dramatizing a loss — skip it.
Honesty is the whole mechanism. I wrote about this more directly in never lie about your business — the same principle applies to every public post.
Which channels work for building in public
LinkedIn is my primary channel. This surprises people, but LinkedIn has the highest organic reach of any platform right now for B2B content. A post that would get 200 views on X gets 8,000 on LinkedIn with the same content. If you're building anything with a professional or B2B angle, LinkedIn is where you post first.
X/Twitter is for developer audiences and real-time feedback. Threads do well for technical content — the architecture decisions, the stack choices, the API design tradeoffs. The engagement is lower in reach but higher in signal. The people who reply on X tend to be the people who understand what you're actually building.
HN is for technical deep-dives that can stand alone as essays. "How I built X in Y" or "What I learned after Z months of Z" can hit the front page. The key is the post has to be genuinely interesting to a technical reader, not just a product announcement.
Reddit works for specific niches. If you're building for founders, r/entrepreneur and r/SaaS. If you're building for developers, r/programming. Don't try to spam — participate in threads where you have something to add, and link to your writing when it's genuinely relevant.
Your blog is the long game. A LinkedIn post disappears in 72 hours. A blog post compounds for years. I write about the indie hacker path and what actually matters long-term — the same compounding logic applies to content.
The practical rule: write the content once (the ship update, the lesson, the monthly number), then reformat for each channel. LinkedIn gets the punchy version. X gets the thread. The blog gets the full context. Don't write four separate posts — write one post four ways.
How the compounding effect works in practice
The first 50 posts feel like shouting into the void. You will get 12 views, 3 likes, zero replies. This is normal. Every person doing this successfully felt exactly this. The mistake is interpreting low engagement as a signal to stop.
Posts 51 through 100 are where things shift. You'll start getting replies from people who've been quietly reading. You'll get a DM from someone who wants to collaborate. One post will get picked up and shared by someone with a bigger audience. Your follower count starts moving.
By the time you have 150+ posts across platforms and 18 months of consistent output, the audience you've built is real. Those people already know what you're building, already trust your judgment, and will show up on launch day because they feel like they've been part of the process.
This is why building in public needs to start before you have anything to sell. The revenue report I published for DocAPI and FarmPosts worked because the audience existed — and that audience was built almost entirely through two years of public updates, not advertising. Building in public is just one layer of the strategy — for the complete picture of how to build and ship an AI product as a solo founder, see the full indie hacker AI product guide.
What to post this week — a concrete starting template
Stop waiting for the right moment or the right strategy. Here's what to post depending on where you are right now:
If you shipped something this week: Write the ship update. 3 sentences: what you built, why you built it, what you're going to watch. Post it Tuesday morning.
If you learned something this week: Write the insight. One concrete lesson, with the specific situation that caused it. "I learned that..." followed by the actual thing you learned, not a vague observation.
If a metric changed: Post the number with context. The absolute number, the change, and one sentence on what you think caused it. Don't post a percentage without the base.
If you made a mistake: Post the mistake and the lesson. This is the most valuable content you can create. It helps everyone behind you and it makes you more credible to everyone ahead of you.
If you did all of the above: Pick the most honest one. Post that.
The minimum viable commitment is one post per week. It doesn't have to be long. It doesn't have to be polished. It has to be true.
FAQ
How do you start building in public?
Post one update this week about what you shipped, learned, or measured. You don't need a strategy first — you need a first post. Tuesday mornings work well for engagement. Write 3–5 sentences, post it, and repeat next week.
What should you share when building in public?
Revenue numbers (even small ones), mistakes, pivots, specific metrics with context, and the questions you couldn't answer. The filter: would a founder 6 months behind you find this useful? If yes, post it. If it's just ego management, skip it.
Does building in public actually drive users and revenue?
Yes, but it compounds slowly. The first 50 posts feel like shouting into the void. By posts 51–100, posts start getting shared and DMs start arriving. The audience you build before launch is what makes the launch work — that's the actual ROI.
Which platform is best for building in public?
LinkedIn for B2B and professional audiences — it has the highest organic reach of any platform right now. X/Twitter for developers. HN for technical deep-dives that can stand alone as essays. Your blog for SEO and long-term compounding.
How often should you post when building in public?
At minimum, once per week. The cadence that works: a weekly ship update every Tuesday, a monthly transparency post with numbers and lessons, and one-off viral takes when something interesting happens. Consistency in the weekly posts is what builds the trust that makes the viral posts land.