How often should you post when building in public?
By Naod Tadele · · 5 min read
The most common build in public pattern goes like this: a burst of daily posts during a launch, then silence for a month, then an apology post, then another burst.
It's understandable. Posting feels urgent when something big happens and optional the rest of the time. But the silence costs more than the bursts earn, because the people who started following you during the launch forget why they did.
So how often should you actually post?
The short answer: three to five times a week
For most solo founders and small teams, three to five posts a week, at most one a day, is a rhythm you can keep for months. That's frequent enough that followers see steady progress, and light enough that it doesn't eat your coding time.
More than that is fine if you enjoy it. Less than that is fine too, as long as it's steady. One post every week, every week, beats seven posts one week and none the next.
Why consistency beats volume
- Trust builds on repetition. Someone who sees your product mentioned every few days for a month starts to believe it's real and active.
- Stories need episodes. Progress is only visible when there's a regular record of it.
- You get better at it. Writing posts weekly makes each one faster and sharper.
How to stay consistent without burning out
Batch your posting
Don't decide what to post every day. Once a week, write several posts and schedule them. Deciding once is far less draining than deciding five times.
Keep a mix
If every post is a feature announcement, you'll run dry fast. Rotate between what you shipped, what you learned, a number and a question. 30 post ideas can help on slow weeks.
Have a fallback post
On weeks with nothing to show, post a weekly update anyway: what you worked on, what was hard, what's next. "Slow week" posts are often the most relatable ones.
Lower the bar
A two-line post that goes out beats a perfect thread that stays in drafts.
A simple weekly schedule
- Monday: something you shipped last week
- Wednesday: a lesson or behind-the-scenes post
- Thursday: a question
- Friday: your weekly update
Four posts, one short writing session, done.
Automate the rhythm, not the voice
The hard part of consistency isn't writing. It's remembering, and finding time, every single week.
Loudcode keeps the rhythm for you. You set your posting days and times once. It drafts posts from your GitHub, revenue and a 30-second weekly check-in, and "Add to queue" slots each approved post into your next free time. The words are still yours: nothing goes out without your approval.