INDEPENDENT EDITORIAL
What to post when building in public
"What do I even post?" is the question that quietly kills most build-in-public habits. The answer isn't more creativity — it's a menu. This is a practical set of post types that reliably work, so you never face a blank page wondering what's worth sharing.
The blank-page problem is rarely a shortage of things to say. You shipped, you fixed, you decided, you struggled — plenty happened. The problem is that you don't have a format ready, so each post feels like it has to be invented from scratch, and inventing is exhausting. Working founders solve this by not inventing. They rotate through a small, stable menu of post types and fill each one with whatever real thing happened that day. Here's that menu.
The ship note
The backbone of building in public. Every time something visible goes live — a feature, a redesign, a meaningful fix — you say so, plainly, with one piece of proof. "Shipped inline editing today, you can finally rename things without opening a modal," plus a short screen recording. Ship notes work because they're concrete, they show momentum, and they're effortless: you're reporting what just happened, not manufacturing a take. If you only ever posted ship notes, you'd already be ahead of most.
The lesson learned
The highest-trust format. You hit a wall, learned something, and you share it so the next person doesn't. "Spent two days assuming the slow page was a database problem. It was an image nobody compressed. Always profile before you optimise." Lessons travel because they're useful to people who aren't even your customers yet, and they position you as someone worth following for the insight, not just the product updates.
The metric or milestone
Numbers anchor a story and invite people to root for you. First paying customer, a hundred signups, a churn number you're not proud of, MRR crossing a threshold. You don't have to share revenue if you're not comfortable — usage, retention, or a qualitative milestone work too. The trick is to pair the number with the texture: not "hit 50 users" but "hit 50 users, and the 50th one emailed me a bug at midnight — that's the kind of user you want early."
The decision or reversal
Founders make dozens of calls a week, and the reasoning behind them is genuinely interesting content. Why you picked this pricing model, why you said no to a loud feature request, why you reversed a decision you announced last month. Reversals especially perform well — "I was wrong about X, here's what changed my mind" is rare, honest, and magnetic, because almost no one posts their changes of heart.
The behind-the-scenes
Process content pulls back the curtain: how you organise your week, the tools in your stack, a screenshot of your messy whiteboard, how you talk to early users. It satisfies the curiosity that makes building in public compelling in the first place — people want to see how the sausage is made, especially when they're building something themselves.
The honest struggle
Used sparingly, vulnerability is powerful. A week where nothing worked, a feature that flopped, the doubt that crept in. The rule is to never leave it as pure venting — pair the struggle with what you're doing about it. "Growth's been flat for a month and it's getting in my head. Here's the experiment I'm running this week" invites support and ideas; "everything is terrible" just invites scrolling past.
The question
Not every post should broadcast. Asking your audience a real question — "how do you handle onboarding emails for a tool people use daily, not occasionally?" — does double duty: it gives you genuinely useful input and it pulls people into a conversation, which the algorithms and the relationship both reward far more than a one-way announcement.
Rotate, don't agonise
The point of the menu is that you stop deciding whether to post and only decide which format fits what happened. Shipped something? Ship note. Learned something the hard way? Lesson. Hit a number? Milestone. Changed your mind? Reversal. The creative load drops to near zero, because the structure is pre-decided and you're just pouring this week's reality into it. That's how building in public becomes sustainable instead of a recurring crisis of imagination.
Where LCNCagents fits
The menu solves what to post; the friction is connecting it to what actually happened in your week. LCNCagents closes that gap by turning the work you ship into ready-to-edit draft posts — your shipped features and fixes arrive pre-shaped as ship notes and updates, so you're choosing from real material instead of staring at a blank composer. You add the angle, the lesson, the human texture, and publish. The hardest part — noticing there's something worth posting — is handled for you.
One last principle: connect it back
However personal or wide-ranging your posts get, the through-line should always trace back to the thing you're building. People are following a founder building a specific product, and the posts that compound are the ones that, even when they're about a lesson or a struggle, quietly remind people what you're working toward. Be a real person — but a real person who is unmistakably building something.
FAQ
What should I post when building in public?
Rotate through a small menu of proven post types: ship notes, lessons learned, metrics and milestones, decisions and reversals, behind-the-scenes process, questions, and the occasional honest struggle. You don't need novelty every day — you need reliable formats to fill with what actually happened.
Is it okay to post about failures and mistakes?
Yes, and they often outperform wins. Honest posts about a mistake or a cut feature build more trust than polished success stories. Just pair the failure with what you learned or changed.
How personal should build-in-public posts be?
Personal enough to be a real person, not so personal it becomes a diary. Share the reasoning and decisions behind the product — but always connect back to the work you're building.