How to Build in Public in 2026: What to Share, Where to Post and How to Keep It Up

#What "build in public" means

Building in public means sharing the process of building your product as it happens: what you shipped this week, what it earned, what you tried that didn't work, and what you're deciding next. The audience follows the story, which means that by launch day you have people who already care.

It isn't a new idea. Buffer says it has been open about its finances and team salaries since 2013, and still publishes revenue on its transparency page. In 2015 Baremetrics started Open Startups, described as SaaS companies voluntarily sharing their real revenue metrics publicly; its list of open startups is still live. Plausible Analytics runs a public dashboard of its own website traffic. Those are the far end of the spectrum. Most founders who build in public share much less, and it still works.

#Why founders do it (and when it doesn't fit)

What it does well:

• An audience before launch. People who watched you build are the first to try it, review it and share it on launch day.
• Feedback early. Posting a half-finished screen gets you opinions before you've spent a month on the wrong thing.
• Accountability. Saying "I'll ship X by Friday" in public is a strong deadline.
• Trust. Real numbers and honest mistakes are rare in marketing. They make the product feel real.
• Mentions and links. Founders who share useful numbers get quoted, linked and invited onto podcasts. That helps with search and with AI answers that draw on those pages.

When it doesn't fit:

• Your buyers are enterprise procurement teams who won't follow a founder's updates.
• You're in a market where competitors can copy you quickly and the edge is the idea itself.
• Sharing numbers would put customers, employees or investors in an awkward position.
• You'd hate it. A grudging update every month helps no one.

If one of these applies, you can still share lessons without numbers, or build in public only within a small community.

#What to share, and what to keep private

The best build-in-public posts teach something. Ask: "Would another founder learn from this, even if they never use my product?"

Numbers are optional, but specifics aren't. "We're growing fast" is noise. "Signups went from 12 to 41 a week after we added a free plan, but paid conversions didn't move" is a post people read and remember.

Be careful with screenshots. Dashboards, inboxes and admin panels leak emails, names and payment details. Use test data or blur everything that isn't yours.

#Where to build in public in 2026

Pick one main channel where your buyers already are, and one place you own. A channel you own (a blog, a changelog, a newsletter) survives algorithm changes and platform shutdowns.

A note on directories of builders. Sites like buildinpublic.com list people who build in the open. They're useful for finding peers to follow and reply to, which matters more early on than your own posting.

#A weekly routine you can keep

Building in public fails most often because founders stop after three weeks. Make it small enough to survive a bad week.

1. Monday: one progress post. What you shipped last week, one number, one thing you learned. Five minutes if you keep notes during the week.
2. During the week: one work-in-progress post. A screenshot, a decision you're stuck on, a question. Ask for opinions.
3. Every day: reply to five people. Comment on other builders' posts with something useful. This is where most followers come from at the start.
4. Monthly: one longer post. A month in review on your blog or newsletter, with the numbers and the lessons. Cross-post a summary to your main channel.
5. At milestones: a story. First user, first paying customer, first $100 in a month, a launch. These are the posts people share.

Keep a "shipped" log. A note where you write one line every time you ship or learn something. On Monday you copy from it instead of trying to remember.

#Your first post

The first post is the hardest because there's nothing to report yet. Don't wait for a milestone. A template:

I'm building [product]: [what it does] for [who].

Why: [the problem, in one specific sentence, ideally your own].

Where it is today: [honest stage: an idea, a prototype, 5 beta users].

I'll post an update every [Monday] with what I shipped, one number and one lesson.

If you [have this problem], I'd love to hear how you handle it now.

It tells people what to expect from you and asks a question your future users can answer. Pin it to your profile.

#Your first 30 days

After a month you'll know which format your audience responds to and whether the channel is right. If a month of honest effort gets no replies at all, the channel is probably wrong, not the idea of building in public.

#Post formats that work

• The weekly update. "Week 6 building Acme: shipped recurring invoices, 23 signups (up from 15), one churned customer told me why. Here's what I'm changing."
• The decision post. "Should the free plan have a client limit or a feature limit? Here's what I'm leaning toward and why." Then actually listen.
• The numbers post. A screenshot of a chart (with private data hidden) and three sentences on what it means.
• The mistake post. What went wrong, what it cost, what you changed. These often do better than wins, because they're rarer.
• The launch recap. Where you launched, what each place sent, what you'd do differently. See our Product Hunt and Show HN guides for the launches themselves.

Write them yourself, in your own voice. People follow a person, not a brand account, and the founder subreddits and Hacker News increasingly remove AI-written posts.

#Common mistakes

• Announcements disguised as updates. "Excited to announce our new feature!" every week is marketing, and people tune it out.
• Only sharing wins. Followers stop believing a story with no setbacks.
• Inflated or unverifiable numbers. Someone will ask. Sites like Indie Hackers and others now let founders verify revenue through payment providers, and readers increasingly expect it.
• Posting and leaving. Building in public is a conversation. Reply to comments and to other builders.
• Spreading across six platforms. One channel done consistently beats six done badly.
• Measuring by follower count. Track replies, signups from your posts and conversations with potential customers instead.

#How Verdy fits

Building in public is easier with a habit and a scoreboard, and that's what Verdy's free launch console is built around.

• Daily missions and streaks. Five missions a day, one each for a directory or launch, a community, a social post, a website fix and a link, with a streak for showing up. The social mission is your build-in-public post.
• Ready-made places to post. The curated list includes #buildinpublic and #indiehackers on X, a build-in-public thread format, r/buildinpublic, Indie Hackers and WIP, alongside about 150 launch opportunities overall.
• A public builder profile. Switch it on and you get a page at your own handle showing your product, level, XP, streak, stats and badges, never your copy, email or history. Link it from your bio as a running record of the work.
• Friends. Add another founder by code or link and you both see each other's week: XP, streaks and how many days in a row you've both shipped. A friend racing you is a better accountability system than a follower count.

#FAQ

#What does build in public mean?

It means sharing how you build your product as you go: what you ship, your numbers, your decisions and your mistakes, usually on social media, a blog or a community. The goal is to build an audience and get feedback before and after launch, rather than revealing everything only on launch day.

#How do I start building in public?

Pick one channel where your buyers are, write a short first post about what you're building and why, and then post a weekly update with one number and one lesson. Spend more time replying to other builders than posting. Keep a running log of what you ship so updates take minutes, not an hour.

#What should I share when building in public?

Things others can learn from: what you shipped, results of experiments, revenue or user numbers if you're comfortable, decisions and the tradeoffs behind them, and mistakes. Keep customer data, security details, secrets, and anything about people who didn't agree to it private.

#Is building in public on X still worth it in 2026?

For developers, indie makers, and AI and SaaS founders, yes, because many of them still read and post with #buildinpublic there. X announced in April 2026 that it was closing Communities, so rely on your own posts, replies and a channel you own rather than any single X community.

#Do I have to share my revenue?

No. Revenue numbers get attention, but they're optional. You can share users, signups, shipping pace or lessons instead. If you do share revenue, be accurate; some platforms now let founders verify revenue through their payment provider.

#How often should I post when building in public?

Weekly is enough for a progress update, plus replies to others most days. Consistency over months matters far more than frequency. If weekly is too much, post every two weeks, but keep the schedule.

#Final recommendation

Choose one channel and one place you own, post a weekly update with a real number and a real lesson, and reply to other builders every day. Keep customers and secrets out of it, and don't let a single platform hold your whole audience. To turn it into a daily habit with streaks, missions and a public profile, start in Verdy's launch console, and use our Reddit guide and first 100 visitors plan to turn followers into users.