How to build in public without feeling cringe

From the SoleOS answers series — written about our own product space; grounded in published definitions and documented behavior, never invented numbers.

Building in public means sharing your product's real numbers, decisions, and failures as they happen, instead of only announcing polished wins after the fact — and done honestly, it's one of the cheapest distribution channels a bootstrapper has, because an audience that watches you work ends up trusting you before you ever ask them to buy. The cringe people are afraid of isn't the transparency itself; it's the performance layered on top of it — engagement bait, fake vulnerability, milestone spam. Cut the performance and keep the substance, and it stops feeling like marketing and starts feeling like a person doing interesting work out loud.

What building in public actually is

At its simplest, building in public is narrating your product's progress in a public channel: what you shipped this week, what a metric did, why a feature got cut, what a customer said that changed your roadmap. It's not a genre of hustle-culture screenshots — it's a documentation habit, the way an engineer treats a changelog: regular, specific, and boring in the best sense. The audience isn't following you for inspiration; they're following you to see how a real product gets built, which means the update where a feature flopped is more valuable content than the one where everything went great.

This matters early especially, because before you have a brand or a channel, your process is the only interesting thing you have to talk about. If you're still deciding what to build, the same instinct — sharing your reasoning instead of hiding it — is also how you validate a SaaS idea in public: posting the problem you're chasing and the assumptions you're testing gets you real objections before you've written a line of code.

Why it's high-leverage for bootstrappers

Paid acquisition scales with budget you don't have. Building in public scales with time you're already spending on the business, because the update is a byproduct of work you did anyway — you just narrate it. Every post is a small trust deposit: by the time you launch or ask for an upgrade, part of your audience has already watched you make a dozen decisions and seen you be right and wrong in public. That's a warmer path to a first customer than a cold ad, and it costs nothing but consistency.

It also compounds in ways a single launch doesn't. A Product Hunt spike fades in a day. A year of honest updates becomes a searchable, referenceable body of work — other founders quote your numbers, newsletter writers cite your posts, and new visitors six months from now can scroll back through the whole arc instead of arriving mid-story. That archive is free content marketing you never sat down to "do content marketing" for.

What to share — and what not to

Share what's true and specific: revenue by month, churn and why a customer left, a pricing change and the reasoning behind it, a feature you killed after it flopped, a support ticket that taught you something. Numbers beat adjectives — "$1,200 this month, down from $1,450 because I lost my two biggest accounts" says more than "tough month." That kind of narration applies at every stage, whether you're chasing your first $100 in MRR or pushing from $100 to $500 — the interesting part of both is the messy middle, not the milestone.

What not to share: anything you'd be embarrassed to have a customer read back to you later, anything that exposes a customer's private data or a cofounder's disagreement without consent, and — a subtler trap — updates you're posting only because you feel obligated to. An empty week is better left unposted than padded with a non-update dressed up as news.

Honesty over highlight-reel is the whole game. A feed of only good news reads as lucky or fake, and readers can tell. The founders people root for are the ones who post the plateau months too.

Where to do it

X (Twitter) and Indie Hackers are the default homes for build-in-public content because the audience there already expects this format — short updates, dashboard screenshots, threads on a hard decision. Relevant subreddits (your product's niche, not generic startup ones) work for deeper discussion, but they punish anything that reads as self-promotion, so the bar for substance is higher. A personal blog or newsletter is worth having as the permanent home for the deeper monthly recap, with social posts acting as the trailer that links back to it.

Pick one or two channels and actually show up, rather than spreading thin across five. A dashboard you check daily — the guides cover setting one up — makes the "what happened this week" post fast to write, since you're pulling from numbers already in front of you instead of digging for them.

What makes it cringe, and how to avoid it

Cringe has a short list of specific causes, easy to catch once you can name them:

• Engagement bait — "Comment below and I'll DM you my exact funnel," or fake polls farming replies. Only ask a question when you actually want the answer.
• Fake vulnerability — a "failure" story that's obviously a brag in disguise ("I failed by growing too fast"). Only post a failure when it actually cost you something, and say what.
• "Please upvote / please retweet" — asking for distribution instead of earning it. If the content is good, people share it unprompted; needing to ask is a sign the content isn't there yet.
• Humble-bragging — a flex buried in false modesty ("still can't believe little old me hit six figures"). Just state the number plainly and move on.
• Milestone spam — a celebration post for every small uptick, which trains your audience to skim past you. Save celebrations for milestones that took real effort.

The through-line: all five optimize for a reaction instead of for being useful or true. Write each post as if the only reader is another builder one step behind you, not an audience you're trying to impress.

Consistency beats virality

One viral post gets you a day of traffic and a spike of followers who mostly unfollow within a week. A weekly cadence for a year gets you compounding trust, a search-indexed archive, and a small number of readers who become customers, collaborators, or vocal fans — not because any single post was brilliant, but because you were reliably there. Treat it like a beat you file on schedule rather than something you do only when you have exciting news. The unglamorous weeks are where the trust actually gets built, because they prove the good weeks weren't a fluke.

Turned into a system, this becomes a real distribution engine: the weekly post feeds the monthly recap, the recap feeds a newsletter, and the whole archive becomes the thing new visitors read before they ever talk to you. That's also why the habit is worth streamlining the boring parts of — pulling your own numbers shouldn't be the reason a week goes unposted.

It isn't mandatory

Plenty of founders grow perfectly well without ever posting a public update — through SEO, partnerships, existing networks, cold outreach, or a product good enough that word of mouth does the work. Building in public is a distribution channel, not a moral obligation, and it suits people who don't mind being visible and can sustain a writing habit for months. If narrating your work would drain energy you'd rather spend building, skip it — a strained, resentful update is worse than no update at all.

One disclosure: this guide is published by SoleOS, a portfolio dashboard for solo founders, so we have an obvious interest in founders tracking their numbers well enough to have something worth posting about. You don't need SoleOS to build in public — a spreadsheet and your existing analytics logins are enough to write an honest weekly update; a unified dashboard mainly saves time once you're running several products and don't want to log into five tools to find one number.

Frequently asked questions

How often should I post?

Pick the loosest cadence you can actually sustain for a year — weekly is common, monthly is fine too — and protect it like a deadline. A consistent monthly update beats a weekly one that quietly dies after six weeks.

What if my numbers are bad?

Post them anyway, with the reason. A declining month with an honest diagnosis reads as credible and often gets more genuine engagement than a good month, because readers rarely see that kind of candor and it makes the good months more believable when they come.

Do I need a big following to make this worthwhile?

No. The value compounds through the archive and the trust it builds, not through reach. A dozen engaged readers who become customers or referrers is a better outcome than ten thousand passive followers who never convert.

Should I build in public before I have any users?

Yes, if you're using it to pressure-test an idea rather than to announce a launch — sharing your assumptions and getting pushback is part of how you validate demand before writing code.

Is it okay to share only some numbers and not others?

Yes. You're not obligated to publish everything — bank balance, personal runway, and anything that would expose a customer are reasonably off-limits. The standard isn't total disclosure, it's not faking what you do disclose.