Building in Public: How Founders Turn Transparency Into Their Biggest Growth Channel
The complete building in public playbook — what to share, where to share it, how to measure ROI, and a 90-day action plan for founders.
Whether you're looking for an angel investor, a growth advisor, or just want to connect — I'm always open to great ideas.
Get in TouchAI, startups & growth insights. No spam.
Building in public is not a content strategy. It is a distribution strategy disguised as honesty. When done right, it compounds: every post you publish today is a trust deposit that pays dividends six months from now when someone is evaluating your product. This guide covers the full playbook — the philosophy, the mechanics, the dark side, and a 90-day week-by-week plan to get you started.
I remember the first time someone told me to "build in public." It was 2019, and the advice felt niche — something indie hackers did on a forum called Indie Hackers while bootstrapping SaaS tools in their spare bedrooms. It felt authentic but small. A handful of founders sharing revenue milestones in public, getting polite applause from their peers.
That world no longer exists.
In 2026, building in public has moved from the fringe to the mainstream. It is now a legitimate distribution channel that B2B SaaS companies, consumer apps, and even venture-backed startups use deliberately. Notion built an entire community strategy on top of it. Linear's founders posted design decisions that became legendary in product circles. Loom shared internal retrospectives before being acquired. The pattern is not coincidental — it is strategic.
But here is where most founders get building in public wrong: they think it means sharing revenue screenshots.
Revenue screenshots are one data point. Building in public is a posture. It is the decision to make your process visible — your decision-making, your failures, your course corrections, your reasoning, your product evolution. Revenue is the output. Building in public is about making the inputs visible.
The three pillars of modern building in public:
1. Process transparency — showing how you think, not just what you decided. When I decided to rearchitect a core part of AutoResearch, I did not just announce the new feature. I wrote about why the original architecture failed, what tradeoffs I was evaluating, and which option I ultimately chose and why. That single post got more inbound DMs than any product announcement I have ever made.
2. Metric transparency — sharing trends, not just vanity peaks. The indie hacker era was dominated by "$X MRR" posts. That still works for audience growth, but what builds genuine trust with buyers and investors is trend data. MRR growing 18% MoM for six consecutive months says more than a single screenshot at a high-water mark.
3. Learning transparency — documenting what did not work. This is the hardest and the highest-leverage form. When you share a failure with specificity — what you tried, what happened, what you learned — you signal intellectual honesty. Buyers want to work with founders who can identify and correct mistakes. Investors want to back founders who have pattern recognition earned through real reps.
The evolution from indie hacker content to mainstream B2B building in public is also a content quality evolution. Early BIP content was casual and unstructured. Today's best practitioners treat it as a craft: tight narratives, specific data, actionable frameworks, and distribution discipline. If you are a founder starting in 2026, you are entering a more competitive content environment than 2019, but also one with far better infrastructure — newsletters, short-form video, LinkedIn algorithms that actively reward founder content, and X Communities that aggregate niche audiences efficiently.
The founders who win with building in public in 2026 are not the ones who share the most. They are the ones who share the most usefully.
Let me give you numbers before philosophy.
Edelman's Trust Barometer has consistently shown that B2B buyers trust "a person like me" more than advertising. In the 2025 edition, 74% of B2B buyers said they would pay a premium to work with a company they trust, and "founder visibility" was among the top five trust signals. This is not anecdotal — it shows up in pipeline data.
Here is what I have observed across my own products and in conversations with founders who build in public consistently:
Shorter sales cycles. When a prospect has been following your public journey for three months before they reach out, the first conversation is not introductory. They know your positioning, your values, your product philosophy. You are negotiating terms on the first call, not educating. I have had enterprise deals close in under two weeks because the founder's newsletter content had done the trust-building over six months.
Higher inbound-to-close rates. Inbound leads from content typically convert at 2-4x the rate of outbound. When the inbound is from someone who has been consuming your building in public content — who has seen your failures and recoveries, your product thinking, your customer empathy — the conversion rate is even higher. They are self-qualified. They came to you.
Investor interest. This one surprised me when I first experienced it. Investors increasingly monitor founder content as a signal of communication ability, strategic clarity, and community resonance. Several of the best investor conversations I have had started with "I've been following your posts about X." The content was the cold email. If you are raising money in 2026, a consistent public presence is not a vanity metric — it is due diligence support.
Compounding organic reach. Paid acquisition costs more than it ever has. Apple's ATT changes gutted performance marketing for consumer apps. Google's AI-generated answers are cannibalizing SEO click-through. In this environment, owned distribution — your newsletter, your social following, your community — is a moat. Building in public is the fastest way to grow owned distribution authentically, because it gives people a reason to follow you that is not purely promotional.
Talent attraction. The best engineers and product managers research founders before accepting offers. A consistent public presence that demonstrates how you think about hard problems, how you treat failures, how you communicate with your team — that is a recruiting asset. I have had senior hires tell me explicitly that reading six months of my posts made them comfortable making the leap.
The counterargument you will hear is that building in public is time-consuming and the ROI is hard to measure. Both are true. I will tackle measurement in section eight. On time: yes, it costs hours. But those hours compound in a way that paid ads never will. An ad stops the moment you stop paying. A post stays indexable, shareable, and findable for years.
This is the question I get most often, and the answer is not instinctive. Most founders either over-share in ways that create legal or competitive exposure, or under-share to the point that their "building in public" is indistinguishable from a corporate press release.
Here is the framework I use:
Do not say "We decided to focus on SMB." Say "We spent three weeks analyzing our win/loss data and realized we were winning 73% of SMB deals but only 22% of enterprise deals. The deals where we lost enterprise, the same two objections came up every time: SOC 2 and SSO. We are not going to build those in the next 12 months. So we are making SMB our primary focus and declining enterprise inbound until we can serve it properly."
The second version is useful. It teaches people something about how to think about ICP decisions. It signals that you are analytical. It also pre-empts the "why don't you have SSO" questions in demos.
You do not have to share your exact MRR if you are not comfortable with that level of exposure. But you can share directional data. "We grew revenue 23% in February. Our activation rate improved from 34% to 51% after shipping the new onboarding flow" is genuinely useful content that demonstrates growth without putting a precise number on your valuation.
If you are comfortable sharing exact numbers — and many founders are — great. The specificity makes the content more credible. But do not let discomfort with exact figures stop you from sharing the trend.
The most valuable content I have ever published was a postmortem of a feature launch that failed. We spent six weeks building it. We launched it to a segment of our users. Adoption was 4%. I published a 1,200-word breakdown of what we built, why we thought it would work, what the actual behavior data showed, and what we concluded. That post has been shared more than any product announcement I have made. Why? Because it is honest, it is instructive, and it signals that we learn.
When a customer call reveals something surprising about how people use your product, share the learning. "Had a call today with a customer who uses our product in a way we never anticipated — they've built an entire internal workflow around it that we're now documenting as a use case." This kind of post builds trust with potential buyers who want to know that you listen to customers.
If you are in a raise, do not share anything that could be considered a public solicitation of investment unless you have cleared it with legal counsel. If you are in a dispute, do not share anything about it. If your financials are subject to investor confidentiality agreements, check those agreements before you publish MRR screenshots.
You can share that you made a hard team decision without sharing who was involved or why. "We made a change to our leadership team this month" is a legitimate thing to acknowledge without becoming a public tribunal. Your team members deserve privacy even if you are a public founder.
Your product roadmap is a liability if you share it too specifically. Sharing themes is fine — "We're focused on making collaboration workflows faster this quarter." Sharing specific feature specs in advance is a gift to competitors who can build faster and beat you to market.
This one is obvious but worth stating. Anything related to patents, trademarks, legal disputes, regulatory filings — keep it private until it is resolved and public by nature.
The transparency spectrum at a glance:
| Always Share | Share Selectively | Keep Private |
|---|---|---|
| Learnings from failures | Exact MRR | Active legal disputes |
| Decision frameworks | Roadmap specifics | Team conflicts |
| Metric trends | Competitor analysis | IP/patent details |
| Customer insights (anon) | Partnership discussions | Raise negotiations |
| Product philosophy | Hiring pipeline | Exact cap table |
Not all platforms are equal, and not all products belong on all platforms. Here is how I think about platform selection as a founder.
X is still the best platform for reaching technical founders, early adopters, and the startup ecosystem. The algorithm rewards engagement velocity — posts that get a reply and a repost in the first 30 minutes tend to get amplified significantly. This favors opinion posts, contrarian takes, and posts that ask a genuine question.
The X audience tends to be tech-heavy and skews younger in startup demographics. If you are building a developer tool, a B2B SaaS, or any product targeting the startup ecosystem, X is your highest-leverage starting point.
Best format on X: Threads. A well-structured thread with a punchy opener, 6-8 substantive posts, and a clear CTA at the end consistently outperforms single posts. The opener is everything — it is the ad headline for the rest of the thread.
Posting cadence: 1-2 posts per day if you are building audience. 3-5 posts per day if you are in growth mode. Quality matters more than frequency, but frequency matters more than most people admit.
The X trap to avoid: Getting into debates. Engagement bait works short-term but attracts an audience that does not buy your product. Stay on-topic: your product, your market, your learnings.
LinkedIn has had a genuine renaissance in the last three years. The algorithm is aggressively pushing native text posts, and the platform skews professional in a way that X does not. If your product is B2B — and especially if your buyers are senior decision-makers at established companies — LinkedIn is where they spend time.
The LinkedIn audience is less cynical than X and more receptive to personal narrative. A post about your founder journey, the moment you almost quit, what you learned from a failing product — that kind of content performs exceptionally well on LinkedIn and would feel performative on X.
Best format on LinkedIn: First-person narrative posts (500-800 words) or short bullet-point listicles. Carousels have died in recent algorithm updates. Native video is gaining traction. Long paragraphs without white space get buried.
The LinkedIn hook formula: Line one is the hook. Make it a specific claim or counterintuitive statement. Never start with "I" as the first word — it suppresses reach. Start with the insight: "73% of our early users churned in the first week. Here's what we did about it." That sentence gets the click-to-expand. Then deliver the substance.
Posting cadence: 3-4 times per week. LinkedIn is less forgiving of high-frequency posting than X — there is a quality bar that readers hold you to, and posting too frequently without substance will tank your reach.
If social platforms are rented land, your newsletter is owned land. Algorithm changes do not affect it. Platform shutdowns do not kill it. Your subscriber list is an asset on your balance sheet in a way that your Twitter following simply is not.
Building a newsletter alongside your building in public practice is the highest-leverage thing you can do for long-term distribution. It takes longer to build than social — growth is slower, the feedback loop is delayed — but the relationship with a newsletter subscriber is qualitatively different from a social follower. They gave you their email address. That is permission marketing in the truest sense.
Substack and Beehiiv are the two platforms worth evaluating in 2026. Substack has the larger existing network and discovery mechanism. Beehiiv has better analytics and monetization infrastructure. For most founders starting out, Substack's built-in recommendation engine makes it the better starting point for discovery.
Newsletter cadence: Weekly is the gold standard for keeping open rates high. Bi-weekly works if your content is long-form and substantive. Monthly is too infrequent to build a habit with your readers.
YouTube is the highest-trust platform because it requires the most commitment from the viewer. Watching a 12-minute video from a founder is an investment. When someone watches three of your videos, they know you — your cadence, your reasoning, your personality. That kind of familiarity converts.
YouTube is not the right starting platform for most founders because the production barrier is real and the audience-building timeline is long. But if you are comfortable on camera and have the patience for a 6-12 month runway before meaningful audience growth, YouTube is the highest long-term ROI platform.
Best formats for founders on YouTube: Dev logs (building the product in real time), monthly retrospectives to camera, "how we built X" deep dives, and product walkthroughs with founder narration.
The YouTube reality check: Consistency is everything. YouTube's algorithm rewards channels that publish on a predictable schedule. If you cannot commit to biweekly videos, do not start. An abandoned YouTube channel is worse than no YouTube channel.
| Product Type | Primary Platform | Secondary Platform |
|---|---|---|
| Developer tool | X/Twitter | GitHub discussions |
| B2B SaaS (SMB) | Newsletter | |
| B2B SaaS (enterprise) | Newsletter | |
| Consumer app | X/Twitter or TikTok | YouTube |
| No-code / low-code | X/Twitter | YouTube |
| Community product | Newsletter | X/Twitter |
Start with one platform. Master it. Then add a second. Founders who try to be everywhere simultaneously produce mediocre content on all platforms. Founders who go deep on one platform build genuine audience before expanding.
Theory is useless without execution templates. Here are the six formats that consistently perform well for building in public content, with fill-in-the-blank templates for each.
What it is: A regular update on what you built, what broke, and what you are building next. Weekly or biweekly cadence.
Why it works: Regularity builds habit. Readers who follow your dev log develop genuine investment in your product's progress. They feel like insiders.
Template:
Dev Log #[NUMBER] — [DATE]
What shipped this week:
- [Feature/fix] — [one-line description of impact]
- [Feature/fix] — [one-line description of impact]
What broke:
- [Issue] — [what happened, what we did]
What I learned:
[One specific insight from this week's work]
What's next:
- [Top priority for next week]
- [Second priority]
[Optional: one metric — "Activation rate is now X%"]What it is: A structured snapshot of your key metrics at month-end. Revenue, growth rate, churn, activation, NPS — whatever your most important numbers are.
Why it works: Consistent data publication builds credibility over time. Readers who follow you for six months can see trajectory, not just snapshots.
Template:
[Month] Metrics
Revenue: $[X] ([+/-X%] MoM)
Users: [X] ([+/-X%] MoM)
Activation rate: [X%]
Churn: [X%]
NPS: [X]
The highlight: [One thing that went well and why]
The lowlight: [One thing that underperformed and what you're doing about it]
The question I'm still sitting with: [One unresolved strategic question]What it is: A structured breakdown of something that did not work — a launch, a feature, a marketing experiment, a hire.
Why it works: Authenticity. Postmortems are the highest-engagement format in building in public because they are rare and credible. Anyone can write a success story. Only founders with genuine intellectual honesty write postmortems.
Template:
We tried [X]. It failed. Here's the full breakdown.
**What we built:**
[2-3 sentences on the initiative]
**Why we thought it would work:**
[The hypothesis]
**What actually happened:**
[The data]
**Where the hypothesis was wrong:**
[Root cause analysis — be specific]
**What we're doing differently:**
[Concrete next step]
**What I'd tell my past self:**
[The one-sentence lesson]What it is: A public record of a major product or strategy decision, including the options you considered and why you chose what you chose.
Why it works: Decision journals attract smart readers who enjoy thinking through problems. They position you as a thoughtful operator. They also generate high-quality replies that often contain useful perspectives you had not considered.
Template:
Decision: [What you decided]
Context: [Why this decision needed to be made now]
Options we considered:
1. [Option A] — pros: [X], cons: [Y]
2. [Option B] — pros: [X], cons: [Y]
3. [Option C] — pros: [X], cons: [Y]
Why we chose [Option X]:
[Your reasoning, including the factors that tipped the decision]
What we're watching to know if we were right:
[1-2 leading indicators]
What would make us change course:
[The specific signal that would trigger a pivot]What it is: A technical or strategic breakdown of how a specific feature, system, or process was built.
Why it works: High shareability among technical audiences. Positions you as a practitioner, not just a commentator. Drives traffic to your product from people who find the implementation interesting.
Template (for X thread):
Tweet 1 (hook): We just shipped [X]. Here's how we built it — including the two ideas we threw away. [thread]
Tweet 2: The problem we were solving: [specific user pain in one tweet]
Tweet 3: Our first approach: [what we tried]. Why it didn't work: [specific reason]
Tweet 4: Our second approach: [what we tried]. Why it didn't work: [specific reason]
Tweet 5: What we actually built: [the solution]
Tweet 6: The technical decision that mattered most: [one specific choice and why]
Tweet 7: What we got wrong even in the final version: [honest admission]
Tweet 8: What users are doing with it that we didn't expect: [one observation]
Tweet 9 (CTA): If you're building something similar, [relevant resource] or [question to engage replies]What it is: A structured breakdown of a product launch — what worked, what did not, what the numbers showed, what you would do differently.
Why it works: Launches are high-stakes moments that attract attention. A retrospective extends the life of the launch moment and generates learning content that continues to get traffic long after the launch is over.
Template:
[Product/Feature] Launch Retrospective
Launch date: [date]
Launch platforms: [where you launched]
The numbers:
- Day 1: [signups/downloads/revenue]
- Day 7: [metric]
- Day 30: [metric]
What worked:
- [Specific tactic] — [specific result]
- [Specific tactic] — [specific result]
What didn't work:
- [Specific tactic] — [what happened instead]
- [Specific tactic] — [what happened instead]
The surprise:
[One thing that happened that you didn't anticipate]
If I launched again tomorrow, I would:
1. [Specific change]
2. [Specific change]
3. [Specific change]The principles of building in public are universal, but the execution differs significantly based on whether you are selling to businesses or consumers.
B2B buyers are evaluating you as a vendor, not just as a founder. They care about operational excellence, product reliability, customer success, and strategic clarity. Your building in public content should reflect these values.
Focus on process and decisions: B2B buyers want to understand how you make decisions, because they are essentially betting that your decision-making will produce a reliable product. Show your prioritization framework. Share your support ticket analysis. Document how you approach enterprise security requirements.
Share customer success stories with permission: In B2B, social proof is currency. A detailed case study — even anonymized — showing how a customer achieved a specific outcome with your product is worth more than any marketing copy. Build these into your regular content cadence.
Be specific about your ICP: B2B buyers are filtering constantly. A founder who clearly articulates who they serve and who they do not serve creates confidence. "We serve seed to Series B SaaS companies with a product-led growth motion" is more valuable than "We serve startups." It tells potential buyers immediately whether they are in your world.
Metrics to share in B2B: Uptime, support response time, time-to-value for new customers, activation rates, retention cohorts by segment. These operational metrics are what B2B buyers actually want to see — they signal product maturity and operational discipline.
Tone: Professional but human. You are not writing a press release. But you are also not writing a casual thread that might read as flippant to a CFO evaluating a $50k annual contract. Find the voice that is specific and honest without being casual to the point of undermining confidence.
B2C building in public is closer to the original indie hacker tradition — more personal, more product-focused, more design-driven.
Focus on product and design: Consumer users fall in love with products that feel thoughtful. Sharing the design process — sketches, iterations, the reasoning behind UI decisions — builds the kind of aesthetic investment that drives word-of-mouth.
Share user stories: Consumer products live or die by the emotional resonance they create. When a user tells you your app changed their morning routine, share that story (with permission). User stories humanize the product and create the social proof that consumer products run on.
Be transparent about the journey: Consumer audiences are more forgiving of vulnerability than B2B audiences. The personal narrative of what motivated you to build this product, the sacrifices you made, the almost-quit moments — these resonate with consumer audiences in a way that B2B audiences sometimes find distracting.
Metrics in B2C: Download counts, daily active users, retention curves, app store ratings, NPS. Unlike B2B, raw user numbers are more meaningful social proof in consumer contexts — they signal that real people are choosing your product in a competitive market.
Tone: Conversational, personality-forward. Your personality is a feature in B2C. People follow founders whose voice they find compelling, and they download products made by founders they feel they know.
I have been building in public for years, and I would be doing you a disservice if I did not address what no one tells you when they evangelize transparency.
When you publish your roadmap themes, your growth tactics, your customer acquisition channels — you are publishing a playbook that your competitors can read. I have had features copied within weeks of publishing a thread about them. I have had growth tactics replicated by better-resourced competitors who could execute faster.
How to handle it: Share the learning, not the blueprint. You can discuss the reasoning behind a product direction without giving a step-by-step implementation guide. Share what you are observing and why it matters — not the exact code or the specific channel configuration that is driving results. Lag your content: share what you did three months ago, not what you are doing today.
The moment you have any kind of audience, you will attract bad-faith engagement. People who misrepresent what you said. Founders from competing products who comment to undermine your credibility. Former employees or collaborators with axes to grind. Strangers who simply enjoy causing conflict.
How to handle it: Do not engage. Seriously. Mute, block, move on. Engaging with trolls gives their content distribution by generating engagement. The founders who handle this best develop a ruthless filtering instinct — they can identify bad-faith engagement in the first reply and decide in under five seconds whether it merits a response (almost never) or a mute (almost always).
Building in public can start to feel like a performance of vulnerability. After sharing a few failures, you might notice that your audience expects more failure content — and that you start unconsciously searching your experience for failure stories to share, or worse, manufacturing a performance of struggle that is not authentic.
How to handle it: Remember why you started. The goal is not vulnerability for its own sake — it is useful transparency. If a failure or challenge is genuinely instructive, share it. If you are sharing it because you think it is what your audience wants, stop.
When you share specific metrics, you are giving your competitors a benchmark to compete against. If you publish that your NPS is 62, every competitor immediately knows where the bar is. If you publish that your churn is 3.2% monthly, you have told competitors what they need to beat.
How to handle it: Share trends and ranges rather than precise figures in areas that matter competitively. "Our NPS is in the high 60s and has improved each quarter this year" is useful content that does not give competitors a precise target. "Our NPS is 67.3" is unnecessarily precise.
Building in public on rented platforms means you are always one algorithm change away from your reach being cut significantly. I have seen founders build tens of thousands of followers on X, only to see their reach collapse after an algorithm update. LinkedIn has done the same to carousel creators. YouTube has done it to certain content categories.
How to handle it: Build your newsletter from day one. Every platform you use should have a path to email capture — a link in bio, a pinned post, a newsletter mention at the end of every thread. Your newsletter is the backup that survives any platform change.
The most common objection to building in public is that the ROI is unmeasurable. I understand the frustration — it is genuinely harder to measure than a Facebook ad. But it is not unmeasurable.
Here is the measurement framework I use:
For each platform where you are active, track what percentage of your followers have signed up for your product. If you have 5,000 LinkedIn followers and 250 of your signups mention LinkedIn as their discovery source, your LinkedIn follower-to-signup rate is 5%. Over time, track whether this rate is improving — are your followers more likely to convert as your content quality improves?
How to track: Add a "How did you hear about us?" field to your signup flow. Include specific options ("LinkedIn," "Twitter/X," "newsletter," "a specific post") rather than just "social media." Specificity in the answer requires specificity in the question.
For each customer who mentions your content during the sales process or in onboarding, record it. Build a simple spreadsheet: customer name, revenue, content type that influenced them. After six months, you will have data on which content format drives the highest-value customers.
In my experience, newsletter subscribers and YouTube viewers tend to close higher-ACV deals than X followers. They have invested more time in understanding you and your product, and they arrive with higher trust and lower price sensitivity.
When a post goes viral or significantly outperforms your baseline, track whether inbound signups or demo requests spike in the following 48-72 hours. You will not always be able to attribute individual signups to individual posts, but you will notice correlation patterns over time.
Tool: Google Analytics with UTM parameters on all links in posts and your newsletter. When you publish a post with a CTA that links to your product, use a unique UTM so you can see in GA exactly how many sessions came from that post.
Brand search volume — how many people are Googling your company or product name — is a lagging indicator of brand awareness growth. Building in public drives brand search as people who encounter your content for the first time want to learn more. Track this monthly via Google Search Console (for your website) and Google Trends (for general interest).
Monitor how often you and your product are mentioned in relevant forums, communities, and threads compared to your competitors. Tools like Mention or Brand24 can automate this. As your building in public practice scales, your share of voice in relevant communities should increase.
You do not need sophisticated tooling to measure this. A monthly Google Sheet with five columns — platform, follower/subscriber count, MoM growth rate, attributed signups that month, attributed revenue that month — is enough to track whether your investment is working. The key is consistency: measure the same things in the same way every month so you can see trends.
Here is the week-by-week guide I wish someone had given me when I started building in public. This is designed for a founder who is starting from near-zero and wants to build a consistent practice.
Week 1: Set up your infrastructure
Pick one primary platform. Do not try to be everywhere. Based on your product type, use the platform matrix from section four. Create or refresh your profile with a clear bio that answers: who you are, what you are building, and who it is for. Pin a post that introduces yourself and your product.
Start your newsletter. Even if you have zero subscribers. The discipline of writing for an audience — even a hypothetical one — will improve the quality of everything else you write. Sign up for Beehiiv or Substack and publish your first edition: "Why I'm building [product] and what I'll share as I build it."
Week 2: Find your first 10 topics
Open a new document and brain-dump the 10 most useful things you know about your market, your product, or your customer that most people in your position would not share. Do not filter for quality yet — just generate. These are your first ten posts.
Common sources: a misconception you held before you started building, a customer call that surprised you, a feature you built that nobody used and why, a metric that looked good but masked a problem, a decision you made that you would change, a competitor you respect and why, a competitor you think is wrong and why.
Week 3: Publish without overthinking
Publish three posts this week from your topic list. Do not edit them for more than 20 minutes each. The biggest enemy of a building in public practice is perfectionism — you will not publish if you spend four hours on every post. Set a timer. Write. Publish. Move on.
At the end of week three, look at what you published and ask: is this useful? Is it specific? Does it reflect how I actually think? If yes to all three, you are on the right track even if the engagement is low.
Week 4: Engage more than you publish
Spend week four engaging with other founders, with your target customers, and with people in adjacent communities before you worry about your own post volume. Reply to threads in your space. Ask genuine questions. Share other people's work that you found valuable. Building in public is not a broadcast strategy — it is a conversation strategy. Engagement first, publishing second.
Week 5: Audit your first month
Look at your posts from month one. Which ones got the most engagement? Which ones got the most direct messages? Which ones felt most natural to write? There is almost always a pattern — a format or topic type that resonates more than others. Double down on it.
Week 6: Launch your first recurring format
Pick one recurring format from section five and commit to it weekly. Dev logs work if your product is technical and evolving quickly. Monthly metrics work if you are comfortable sharing numbers. Decision journals work if your product decisions are complex and interesting. Pick the one that feels most natural and launch it this week.
Week 7: Your first postmortem
Publish your first postmortem. It does not have to be a catastrophic failure — it can be a small one. An email that got bad open rates. A landing page that did not convert. A feature that nobody used. Apply the postmortem template from section five. This is the content that will generate the most authentic engagement and the most direct messages from people who relate to the experience.
Week 8: Cross-promote to newsletter
Every post you publish this month should include a reference to your newsletter. Not a hard sell — just a mention. "I write about this more deeply in my weekly newsletter [link]." By the end of month two, you should have 50-100 subscribers even without a big audience, because you are converting your existing social followers.
Week 9: Publish your first major piece
Write a piece of content that is designed to be definitive — a complete guide, a detailed case study, a comprehensive breakdown of something you know deeply. This is the content that people bookmark and share repeatedly. It should take you 3-4 hours to write and be 1,500-3,000 words.
Topics that work well for definitive pieces: "Everything I know about [topic] after [X time/attempts]," "The complete guide to [specific process]," "What nobody tells you about [common challenge in your market]."
Week 10: Engage with your audience directly
By week ten, you should have enough audience that direct engagement is meaningful. Reply to every comment on your posts this week — personally and substantively. Message everyone who shared your content to thank them. Ask your newsletter subscribers a direct question: "What would be most useful for me to write about next month?" These conversations generate both content ideas and genuine relationships.
Week 11: Measure what is working
Apply the measurement framework from section eight. Pull your data: Which posts drove the most signups? Which newsletter editions had the highest click-through rates? Are you seeing any correlation between post volume and inbound lead volume? Adjust your content calendar for month four based on what the data shows.
Week 12: Set month four goals
By the end of month three, you should have: a consistent posting cadence on one platform, a newsletter with real subscribers, at least one recurring content format, and your first postmortem published. Now set specific goals for month four: follower count target, newsletter subscriber target, specific content experiments to run.
The founders who sustain building in public past the three-month mark are the ones who treat it like a product — setting goals, measuring outcomes, iterating based on data, and not quitting when a particular post underperforms.
Q: Do I have to share my revenue publicly to build in public?
No. Revenue transparency is one form of building in public, not a prerequisite. Many founders build significant audiences by sharing process, decisions, and learnings without ever publishing an MRR number. That said, specific metrics — any specific metrics — consistently outperform vague content. If you are not comfortable with revenue, share something else that is measurable: activation rate, NPS, user count, time-to-value. Specificity builds credibility regardless of which metric you choose.
Q: I'm pre-launch. Should I wait until I have something to show?
Absolutely not. Pre-launch is actually one of the best times to build in public, because you can take your audience on the journey from zero. Documenting your market research, your early customer interviews, your product decisions before you have a product — this creates narrative continuity that post-launch content lacks. When you eventually launch, your audience feels like they were part of building it. That emotional ownership drives early adoption in a way that cold outreach never can.
Q: How do I handle it when a post does terribly?
Every founder who builds in public has posts that get three likes. It is normal. The instinct is to quit or to conclude that "building in public doesn't work." Resist it. Audience building is not linear. Viral posts happen inconsistently and unpredictably. Your job is consistency — showing up with useful content on a predictable schedule. The compound effect of consistency is what generates results, not any individual post.
Q: My co-founder disagrees with building in public. How do I handle this?
This is more common than people admit. Address it directly: have a conversation about what specifically your co-founder is concerned about. Is it competitive exposure? Is it the time cost? Is it discomfort with public vulnerability? Each of these concerns has a legitimate response. If the concern is competitive exposure, agree on topics that are off-limits. If it is time, agree on a minimal cadence. If it is discomfort with vulnerability, start with formats that feel less personal (product decisions, industry observations) before moving to failure postmortems. Most co-founders who resist building in public are not opposed to transparency — they are nervous about a specific risk. Find and address the specific risk.
Q: How long before I see results?
Expect nothing meaningful for 90 days. Modest results by six months. Significant compounding by 12-18 months. This is not a linear process and it is not a fast one. The founders who succeed at building in public are the ones who treat it as a long-term compounding asset, not a short-term growth hack. If you need results in 30 days, invest that time in direct sales instead. Building in public is a 12-month minimum commitment to see real returns.
Q: What if I work in a heavily regulated industry?
Healthcare, finance, legal, defense — these industries require a different approach. The core principles apply, but the content has to be more careful. Focus on process content that is industry-agnostic — hiring, product development, team building, growth strategy — rather than product-specific content that might touch on regulatory territory. Have your legal counsel review any post that mentions your product category, your customers, or your metrics before you publish. It adds friction but it protects you.
Q: Should I separate my personal brand from my company brand?
In early-stage startups, I recommend leading with the founder brand and building the company brand alongside it. People follow people, not logos. Your personal credibility will always outperform an account that posts as "CompanyName." As the company grows and you hire a team, you can gradually shift more content to the company account while maintaining your personal brand for thought leadership. The mistake founders make is building the company account exclusively and then having no personal equity when they eventually want to build in public as a founder.
Q: How do I maintain this when I'm building a demanding product?
Batch your content creation. Spend two hours on Sunday writing four posts. Schedule them throughout the week. Do not try to write in real-time — most posts that feel spontaneous were actually written in advance. The "just shipped this" tweet often took 20 minutes to write after the shipping was done. Treat content creation as a time-boxed activity with a fixed slot in your week, not as something you do when inspiration strikes.
Building in public is not about performing openness. It is about making your process useful to other people — your potential customers, your future employees, your community, your market. When you approach it that way, the content writes itself, because you are simply documenting what you are already doing.
The founders who build the most durable businesses in the next decade will be the ones who understand that distribution is a product decision. Building in public is not separate from building your product — it is part of how you build the moat around it.
Start this week. Post something specific and true. Do it again next week. Do it for 90 days without worrying whether it is working. Then look at your data.
You will be surprised by what you find.
Udit Goenka is the founder of AutoResearch and writes about building AI products, growth, and the founder experience at udit.co.
Anthropic releases the complete Claude Model Specification publicly — the 'soul document' that defines Claude's values, safety hierarchy, and behavior guidelines for operators and users.
Apple Music announces metadata tags for AI-generated music, creating opt-in disclosure labels that could set a new standard for streaming platforms and the creator economy.
A rare look inside a 38-company angel portfolio: the tracking system, vintage analysis, wins, losses, and the decision framework that evolved over seven years.