Unpopular opinion: "Build in public" is slowly becoming an echo chamber.
by•
Don't get me wrong—sharing progress is great for accountability.
But lately, it feels like 90% of "build in public" posts are just founders selling tools, templates, or courses to other founders, rather than talking to actual end-users.
If your target customer isn't an indie hacker, posting MRR screenshots on X won't move the needle.
Am I wrong here, or are we spending too much time optimizing for founder validation instead of customer acquisition? Curious where everyone stands.
33 views


p/runevr
p/producthunt
p/google-cloud-platform
p/reso
p/many-displays
p/slotify-2
p/airuncode
p/ai-context-flow
p/kodlo
p/aperture-7
p/lasso-11
p/raycast
p/dino-kids
p/supabase
p/jev
p/kuc-kuc
p/offiai
p/murror
p/dex-by-exmergo
p/htmldrag
Replies
Agree, and it gets sharper when your users aren't founders at all. Ours are mostly students and early-career job seekers. None of them read MRR threads.
One small thing we noticed on our own LinkedIn page: document (carousel) posts got more impressions and far more clicks than videos posted the same week. Tiny numbers, but it pushed us toward writing useful things for job seekers instead of progress updates for other builders.
Where do your actual users spend their time? That feels like the real question behind this.
@bhavishyasingla1 Spot on. The "MRR thread" trap is real—founders end up marketing to other founders instead of their actual ICP.
Love the document post insight, too. For students and job seekers, swipeable, bite-sized value beats a 2-minute video every time.
For us, our users are mainly on [e.g., Reddit and niche Discords], mostly looking for answers when a specific problem hits rather than casually scrolling. It really forces you to shift from "hype marketing" to "problem-solving content."
The Build in Public scene is great for people just getting started - some of my most cracked founder friends started in the BiP / indie hacker scene but universally found it eventually limited them.
The community is so anti-VC and anti-growth it usually stunts them - things like a fear of paid media, etc. is usually pretty damaging once you reach a certain scale.
Still a big fan of building in public and founder-led content but the community most people associate with BiP is becoming pretty toxic.
@elliotpadfield Really well put. I’ve seen this exact ceiling play out: founders crush the first $5k–$10k MRR through sheer community goodwill and BiP hype, but stall out when they need repeatable, unglamorous distribution channels (paid ads, enterprise outbound, SEO).
The shift from "sharing my journey" to "running an actual customer-focused business" can feel almost like a betrayal in those circles.
Do you think founder-led marketing can survive long-term without getting dragged into that echo chamber, or does it inevitably force founders to pivot their brand identity as they scale?
It's not really the approach itself that's the problem, but rather its implementation.
It's like calling a watch a bad tool for hammering nails.
From my perspective, one of the underrated benefits of building in public is the value it creates for subscription-based products. People can see that when they buy a yearly subscription, they're not just paying for the product as it exists today. By looking at the public development history, they can get a pretty good sense of whether they'll receive a steady stream of useful improvements over the coming year... or not.
In a way, a public track record reduces the uncertainty that comes with subscriptions. Customers aren't just evaluating the current feature set; they're evaluating the team's demonstrated ability to keep shipping.
@generalgda Love the watch-and-hammer analogy, and that point on annual subscriptions is brilliant.
There’s a crucial distinction between vanity BiP (tweeting Stripe dashboards to other founders) and utility BiP (public changelogs, roadmaps, and consistent shipping cadence for actual users).
When customers buy annual SaaS, they’re essentially underwriting a team's shipping velocity. Seeing a steady stream of bug fixes, community-requested features, and transparent updates de-risks that bet completely. That’s BiP at its best—using transparency to build buyer trust, not just social clout.