Building in Public as Distribution: A Founder’s Playbook

This month a company that built almost its entire brand in public quietly laid off most of its staff and said nothing. Bankless, a crypto-media business that grew on openness, downsized behind the scenes, and the news leaked anyway. Within hours the same audience that had cheered every milestone turned the comment sections into a courtroom. A co-founder stepped back. The lesson founders pulled from it was the wrong one. Most read it as a warning against building in public at all.

It is the opposite. Bankless did not get punished for building in public. It got punished for going dark. The years of openness were never the liability. The silence was. When you build an audience by showing your work, you sign a contract you cannot read until it is too late: the moment the news gets hard, the audience expects you to keep showing up, and absence becomes the loudest message you can send.

So here is the durable version, with the dated event left at the door. Building in public is not a personality trait and it is not a content hack. It is a distribution system. Done with discipline, it turns the ordinary act of building a company into the channel that gets that company seen, trusted, and bought. Done lazily, it produces a feed full of noise, a founder addicted to small dopamine hits, and a product nobody is actually waiting for. The difference between the two is not how much you share. It is what you share, and whether it is proof or performance.

I have built in public across two ventures. I have posted the wins, posted the numbers, and posted into total silence for months. What follows is the operating model I wish I had on day one: two original frameworks, a hard look at the trap most founders fall into, and a weekly cadence you can run starting Monday.

The Problem Nobody Names: You Built Something Nobody Watched

Ask a struggling founder what went wrong and you will hear about the product. Wrong feature set. Bad onboarding. Shipped too slow. Sometimes that is true. More often it is a comfortable story that hides the real failure, which is quieter and more embarrassing: the thing got built, and almost no one knew it existed.

This is the default outcome, not the rare one. A founder spends nine months heads-down. Launch day arrives. The launch is a tweet, a Product Hunt post, and an email to forty friends. Traffic spikes for a day and a half, then flatlines. The founder concludes the market did not want it. The market never got a chance to want it, because the market never heard a coherent story told over enough time to register.

Distribution is the actual bottleneck for most early companies, and it has been for years. The reason it stays invisible is that distribution failure looks identical to product failure from the inside. Both feel like “nobody bought it.” But they have opposite cures. A product problem is fixed by building. A distribution problem is made worse by building, because every month spent heads-down is another month the company exists without a single person outside the building forming an opinion about it.

Here is the part that should change how you think. Audience does not arrive at launch. It accrues, slowly, over the months before launch, the same way compound interest works on a balance you can barely see growing. If you start the audience meter at zero on launch day, you have guaranteed a cold start. If the meter has been running for six months while you built, launch day is a release to people already leaning in.

That is the whole case for building in public, stripped of the hype. It is not about being transparent because transparency is virtuous. It is about running the distribution meter and the build meter at the same time instead of in sequence. The build was always going to happen. The only question is whether it happens silently or whether the act of building is itself broadcast as it occurs. I wrote a full argument for sequencing in the audience-first playbook; building in public is the mechanism that makes audience-first practical for a founder who also has to, you know, build the thing.

But here is where most advice stops and most founders go wrong. They hear “build in public,” they start posting, and they post the easy stuff. The result is volume without trust. To see why volume is not the goal, you need the first framework.

The Proof Ladder: Why Most Building in Public Generates Zero Trust

Not all sharing is equal. A founder who posts ten hot takes a week and a founder who posts one screenshot of a live revenue dashboard are both “building in public,” and they are not in the same business. One is generating reach. The other is generating trust. Reach is rented. Trust is owned. The Proof Ladder is the model I use to tell them apart.

Every piece of building-in-public content sits on one of five rungs. The rungs are ordered by a single property: how hard the content is to fake. That property turns out to predict almost everything that matters, because trust is not produced by what you say. Trust is produced by saying things you could be caught lying about, and not getting caught.

Read it from the bottom. Rung 1 is opinions and hot takes. “Most onboarding flows are broken.” “Founders underrate distribution.” These are cheap to produce, they travel well, and they build essentially no trust, because anyone can have an opinion and the algorithm rewards confident ones whether or not the person has earned the right to hold them. Rung 1 generates reach. It is not worthless. It is just not the asset.

Rung 2 is process and thinking. You show how you actually work: the way you scope a week, the checklist you run before shipping, how you decide what to cut. This is more credible because it has texture, and texture is harder to invent than an opinion. Rung 3 is decisions and reasoning shown under real constraints. Not “here is a clever idea” but “here is the actual fork I faced, here is the data I had, here is what I chose and why, and here is what it cost me.” Rung 3 is hard to script because real constraints are specific and specificity is expensive to fake.

Rung 4 is numbers. Revenue, signups, churn, the conversion rate that embarrassed you. Numbers carry high trust, but with a condition attached: they only count if they are verifiable or at least consistent over time. A revenue figure posted once is a claim. The same figure posted every month, moving the way a real business moves, with the bad months included, becomes evidence. Rung 5 is verifiable artifacts. The live product anyone can open. The public dashboard pulling real data. The screenshot of a customer payment, a support thread, a contract. These are the hardest things in the world to fake, which is exactly why they carry the most trust per post.

The contrarian point inside this framework is simple and uncomfortable. Most founders who “build in public” camp on Rung 1, because Rung 1 is easy and the likes come fast. They mistake the reach for progress. But the thing you are actually trying to manufacture, the thing that converts into customers and hires and investors and press, is trust, and trust only compounds from Rungs 3 through 5. A feed that is all Rung 1 is a feed that is loud and empty. The work is to climb.

The Four Conversions: How Process Actually Becomes Product

The Proof Ladder tells you what to share. It does not tell you why sharing it is worth a founder’s scarcest resource, which is time and attention that could go into the build. For that you need to see what the sharing converts into. Building in public is only a distribution strategy if the act of sharing produces durable assets the company keeps. If it produces only likes, it is a hobby.

Here is the model. Every honest piece of process you put out can convert into one of four assets. Not all four at once, usually one or two. But a post that converts into zero of them is not building in public. It is just posting.

The first conversion is audience into distribution. This is the obvious one and the one everyone names. You build a following of people who care about the problem you work on, and when you ship, you are shipping to a warm room instead of an empty one. But notice the word “care.” Distribution is not raw follower count. A founder with 2,000 followers who all build in the same niche has more usable distribution than a founder with 40,000 followers collected through unrelated viral posts.

The second conversion is reasoning into authority. When you consistently show good judgment in public, people start to treat your judgment as a reason to trust your product. This is the conversion that produces inbound you did not chase: the journalist who quotes you, the customer who arrives already sold, the search result that ranks because other builders linked to your thinking. I made the case in the AI-native founder playbook that a founder’s published reasoning is now a real moat, harder to copy than most features. Authority is that moat being built one post at a time.

The third conversion is receipts into credibility. This is the conversion founders most often skip and most need. A receipt is anything verifiable: a real number, a real artifact, a real customer outcome. Receipts do not win you a casual follower. They win you the high-stakes yes. An investor doing diligence, a senior hire weighing your offer against a safer one, a partner deciding whether to integrate. Those people are not moved by a clever thread. They are moved by a public track record that was impossible to manufacture.

The fourth conversion is feedback into product. When you build in public, the audience stops being a passive crowd and becomes a research panel that volunteers for free. They tell you which feature they want, which pricing makes them flinch, which word in your headline does not land. Founders who build in silence pay agencies for this and get it late. Founders who build in public get it daily, in the replies, from the exact people who would buy.

Climbing the Ladder: What Each Rung Looks Like in the Wild

Frameworks are clean. Feeds are messy. So here is what climbing the Proof Ladder actually looks like, using founders who have run the experiment long enough for the results to mean something.

Start with the strongest existing case. Pieter Levels has built in public on X since around 2018, when he put a live, public revenue page on each of his projects. Not a screenshot, a page. By 2025 he had roughly 600,000 followers and about 3.1 million dollars in total annual revenue across a portfolio he runs with zero employees. Photo AI alone went from 5,400 dollars in its first week after launch in February 2023 to roughly 132,000 dollars in monthly recurring revenue eighteen months later. Nomad List has run for over a decade and reportedly clears about 5.3 million dollars a year.

The instinct is to credit the follower count. That is backwards. Levels did not get the revenue because he got famous. He got both because he lived on Rung 4 and Rung 5 for years. The public revenue pages are Rung 5 artifacts, updating continuously, impossible to fake because anyone could check. Seven years of that does something no amount of Rung 1 posting can do. It makes every new launch land on people who already have proof he ships real things that make real money.

Now the cautionary half. Buffer was one of the original open-startup companies. It published salaries, revenue, and equity, and it built a real reputation on that openness. Over time Buffer quietly pulled back, and most of the famous dashboards went dim. Nothing scandalous happened. But the company learned the same lesson Bankless learned the hard way: the openness you start is not free to stop. Once an audience treats your numbers as a public good, reducing what you share reads as a story even when it is not one. The ladder has a property nobody mentions. You can climb it. Climbing back down is expensive.

Look across the smaller end and the pattern repeats. A wave of one-to-five-person software businesses built durable revenue while building in public: tools clearing high six figures and crossing a million in annual revenue, run by founders who shared the climb. None of them got there on hot takes. They got there because the public record of the build became the reason strangers tried the product.

There is hard data underneath the anecdotes too. Non-technical founders who build in public on LinkedIn and X see meaningfully higher engagement on business-narrative posts than on plain feature announcements, by a factor that is not subtle. The collective networks of a startup’s own people tend to run roughly ten times larger than the company page’s follower base, and content from individuals consistently outperforms content from brand accounts by a wide margin. One founder reported driving the large majority of inbound leads through personal content alone. The mechanism is not mysterious. People follow people. They tolerate brands. Building in public is the founder choosing to be the channel, instead of renting a worse one.

The takeaway from the wild is the same as the takeaway from the framework. The founders who win at this are not the loudest. They are the ones whose feed, read end to end, is a track record rather than a highlight reel. Which brings us to the way it goes wrong.

The Performance Trap: When Sharing Replaces Shipping

There is a failure mode in building in public that is more dangerous than not doing it at all, because it feels like progress while it quietly removes progress. I call it the Performance Trap. It is the slow substitution of performing the work for doing the work.

It does not announce itself. It creeps. You post about a feature and the post does better than the feature would have. You write a thread about your “framework for prioritization” and it gets shared more than anything your product has ever done. Your brain, which is a reward-seeking machine, notices. Posting pays out in minutes. Building pays out in months, if ever. Given a free choice and a hard week, the founder drifts toward the thing that pays today. Within a quarter you have a founder who is, in measurable terms, a content creator who happens to have a startup attached.

The matrix has two axes. One is how much you share. The other is how much you actually build. Most advice treats only the sharing axis, which is the whole mistake. The build axis is what decides which quadrant you are in.

Top-left is the Stealth Builder. High build, low share. A real product, real progress, and almost no one watching. This founder is not lazy. They are just running the meters in sequence, and they will discover on launch day that a finished product and a cold audience is a brutal combination. Bottom-left is the Ghost. Low build, low share. Nothing is happening and no one knows, which at least has the honesty of being obviously a problem.

Top-right is the target. High build, high share. The build is genuinely happening and the act of building is genuinely broadcast. The two meters run together. Distribution compounds while the product gets real. This is the only quadrant where building in public earns its name.

Bottom-right is the Performer, and it is the trap because it looks like the target. High share, low build. The feed is alive. The threads perform. The follower count climbs. And the company underneath is hollowing out, because every hour that should have gone to the product went to the post about the product. The cruel part is that the Performer’s feed often outperforms the genuine builder’s feed, because performance optimized for engagement beats honesty optimized for accuracy. The Performer is winning the game on the screen and losing the game that matters. You do not fall into this quadrant in a day. You drift, one rational-feeling choice at a time. The defense is not willpower. It is a rule, and we will get to it.

The Disclosure Line: What to Share, What to Protect, What You Can Never Hide

“Build in public” gets misheard as “share everything.” That is not the strategy and it never was. The strategy is strategic visibility: share your thinking and your evidence, protect your tactics and your timing, and understand that one category is different from both. The Disclosure Line is how I sort it.

There are three buckets, not two. Most founders only see two, share and protect, and the missing third bucket is the one that ended Bankless badly.

The green bucket is share freely. Vision, reasoning, and the lessons you took from your own mistakes. None of this is a competitive secret, and all of it is what makes a stranger decide you are worth following. A founder who is shy about vision and reasoning is leaving the entire authority conversion on the table.

The amber bucket is share selectively, and the operative word is selectively, not secretly. You can share revenue, but the moment you do, you have committed to a cadence, because a number shown once and then withheld reads as a number that got worse. You can share the roadmap, but share the direction and not the dates, because a public date you miss is a debt the audience will collect. You can teach growth tactics, but teach the durable principle, not the live edge that dies the day a competitor copies it.

The red bucket is the one founders forget exists, and it is not “protect.” It is never go dark. Setbacks, layoffs, a pivot that hurts, a public promise you failed to keep. You have real freedom in how you frame these. You have zero freedom to disappear. This is the rule the Performance Trap and the Bankless story both point at. When you build an audience by being present, your presence becomes the product, and the absence of it during hard news is read, correctly, as either fear or contempt. The audience does not actually demand that you win. It demands that you stay in the room. Founders who internalize that survive their bad quarters in public. Founders who do not, do not.

What Building in Public Compounds Into

It is worth being concrete about the payoff, because “it builds trust” is too soft to plan around. Done right, over a year, building in public compounds into four assets a company would otherwise have to buy, and mostly cannot.

The first is a distribution channel you own. Not rented attention that vanishes when the ad budget stops, but a standing audience that shows up because of who is talking, not because of a bid. This is the asset that makes the second, third, and tenth product cheaper to launch than the first. The founder who has built in public for two years is not starting from zero ever again. I described the compounding revenue math behind owned channels in the zero-to-ten-thousand-MRR playbook, and owned distribution is the input that makes that math work.

The second is a hiring advantage. Senior people are not won by a job description. They are won by a year of public evidence that the founder is sane, competent, and honest under pressure. A strong candidate weighing two offers will pick the founder whose track record they can read. Building in public makes that record exist.

The third is search and citation surface. Founder content gets linked to, quoted, and increasingly cited by the AI systems people now use to decide what to try. Product pages rarely earn that. Honest, specific, repeated thinking does. Every Rung 3 post is a small piece of surface area that keeps working long after you posted it.

The fourth is optionality. When you have an owned audience and earned authority, you can change your mind in public. You can kill a product, which I argued is a core founder skill in the case for killing ideas faster, and the audience follows you to the next one because they were trusting you, not the product. A founder without that audience has to rebuild belief from scratch every pivot. A founder with it carries the belief across.

The Contrarian Take: Building in Public Is a Liability, Not a Megaphone

Here is what most of the advice gets wrong, including a lot of advice that is otherwise good.

Building in public is sold as a megaphone. A free one. The pitch is that you simply start sharing and attention flows toward you at no cost. That framing is not just incomplete. It is the reason founders get hurt by this strategy.

Building in public is not a megaphone you pick up. It is a liability you take on. The moment you start, you have created an expectation, and an expectation is a debt. Every person who started following because you shared the climb is now holding a position in you. They expect the next update. They expect the story to stay coherent. They expect you to be there when it gets hard. None of that is free. You financed your distribution with a promise, and the promise has terms.

This reframe changes every decision. If building in public is a liability, you do not start it casually, the way you would casually pick up a megaphone. You start it the way you take on any obligation: deliberately, at a size you can service, with a plan for the bad quarter and not just the good one. You do not share a revenue number because it is high this month. You share it only if you are prepared to share it the month it drops. You do not promise a launch date for the applause, because the applause is a loan and the missed date is the bill.

Look again at Bankless through this lens. The mistake was not years of openness. The mistake was treating openness as a megaphone, something you hold when convenient and set down when not. But it was never a megaphone. It was a liability the whole time, and liabilities do not disappear because you stopped looking at them. When the company went quiet during layoffs, it was not declining to use a tool. It was defaulting on a debt, in front of every creditor at once. The audience reaction was not cruelty. It was a margin call.

The reframe is also strangely freeing. A megaphone makes you feel you should always be louder. A liability makes you ask the right question instead, which is not “how do I get more reach” but “what can I actually service.” And the honest answer for most founders is: less, more consistently, with proof. A small audience you never go dark on is worth more than a large one you ghost. That is the whole game, and almost no one frames it that way, because “take on a manageable liability and service it forever” does not sell a course.

What to Do Monday Morning: The Weekly Operating Cadence

Frameworks are useless without a cadence. Here is the operating loop I would hand a founder starting from zero. It costs about three hours a week, which is the most you should spend, because the build still has to win the calendar.

1. Pick one platform and one problem. One platform, because two done badly beats nothing and one done well beats two done badly. Pick where the people who have your problem already gather, which for most founders is X or LinkedIn. One problem, because your feed needs a spine. If a stranger reads ten of your posts, they should be able to finish the sentence “this person is the one who thinks hard about ___.” If they cannot, you have reach without authority.

2. Run the build first, then narrate it. This is the rule that defeats the Performance Trap. The post is downstream of the work, never upstream. You do not decide what to build based on what would post well. You build what the company needs, and then you narrate what happened. If a week produced nothing worth narrating, the correct move is to post nothing that week, not to manufacture a thread. Protecting this order is the single most important discipline in the whole strategy. The framing I use for keeping the build ahead of the noise is in the founder operating system.

3. Climb the ladder on purpose. Audit last week’s posts against the Proof Ladder. If everything sat on Rung 1, you ran a content account, not a build-in-public channel. Each week, force at least one post onto Rung 3 or higher: a real decision with its real reasoning, a real number, a real artifact. One genuine receipt outperforms five hot takes, and it is the receipt that converts.

4. Validate in the open. Building in public is the cheapest research method that exists. Before you build the next thing, post the problem and the proposed shape and watch the replies. The people who object loudest are doing your discovery for free. This is the same forty-eight-hour validation logic from the rapid validation playbook, run continuously instead of once.

5. Honor the Disclosure Line, especially the red bucket. Decide now, while nothing is wrong, what you will do when something is. Write the rule down: when a setback happens, you post within a defined window, you frame it honestly, and you do not go dark. The time to make that decision is before you need it, because in the bad week your instinct will be to hide, and the instinct is wrong.

6. Review monthly, not daily. Daily metrics will pull you toward whatever spikes, which is the Performance Trap wearing a dashboard. Once a month, ask the only question that matters: did the sharing convert into one of the four assets, or did it just produce likes? If it produced only likes, you are in the bottom-right quadrant and you need to climb back up the build axis. The honest monthly review is the whole immune system.

Frequently Asked Questions

What does building in public actually mean?

Building in public means sharing the real, ongoing process of building a company, including decisions, numbers, setbacks, and lessons, while you build it rather than after. As a distribution strategy, it means running the audience meter and the build meter at the same time, so that the act of building also markets the company. It is not the same as posting opinions about your industry. The defining feature is that you are showing your own work, not commenting on the field.

Does building in public still work, or is it saturated?

The Rung 1 layer, opinions and hot takes, is saturated and was never the part that worked. The higher rungs are not saturated, because they are hard. Posting a verified number every month for two years, or running a public dashboard, or narrating real decisions with real constraints, is genuinely difficult, which is exactly why it still converts. Saturation hits the easy content. Proof does not saturate, because most people will not do the hard version.

How is building in public different from content marketing?

Content marketing produces content as a separate work stream, usually polished, often written by a team, and aimed at a keyword or a funnel stage. Building in public produces content as a byproduct of the work itself: the artifact is the build, and the post is the narration of it. Content marketing scales by hiring. Building in public scales only with the founder’s own honesty and consistency, which is its limitation and also its defensibility, because the byproduct of a real build is very hard for a competitor to fake.

Should I share revenue numbers publicly?

Only if you will commit to sharing them on a consistent cadence, including the months they fall. A revenue number shown once and then withheld reads as a number that got worse, which is often worse for trust than never having shared. Numbers are high on the Proof Ladder because they are verifiable evidence, but they only build trust when they form a continuous, honest record. Share selectively and consistently, or do not start.

What is the biggest mistake founders make building in public?

Two mistakes tie. The first is the Performance Trap: letting the posting replace the building, because posting pays out faster, until the feed is alive and the company is hollow. The second is going dark during bad news. An audience built on your presence reads silence during a hard moment as fear or contempt, and the trust you spent months building can fall in a week. Both come from treating building in public as a megaphone rather than the liability it actually is.

How much time should building in public take?

Around three hours a week is a sensible ceiling for a founder who still has to build the product. Most of that is narration, not creation, because the events you are narrating already happened during the work. If building in public is consuming a full day a week, you have likely drifted into the Performer quadrant, where producing content has quietly become the job. The build must keep winning the calendar.

Do I need a large audience for this to work?

No. Usable distribution is not raw follower count. A small audience of people who share your specific problem converts far better than a large audience collected through unrelated viral posts. A few thousand of the right followers, who never see you go dark and regularly see your receipts, is a real distribution asset. The goal is a trusted relationship at a size you can service, not a number you cannot.

Can building in public hurt my company?

Yes, in three ways. It can pull you into the Performance Trap, where sharing replaces shipping. It can create public promises, on dates or numbers, that become debts you cannot pay. And it can expose you during a downturn if you have not decided in advance how you will handle hard news. All three are managed by the same discipline: treat building in public as a deliberate liability you size and service, run the build before the narration, and decide your bad-news rule before you need it.