Why Build in Public Fails for Most Indie Hackers (And the One Fix)

The number nobody talks about

The average solo founder spends 5 to 6 hours a week on content. Most of those hours produce zero customers.

Read that again. Almost an entire workday gone to writing. For nothing measurable.

You can find that number on Reddit threads, Hacker News comments, and Indie Hackers posts. People share it the way someone shares a confession. They expected build in public to be a multiplier. It turned out to be a tax.

It is not laziness. It is context cost.

Programmers know what context switching costs. Half an hour of focus, gone, every time you switch tasks. The deep work tax.

Now picture build in public the way most founders do it.

Build all week. Stop on Sunday. Open LinkedIn. Try to remember what happened. Try to make it sound interesting. Edit. Hate it. Edit again. Post. Check the likes. Cringe. Promise yourself you will do better next week.

The cost is not the writing. The cost is the switch. Building uses one part of your brain. Writing uses another. Going from one to the other on a fresh canvas is brutal. Most founders quit because the switch is too expensive. They are not lazy. They are tired.

The five hour week pattern

Talk to ten founders who tried build in public. Most will describe the same loop.

• Week one. Excited. Three posts. Decent engagement. Big plans.
• Week two. Two posts. Still feels good.
• Week three. One post. Apologetic about it.
• Week four. Silence. Maybe one screenshot. Maybe nothing.

Then a quiet stretch. Then a guilty restart. Then silence again.

This is the pattern. Not because the founders gave up on the idea. Because the math broke. Five hours a week is too much when the return is zero customers and a few likes from other founders.

What successful build in public founders actually do differently

I read every "how I grew on Twitter" thread I could find. Watched the YouTube case studies. Pored over the Reddit AMAs.

The pattern that shows up everywhere is the same. The founders who win at build in public do not have more discipline. They do not have a magic schedule. They have one thing in common.

They never sit down to write a post.

Instead, they capture content as a side effect. They record looms while they think. They voice note while they walk. They paste their actual chat with a user. They share a screenshot of the moment a thing broke and what they thought at the time.

The post is not a separate task. It is a byproduct.

They document decisions, not features

Here is the second thing the winners get right.

The founders nobody follows post features. "Shipped a new dashboard." "Added Stripe." "Improved performance."

The founders everyone follows post decisions. Why they killed pricing tier B. Why they refunded a customer. Why they spent four days on a feature one user asked for. Why they switched from Postgres to SQLite for the side project.

A feature post is a TODO that closed. A decision post is a story. A decision post has a why, a tension, a choice. That is the shape of a thing people share.

If you are forcing yourself to come up with weekly posts, your problem is probably that you are listing TODOs. Switch to listing decisions. The list will write itself.

The one fix

Here is the fix in one sentence.

Stop trying to write posts. Start saving the words you already say.

Every vibe coder narrates their day. To Cursor. To Claude. To a teammate on Slack. To themselves out loud while debugging. That narration already contains every decision, every failure, every user moment, every pivot.

The technology to capture this exists. Voice typing. Loom. Even your terminal history. The tools to turn that capture into posts exist too. Mahasen is one. The choice you have to make is the same regardless of tool.

Do you treat writing as a separate job? Or do you treat building and writing as the same loop?

The founders who pick the second one are the ones who keep posting two years in.

What this looks like in practice

A vibe coder's Tuesday.

Okay so I am ripping out the old auth flow because Supabase started supporting magic links the way I always wanted. I had this hacky workaround. It is gone now. Saved myself maybe 200 lines of glue.

That is forty seconds of voice. It is one LinkedIn post. The hook is the workaround. The turn is the new feature. The landing is the line count saved.

You did not stop building. You did not switch to writing mode. You shipped the change and the post happened on the side.

Multiply that by the number of times you talk through a decision in a week. Twenty. Forty. You have your year of content.

The honest math

Build in public works when posting costs almost nothing. It fails when posting costs five to six hours a week.

If you do the work to drop the per post cost to thirty seconds, the math flips. You can post daily. You can post in your real voice. You can run the build in public flywheel without burning out.

The fix is not more discipline. The fix is to stop paying the context switching tax. That is the only version of build in public that scales for solo founders.

You have one job to ship. The marketing should not be a second one.

Frequently asked questions