Concrete build logs
Day-by-day updates showing shipped features, fixes, experiments, launches, and specific artifacts rather than vague progress.
32%
Best tweets about Build in Public
Browse the best tweets about building in public, from launch updates and revenue milestones to transparency, audience feedback, distribution, and lessons.
Genuine build-in-public updates with decisions, numbers, customer feedback, progress, failures, launches, and lessons rather than empty promotion.
Original Xholic analysis
The strongest build-in-public updates show the work: what shipped, what customers said, which numbers changed, and why a decision followed. The conversation also questions whether public attention reaches buyers or distracts from execution. Founders disagree about how much to disclose, but specific lessons offer more than a posting streak or a celebratory screenshot.
38% of posts
All-time engagement
46% of posts
Published in 90 days
Conversation map
Day-by-day updates showing shipped features, fixes, experiments, launches, and specific artifacts rather than vague progress.
32%
Revenue, MRR, signups, visits, reviews, and milestones shared with context about how they happened or what they mean.
32%
Critiques of vanity metrics, posting streaks, generic diaries, and optimizing for applause instead of useful evidence or product outcomes.
32%
How public documentation creates accountability, feedback, credibility, relationships, waitlists, leads, and customers—and why founder engagement alone may not convert.
32%
Failed launches, churn, slow weeks, doubts, bugs, and wrong turns shared alongside wins and the lessons they produced.
28%
The reasoning behind product changes, killed features, pivots, onboarding fixes, customer feedback, and unmet demand.
26%
The time cost of posting, copycats, exposed leverage, and the choice to share tested lessons while keeping sensitive strategy private.
20%
Tone and stance
Performance benchmark
Posts with media make up 26% of this collection. Their median all-time score is 14.1, compared with 5.38 for text-only posts.
Format mix
Consensus and debate
Shared view
A screen recording, onboarding change, bug fix or launch result gives readers something concrete to examine. Explaining the user behavior or feedback behind the change makes the update useful beyond the founder’s diary.
Shared view
Signups and revenue are more informative alongside the actions or problems behind them. One launch update reports 359 users but $0 revenue; another pairs visits and signups with nine difficult reviews.
Shared view
Posts calling for failed launches, churn, doubts and wrong turns argue that wins alone leave out the decisions others could learn from. A founder’s failed SaaS launch offers a concrete example of posting when things go wrong.
Open debate
Some founders describe public history as a source of accountability, credibility and prospective customers. Others warn that exposed features, finances or strategy can help competitors and create unwanted attention.
Open debate
One view favors specific revenue figures as evidence; another says founders can build trust through lessons, mistakes and decisions without revealing sensitive customer details, churn reasons or live roadmap bets.
Open debate
Founders credit public sharing with leads and launch signups, while critics point to peer praise without paying customers and the time spent turning execution into content. The posts present competing experiences, not a guaranteed growth playbook.
What performs
In the supplied analytics, numbers and traction and concrete build logs each cover 16 tweets (32%). Their median all-time scores are 9.75 and 5.3, respectively; theme membership and scores do not establish why a post performed as it did.
The 13 posts with media have a median all-time score of 14.066, versus 5.384 for text posts. Announcements have a 9.98 median and opinions a 5.351 median; these descriptive differences do not show that media or format caused engagement.
Statistical standouts
Creator landscape
The five most represented creators account for 20% of the selected posts.
1. Alexa | Startup founder
@alexabelonix
2 posts
2. Andrew Zacker
@andrewzacker
2 posts
3. David Ch
@chhddavid
2 posts
4. Hardik Gohil
@GohilHardy
2 posts
5. Layton Gott
@Layton_Gott
2 posts
6. Marcos Placona
@marcos_placona
2 posts
Hardik Gohil’s two updates move from initial setup and authentication to named product changes and a user source. Layton Gott’s two posts argue for sharing real numbers and difficult weeks, not only wins.
Alexa’s paired posts ask founders to explain failed offers, repeated customer feedback and changed minds while keeping sensitive leverage private. Marcos Placona similarly contrasts audience-friendly milestones with decisions made for accountability.
Since the previous snapshot
Themes, sentiment, stance, and post format are classified per tweet. All counts, shares, medians, creator concentration, freshness, and performance comparisons are then calculated directly from the published snapshot.
Xholic's all-time score compares engagement while accounting for reach, post age, and creator consistency. It is used for relative comparisons within this collection.
This report analyzes the exact 50-post snapshot shown below. AI identifies editorial categories and drafts explanations; all statistics are calculated from the snapshot, and every narrative claim is checked against cited posts before publication.
Best Build in Public tweets
Ranked 01–50
@zarazhangrui ·
Tip for building in public: If making content feels like extra work, show the work already happening inside your product. A tiny screen recording, the first version, or the user behavior that changed your design. The reasoning matters more than production value.
@OnatAksaray ·
Building in public vs building in silence: Building in silence: - No accountability - No feedback - No connections - No opportunities - No one knows you exist Building in public: - Daily accountability - Real-time feedback - Friends in your niche - Random opportunities - People rooting for you I built in silence for a year. Went nowhere. Then a year of building in public? $10k-15k/mo and a business I love.
@alexwtlf ·
Build in public is dead. every time you ship something cool, 100 copycats appear the next day. or a seed startup just releases your exact feature. at this point, builders are just doing free work for people with better distribution
@volosatovde ·
Why building in public is powerful: You show the entire journey of how you build your product. If you ever decide to sell your startup - buyers can see the full history and verify your progress. If you raise funding - investors see real traction, not just a pitch. You attract users along the way. You see real reactions. And sometimes - that visibility turns into sales. Building in public creates trust. What other benefits have you seen from building in public? Drop your thoughts 👇
@GohilHardy ·
Building in Public: Day 1 🚀 Usually, I build things in silence. This time, I'm sharing the journey from day one. I'm building another launch platform, but with a different approach and no pay-to-win mechanics. The goal is simple: Help builders get their products seen. Today's progress: - Initial setup done - Authentication completed Day 1 of the journey. Let's see where it leads.

@joncphillips ·
The problem with building in public is that the interesting parts, the doubts, the wrong turns, the stuff that almost killed it, is exactly what nobody posts. We celebrate the follower counts, the MRR screenshots, etc… and that’s fine, but I’m not learning anything from that! I want to read the horror stories, the reasoning behind the decisions, the life events that made you decide to do X or Y, the pivots!
@1Umairshaikh ·
Building in public used to mean sharing your journey. Now it means posting your AI-generated app every 3 days and wondering why nothing sticks. Shipping isn't the strategy. Distribution is.
@Layton_Gott ·
90% of "build in public" accounts will die in the next 6 months... And it's not because of the algorithm. It's because they only know how to post wins. So the moment things slow down, they stop posting. No MRR screenshot this month? No post. Rough user feedback? No post. Real building in public isn't just the highlights… It's a commitment to show up whether the numbers are up or down. The audiences that actually compound are built during the good AND bad weeks. Anyone can post a win not everyone can post a mistake.
@Layton_Gott ·
Building in public is free marketing that most founders waste. Here's how to actually do it right: Share real numbers. "Great progress this week" gets ignored. "We hit 200 users, here's what we did" gets bookmarked. Show the lows. Everyone posts wins. The bug that took 6 hours to fix is what makes people trust you. Make it personal. Nobody follows a product. They follow the person building it. Be consistent. One post a month does nothing. Three a week builds an audience. My brother and I build Scribe entirely in public. Every win, every failure, every lesson. That alone has driven more growth than any ad ever could. If you're building something and not sharing the process, you're leaving your best marketing on the table.
@GohilHardy ·
Building in Public: Day 12 🚀 Today's focus was all about improving @lab_startups Shipped a few updates: - Switched from Umami → PostHog for better product analytics - Updated the navbar - Brought the leaderboard back - And... we got a user from ChatGPT 👀 Small improvements every day.

@Col_ASY ·
Likes from other founders: 400 Comments saying "Looks clean!": 50 Actual paying customers: 0 The "Build in Public" timeline is a great support group It is a terrible distribution channel. Stop marketing to your peers.
@YoannaJuille ·
Another week of building in public. Weekly Recap : - 7/7 daily posts on X. - One deep-dive LP audit done for a happy founder. - The Lutains landing page redesign is currently in the oven. - Taking it slow this weekend to stay fresh. - And we are 900 here !!! Next week, the strategy changes a little. We’re moving into outreach and finding our first customers. Have a nice Sunday :)

@alexabelonix ·
“Build in public” does not mean leak your leverage. That part gets romanticized by people who are not negotiating with customers, investors, acquirers, or competitors. Some things should stay closed: revenue details customer names enterprise objections churn reasons roadmap bets weak spots competitors can use But you can still be valuable. Share: lessons frames mistakes decisions customer patterns market shifts taste standards You do not need to show the ledger to build trust. You need to show the judgment.

@alexabelonix ·
The best founder content does not say: “Look at me.” It says: “Look how I think.” That is why build-in-public can work. And why it can become cringe. Nobody serious needs 19 updates about your landing page button. But people do want to know: how you chose the market why the first offer failed what customers kept repeating what changed your mind what you stopped doing what metric fooled you what you now believe about distribution Share the decision-making. That is the valuable part.

@chhddavid ·
Day 228 of building in public I hit $10k MRR in 7 months, then $16k in 5 days... On my 2021 MacBook Air M1 w/ 8GB RAM. You don't need: - A maxed out $4k Mac - VC funding - $800/day in ad spend - Paid UGC - 30 employees - Openclaw or whatever All you need is 1 validated idea and motivation to keep going. For me the motivation was to make more money and to help non-technical ppl build their dreams. Seven months later I'm making it it big with @shipper_now in a very busy market where competitors raise HUNDREDS of MILLIONS and have teams of +100 people. I started with 1 goal in mind: I could become extremely successful by taking just 0.5% of what these other guys make... And now, completely unbiased, I've come to realise: - We've built this amazing app in public for 7 months straight - We've learned SOOOO many lessons - We've come to genuinely have a better product than our competitors - And we're starting to get recognition!! Reflecting... so crazy how far we've come - And as always, WE'RE JUST GETTING STARTED.


@metahumanmorph ·
Building in public was a mistake. It turned execution into performance. The feedback loop felt productive. Quiet execution is underrated.
@mahasr199 ·
Here are all the negative things that happen when you build in public *AND* you are an actually hyper profitable company 1. People pitch you complete dog shit services. 2. Ambulance chasing lawyers try to figure out how to take some of it. 3. Consumers get pissed cause no one likes the owner getting rich. 4. Your competitors get pissed cause they can't make money and start chriping. 5. Your competitors get inspired and they start copying. 6. Employees start to get full picture and get poached aggressively. 7. Target on your back from regulators in the inadvertent industry turn. 8. "Friends" get close because of clout but are actively stealing and will talk behind your back when any of the above happens. Positive things you get in return: 1. I guess some dudes follow you and engage with your posts? This is only applicable if your business is decently profitable (call it FCF 5mm+/annum). If you are in the fund raise game or unprofitable, build in public. No one is envious of that.
@hariprasad_bg ·
3 things I got wrong building in public: • Posting vanity metrics nobody cares about • Sharing features instead of problems • Waiting for perfect before sharing The rawer the post. The better the reach.
@MakadiaHarsh ·
I've been posting on X for years now. Since then? 1. Documented my entire journey publicly 2. Shared wins and losses transparently 3. Built trust with 230K+ people 4. Landed clients who already knew my work The best part? People reach out already convinced. No cold pitching. No convincing. They've been watching. They know what I build. Building in public = pre-qualified leads.
@StevenCravotta ·
How to "build in public" without giving away your strategy: Share the process of things you've already built. Talk about your revenue and your journey. Don't share your future roadmap. Don't talk about what you're currently working on.
@dominikmartinX ·
Building in public is free marketing. But most people share the wrong things. Here's what to post and what to keep private: SHARE: revenue numbers. "Made $340 this month from a $27 product" is more interesting than "crushing it." Real numbers build trust. Even small ones. People respect honest data from peers, not big claims from strangers. SHARE: mistakes and failures. "I launched to the wrong audience and got 2 sales" teaches more than "10 tips for a perfect launch." Failure content gets saved. Success content gets scrolled past. KEEP PRIVATE: your exact playbook in real-time. Share the strategy after you've tested it. Not while you're testing it. Share your pricing experiment while it's running and people's opinions mess up your data. KEEP PRIVATE: complaints about customers. Even anonymous complaints. Your audience reads between the lines. The founder who complains about customers is the founder customers avoid. SHARE: tools and costs. "My stack costs $50/month: Claude + Beehiiv + Gumroad" is the kind of post people bookmark. Specifics. Receipts. Let people copy your setup. What are you building right now?
@robj3d3 ·
Building in public #001 ($20.5k MRR 💰) Managing many X accounts is a headache. SuperX makes it easy, but nobody uses it. So I added a new step to onboarding 👇

@vitaliidodonov ·
The best part about building in public: By launch day, there's already a waitlist of people who trust you. We shared everything while building Stanley. 700 signups on day 1. Beat OpenAI on Product Hunt. Building and selling are the same thing.
@andrewzacker ·
Day 7 of daily build in public video updates. - Our SaaS launch failed 😢 - Why I spent 5 hours recording Reels - Why I'm posting daily even when things go wrong
@chhddavid ·
Day 232 of building in public MRR: $18k Goal: $50k Some people have asked me how I got my first MRR for @shipper_now, so here's my answer: - Launched (way too) soon: ProductHunt, Reddit, X, HackerNews etc - Planted SEO seeds - Started building in public on X + Reddit That's literally it! This is how we got our first $1 MRR → $5k MRR!
@marcos_placona ·
Most people build in public for the audience. The ones who actually benefit from it do it for the accountability. Here's the difference in practice: Building for the audience means you post the wins, the milestones, the "we just hit 1000 users" moments. You curate. You perform. And the moment growth slows down you go quiet - because there's nothing impressive to share. Building for accountability means you post the decision you made today and why. The feature you killed. The customer who churned and what they said on the way out. The week where nothing moved and what you're doing about it. The audience-first approach creates a weird trap - you start making product decisions that look good in posts rather than decisions that are good for the product. You optimise for the narrative instead of the outcome. I've seen founders delay a pivot by 3 months because they'd been publicly committed to a direction that wasn't working. The audience became a cage. The accountability-first approach does something different. It forces clarity. When you have to explain a decision publicly, you make better decisions. When you commit to shipping something next week in front of an audience, you ship it. The external pressure becomes a tool you use on yourself. The audience can smell the difference too. Posts that are built around "look what we did" feel like press releases. Posts built around "here's what we figured out" feel like conversation. Build in public by all means. Just be honest about who you're doing it for.
@victor_bigfield ·
unpopular opinion: most "build in public" accounts are just posting stripe screenshots on the 1st of every month. i've done it too. feels good for 5 minutes. but nobody learns anything from your revenue going up. they learn from you saying "my churn is 15% and i have no idea how to fix it yet."
@TimoCodes ·
The build-in-public contract: 1. The wins are visible. So are the bugs 2. The shipped features are visible. So is the technical debt. 3. The growth is visible. So are the slow weeks Transparency is the mechanism, not the cost. If you only share the wins, nobody trusts the wins.
@andrewzacker ·
Day 11 of daily build in public video updates. - Tomorrow we launch on Uneed. Nervous. 🚀 - Change to our signup page to improve conversion (showing the exact tweak) - How I'm promoting our SaaS with short-form content
@jonahlau_ ·
Building in public has a performing tax that nobody mentions Documenting what you're doing, writing the thread, engaging with replies, turning every decision into content. It's useful for some people but it's also taking 30% of your capacity. That's time you're not spending building, closing deals, or thinking without an audience watching. For some people the trade is worth it. They're good at performing and the visibility pays back more than it costs. But for a lot of people it's just expensive signaling. If you're technical and you'd rather ship than explain, the performing tax is too high. You're better off building something people need and letting the dependency do the work. If you're relationship-driven and you'd rather be in rooms than writing threads, the tax is too high there too. You're better off being useful to the ten people who matter than visible to ten thousand who don't. Building in public works but it's not free. The cost is your attention and a chunk of your execution capacity, and most people don't realize they're paying it until they've been doing it for a year.
@terencebuilds ·
I post my wins and my lessons. What I don't post: The nights I doubt all of it. The constant worry of competitors. The fear that I'm wasting years of my life. Building in public doesn't mean sharing everything. But maybe it should mean sharing this sometimes too. #BuildInPublic
@TimoBuilds_ ·
[Day 196] building in public powered by movement Started at midday, back again in the evening. 2 projects. Same goal: move forward. 1️⃣ Project: Webdesign Customer ✔ final improvements after client meeting ✔ last steps before handover → finally back to app business 2️⃣ Project: FocusMap .pro ✔ fixed bug reported by @tim_neunzig (thx!) ✔ pushed 2 Reddit posts for the free roadmap feature ✔ started SEO again: → content marketing → keyword research (missed this…) Feels weirdly familiar. 1.5 years ago I was deep into SEO. No audience. No building in public. Just me, sites, and Google. Now I’m back. But this time, I don’t build in the dark. I build in public. Keep moving.
@RIICommunity ·
“Build in public” is overrated Nobody cares about your journey They care about: • Results • Insights • Lessons they can steal Stop posting: “Day 17 of building…” Start posting: “What failed, why, and what changed” Attention follows usefulness
@yashhq_22 ·
Stop selling “build in public” like it’s some growth cheat code. It’s not just progress updates and launch threads. It’s showing your messy drafts, doubts, and dead ends. Most people aren’t ready to be that honest online.
@askwhykartik ·
The new founder playbook: Ship + share in parallel. Every feature you build? Document it. Every milestone? Make it shareable. Every bug fix? Content gold. This isn't vanity. Your build journey IS your distribution. Content compounds into customers. Transparency turns into trust. Performance art becomes your moat. Build in public or build in obscurity.
@HsrRaza ·
Everyone says “build in public” like it is some growth hack. The real reason to build in public is simpler: It forces you to stop pretending. You cannot keep saying “I am working on something big” for 8 months when people can see you have not shipped anything. You post the ugly first version. You share the mistakes. You show the slow progress. And over time, people do not just follow the product. They follow the story.
@victor_bigfield ·
unpopular opinion: "build in public" in 2026 has become just posting a stripe screenshot on the 1st of the month. real build in public is sharing what's not working. the weeks at -$200 MRR. the churns you don't understand. the rest is just flexing.
@asaio87 ·
Building an audience then launching a product is wrong but not because of the reasons you might think of. Its hard to build in public like before, get the followers and hope your product will be bought by thousands of people. i think that movement has died. here is what to do instead: - build the product right away - post on social media daily just to get better at it - show your face daily - use some of the best videos to run ads (meta, tiktok) - focus on SEO (create content, build backlinks) - create long-form YouTube (1 video a week) - scrape for email addresses to email people stop building in public for the sole purpose of growing your app this approach will fail build in public just to get used to social media and try things
@bilalpirzadaa ·
I think "Build in Public" accidentally trained founders to optimise for applause instead of evidence. We celebrate: • Shipping every day • Streaks • Screenshots • Revenue milestones We rarely celebrate: • Killing a bad feature after talking to 3 users. • Refunding someone because the product wasn't good enough. • Admitting an idea has no demand. • Spending a week doing customer interviews instead of writing code. The uncomfortable truth: You can look like you're winning on X while building something nobody actually wants. I'm going to document the boring decisions that make products survive, not just the exciting ones that get likes. If you're building for users instead of the algorithm, follow along.

@seraleev ·
One thing I rarely talk about here, but it’s something you should know if you’re building in public. Every couple of weeks, I find myself dealing with disputes over the use of my intellectual property. People copy app icons, app names, ad creatives, and sometimes even use videos featuring me and my kids to promote their own projects. Building in public helps you grow. But it comes with a price.
@IamMLeclercq ·
Everyone loves the « I just launched ! »posts But the real Build in public is spending 3 hours debugging a Stripe webhook just so one user can upgrade smoothly 🚀
@adrien_brbr ·
90% of "building in public" is a diary with analytics screenshots. Same format every week. MRR update. "Here's what I learned." "The journey continues." That's not transparency. That's content marketing in a hoodie. Real BIP is posting the decision you're scared to share. The metric that embarrasses you. The strategy that might be completely wrong. If it doesn't make you uncomfortable to hit post, it's not building in public.
@IAmAaronWill ·
Building a Build In Public content system. > System asks you questions > You brain dump what you've built > System turns it into 7 posts > Outputs to Notion Currently testing the first brain dump. 7 questions in, 7 posts out. Will report back.

@itzsam_ai ·
The build-in-public playbook nobody shares: 1. Document the journey, not the destination 2. Share numbers (good AND bad) 3. Ask questions, not just share updates 4. Tag people you learn from
@sharyph_ ·
What Nobody Tells You About Building in Public Everyone says "build in public." Here's what they don't tell you: Most people don't care about your journey. They care about the results. What works: → Sharing specific lessons learned → Showing before/after transformations → Teaching what you just figured out → Providing proof that your system works What doesn't work: → Daily "just coded for 6 hours" updates → Vague "working on something big" posts → Complaining about how hard it is → Progress updates with no insights Building in public isn't a diary. It's strategic documentation that provides value. Every update should answer: "What can someone learn from this?" If the answer is nothing, don't post it. I share my systems, my numbers, my failures...but only when there's a lesson attached. That's the difference between building in public and performing your productivity.
@marcos_placona ·
building in public is useful. but listening in public is probably more useful. shipping updates makes people aware of the product. watching where people complain tells you what the product should become.
@VivienMahe ·
Unpopular opinion on "build in public": It does not mean sharing every metric. It means sharing what you're learning, not just what's working. The MRR screenshot trend is making that worse.
@elgermerlo ·
BUILD IN PUBLIC update: Running a simple experiment - Launched on HN, some comments here on X and Uneed today - +450 visits - 40 signed up users - 9 reviews that really hurt but shows what's the real pathway Stay tuned, it's just starting up.
@brianmcgrath ·
Build-in-public works best when the artifact is specific. A landing page. A pricing decision. A broken onboarding step. The work gives people something real to understand instead of another progress update.
Best Build in Public tweets
Xholic studies what works in your niche, drafts posts in your voice and schedules them for the hours your audience is online.
$0 today · Cancel anytime
Browse all tweet collectionsKeep exploring