Skip to content
Growth

The Myths People Believe About Building in Public

The myths people believe about building in public, what actually holds up in the sources, and a short FAQ on revenue, channels, effort and privacy.

By Published 8 min read

Flat-vector illustration of a glass-walled workshop at night with a laptop and a half-built product on the bench, small reply bubbles rising toward a lit path that leads to an open door.
On this page

Building in public does not mean posting your revenue, treating X or Indie Hackers as your entire marketing plan, or publishing everything you know about the product. The claims that hold up in the sources are narrower. Public updates help most when the people who would buy from you already read those feeds. The useful posts are specific: a decision, a miss, a challenge, or a change, rather than a vague progress note or a product link on every update. And the habit works as one channel, not as a substitute for talking to users.

Founders keep asking the same things. A thread on r/indiehackers asked whether building in public is important. On Indie Hackers, a founder with an MVP still asked what to put in the posts: revenue, features, feedback, mistakes, or all of it.

Myth: Building in public is the marketing you need

What actually holds up

In a 2023 Indie Hackers roundup, Cory Zue of SaaS Pegasus put this plainly. Early on, he wrote, you might think building in public is the only form of marketing you need, when it is usually a pretty terrible channel unless your product is aimed at other indie hackers. The cost is the time you do not spend learning channels your actual users already use. Ayush Chaturvedi, in the same piece, said people starting out romanticize it, and that the people who keep it going treat it as one strategy inside a larger business. Zue also said he would not make it his primary or only marketing channel if he were starting from scratch. Public posts can still help you test whether a problem is real, but they do not replace conversations with people who have that problem.

Myth: Posting on X or Indie Hackers will bring customers, whatever you sell

What actually holds up

Audience fit matters more than the habit of posting. Chaturvedi used a direct comparison in that roundup: if you are building a Twitter tool and your audience is on Twitter, posting there can make sense. If you are building a SaaS for HR professionals and you expect to get customers by building in public on Twitter, that is not going to work out. Zue made the same point from the other direction: it works best when the product is for people who already follow this style of update, such as developers or other indie hackers. If your buyers are not in those feeds, the posts may still help you think out loud or meet peers, but they will not find your users for you. Do that work where those buyers already spend time, or use this walkthrough of Reddit and Indie Hackers for first users when that is genuinely the right room.

Myth: You have to share revenue, or it does not count

What actually holds up

Revenue is optional. Buffer's open metrics page has included company finances and team salaries, starting in 2013, which sits at the open end of the range. That is a company choice, not a requirement for every solo maker. In the same roundup, Zue warned against posting MRR numbers all the time even though they consistently get engagement. He called that a cheap hack that attracts an uninteresting, uninvested audience. When Ryan Morrison asked what to share, revenue was one option on a list that also included features, feedback, and mistakes. You can share a number if you are comfortable keeping it public. You can also share none.

Myth: The point is to grow a large audience quickly

What actually holds up

John Ladaga, quoted in that roundup, compared using building in public to grow a quick audience and attract a ton of users to writing one blog post and hoping it ranks at the top of search. He called it a long-term game. Engagement on revenue posts, as Zue noted, is a weak signal: the people who react are not automatically buyers or useful contacts. A reader still needs a clear product page and a next step. A listing you add on IndieNeed gives them that page, and products going live today are examples of how those pages are written. Public posts also sit alongside other early channels in this guide to the first 100 users.

Myth: You should only post wins, or wait until the numbers look impressive

What actually holds up

A lot of the pressure comes from waiting for a milestone before writing anything. ScottPlusPlus wrote about what to share before a dream MRR and argued that expertise and success stories are not the only useful accounts. The prompts he listed for writing earlier are ordinary: a day's work, a mistake, advice that has not worked, a hard lesson learned again. Sameer Sanagala set four rules when he started posting after building in silence. The first was not to share only upticks and milestones, but also when things were not going in his favor. He also argued against posting only final decisions, and against simply dropping product links and marketing numbers. ScottPlusPlus was explicit that he could not claim this style produces a given number of followers.

Myth: You should either polish every post or post constantly on every channel

What actually holds up

Zue described two approaches that, in his view, both work. One is to put very little effort into it and share what you are doing at that moment. The other is to put a lot of effort into a piece that might be widely shared, such as something that could reach Hacker News. The mistake he sees is the middle: putting a fair amount of effort into something mediocre that will not get broadly shared, which he called a bad use of time. Consistency shows up as Sanagala's fourth rule, and as ordinary advice in ScottPlusPlus's piece, but neither source gives a posting quota.

Myth: Building in public means sharing everything

What actually holds up

The phrase sounds like total transparency, and some comments on the Indie Hackers "what should you share" thread do say "share everything." That is one preference, not a standard. Igor Lanko suggested thinking about what you would discuss with a friend about the product, and not using every post to plug it. Platform rules already limit what you can post about other people. Under Reddit's site-wide rules, you must respect other people's privacy, must not reveal someone's personal or confidential information, and must follow each community's rules and not spam. Customer data, security details, and anything under a contract sit on the private side of that line even if a thread is asking for "all of the above."

Myth: Skipping it protects the idea; doing it means you will be copied

What actually holds up

Both versions oversimplify the same fear. Zue said that at an early stage, ideas are not that useful, and that building in public does not matter much on that front. Where it can hurt, he wrote, is later, once you are making real money (his example was $10k a month or more), because it can make potential competitors aware of a market opportunity they might not otherwise see. He also said that sharing revenue and how the business works attracted and helped copycats as the company matured, and that the downsides can start to outweigh the advantages. Chaturvedi listed copycats as a real downside, not a rumor. The risk grows as the business becomes worth copying, which is a reason to be careful with mechanics and numbers, not a reason to hide an untested idea.

FAQ

Do I have to post on X, and only on X?

No. In the what should you share thread, J Read asked whether it is only Twitter. Post where the people you want to reach already read; X is a common default because many indie makers are there, not because it is required. If you use Reddit, read that community's rules first; Reddit's own rules require authentic participation and no spam.

How often should I post?

The sources do not give a number that works for everyone. Sanagala's fourth rule was to be consistent. Zue's low-effort approach is to share what you are doing when you are doing it, which only works if you can keep it going.

Can this replace talking to users or a launch plan?

No. Chaturvedi warned about being misled into thinking that building in public is the marketing for your product. If a public launch is close, this 2026 launch-order piece maps the other places to appear, and once the product is live, this four-week promotion plan is about acting on feedback, which is a separate job from posting for other founders.

What if I only have other makers following me?

Then you are seeing the limit of the channel. Zue and Chaturvedi both said the posts work best when your product is for the people who already follow this kind of update. Other makers can still give useful feedback or introductions, but that does not make them buyers. Judge the time by feedback, signups, or contacts, not likes.

If people do follow along, how do they actually try the product?

They need somewhere that states what the product does, plus a next step such as a waitlist, a beta form, or a live listing. Put the product URL in your profile and include it only in some of the posts; Igor Lanko argued against plugging the product in every update. Submit the product for a public page people can open after a post, or browse today's launches for listing examples.

Launch your product on IndieNeed

Free to submit, hand-reviewed, and you pick the launch day.

Submit a product

Products to explore

  • Market Verdict logo

    Market VerdictFeatured: a paid launch

    Validate business ideas with a data-driven viability score.

  • DevTV logo

    DevTVFeatured: a paid launch

    A TV-style browser app for developer content. No backend.

Related articles