The "Build in Public" Marketing Playbook for Solo Developers and Vibe-Coders

What build in public actually is

Build in public is exactly what it sounds like. You build a product in the open, and you post the journey as you go: what you shipped today, how many people signed up, the bug that nearly broke you. Numbers included.

Done honestly, it is the cheapest distribution channel a solo developer has. There is no ad spend, no sales team, no referral program. There is just you, a keyboard, and a daily habit of telling people what you built.

It works because it does four jobs at once:

• It builds trust. People watch you work. Watching beats reading ads, every time.
• It creates an audience for the launch you do not have yet.
• It gets you feedback before you ship, when a fix costs an afternoon instead of a relaunch.
• It holds you accountable. Shipping to people who follow you is scarier than shipping to an empty repo, which is precisely the point.

The caveat: it only works if it is genuinely useful to other people. A build-in-public diary nobody can learn from is just a public diary. Anyone can read that you refactored your auth module. The post earns its place when a reader walks away with a lesson.

Before you start

Before your first post, make three decisions. They do the heavy lifting so the posts do not have to.

One product. Not three side projects, one product. A feed that keeps changing its subject tells people there is nothing worth finishing. You are selling focus.

One audience. Name who you serve in a single sentence, like "freelancers who hate invoicing" or "solo builders who want SEO traffic." The audience determines your channel, your post topics, even which screenshots you take.

One non-vanity goal. "Trending on Hacker News" is not a goal. A goal is "300 people on the waitlist by launch day" or "first 10 paying users by week 8." Something you can measure and that pays rent.

Then decide where your people already are. One primary channel is enough. Nobody here has time to run five communities at once, and splitting attention across five is how you burn out by week three. Add a second channel later, once the first runs on autopilot. Starting small is the strategy.

Choosing your channel

Here is the honest map of where to build in public, and who it reaches.

X is the default for maker culture. The build-in-public movement lives there, and the hashtag still runs hot. If your users are founders, developers, or software people, start on X.

LinkedIn works when your buyer is B2B. Nobody on LinkedIn wants your screenshot of a failed test run. They do want "I rebuilt our onboarding flow and signups went up, here is how I did it." Professional lessons travel there.

Indie Hackers was built for exactly this. It tolerates genuine progress posts that would read as spam anywhere else, and its audience is already in building mode.

Reddit's maker communities accept progress posts if they are honest. r/SideProject and r/IndieHackers skew technical and hostile to fluff. Run your real numbers there, or do not run them at all.

Discord and Slack communities reward consistency over single hits. One server where you show up weekly beats a dozen where you lurk.

The rule that beats all of these: pick where your target user already scrolls, not where founders hang out. If you sell to wedding planners, post where wedding planners read. Founders will cheer you on, but they are not your first customers.

The cadence that compounds

Two posts. That is the entire system.

One short daily update. What you shipped or learned that day. 100 to 300 words and one screenshot. No more.

One deeper weekly post. A lesson, a metric breakdown, or a mistake and how you fixed it. This is where readers get the value that makes them stay.

A 90-day commitment beats a viral post. Viral posts are lottery tickets. Ninety days of steady updates is a business decision. The compounding happens because every update is a small trust deposit, and trust is the currency your first paying customer will deal in.

What to actually post

Each format does a different job, so use them all. The table below is the reference I keep returning to.

Your posting mix should stay close to this: half value to the audience, a quarter your progress, a quarter asks and questions for feedback. Value first, always.

The core rule: half of every post is value to the audience, a quarter is progress for trust, and a quarter is an ask for feedback.

A strong weekly post is easy to write once you have a skeleton. Mine looks like this, and you are welcome to copy it:

Week {N} build log, {Month} {Day}
Shipped this week: {the feature}
Waitlist: {count} signups, {source} drove most of them
One mistake and the fix: {what broke, how I fixed it}
One lesson a reader can use: {your takeaway}
Early access: {link}

From audience to waitlist

From day one, make signing up frictionless. An audience you cannot contact is a party you cannot invite.

Put a sign-up link everywhere. A simple "sign up for early access" link belongs in your bio and at the bottom of every weekly post. Asking costs nothing.

Run a public pre-launch page. A waitlist with a visible number is itself content. Post its growth, and you turn a landing page into a proof point.

Collect testimonials while you build. Ask early users why they signed up, in their own words. You will want those quotes on launch day, and asking early is the only way to have them.

Bank everything for launch. Every follower, every DM, every thread comment becomes fuel for your launch emails and your Product Hunt launch. The audience is the asset. Use it.

From waitlist to customers

Launch day converts the audience into revenue, but only if you set it up beforehand.

Give waitlist members early-access pricing. A real discount or a founders rate makes signing up early feel like a win, and it rewards the people who carried you through the build.

Follow up personally. Message everyone on the waitlist the moment they can get in. A direct note saying "you are in, here is your link" converts better than any launch email blast.

Turn the first conversations into case studies. Your first paying customers are the ones who will tell the rest of the world what you fixed for them. Ask for permission, then repost their story.

Keep the feedback loop visible. When a user names something they want and a public post shows it shipping, that user stays, and they tell other builders. One shipped request is worth ten ads.

The guardrails

Build in public has a memory. It rewards honesty and punishes shortcuts. These are the lines I hold.

Disclose that you are the founder. On Reddit and Product Hunt especially, undeclared promotion is the fastest route to a ban. Say who you are in the first line of the post. For the full rules of the community that converts best while you build, see our Reddit playbook.

Never buy engagement or fake metrics. The community detects it fast and punishes it publicly. One gamed follower count can kill months of trust.

Never spam the same update everywhere. Tailor each post to its channel. A LinkedIn crowd and a Reddit crowd want different versions of the same story.

Avoid doomposting and drama bait. Hot takes attract an audience that does not buy. They bring engagement you cannot spend.

Keep the ratio. When your feed is mostly value with a few asks, people follow because of you. Flip it, and they follow in spite of you.

What 90 days buys you

Here is what three honest months of building in public actually compound into: an audience that watched your product get better, a waitlist that shows up on launch day, feedback that fixes bugs before real customers hit them, and a visible record of work that no landing page can fake. None of it costs ad money or marketing skill.

Set the small goal tonight. Pick one product, one audience, one channel. Write the first daily update tomorrow morning, and commit to ninety of them.

When you want to cash the launch in, my guide to launching on Product Hunt walks you through the mechanics, and the Reddit first-customers guide covers the community that converts while you build.

Go build in public, and let the internet watch you win.