The founder playbook for sharing your journey openly to attract customers, collaborators, and community — without giving away your secrets.
Building in public means sharing your progress, your decisions, your setbacks, and sometimes your numbers with an audience while you are still building the company, not after you already have a story with a tidy ending.
Take Priya, who is building a scheduling app for independent barbershops. Instead of working quietly for a year and then launching with a polished announcement, she posts a short update every week: what she shipped, which shop owners signed up, and what broke. In her third month, exactly two shops used the app and one of them asked for a refund. She posted that too.
That does not mean sharing everything. Building in public is selective transparency, not an unfiltered diary. Priya does not post her cofounder's home address, her exact bank balance, or the specific pricing logic that took her two months to get right. She posts enough real detail that people can tell she is not manufacturing a success story, while keeping back the details that would only help a copycat or expose someone else's private information.
The practical reason this matters: an audience that watches you struggle in month three is far more invested in your company by month twelve than one that only hears about you on launch day. You cannot buy that kind of relationship with a single well produced announcement.
A useful test before you post: would this update embarrass you, or would it just make you a little uncomfortable? Discomfort is normal, and it usually means the post is honest. Embarrassment, like naming someone without asking or revealing a number you promised a partner you would keep private, means do not post it.
Trust is the scarcest resource for a new company online, and it is expensive to fake. When Alex, a solo founder building an invoicing tool for freelance designers, posted his monthly revenue screenshots going from $340 in his first month to $2,100 four months later, three of his next ten customers told him directly that the numbers were the reason they were willing to buy from a two person company they had never heard of. A polished landing page cannot produce that same effect, because a landing page cannot be wrong. Alex's numbers could have looked bad, and the fact that he posted them anyway is what made them convincing.
Building in public also works as distribution and recruiting at the same time. Customers, future employees, and other founders who might become collaborators are often reading people who post honestly about their work, and a well told story about a real decision reaches people that a marketing page never will. When Alex explained, in a single post, why he chose to charge freelancers a flat monthly fee instead of a percentage of each invoice, that post was shared far more than any feature announcement he wrote, because a real reason is more interesting than a list of features. Every post like that is a chance to reach someone who would never have found him through search or ads, and unlike an ad, the reach does not stop the moment the budget runs out.
There is also a behavioral effect that has nothing to do with what the audience thinks of you. Telling a group of people, publicly, that you plan to ship a feature by Friday changes how you spend your Tuesday. Maria, who builds a fundraising tool for small nonprofits, started posting a Monday plan and a Friday recap every week specifically because she noticed she finished far more of what she intended to when other people were watching for the recap. That is not a trick. It is a normal, well documented effect of public commitment, and it works whether or not anyone actually reads the post.
Where you post matters less than posting somewhere consistently, but the platforms are not interchangeable. Each one reaches a different kind of audience, and picking the wrong one for your business means writing into a room nobody relevant is actually in.
| Best for | |
|---|---|
| X / Twitter | Founder communities, tech/startup audience |
| B2B businesses, professional audience | |
| Substack / Newsletter | Long-form updates with a loyal following |
| YouTube | Video walkthroughs, tutorial content |
| Indie Hackers | Product/SaaS founders specifically |
Pick one platform and be consistent. Quantity matters far less than consistency. A smaller, engaged audience on one platform beats a thin presence spread across five.
Which platform fits your situation
What best describes your audience and your main strength as a communicator?
The hardest part of building in public is the first post, because it is the one where you have the least to show and the most self consciousness about showing it. The fastest way through that is a plan for exactly what the first week looks like, so you are not deciding what to post from scratch every day.
Your first week
0/4Check your understanding
Jordan is building a project management tool against a better funded competitor. A feature that took three months to build is central to why customers are switching from that competitor. Jordan is drafting a public post about it. What should Jordan do?
Maria wants to start building in public but feels she has nothing impressive to share yet, since her app has zero paying users. What does the lesson suggest she do?
A founder building a B2B compliance tool for law firms is deciding where to invest most of her public building energy. Her buyers are professional decision makers, not general consumers. Which platform does the lesson point to as the best general fit?
A founder is about to publish a build-in-public update that includes a screenshot of a Slack conversation with a customer, including the customer's full name and company, without asking first. What is the problem with this post?
Ask a question about this lesson or share your take.
Loading…
| Revenue, customers, and growth rate, shared selectively. Even approximate figures are valuable |
| Nothing extra to withhold here, beyond figures a competitor could use to undercut your pricing |
Before you screenshot a conversation
If an update includes another person, a customer quote, a screenshot of a message, a photo from a meeting, ask that person first. A simple rule of thumb: if you would be surprised to learn someone had screenshotted your private conversation and posted it, do not do it to someone else, even with good intentions.