Back to Day 3: Distribute

Building in Public

Building in public is the most leveraged distribution channel an indie hacker has if they treat it like a discipline rather than a vibe. Done right, it compounds — the same time spent posting in month 12 reaches 10× the audience as the same time in month 1, signups arrive without paid acquisition, and the trust you build outlasts any individual launch.

Done badly — milestone-baiting, daily growth tweets aimed at other founders, vanity revenue screenshots without context — it actively damages your credibility and trains the algorithm to show your posts only to other indie hackers, not to actual buyers.

This guide is the version that compounds.

Why It Matters

The economics: founders who build in public consistently report 3–5× faster organic audience growth, 30–50% lower customer acquisition cost, and meaningfully higher trust signals during sales conversations compared to founders who stay quiet until launch. Pieter Levels, Tony Dinh, Marc Lou, Danny Postma, and most of the next wave of profitable indie hackers built distribution this way before their products were finished.

The catch: most attempts fail. They fail because they optimize for engagement from other founders ("congrats on the MRR! 🚀") instead of attention from buyers, or because they post sporadically when something exciting happens and disappear in between. The algorithm punishes both.

The version that works treats building in public as content marketing with a documentary format — consistent, narrative-driven, opinionated, and pointed at the specific buyer you want to reach.


The First Decision: Pick Your Audience

Most building-in-public advice glosses over this and it is the most important call you make.

You are choosing between two distinct audiences:

Other founders (Indie Hackers, founder-Twitter, r/SaaS):

  • Easy wins. Founder content is mutually-supportive and likes/RTs come fast.
  • Highest social proof for raising or for hiring future founders.
  • Almost zero direct buyer overlap unless your product is itself for founders.
  • Trap: you build a 50,000-follower founder audience and zero customers.

Your actual buyers (the niche communities where your ICP lives):

  • Slower wins. Real buyers comment less and share less than other founders.
  • Direct conversion path — every follower is a potential customer.
  • Less social proof, harder dopamine hit.
  • The only path that pays out as customer revenue.

The pragmatic answer: pick one as your primary audience and one as a secondary. If your product is for developers, pick devs (r/programming, dev Twitter, niche Discord) primary and founders secondary. If your product is for marketers, pick marketers primary, founders secondary. The single biggest building-in-public mistake is reversing this, optimizing every post for the audience that gives the fastest dopamine and the slowest revenue.


What to Share, What to Hold Back

A useful frame: every post is in one of five categories. Three of them work, two of them do not.

Categories that work:

  • Lessons with numbers. "Spent $400 on Google Ads. CTR 1.8%, signup rate 3%. Real CAC $24. Killed the campaign — here is what I learned." Specific, verifiable, useful to anyone running similar experiments.
  • Decisions with reasoning. "We chose Postgres over Convex because [3 specific reasons]. We were wrong about reason #2 within a month — here is why." Shows judgment, not just outcomes.
  • Failures and reversals. "Six months ago I posted a feature roadmap. Here is everything we cut and why." Trust comes from showing what you got wrong, not from showing what you got right.

Categories that fail:

  • Pure vanity metrics. "Just hit 1,000 users! 🎉🚀" with no context, no lesson, no story. Pleases other founders, alienates buyers, gets ignored by the algorithm after the third one.
  • Roadmap teases. "Big things coming soon 👀" without specifics. Costs you credibility every time you post one without follow-through.

What to hold back:

  • Customer names, screenshots, or quotes without explicit permission.
  • Specific churn rates and individual customer details. Aggregate trends are fine; "we lost 8% MRR last month" is fine, "we lost CompanyX, here is what I think happened" is not.
  • Anything that creates legal exposure if you raise capital — this is rare for most indie hackers but matters if you are in regulated spaces or planning a venture round.
  • Fights and grievances against specific competitors. The internet remembers.
  • Personal information that creates security or doxxing risk.

The mental test: if a journalist quoted this post in a profile of you in three years, would you be comfortable? If yes, post. If no, rewrite.


Cadence: Consistency Beats Volume

Sustainable cadence beats heroic bursts. The realistic posting schedule that compounds:

  • 3–5 substantial posts per week on your primary platform. Not 1, not 20. Below 3 and you fall out of the algorithm. Above 5 and quality drops.
  • 15–30 thoughtful comments per week on other founders' and buyers' posts. Engagement is half the work; broadcasting alone does not compound.
  • One longer-form piece per month — a thread, an essay, a build update with screenshots and numbers. This is what gets bookmarked, screenshotted, and quoted in months 6+.
  • Vacation policy: tell the audience when you are taking a week off. Disappearing without a note resets your algorithm momentum.

The right rhythm for most solo founders is one substantive post per weekday morning, one engagement window of 30 minutes, and a longer piece you draft over the weekend and ship Tuesday morning. Block it on your calendar like any other recurring obligation.

What does NOT work: bursting 30 posts in a launch week and disappearing. Posting reactively only when something interesting happens. Posting twice a day for a week and then nothing for three weeks. The algorithm rewards the founders who show up whether or not it is exciting.


Format Types That Compound

Every platform has a few formats that consistently outperform. Match your content to the format:

Twitter / X:

  • Numbered threads with concrete numbers in the hook tweet. "I spent six months trying to charge for [thing] and lost $4,200. Here is what I learned. 🧵 (1/12)" — opens a loop, sets stakes, promises payoff.
  • Before / after screenshots. Bad page → good page. Old onboarding flow → new onboarding flow. Dashboard from month 1 → dashboard from month 12.
  • Charts with one-sentence takeaways. A simple line chart of MRR with "Month 4 was the inflection — here is what we changed" outperforms the same data in prose by an order of magnitude.
  • Counter-conventional takes that are right. "Most SaaS advice tells you to ship a free tier. We tried it for 6 months and it cost us — here is what we did instead." Saying the unobvious thing earns attention.

LinkedIn:

  • Personal-essay format with a hook. First sentence reads like a memoir, last paragraph contains the takeaway. "I almost shut down the company in February. Here is what saved it."
  • Carousels with one idea per slide. LinkedIn pushes carousels harder than text-only posts and they convert profile views to follows at 2× the rate.
  • Case studies with concrete results. "How [client / project] grew X to Y in Z" with real numbers, real screenshots, named (with permission) or anonymised carefully.

Indie Hackers:

  • Monthly revenue and lessons posts. Format is established; readers expect numbers + lessons + what is next.
  • Tactical write-ups of one specific experiment. "I tested [tactic] for 30 days. Here is the data and the playbook." This gets featured in the IH newsletter more reliably than philosophy.

YouTube (secondary, but high-leverage if you are willing):

  • Build-along videos of specific features ("I built [X] in [Y]"). Demos compound; talking-head philosophy does not.
  • Honest tear-downs of your own product or others'.

The Narrative Spine

Posts that compound do so because they connect to a larger story. Without a spine, even good individual posts feel disjointed and the audience cannot summarize who you are.

Before you start posting, write a one-paragraph spine. Three pieces:

  1. Who you are building for. Not "everyone." A specific role, industry, or pain. "I build for solo SaaS founders who want growth tools without an agency."
  2. What you believe is broken about how that audience does this today. A hot take, contrarian or not. "Most growth tools optimize for clicks; the right metric is cohort retention."
  3. What you are doing differently and why. The product, framed as a consequence of belief #2.

Every post is then a data point in service of this spine. New feature launches, lessons, failures, decisions, demos — all of them either reinforce who you build for, what you believe, or how that translates into product.

You can refine the spine quarterly. You should not change it weekly. Audiences follow consistency of viewpoint; they unfollow whiplash.


Engagement, Not Broadcasting

Half of building-in-public is what you post. The other half is what you reply to.

  • Reply to other founders' posts in your niche with substantive comments. Not "💯" — actual specifics, counter-takes, your own data points. This is how strangers find you.
  • Reply to your own commenters within hours, not days. Algorithm rewards engagement velocity.
  • DM warm leads sparingly. When someone engages with your content for the third time, a brief, non-pitchy DM ("noticed you've been engaging — what brought you here?") is fine. Cold DM pitches to anyone who likes a tweet are spam.
  • Quote-tweet thoughtfully. Adding context, disagreement, or extension to a popular post in your niche puts you in front of the original audience.

The founders who hit 100k followers from building in public spend roughly equal time creating and engaging. The founders who plateau at 2,000 only broadcast.


Repurposing — One Idea, Many Surfaces

A single insight that lands on Twitter is doing 10% of the work it could do. The compounding move is treating each big idea as a content unit and shipping it across surfaces.

The repurposing pattern:

  1. Twitter thread (where you test the idea — fast, low-stakes, you see what resonates).
  2. LinkedIn essay (rewritten in a more measured voice, with the engagement data from Twitter as social proof).
  3. Blog post on your domain (long-form, with full code/screenshots/data — owned channel, lives forever, contributes to SEO and AEO).
  4. Newsletter issue (extending the idea with what you learned from the responses).
  5. Podcast appearance pitch (turn the strongest piece into a guest spot on a relevant podcast — "I have data and a contrarian take on X" is a podcast pitch that books).

Each surface reaches a different audience and the work compounds. A single Twitter thread that takes two hours to write becomes 8–12 hours of total content with 5× the reach.


Measuring What Matters

Vanity metrics are the trap. The metrics that matter:

Metric What it tells you Healthy direction (12-month view)
Followers in your ICP Whether you are reaching buyers, not just other builders Up
Profile-to-website click rate Whether your bio + pinned post convert attention into traffic Up — aim for 1–3% of profile visits → site visits
Site visits attributable to social The actual top-of-funnel impact Up
Email list growth from social Owned-channel value of the work Up
Customer self-attribution "How did you hear about us?" — Twitter/LinkedIn/IH should appear Up over time
Engagement from buyers vs. founders Whether you are talking to the right audience Buyer share trending up

If the only metric going up is "follower count" but visits, signups, and revenue are flat, you are building a founder echo chamber. Adjust the audience choice in Section 1 and the topic mix.

Track these in a one-line-per-week sheet. The compounding is not visible week-to-week; it shows up across quarters.


When to Pivot or Stop

Building in public is not a forever-decision. Reasons to pivot or stop:

  • Off-brand drift. Your product moved enterprise but your audience is still solo indie hackers. Pivot the content; the audience may unfollow, but the new audience will arrive.
  • Maintenance fatigue. Posting daily for two years has a cost. If quality is dropping, cut to 2–3 posts per week and lean on longer-form. Better fewer good posts than many mediocre ones.
  • Acquisition / fundraise constraints. A serious M&A conversation or regulated round may temporarily restrict what you can share. Communicate the silence ("heads down for a bit, will explain when I can") rather than disappearing.
  • It is literally not working after 12 months. If consistent shipping, real audience-fit, real engagement, and real measurement still produce no traffic and no signups after a year, the channel is wrong for your product or your voice. Cut and double down on something else.

The threshold for "not working" is 12 months, not 3. Most founders quit at month 4, just before the compounding kicks in.


Common Mistakes That Tank Credibility

  • Inflated numbers. Every founder who exaggerates MRR by 2× gets caught eventually, usually by a Stripe leak or a misaligned screenshot. Once caught, the audience never trusts the numbers again.
  • Daily founder-bait. "Want to grow your SaaS? Here are 7 tips" with zero specifics, posted three times a week. The algorithm initially rewards it; the audience tunes it out within months.
  • Selling on every post. Even soft sells. The 80/20 rule (80% useful, 20% product) is the floor; below that, audiences flee.
  • Deleting honest posts that aged badly. If a roadmap missed, post the update. The trust delta from showing the miss > the trust loss from the original miss.
  • Thread-stuffing screenshots of your own engagement. "wow this thread is doing numbers!" is the indie-hacker tell that makes buyers immediately disengage.
  • Talking to other founders only. The single biggest one. If your replies and quote-tweets are all to other indie hackers, your distribution is to other indie hackers.

Deliverable

  • A defined narrative spine (who, what's broken, what you do)
  • A primary platform chosen based on where buyers actually live
  • A 90-day content calendar — 3–5 posts per week, mixing lessons, decisions, and reversals
  • A repurposing plan — Twitter thread → LinkedIn → blog → newsletter
  • A weekly measurement sheet tracking buyer-mix, attributable traffic, and signups
  • Two named "founders worth studying" in your niche whose content you will pattern-match against (not copy)

What's Next

Pair this with Social Media Setup and Optimization so the profiles people land on convert their attention into follows. Then move to Community Seeding Strategy — building-in-public reaches people scanning timelines; community seeding reaches people actively searching for tools like yours.