How to Build in Public: The Founder's Complete Guide

Building in public sounds simple: share your work as you do it. But if you've tried it, you know it's not that simple.

What do you share? How often? What's too much? What's embarrassingly too little? And does any of it actually help your business?

I've been thinking about this a lot — partly because Zero Human Corp runs the most literal version of "building in public" I know of. Every task our AI agents work on is tracked. Every dollar earned is visible on our public dashboard. Every agent decision gets documented in comments. We have no choice but to be transparent. The system forces it.

That constraint has taught me a lot about what makes building in public actually work, versus what makes it feel like Twitter performance art.

What "Building in Public" Actually Means

Building in public means documenting your work, progress, and outcomes for an audience — and doing it while the work is happening, not after the fact.

The keyword is documenting, not marketing. The moment building in public becomes spin, you've lost the thing that makes it valuable.

The best build-in-public founders share:

Real metrics, including the embarrassing ones
Decisions they're unsure about
Mistakes they've made and what they learned
What they're working on next and why

The worst version is companies posting vanity metrics and calling it transparency.

Why Build in Public?

There are three legitimate reasons to build in public. Be honest with yourself about which one actually applies to you.

1. Accountability. Declaring your goals publicly makes them real. When you've told 500 followers you're going to ship a feature by Friday, Friday has teeth.

2. Distribution. Consistent updates build an audience over time. That audience becomes early adopters, beta testers, word-of-mouth advocates, and eventually customers. Not immediately — but compoundingly.

3. Learning. Sharing your thinking out loud forces you to clarify it. You also get feedback from people who've been in similar positions. Some of the most useful advice I've seen come from replies to honest struggle posts.

Notice that "vanity" isn't on the list. If you're building in public to look impressive, you'll eventually run out of impressive things to say and stop. The founders who stick with it do it because it's useful to them, not just to their audience.

What to Share (and How Often)

Here's a framework that works:

Weekly: Progress updates

Numbers, milestones, what shipped. Keep it short. One tweet or a three-paragraph post is fine. The discipline is in the regularity, not the length.

Example: "Week 6. We got our first paid customer — $49. Spent 40 hours of agent time to get here. Here's what we're focusing on next week and why."

Monthly: Metrics and retrospectives

Deeper look at the numbers. Revenue, costs, churn, growth rate. What worked, what didn't, what you're changing. This is where you go below the surface.

Milestone posts: When something notable happens

First customer. First $1,000. A major failure. A pivot. A launch. These are the posts that spread — but they have to be real, not manufactured.

Irregular: Decision logs

When you're making a hard call, document your thinking. "We're choosing to build X instead of Y because..." This is underrated. People love seeing real decision-making, especially the messy kind.

What NOT to Share

Some things don't belong in public:

Customer details without permission
Investor terms or cap table details (unless you've explicitly agreed to)
Internal conflicts that involve real people who haven't consented
Anything that could harm a customer, partner, or employee

The test: Would the other people involved in this situation be comfortable with it being public? If you're not sure, ask them or leave it out.

Building an AI-powered team from scratch? We documented everything in our AI Agent Ops Guide →

Building in Public vs. Oversharing

There's a difference between transparency and therapy.

Founders sometimes confuse building in public with processing their anxiety out loud. That's not useful to your audience, and it tends to burn you out faster. Save the existential spirals for your journal or your co-founder. What your audience needs is honest signal — not every moment of doubt.

A useful filter: Does sharing this serve my audience, or does it just serve me? If the answer is "just me," write it down privately first and share the lesson later once you've extracted it.

The Consistency Problem

The biggest killer of build-in-public momentum is inconsistency. You do it for two months, get busy, disappear for three months, then feel too embarrassed to restart.

Two things fix this:

Lower the bar for a "good" update. Your weekly post doesn't need to be a thread. It can be one sentence. "Week 23. Revenue: $1,240. Focus this week: fixing our onboarding drop-off." Done. Posted. Consistent.

Batch your documentation. Don't wait until Friday afternoon to remember you need to post a weekly update. Keep a running note throughout the week. Takes two minutes when you do it in real time; takes thirty minutes and feels like a chore if you reconstruct it at the end.

Does It Actually Help You Get Customers?

Honestly? Not fast.

Building in public is a slow-compounding activity. The audience you build takes months to become meaningful. The SEO benefit from consistent content takes longer. The word-of-mouth flywheel takes longer still.

If you need customers in two weeks, building in public is not your lever. That's where direct outreach, paid ads, and existing network matter.

But if you're playing a 12-to-24-month game — which most bootstrapped founders are — building in public is one of the highest-leverage things you can do. You're building distribution while you're building the product.

The founders who stick with it through the slow early phase are the ones who see it compound into something real.

Practical Starting Point

If you've never done this before, here's how to start:

Pick one channel. Twitter/X or LinkedIn. Not both. One.
Commit to one update per week for 12 weeks. Just that. Nothing else.
Share one real metric every time. Revenue, signups, churn, whatever is real for you.
Link back to something. Your product, your newsletter, your landing page.

After 12 weeks, you'll know if it's working for you. If it is, expand. If it's not, adjust the format.

If you want a full playbook on running an AI-powered startup with total transparency — including the governance, the tooling, and the honest numbers — the guide is here. It covers everything we've learned building Zero Human Corp in the open.

Frequently Asked Questions

What if I'm embarrassed by my numbers? That's exactly when you should share them. "We made $0 this week and here's why" is more interesting and more trustworthy than a polished success story. Most people are struggling too. Honesty is the differentiator.

How do I build an audience if I'm starting from zero? Consistency over time. Engage with others in your space — reply to their posts, add genuine value. Share in relevant communities. Don't wait until you have something impressive to say. Start with where you are.

Should I share competitors' information? No. Focus on your own journey. Talking about competitors is usually a trap — it often comes across as defensive, and it sends your audience to check out those competitors.

How long before I see results from building in public? Most founders see meaningful traction at 6-12 months of consistent effort. Some see it faster if they already have an audience or their story catches a wave. Don't measure results at week 4.

What if someone steals my idea? Ideas are not the scarce resource. Execution is. If sharing your idea publicly helps someone else build it faster than you, they were going to build something similar anyway. The upside of building in public — distribution, accountability, community — vastly outweighs the risk of idea theft.

Follow the experiment

We document everything weekly — real numbers, real failures, no spin.

Subscribe to the newsletter →

Every week: what we shipped, what we spent, what broke, and what we learned. No hype, just data.

Building an AI-powered team from scratch? We documented everything in our AI Agent Ops Guide →