Building in public works when you treat it like a short weekly habit, not a second job: pick one channel where buyers hang out, share decisions and numbers you are willing to defend, keep customer details private, put the product link in your bio or a reply, and spend most of your time answering people who write back. That is how you build in public without oversharing or turning the feed into unpaid marketing work.
This guide is for solo makers with almost no audience. You will get a clear share / do not share line, a 30 to 45 minute weekly rhythm, a four-part post shape, a light way to track whether posts drive signups, a made-up running example, a 14-day starter plan, and the traps that burn people out.
What does building in public actually buy you?
Building in public is the habit of sharing real work as you do it: what you shipped, what broke, which decision you made, and what you are trying next. Done well, it buys three things that launch days rarely buy on their own.
Trust over time. People who watch you ship for weeks learn how you think before they ever click signup.
Feedback while the clay is still soft. A short post can surface a misunderstanding early, the same way a rough demo does when you get brutal feedback from other makers.
A trail people can find later. Search, bookmarks, and "who was that person who wrote about X" only work if you left a trail.
Here is what it does not buy you. It is not a launch. A week of posts is not the same as a Product Hunt day. Followers are not buyers. Other founders liking your screenshots does not mean a teacher, coach, or ops lead will pay. If you treat every post like a mini launch, you will either spam the pitch or quit when the likes stay flat.
Where should you build in public if you have no audience?
Pick one home channel for the next 30 days. One. Spreading thin across X, LinkedIn, Reddit, Indie Hackers, and a blog is how building in public becomes a second job.
Choose the place where your buyers already talk, not only where other founders hang out. A rough rule of thumb (an opinion, not a law):
X if your buyers scroll short updates and you can write in public without long drafts.
LinkedIn if your buyers are people with day jobs and job titles (ops, sales, coaching, agencies).
A niche forum or subreddit if your buyers already ask the exact problem your product solves, and you can answer without pitching every time.
Stay on that channel until you have proof that replies or signups move. If you need a wider weekly distribution habit later, steal one calm pattern from this SideHunt guide on one weekly distribution habit for a side project instead of inventing five new posting routines.
What should you share, and what should you never share?
Draw the line before you post. Share the work. Protect the people.
Share
Decisions. Why you cut a feature, changed the first-run flow, or picked one integration over another.
Mistakes you already fixed. "I shipped a broken export and three people emailed me" is useful. Live outages with no status are not.
Numbers you are willing to defend. Signups this week, activation rate, churn count, support load. Round if you need to. Say when a number is approximate.
Process. What you tried, how long it took, what you will try next.
Never share
Customer data or names without clear permission. No screenshots of support inboxes, no "my user Jane said", no identifiable quotes until they agree in writing or email.
Security details that help an attacker: exact stack versions you have not patched, admin URLs, how your auth fails open.
Unshipped promises and hard dates you cannot keep. "Coming Friday" becomes a trust debt when Friday slips.
Anything that breaks a contract: NDAs, employer IP rules, partner agreements, investor quiet periods.
If you are unsure, write the post, then ask: would I be fine if this were screenshotted next to my product name in a year? If not, cut it.
How do you keep building in public to 30 to 45 minutes a week?
Block one weekly slot. Thirty to forty-five minutes is enough for one solid post plus replies. Put it on the calendar like a deploy window. Outside that block, collect notes in a scratch file so you are not drafting while you code.
Use a simple four-part shape every time. It stops the blank page and keeps you out of vague motivational copy:
What happened. One concrete event from the last week.
The real detail or number. A count, a quote you have permission to use, a before/after, a time cost.
What I am trying next. One next step, not a roadmap dump.
One question. Ask something a buyer or peer can answer in a sentence.
Example skeleton (the product name below is made up later in this post): "Shipped the Monday check-in email. 11 of 14 trial users opened it; 4 replied with a real blocker. Next I am cutting the setup from five fields to two. If you coach clients weekly, what is the one question you wish they answered every Monday?"
That shape works for build in public on X or LinkedIn. Keep the same bones; only the length changes.
Why should every post start with a fact?
Lead with the detail. "We hit 40 activated users" beats "Excited to share a milestone." "The onboarding email had a broken link for 9 hours" beats "Building in public is humbling." Fact-first writing is easier to trust and easier to skim.
Put the product link in your bio, profile, or a reply, not in every post. Repeated pitch links train people to scroll past you. When someone asks "where do I try this?", reply with the link. Soft, once, when it is earned.
Should you publish open metrics?
Optional. Honest open metrics can build trust. They can also become a second dashboard job you dread updating.
If you publish a metrics page, keep it tiny: a few numbers you already track, updated on a fixed cadence (weekly or monthly), rounded is fine, and a one-line note on what "down" means so a dip does not look like a cover-up. Companies like Buffer's Open page and their public metrics dashboard show revenue, customers, and related figures in public. That is a useful reference for tone and scope; it is not a template you must match at solo scale.
When numbers go down, say so in one plain sentence and name the next check. Silence after a loud up-week trains people to assume the worst.
What do you do about copycats and competitors?
Someone will ship a similar idea. That is normal. Building in public does not hand them your code; it hands them your story. Keep the moat where it belongs: speed of learning, relationships with early users, and the boring operational details you do not need to livestream.
Do not post unreleased roadmap dates or unique implementation tricks you are not ready to defend.
Do post the customer problem and the decision criteria. Copying a problem statement still leaves them to do the work.
If a competitor quotes you, stay calm. Correct facts once if needed, then go back to shipping.
Where is the real payoff: replies and DMs?
The feed is the billboard. The replies and DMs are the shop floor. Budget half of your weekly block for answering people. Ask a follow-up. Offer a short Loom if it helps. Invite a 15-minute call when someone sounds like a real buyer.
Ignore vanity metrics that do not connect to conversations. A quiet post that starts three useful threads beats a viral screenshot that starts none.
How do you know if building in public drives signups?
Tag the profile or bio link once, then watch activated signups, not just clicks. Google Analytics documents campaign URL parameters such as utm_source, utm_medium, and utm_campaign in its URL builders help article; use those on the single link in your bio or pinned post so traffic from that channel is visible in your reports.
Keep one sheet with columns like: week, posts published, meaningful replies, profile clicks (if you have them), signups with that UTM, activated signups, notes. "Activated" means they completed the core action, not only created an account. If you still need a simple metrics setup, start with tracking product metrics before your first 100 users, then add the UTM column.
Review the sheet every two weeks. If replies are healthy but activated signups are flat, the product path is the problem, not the posting habit. If both are flat after a honest month, change the channel or the topic mix before you add more volume.
When should you go quiet?
Going quiet is allowed. Pause public posts when:
You are in a real crunch to ship something users are blocked on.
You are dealing with a security issue, a legal question, or a customer incident that should stay private until it is handled.
The habit is stealing time from the product and your mood is getting worse each week.
Tell your small audience in one sentence: "Quiet for two weeks while I finish X; back on [day]." Then keep the promise. A planned pause beats a slow fade.
A made-up example: Maya and Rivernote
Everything in this example is made up: the person, the product name, and every number. It is here so you can see the rhythm with concrete details.
Maya is a solo maker building Rivernote, a tool that turns rough voice dumps into clean meeting notes for independent consultants. She has no audience. She picks LinkedIn as her one home channel because her buyers are freelancers and small-agency leads who already post there.
Her share line: ship notes, decision posts, and rounded weekly signup counts. Her do-not-share line: no client names, no audio snippets, no "launching March 1" dates.
Week 1 she posts that 6 of 10 trial users never finished the first recording upload, and she is cutting the permission prompts from three screens to one. Three consultants reply with how they currently take notes. She DMs two of them for a 15-minute call.
Week 3 her bio link uses a UTM (utm_source=linkedin&utm_medium=social&utm_campaign=build_in_public). The sheet shows 22 profile clicks, 5 signups, 2 activated (both sent a first recording). She posts the activation number, not only the signup count.
Week 6 a similar tool appears. Maya does not write a rant. She posts what she learned from 12 customer calls about "notes my client will actually open," and keeps shipping. Public building helped her find those 12 people; it did not invent a moat overnight.
A 14-day starter plan
Times below are planning guesses, not measurements. Adjust to your life.
Day | Time | Action |
|---|---|---|
1 | 20 min | Pick one home channel. Write your share / do-not-share line in five bullets. |
2 | 15 min | Add a clear bio link with UTM parameters. Create the one-row tracking sheet. |
3 | 30 min | Draft post 1 with the four-part shape. Lead with a fact from this week. |
4 | 15 min | Publish. Spend the rest of the block on replies only. No second post. |
5-6 | 10 min/day | Collect notes for next week while you work. Do not draft in the feed. |
7 | 20 min | Answer leftover replies and DMs. Log clicks/signups if any. |
8 | 30 min | Post 2: a decision or mistake you already fixed. Ask one question. |
9-10 | 15 min total | Reply. Book one short call if someone sounds like a buyer. |
11 | 25 min | Post 3: a number you can defend (even if small). Put the product link in a reply if asked. |
12-13 | 15 min | Keep answering. Update the sheet. |
14 | 20 min | Review: channel fit, reply quality, activated signups. Keep, tweak topic, or pause. |
Common traps
Posting every day with no replies. Volume without conversation is a treadmill.
Pitch in every post. Move the link to the bio or a reply.
Vague inspiration. If there is no fact, it is not a build-in-public post.
Live customer screenshots. Easy engagement, expensive trust damage.
Five channels at once. One home channel for 30 days first.
Open metrics you hate updating. Skip the dashboard until the weekly post habit sticks.
Treating founders-only feedback as buyer proof. Nice comments from makers are not purchase intent.
FAQ
Do I need followers before I start building in public?
No. You need one channel, a share line, and the patience to answer the first few people who show up. Followers can come later; conversations cannot if you never start.
Is building in public on X different from LinkedIn?
The four-part shape is the same. X wants shorter posts and faster reply loops. LinkedIn tolerates a bit more context and often reaches people with job titles. Pick based on where buyers already are, not where posting feels trendiest.
What if my numbers are embarrassing?
Small honest numbers beat polished silence. "7 signups, 1 activated" with a clear next step is useful. Inflated round numbers you cannot explain are not.
Can I build in public while I still have a day job?
Yes, if you keep the weekly block short and skip anything that breaks your employment rules or IP assignment. When in doubt, share process and decisions about your own side project, not your employer's work.
Where to start this week
Write your share / do-not-share line today. Pick one channel. Block 45 minutes. Ship one fact-first post with one question, then spend the rest of the block on replies. That is building in public without oversharing, and without making it a second job.
When the product is ready for a wider maker audience, you can also list it on MakerHunt.