VisionHow do you build in public on Twitter?
To build in public on Twitter (X), share the real story of your product as it happens: weekly progress, key numbers, decisions and mistakes. Pick a fixed rhythm, such as one update post every Friday plus short daily notes, decide in advance what stays private, and reply to everyone who asks questions.
Picture two founders shipping the same kind of tool in the same month. One works quietly and posts a launch link on day one. The other has spent ten weeks posting screenshots, small wins and one painful bug story. On launch day, the second founder has a few hundred people who already care how it ends.
That's the whole idea of building in public. You let people watch the work, so the launch isn't a cold start. It's simpler than it sounds, and you don't need a big account to begin.
What does building in public mean?
Building in public means sharing the process of making a product openly, including numbers, decisions and setbacks, instead of only announcing finished results. On X, it usually looks like short progress posts and a regular update thread.
Two well-known examples show how wide the range can be. Buffer runs an open metrics page and says it has been open about its finances and team salaries since 2013. The page is a public dashboard with monthly recurring revenue, active users and salaries.
Pieter Levels sits at the other end. His blog says he builds startups by himself, all bootstrapped, and he has written about building them since 2013. In 2014 he publicly committed to launching 12 startups in 12 months, mainly to force himself to finish and ship. One is a company-wide transparency policy. The other is a solo maker sharing the journey. Both count.
Why build in public on Twitter?
Building in public on Twitter gives you three things: trust from people who watch you keep showing up, early feedback before you waste weeks, and a warm audience on launch day. It costs nothing but some comfort.
Here's the thing about X. Short posts and replies make it easy for strangers to drop into your story at any point. A screenshot with one honest line can start a conversation with a future customer, a peer who solved the same problem, or someone who wants to help. Those replies are often worth more than the post itself.
What should you share when you build in public?
You should share progress, numbers that show direction, decisions with your reasoning and mistakes with what you learned. Keep anything that would hurt customers, staff or your security private.
| Share freely | Think twice | Keep private |
|---|---|---|
| Features shipped, screenshots, demos | Exact revenue in very small markets | Customer names or data without permission |
| Signups, users, growth direction | Pricing experiments while they run | Security details and internal tools |
| Decisions and why you made them | Conflicts with partners | Anything about staff that they didn't agree to |
| Mistakes and the fix | Fundraising before it closes | Legal or contract details |
If you're unsure about a post, ask one question: would a customer feel safer or less safe after reading it? That usually settles it.
A weekly rhythm to build in public on Twitter
A good weekly rhythm to build in public on Twitter is one plan post on Monday, short progress notes on two or three weekdays, and one Friday update thread. That's about five posts a week, which most solo founders can keep up for months.
- Monday: "This week I'm working on..." with one clear goal.
- Midweek: a screenshot, a small win, or a question for your audience.
- Friday: a short thread with what shipped, one number, one lesson and next week's goal.
X's help page on threads notes that you can add more posts to a thread after you publish it. You can keep one long-running thread and add each weekly update to it, so new readers can scroll the whole story. If drafting threads feels slow, the free thread maker splits your notes into posts.
How do you write a build-in-public update people read?
A build-in-public update people read leads with one concrete change, adds one number, explains one lesson and ends with a question. Four short parts fit in a single post or a three-post thread.
Here's a template you can copy:
- What changed: "Shipped CSV import this week."
- One number: "12 people tried it on day one."
- One lesson: "Half of them got stuck on date formats, so that's next."
- One question: "How do you handle messy dates in your app?"
The numbers in that template are only an example. Use your real ones, even when they're small. Small honest numbers build more trust than vague big claims. For more formats, see these Twitter content ideas for startup founders and the guide on writing threads people finish.
What mistakes should you avoid when building in public?
The biggest mistakes are posting only wins, sharing numbers without context, ignoring replies and treating updates as ads. People follow a build-in-public account for the honest story, so anything that feels staged breaks the deal.
Based on what I've seen, the quietest killer is ignoring replies. Someone asks a real question, gets nothing back, and stops following along. Reply to every genuine question, even with a short answer. To see which updates landed best, I built a free extension, XVision, whose growth dashboard rates each of your posts against your usual views. That shows which kinds of updates your audience actually wants. Once people start following along, the founder-focused guide on getting followers on Twitter as a founder helps you keep that growth going.
Where building in public leads next
Building in public turns your work into a story people want to follow. Share real progress on a steady rhythm, protect what needs protecting and answer every question. When it's time to ship, my guide on how to launch a product on X shows how to turn that audience into launch-day momentum. If you're a solo maker, the Twitter strategy for indie hackers covers how to fit all this around building. Post your first Monday plan this week.
Frequently Asked Questions
Should you share revenue when you build in public?
Sharing revenue when you build in public is optional, not required. Revenue posts attract attention and trust, and companies like Buffer publish theirs openly. Founders in tiny markets or with fragile deals may prefer to share growth percentages, user counts or milestones instead. Any honest number that shows direction works.
Is building in public risky for a startup?
Building in public carries some risk, mainly competitors copying ideas or customers seeing rough early work. Execution is usually harder to copy than an idea. Keep customer data, security details and live negotiations private, and the benefits of trust, feedback and a launch-day audience usually outweigh the risk.
How often should you post build-in-public updates on X?
Build-in-public updates on X work well at about five posts a week: a Monday plan, two or three short progress notes and a Friday recap. The exact number matters less than the rhythm. Readers come back when they know a weekly update thread arrives on the same day.
Can you build in public with zero followers?
Yes, you can build in public with zero followers. Early updates may get few views, but they create a public record that new followers can scroll later. Replying to other builders on X brings the first readers. Every well-known indie maker on X also started at zero followers.
What is the difference between building in public and marketing?
Building in public shares the process, including problems and small numbers, while marketing usually presents a polished result. Building in public on X earns trust over weeks and months. Marketing converts that trust into signups at key moments, such as a product launch or a new feature release.