What should I post when building in public?

Concrete artifacts of the journey: revenue and user numbers with screenshots, what broke and what it cost, decisions you made and why, and the occasional opinion your work earned. The test for every post: could a stranger learn or feel something specific from it?

Should I share revenue if it is embarrassingly small?

Yes, and small numbers often outperform big ones. "$87 MRR after 4 months, here is what I am changing" is relatable and rootable. Fake-big energy repels the exact builders you want following you.

How often should build-in-public posts go out?

A few per week inside your normal posting mix, not every post. All-updates accounts become diaries nobody reads. Mix in takes, teardowns, and replies; the cadence question is covered in the posting-frequency guide.

Does build in public actually get customers?

Indirectly and reliably: it compounds trust with the people most likely to buy founder tools, and launch-day attention is almost entirely a function of the journey you documented before it. It is a distribution asset, not a sales channel.

Build in Public: What to Actually Post (With Templates)

Tan · founder, VoicePostUpdated July 20263 min read

Build in public advice usually stops at "share your journey," which is how the timeline filled with accounts posting "day 47 of building!" over a screenshot of a to-do list. The genre works, but only the specific version of it. People follow journeys, not products, and a journey is made of numbers, failures, and decisions.

Building the thing in public means people will open your landing page. Run it through the free landing page roaster first: paste a URL and get three brutal fixes, one honest compliment, and your headline rewritten. No signup, three free roasts a day.

Here is what to actually post, as templates you can lift.

The 7 formats that carry the genre

1. The revenue update. The backbone. Number, delta, one insight, screenshot.

MRR update, month 4: $312 (+$95). The change: I killed the free plan. Signups dropped 60%, revenue went up. Here is the graph.

2. The failure writeup. Reliably the best-performing format in the genre, because it is the one nobody fakes.

I spent 20 hours building a feature nobody asked for. Zero users touched it in 2 weeks. Lesson: I built it because it was fun to build, not because anyone's workflow needed it.

3. The decision post. Show the fork in the road; people love weighing in, and replies are ranking fuel.

Deciding today: raise prices for new users or grandfather everyone and eat the margin. Here is the math either way. What would you do?

4. The time-cost confession. Specific waste is universally relatable.

The bug was one character. The debugging took 4 hours. The character: a comma in a cron expression.

5. The tiny win. Small, real, screenshot attached. The founder of SuperX posted a selfie celebrating 26 trial signups on launch day and it did 50,000 views. Real moments with real pictures stop the scroll; polished graphics do not.

6. The earned hot take. An opinion your work gives you the right to hold.

Unpopular after 6 months of building with AI: the model is never the moat, and it was never going to be. Distribution was the moat the whole time.

7. The launch-day story. The capstone: live numbers, what broke, honest surprise. Documented journeys make launch days; the launch-day mechanics are their own discipline.

The trap: performing instead of documenting

The genre dies when it becomes content about content: streak-keeping posts, engagement-bait polls, "big things coming" vagueness. The audience for build in public is other builders, and they have perfect detectors for performed authenticity. The rule that keeps you honest: document what happened, do not manufacture what posts well. If nothing happened today, reply to other builders instead; a reply-heavy day beats a filler post every time (the math is in how the X algorithm works).

The capture problem, and the fix

The real reason founders quit building in public is not shyness, it is that the material evaporates. The bug from Tuesday was a perfect post; by Friday it is gone. The fix is a capture habit: jot the moment when it happens, draft later. This is literally what VoicePost's memory bank does: you drop the raw note (shipped X, broke Y, MRR moved to Z), and the engine drafts the build-in-public post in your voice when the moment fits, with your real history available to cite. The blank compose box stops being the bottleneck.

Related: what to post on X when you have nothing to say covers the wider pipeline, how often should you post covers cadence, and the full growth system lives in how to grow on X in 2026.

Frequently asked questions

What should I post when building in public?: Concrete artifacts of the journey: revenue and user numbers with screenshots, what broke and what it cost, decisions you made and why, and the occasional opinion your work earned. The test for every post: could a stranger learn or feel something specific from it?
Should I share revenue if it is embarrassingly small?: Yes, and small numbers often outperform big ones. "$87 MRR after 4 months, here is what I am changing" is relatable and rootable. Fake-big energy repels the exact builders you want following you.
How often should build-in-public posts go out?: A few per week inside your normal posting mix, not every post. All-updates accounts become diaries nobody reads. Mix in takes, teardowns, and replies; the cadence question is covered in the posting-frequency guide.
Does build in public actually get customers?: Indirectly and reliably: it compounds trust with the people most likely to buy founder tools, and launch-day attention is almost entirely a function of the journey you documented before it. It is a distribution asset, not a sales channel.

Published July 4, 2026 · Updated July 4, 2026