Building in Public Is Not a Strategy — Unless You Run It Like One

"Day 47: shipped dark mode."

Nobody is coming back for the day 48 update. Not your prospective customers, not your investors, probably not even your mom. This is where most build-in-public runs die — the founder posts for six weeks, gets no meaningful engagement, concludes the strategy doesn't work, and goes dark.

The strategy does work. Random updates don't. The difference is not effort. It's structure.

The Examples People Cite

Building in public has a few reference points worth looking at honestly. Pieter Levels has publicly shared revenue figures, Stripe screenshots, and product launches on X for the better part of a decade; his tech stack tweet alone pulled 4.8 million views when he posted it alongside product revenue. Marc Lou has been similarly transparent, and publicly shared hitting $100,000 in a single month on ShipFast, his NextJS boilerplate.

What both have in common isn't volume. It's that every post does specific narrative work. They're not diaries. They're episodes in a running story with stakes, progression, and a reason for the audience to come back next week.

That's the thing most founders skip when they try this.

Why Random Updates Die

A build-in-public feed that reads "shipped feature, fixed bug, had coffee, shipped another feature" has no narrative arc. Each post exists alone. There's no tension between posts, no buildup, no payoff. You're giving readers a timeline of logistics and expecting them to care.

They don't, because there's nothing to follow. Compare to a feed that reads: "month one: quit my job, bet six months of savings on this thing. Month two: first paying customer, but the product broke twice in the same day. Month three: here's the mistake that almost killed it and what I changed." That's a story. You want to know what happens in month four.

Stakes, progression, honest failure — these are the three ingredients. Most founder posts skip all three because they feel too exposed. That's also why they don't work.

The Four Post Types That Actually Move Audience

I've watched thousands of build-in-public posts — my own and others — and consistently, four categories do most of the work. Everything else is noise.

Decisions with the why attached. "I chose X over Y, and here's the reasoning." These work because they demonstrate thinking, invite disagreement, and teach something. People who agree feel validated; people who disagree comment to argue. Both drive the post. The failure mode is announcing a decision without the reasoning — "we picked Postgres" is a tweet about a database; "we picked Postgres over Mongo because of these three specific tradeoffs" is a post people reply to.

Failures with the recovery attached. "This broke, here's what I did about it, here's what I learned." Credibility comes from being visibly fallible. The posts that perform aren't the ones where the founder wallows — those read as attention-seeking. The structure is: what broke, why it mattered, what you changed, what you'd do differently. Kept clinical, they build enormous trust.

Numbers with context. Specific metrics create specificity. But "1,000 signups!" is vanity. "1,000 signups but only 23 activated, and here's what our onboarding is missing" is honest. The best number posts are the ones that feel slightly uncomfortable to share — if you're a little embarrassed, it's probably an honest number.

Opinions formed by building. "After shipping X, I now believe Y." These are the highest-leverage post type. They take something concrete from your build experience and turn it into a broader claim worth arguing about. The leverage comes from the pairing — the specific experience gives the opinion credibility; the opinion gives the experience reach.

A Working Ratio

For every ten posts, I aim for: three decisions-with-why, three opinions-from-building, two failures-with-recovery, two numbers-with-context. Decisions and opinions attract new readers because they're shareable and debatable. Failures and numbers build loyalty with existing readers because they compound trust.

If you only post one type, you only serve one stage of the audience funnel. This is why founders who exclusively post "shipped feature" updates stall — they're hitting the same note repeatedly with no variation in what the post is doing emotionally.

The Vulnerability Thing

The uncomfortable truth about building in public is that the posts that work are the ones you don't want to publish. The decision you're unsure about. The revenue number that's lower than you hoped. The week you almost quit. The bug that shipped to production and embarrassed you.

These are what readers follow for, because they're the parts of building a company that don't show up anywhere else. Polished case studies and ship announcements are a dime a dozen. Honest operator writing is rare. The market rewards the rare thing.

You don't have to overshare. You do have to tell the truth about something, often. If every post is a win, nobody believes you.

Where This Goes Wrong

The most common failure mode isn't posting too little. It's posting too often about logistics. "Working on X today" is not a post. "Traveling to a conference" is not a post. Founders who post several times a day about the mechanics of their day train their audience to skip them. Cadence matters less than density.

The second failure mode is writing for investors when the audience is customers (or the reverse). Investor-language posts — TAM, funding, exit — alienate customers who just want to know if the product solves their problem. Customer-language posts that read as whining don't impress investors. Pick who you're talking to per post, and be clear.

What Actually Happens If You Do This

A build-in-public practice that runs with structure for twelve months produces three things that no paid channel can buy. First, an audience of people who already trust you before they need your product — conversion on this audience is dramatically higher than on cold traffic. Second, a body of public writing that makes hiring, fundraising, and press easier because you have receipts. Third, a defensible distribution moat that compounds monthly while your competitors are still figuring out what to post.

None of that happens from "Day 47: shipped dark mode."

---

If you want the campaign structure — narrative arcs, post variety, a calendar that doesn't require you to stare at it — that's what FeedSquad's Ghost agent is built around. Free tier, no card.

Sources:

• Nomadic Blueprint — How Pieter Levels Built a $250K/Month Solo Business
• Marc Lou — $100,000 in 30 days on ShipFast (LinkedIn)
• Failory — How to Build in Public as a Founder (+20 Examples)