Direct answer
The best build-in-public founders do not simply share updates. They turn their work into distribution by making decisions, constraints, numbers, mistakes, and taste visible. Good build in public is not “look at me building.” It is “watch the business become more legible.”
Build in public is not a personality type
Some people think build in public means being loud.
It does not.
You can build in public quietly. You can write short updates. You can publish monthly memos. You can show dashboards. You can share learnings without turning your life into a startup aquarium.
The point is not exposure.
The point is trust.
A founder who shares useful reality becomes easier to believe.
The three levels of build in public
Level 1: Updates
We shipped this.
We reached this number.
We are launching soon.Useful, but basic.
Level 2: Decisions
We chose this channel because...
We killed this feature because...
We changed pricing because...Better. The audience learns how you think.
Level 3: Operating evidence
Here is the test.
Here is the constraint.
Here is the trade-off.
Here is what failed.
Here is what changed.
Here is the next decision.This is where build in public becomes distribution.
People do not only follow the outcome. They follow the judgment.
The watchlist categories
Rather than pretending one founder “wins” build in public, use categories.
Different founders teach different lessons.
1. The Revenue Builder
This founder shares numbers, experiments, launches, and revenue progress.
What to learn:
- specific metrics create trust;
- revenue updates attract other builders;
- transparency builds accountability;
- numbers without narrative become boring.
Risk:
Revenue screenshots can become casino content. If the only message is “look how much money,” the content attracts spectators more than serious readers.
Afterhours version:
Share numbers only when they teach a decision.
Not: We made €10K.
Better: We made €10K after changing the offer from X to Y because users kept objecting to Z.2. The Product Builder
This founder shares product decisions, prototypes, UX changes, feature cuts, and customer feedback.
What to learn:
- product thinking is content;
- constraints make updates interesting;
- before/after is powerful;
- showing what you removed can be more useful than showing what you added.
Risk:
The audience becomes other builders, not customers.
Afterhours version:
Connect product updates to user behavior.
3. The Audience Builder
This founder shares ideas, essays, lessons, taste, worldview, and personal founder narrative.
What to learn:
- audience grows around repeated beliefs;
- content creates context before product exists;
- trust compounds through consistency;
- the founder becomes the category’s translator.
Risk:
You become known for talking about building, not building.
Afterhours version:
Every belief should connect to an artifact: article, product, video, experiment, tool, result.
4. The Operator Builder
This founder shares operating systems: dashboards, cadences, hiring, rituals, decision memos, retrospectives.
What to learn:
- systems are interesting when they reveal reality;
- people like seeing how companies run;
- internal processes can become external trust;
- operating transparency attracts talent.
Risk:
It can become productivity theatre.
Afterhours version:
Only show systems that changed decisions.
5. The Failure Builder
This founder shares what failed, what was killed, what hurt, what surprised them.
What to learn:
- failure creates trust when specific;
- the audience respects clean kill decisions;
- mistakes become assets if they improve judgment.
Risk:
Failure content can become performative vulnerability.
Afterhours version:
No crying without a lesson. No lesson without a decision.
Build-in-public examples to study
Study:
- indie hackers who share MRR and experiments;
- founders like Marc Lou who make small product shipping feel normal;
- creator-founders who document behind-the-scenes work;
- founder vloggers like Daniel Dalen who make operations visible;
- startup operators who publish decision memos and postmortems;
- founders who write monthly investor-style updates publicly.
The useful question is not:
Who should I copy?The useful question is:
What kind of visibility fits my business?The build-in-public menu
| Lane | Best for | Content format |
|---|---|---|
| Revenue log | SaaS, apps, digital products | Monthly numbers, experiments |
| Product diary | Software, AI tools, apps | Screenshots, decisions, changelogs |
| Founder vlog | visual operations, teams, travel | YouTube, Shorts, photo essays |
| Field notes | corporate escape, psychology | essays, memos, reflections |
| Operating log | teams, agencies, studios | dashboards, rituals, process notes |
| Customer log | validation-heavy businesses | interviews, objections, learnings |
What to share
Share:
- decisions;
- constraints;
- numbers with context;
- before/after;
- failed experiments;
- customer language;
- trade-offs;
- operating systems;
- behind-the-scenes work;
- what you changed your mind about.
Do not share:
- confidential customer data;
- fake vulnerability;
- performative hustle;
- exaggerated revenue;
- anything that makes your team or customers feel used;
- constant “big things coming” posts;
- screenshots with no lesson.
The AfterhoursFounder build-in-public rule
Show the work when showing it makes the work more useful.Not everything needs to be public.
Some things need privacy to become good. Some need public pressure to become real.
The founder’s job is to know the difference.
Final note
Build in public is not a content strategy.
It is an honesty strategy with distribution benefits.
Do it well and people do not just know what you are building. They know how you think. That is much harder to copy.
Sources and further reading
- Reforge — Growth loops thinking: https://www.reforge.com/blog/growth-loops
- Indie Hackers: https://www.indiehackers.com/
- FishTank — What is building in public: https://www.fishtank.vc/company/blog/what-is-building-in-public
- Jonathan Rintala — Build in public examples: https://jonathanrintala.com/blog/build-in-public-saas-top-founders-to-follow/