← Back to blog
June 10, 2026·6 min read

How often should I post when building in public?

How often should I post when building in public?

TL;DR

  • The best posting cadence is the highest frequency you can sustain for a year without burning out, not the highest frequency possible.
  • Consistency matters more than volume, because an audience trusts a founder who shows up reliably over one who posts in bursts and disappears.
  • A realistic starting point for most solo founders is two to three posts a week, with a clear plan for what each one covers.
  • Track whether your cadence is sustainable by how you feel about posting, not just by the metrics.

---

There is no magic number, and chasing one hurts you

Founders keep looking for the correct posting frequency as if it were a setting. It is not.

The advice to post daily works for some people and destroys others. A founder with a fast moving product and easy writing can post every day. A founder deep in a hard build will run dry in two weeks trying to match that.

The number that matters is the one you can keep. A cadence you sustain for a year beats a heroic one you abandon in a month.

So stop asking what the ideal frequency is in the abstract. Ask what you can realistically do every week, even in a bad week, and start there.

Why consistency beats volume

Audiences reward reliability, and the reason is trust.

When you post on a predictable rhythm, people learn to expect you. You become a steady presence they recognize, and recognition is what turns a follower into someone who roots for you.

Bursts do the opposite. Ten posts in one week followed by silence for a month teaches your audience that you are unreliable. The momentum you built evaporates every time you go quiet.

There is also a compounding effect. Each post is a small deposit, and steady deposits over a year build a real audience. Sporadic posting never accumulates because you keep starting over.

Three thoughtful posts a week, every week, will outperform a flurry followed by a drought almost every time.

A realistic starting cadence

For most solo founders, two to three posts a week is the right place to begin.

That frequency is enough to stay visible and build momentum without becoming a second job. It leaves room for the actual work of building the product, which is the point.

Start lower than you think you can handle. It is easier to add a post once you have a rhythm than to cut back after promising daily updates you cannot keep. Underpromise to yourself and let consistency build confidence.

Pick fixed days if that helps. Posting every Tuesday and Thursday removes the daily decision of whether to post, and removing that decision is half the battle.

As writing gets easier and you build a backlog of things to say, you can raise the cadence. Let it grow naturally rather than forcing it from day one.

What to post at each interval

Frequency only works if you know what fills it, otherwise you stall.

A weekly post can be a progress update: what you shipped, what broke, what you learned. This is the backbone of building in public and it always has material because you are always making progress of some kind.

A second weekly post can be a lesson or an observation. Something you figured out, a mistake you made, or a small insight from talking to users. These travel further than pure updates because other founders learn from them.

If you add a third, make it lighter. A question to your audience, a quick reaction to something in your space, or a behind the scenes detail. Variety keeps the cadence from feeling like a chore.

The trick is to never sit down to a blank page. Keep a running note of small wins, problems, and ideas as they happen, and pull from it when it is time to post.

How to know your cadence is sustainable

The clearest signal is not a metric. It is how you feel about posting.

If posting has started to feel like dread, your cadence is too high, regardless of what the numbers say. Resentment leads to abandonment, so a frequency you quietly hate is already failing.

If you are routinely posting filler just to hit your number, slow down. Empty posts to maintain a streak teach your audience to ignore you, which is worse than posting less.

Watch your backlog too. If you always have more to say than slots to say it, you can post more. If you are scraping for something every time, you are at or above your limit.

Reassess every month. Your capacity changes with the product, the season, and your energy, so the right cadence is not fixed. Adjust it deliberately instead of grinding until you crash.

The goal is a rhythm you can hold for a year. Find that, protect it, and let the slow compounding do its work.

---

Frequently Asked Questions

How often should a founder post when building in public? Most solo founders should start with two to three posts a week, which keeps them visible without taking over the build. The exact number matters less than choosing a cadence you can sustain for a year, since consistency builds trust and bursts followed by silence do not.

Is it better to post every day or a few times a week? A few sustainable posts a week usually beat daily posting, because daily output is hard to maintain alongside building a product and most founders burn out. An audience rewards reliable presence over volume, so a steady rhythm compounds while an abandoned daily streak does not.

What should I post about when building in public? Post progress updates on what you shipped and learned, lessons and observations from building, and lighter posts like questions or behind the scenes details. Keep a running note of small wins and problems as they happen so you never sit down to a blank page.

How do I know if I am posting too much? You are posting too much if it has started to feel like dread or if you are writing filler just to hit a number. The best signal is how you feel about posting, because a cadence you resent will be abandoned no matter what the metrics say.

---

Disvia.ai turns your weekly progress and GitHub activity into build in public drafts in your own voice, so showing up consistently stops being a chore: see how at disvia.ai.