I want to build in public
What to post when the month was boring
- Published: Sep 15, 2026
- Updated: Sep 30, 2026
- 5 minutes read
- Make us your go-to for GTM
Build-in-public advice is written around events, and most months contain none. So you skip a week, then two, then posting again feels like it needs an explanation. Four sources fix this because they come from operating rather than from sitting down to think of ideas.
Some months nothing happens.
No launch. No milestone. No number worth announcing. You did the work, the work was ordinary, and now it is Tuesday and you are supposed to post something.
This is where most people building in public quietly stop. Not because they ran out of discipline. Because they ran out of announcements, and every guide they read assumed announcements were the point.
The boring month is the one worth posting through. Here is what I use.
Build-in-public advice is written around events. Shipped a feature, hit a revenue number, raised something, learned a big lesson. The implied system is that you announce things and people follow along.
You fix bugs, have calls, change your mind about something small, answer support tickets. From outside it looks like nothing. The work was real and none of it is announceable.
So you skip a week. Then two. Then posting again feels like it needs an explanation, so you do not. I have watched this happen to more founders than I can count and it is always the same shape. The fix is not more discipline. It is a different source of material, which is the whole point of the three hours a week approach I wrote about earlier.
These come from operating, not from sitting down to think of ideas. That is the whole reason they never run out. If you worked this month, all four exist.
Anyone can hold an opinion. Watching someone update one in public is rare, and it is the closest thing to proof that you are actually paying attention to your own results.
State what you believed, what changed your mind, and what you do now. The admission that the first position was wrong is the part people avoid and the part that makes it worth reading.
Not revenue. Any number. Reply rate, time to onboard, how long support tickets take, how many calls turned into nothing. Small numbers work better than big ones, because a big number invites comparison and a small one invites curiosity.
Say what moved, what you think caused it, and how confident you are. The uncertainty is part of the post, not a weakness in it.
Every month somebody says something you did not expect. They use the product in a way you did not design for. They value something you thought was secondary. They ignore the feature you spent six weeks on.
Write down what they said and why it surprised you. The surprise is the content, because it tells readers what you believed before, which is more interesting than what you believe now.
The hardest one and the one that travels furthest. Not a humblebrag about working too hard. An actual mistake with an actual cost.
The test is whether it would be mildly uncomfortable for a customer to read. If it would be, it is the right post. If it makes you look thoughtful and diligent, it is not a mistake, it is a marketing exercise wearing one. The same instinct applies to case studies, where the story worth telling is usually the customer who nearly left.
Three things that are worse than posting nothing.
Announcing your fourteenth customer with the energy of a Series A tells people the fourteenth customer was the biggest thing that happened. Nobody was going to notice the quiet month. Everyone notices the oversell.
Someone else’s words in your brand colours is content in the same way a placeholder is a design.
If you announced it in March, reframing it in September reads as running low, because you are.
Anyone can post during a good month. Launches write themselves.
The months where nothing happened are the ones where you sound like an operator instead of a marketer, because there is nothing to sell and all you can do is describe the work. That is the version people trust, and the version they remember when they eventually need what you do.
The boring month is not the gap in building in public. It is most of it.
Use what came out of operating rather than announcing. A decision you reversed, a number that moved, something a customer said that surprised you, or a mistake you made. All four exist in any month you actually worked.
Consistently enough that stopping would be noticeable, which for most founders is weekly rather than daily. The failure mode is not posting too little, it is setting a cadence built for people whose job is making content.
Yes, when the mistake is real and had a cost. Posts that make you look thoughtful while admitting nothing are read as marketing. The useful test is whether a customer reading it would feel slightly uncomfortable.
Yes. Manufactured milestones, quote graphics and recycled wins all signal that you have run out of material, which is more damaging than a quiet week nobody was tracking.
Clients come back for more
From stuck to a working revenue system