Building in public is easy in launch week. You have numbers, screenshots and news. The hard weeks are the other 40: you fixed bugs, refactored a database and talked to two users. Nothing feels worth posting, so you post nothing, and your audience forgets you exist.
The good news: slow weeks are full of material. You just have to change what counts as a post. Here’s what to post when nothing happened this week.
Why the quiet weeks matter
People don’t follow build-in-public accounts for milestones. They follow for the process: the decisions, the mistakes, the honest numbers. A steady stream of small posts builds more trust than one big announcement every few months.
There’s also a practical reason. Every platform rewards accounts that post regularly. Going silent for three weeks means your next big announcement reaches fewer people.
14 post ideas for slow weeks
About the work
- A bug you fixed and what caused it. Developers love a good root cause. Keep it short and show the before/after.
- A decision you made and the trade-off. “I removed the free plan’s export feature. Here’s why.”
- Something you deleted. Features, code, pages. Cutting things is a story.
- Your current to-do list, honestly prioritized.
- A tool in your stack and why you picked it over the obvious choice.
About the numbers
- A flat week’s numbers. “MRR didn’t move this week. Here’s what I think happened.” Honest flat weeks get more replies than wins.
- One metric you watch that others don’t, and why.
- A comparison with last month on any number, even a small one.
About users
- A piece of feedback that changed your mind, with permission or anonymized.
- A support conversation that revealed a gap in your onboarding.
- Why someone churned, if they told you.
About you
- What you’d tell yourself on day one. Short lessons do well.
- How you plan your week as a solo founder.
- A question for your audience: “Would you pay for X?” Questions invite replies and give you real research.
A weekly template that removes the blank page
If you post once a week, use the same shape every time. Readers learn to expect it, and you stop agonizing.
| Section | Example |
|---|---|
| Headline number | “Week 31: 4,212 users (+3%)” |
| What I shipped | “Lock screen check-ins, two bug fixes” |
| What didn’t work | “A Reddit post that got 2 upvotes” |
| What I learned | “People search ‘habit tracker for ADHD’ more than I thought” |
| Next week | “Write the ADHD article, test a new onboarding screen” |
Even a week where “what I shipped” is empty has a “what didn’t work” and a “next week.”
Platform by platform
X
Short, direct, one idea per post. Screenshots of dashboards and code perform well. Threads work for longer stories, but a single strong post with an image often reaches more people.
Same content, slightly more context. Explain the lesson rather than just the event. Line breaks help on mobile.
Short video
A build-in-public update works as a 40 to 60-second video: the number on screen in the first second, a quick scroll through your dashboard, one lesson at the end. If filming yourself feels like too much, a screen recording with a voiceover works.
For more video formats that don’t require your face, see how to market a mobile app with short videos.
What not to post
- Vague hype. “Big things coming 👀” with nothing behind it erodes trust.
- Fake vulnerability. If the “struggle” post is really a humble brag, people notice.
- Numbers you’d regret sharing, like revenue tied to a single client’s contract.
- Every single day, out of guilt. Two good posts a week beat seven forced ones.
Batch it so it doesn’t eat your week
The easiest way to stay consistent is to separate thinking from posting:
- Keep a running note on your phone. Every time something annoys you, surprises you or gets fixed, add a line.
- Once a week, turn three lines into posts.
- Schedule them for the week.
Soloreach can turn those notes into a post for X and LinkedIn plus a short video from your dashboard screenshots, and schedule all of them from one calendar. Most founders still write the first draft of their build-in-public posts themselves, and that’s fine.
Turn one event into three posts
A single small event can feed a whole week. Say you fixed a bug where reminders fired twice for some users:
- Monday, X: “Spent the morning chasing a bug where reminders fired twice. The cause was a timezone conversion running on both the server and the device.” Add a screenshot of the diff.
- Wednesday, LinkedIn: The same story with the lesson: “Decide where time conversion happens, once. I learned it the hard way.”
- Friday, short video: A 30-second screen recording of the reminder settings, with the text “Fixed: double reminders. Here’s what caused it.”
Same raw material, three formats, three audiences. You didn’t need a milestone for any of them.
Keep a swipe file
When another founder’s post makes you stop scrolling, save it. Once a month, look at your saved posts and note the pattern: was it a number in the first line, a confession, a screenshot? You’ll quickly see which shapes your audience responds to, and you can reuse the structure with your own story.
Good build-in-public accounts aren’t more interesting than you. They’ve simply decided that small, honest updates count.
FAQ
How often should I post when building in public?
Two to four posts a week on X or LinkedIn is a sustainable pace for most solo founders, plus one weekly recap.
Should I share revenue numbers?
Only if you’re comfortable with it. Many founders share growth rates or user counts instead. What matters is consistency in what you share.
What if nobody engages with my posts?
Early on, that’s normal. Reply to other founders in your space, ask questions in your posts, and give it a couple of months before judging.
Is building in public worth it for B2B apps?
Often yes, because your buyers may be other founders. Even if not, it builds a public record that helps with hiring, partnerships and press.
What if I’m building something I can’t talk about yet?
Share the process without the product: how you validate ideas, how you structure your week, what you’re learning about a market. When you launch, you’ll already have people who care.
