Source-backed founder guide

Build in public: a practical guide to your first week

Learn how to build in public with a seven-day starter plan, a first-post example, useful feedback questions, and clear boundaries for what to share.

By Uriel Bitton

Direct answer

The short version

Building in public means sharing your progress, decisions, and lessons while you create a product, so other people can follow the work and respond. Start with the problem you are solving, show one piece of work, ask a specific question, and explain what changes next. You can do this without publishing revenue, source code, or private customer information.[1][2]

Compare every build-in-public platform

Your first seven days

How to start building in public this week

Use this as a work plan, not a daily posting challenge. Two useful updates can cover the week: your starting question and what you learned. If you have no result yet, say what remains untested.

Use this as a work plan, not a daily posting challenge. Two useful updates can cover the week: your starting question and what you learned. If you have no result yet, say what remains untested.
DayDo the workKeep a noteReady when
1 · Choose a problemName one person and one task your product helps with.Who struggles, what they do today, and what you still need to learn.A reader can tell whether the problem applies to them.
2 · Set boundariesChoose a public home for the project and decide what stays private.Your project description and a list of details to remove before posting.You can explain the work without exposing anyone else's information.
3 · Publish a first postShare the problem, one sketch or decision, and a specific question.A link to the post and the assumption you want to check.Someone can answer the question without signing up for your product.
4 · ListenRead the replies and ask relevant people how they handle the task today.Separate examples of actual behavior from suggestions and encouragement.You know which replies came from people who face the problem.
5 · Try one changeChoose one small test or improvement informed by the work so far.What you changed, why, and what result would make you reconsider.The test has a clear question and fits the time you have.
6 · Record what happenedReview the test, including anything that failed or remains uncertain.The observation, number of participants if relevant, and time period.Your conclusion is no stronger than the evidence you collected.
7 · Publish a follow-upLink back to the first post and explain the result and next step.What changed, what did not, and the next question to investigate.A new reader can follow the decision from question to outcome.

Swipe the comparison sideways to see every column.

The basics

What does it mean to build in public?

To build in public is to make selected parts of the process visible before the finished product arrives. For a SaaS founder, that might mean sharing a prototype, explaining a pricing decision, describing a failed onboarding test, or showing how feedback changed a feature. The reader should be able to understand what you tried and what you learned.

You do not need to make the whole company public. Open source concerns access to a project's source code; building in public concerns how you share the work in progress. A product can do either, both, or neither. A private codebase can still have a useful public development journal.

Keep the writing close to work you already do. Save a short note when you make a decision, remove sensitive details, and share the part another person could learn from. If producing updates starts replacing customer conversations or product work, reduce how often you post.

A worked example

What should your first build-in-public post say?

Give readers four things: who you are helping, what you are making, one decision or piece of work they can inspect, and one question. Here is an illustrative post for a fictional invoice-reminder app. It is not a report of an actual Buildside founder's results.

“I'm building an invoice-reminder tool for solo designers who currently chase payments by hand. This week I'm sketching the reminder screen. My first version lets the designer review each message before it goes out, because I don't yet know when automatic reminders feel too pushy.”

“If you freelance as a designer, how do you decide when to follow up on an overdue invoice? I'm trying to understand your current process before I add automation. Next week I'll share what I learned and which part of the sketch I changed.”

If you attach the sketch, use made-up names and invoice details. The question should make sense even without an attachment or product link. Replace the example with a decision you actually face; do not copy its claims as your own.

  • Name the person and problem in the opening sentence.
  • Show a small piece of work or explain one concrete decision.
  • State what is still uncertain.
  • Ask a question relevant people can answer from experience.
  • Give yourself a next step you can report back on.

Real founder journeys

Three Buildside case studies: what building in public looks like

These short journeys show how founders connect a problem, a product milestone, and a next step. We checked the original public posts and their publication dates on October 20, 2026. The milestones below are what the founders reported; they do not establish that posting caused customer or revenue growth.

1

Alexander Rabin · Kinhin: follow the beta with a specific update[3][4]

On October 11, 2026, Alexander announced Kinhin's public beta: a tool for running CI jobs on Apple Silicon Macs. He invited developers to test it with their own workflows. On October 20, he reported an auto-update fix and asked to hear from people who had tried the tool. The fix was planned for beta 3; that post did not announce beta 3's release. Takeaway: make the journey useful after launch by naming a concrete change, clarifying when it will be available, and giving existing testers a reason to respond.

2

Kyle (@kylereddoch) · Trayage: connect feedback to a testable revision[5][6]

On October 14, 2026, Kyle explained how feedback had shaped a redesign of Trayage, his Mac Downloads cleanup app. He described clearer file suggestions and two menu bar views, then asked what still needed work. Later that day, he reported that version 1.1 was approved for TestFlight beta testing, shared an invitation, and asked how the new layout and smart filters felt. This was a beta milestone, with usability questions still open. Takeaway: tell readers which feedback changed the product, then ask testers to examine those specific changes.

3

Caleb G. (@lublubxt) · SpendMyDay: turn the problem into a testing invitation[7][8]

On October 19, 2026, Caleb described reaching the end of a day without knowing where his time had gone. He was building a mobile time tracker and hoped to offer public TestFlight access. On October 20, he named the app SpendMyDay, reported approval for public testing, and shared a TestFlight invitation asking for thoughts, ideas, and feedback. The documented step was access to a beta; the posts did not report adoption or retention results. Takeaway: follow a problem-led introduction with a concrete way for interested readers to try the product and respond.

Choosing a place

Where should you build in public?

Choose one place to keep your project's history and start with the audience you need to learn from. A Buildside founder or product page can preserve the connected journey, while X, LinkedIn, Reddit, DEV, or Indie Hackers can carry the part that fits that community's conversation. Use a launch platform when your product is ready for its launch format.[9][2][10][11][12][13][14][15]

Before adding another channel, check whether the people responding match the people you want to help. Read each community's rules and write a useful post that stands on its own. A specific question about a workflow is easier to respond to than a product link followed by “any feedback?”[9][2][10][11][12][13][14][15]

After publishing

How do you turn replies into a useful next step?

A reply can suggest something to investigate; it does not automatically validate a feature. Ask whether the person has faced the problem, what they did, and where their current approach failed. Several encouraging comments from other founders may still tell you little about what a customer needs.

For the fictional invoice app, the next step could be to ask a designer to walk through their last reminder, then test whether a review screen fits that process. If nobody has tried the sketch, an honest follow-up is: “I have a draft screen and a question to test. I don't yet have evidence that this saves time.” Share a measured result only after you have one.

  • Record whether the respondent is a potential user, buyer, peer, or observer.
  • Separate what someone actually did from what they say they might do.
  • Choose one repeated difficulty to investigate before adding features.
  • Write down what the feedback changes, including when it changes nothing yet.
  • Link the next update to the earlier question so readers can follow the decision.

Your boundaries

What should you keep private?

1

Customer information

Get explicit permission before sharing a customer's identity, message, quotation, screenshot, or data. Use fictional sample data when demonstrating a workflow, and check screenshots for names, email addresses, and open tabs.

2

Security and access

Keep credentials, access links, sensitive infrastructure details, and unresolved vulnerabilities out of public updates. Show the user-facing change without exposing information that could compromise the product.

3

Business commitments

Do not disclose confidential contracts, negotiations, or someone else's unreleased plans. Describe your own decision at a level you are free to share.

4

Personal information

Choose your own limits around health, family, location, and finances. Sharing product work does not require making your personal life part of the project.

Methodology and disclosure

How this guide was made

The seven-day plan and fictional invoice-app example are Buildside's editorial framework. The three real founder case studies were checked against six dated public Buildside posts on October 20, 2026. Their milestones are founder reports, not independently audited product or business results; the takeaways are our editorial interpretation. Platform references point to official publishing resources. No posting schedule is claimed to guarantee customers.

Buildside publishes this guide and appears where it fits the stated job. Platform facts come from linked official sources; recommendations and workflows are Buildside's editorial assessment.

Official sources checked . Features, access, and policies can change.

Official and first-party sources

  1. [1] Public founder updates

    Public, source-level founder progress, experiments, lessons, launches, and requests.

  2. [2] SaaS product directory

    Public SaaS product pages connected to founders, updates, questions, and product context.

  3. [3] Alexander Rabin: Kinhin beta announcement (October 11, 2026)

    Alexander announces Kinhin's public beta for CI runners on Apple Silicon Macs and asks developers to test their workflows.

  4. [4] Alexander Rabin: Kinhin auto-update fix and beta 3 plan (October 20, 2026)

    Alexander reports an auto-update fix, says it will roll out in beta 3, and asks to hear from people who have tried Kinhin.

  5. [5] Kyle: Trayage 1.1 redesign explained (October 14, 2026)

    Kyle describes feedback that prompted a clearer file-review interface, two menu bar views, and a refreshed visual identity.

  6. [6] Kyle: Trayage 1.1 TestFlight beta announcement (October 14, 2026)

    Kyle reports TestFlight beta approval, links a testing invitation, and asks for feedback on the layout and smart filters.

  7. [7] Caleb G.: the problem behind SpendMyDay (October 19, 2026)

    Caleb explains why he is building a time-tracking mobile app and says he hopes to make it available through public TestFlight.

  8. [8] Caleb G.: SpendMyDay public testing invitation (October 20, 2026)

    Caleb reports approval for public testing and shares a SpendMyDay TestFlight invitation with a request for feedback.

  9. [9] SaaS founder directory

    Public founder profiles connected to expertise, products, and ongoing work.

  10. [10] How to post on X

    Standard posts, media, drafts, scheduling, and Premium longer posts.

  11. [11] Post and share updates on LinkedIn

    Post length, audiences, comment controls, formats, events, polls, documents, and scheduling.

  12. [12] Reddit community settings

    Community types, post formats, title and body requirements, link restrictions, and moderation controls.

  13. [13] Writing, editing and scheduling on DEV

    Editor, drafts, scheduling, series, RSS imports, canonical links, analytics, and ownership.

  14. [14] Indie Hackers

    Current posts, case studies, Build Board, products, jobs, Partner Up, and meetups.

  15. [15] How Product Hunt works

    Audience, launch eligibility, free access, launch goals, and leaderboard factors.

FAQ

Questions founders ask next

Can I build in public with no audience?

Yes. Start with a clear project description and one useful update, then participate in a relevant community that permits that kind of post. Ask people who face the problem a specific question. If nobody responds, seek direct conversations and improve the question rather than treating silence as proof that the idea is bad.

How often should I post while building in public?

Start with a schedule you can sustain, such as one useful update a week. Publish a decision, question, experiment, result, or lesson when you have enough context to make it useful. You do not need to post every day, and the seven-day plan above does not require seven posts.

Does building in public help you get customers?

It can help people discover your work and start relevant conversations, but it does not guarantee customers. Track whether those conversations lead to product use or purchases. Public engagement alone does not establish demand or replace direct customer research.

What should I measure?

Track relevant conversations, people who try the product, completed product actions, and decisions improved by feedback. Keep likes and views separate from customer outcomes. When sharing results, include the number of people or events measured and the time period, and state what remains uncertain.

Can I build in public without sharing revenue or source code?

Yes. Share decisions, prototypes, product changes, mistakes, and lessons at a level you are comfortable publishing. Revenue disclosure and open-source code are optional; neither is a requirement for building in public.

What if someone copies my idea?

Public updates can expose ideas and implementation choices. Share the problem, learning, and user-facing progress at a level that fits your business. Keep proprietary methods and confidential details private. If a project depends on secrecy or customer restrictions, limit the public account to work you can safely discuss.

Continue the decision

Where to build in public

Where should a SaaS founder build in public?

Build in public in three layers: keep a durable home for the founder and product, choose one reach channel where the intended user already participates, and add a launch platform only when there is something ready to try. For many SaaS founders that means Buildside plus LinkedIn or X, followed later by Product Hunt, Hacker News, or a relevant directory.

Best build-in-public sites

The best build-in-public sites by publishing format

The best build-in-public site depends on what you can publish well. Buildside fits connected SaaS progress; WIP fits daily completed-task logs; Indie Hackers fits founder discussion; DEV fits durable technical articles; X fits short real-time observations; and LinkedIn fits professional lessons. Choose the native format you can sustain, then keep the full product context in one durable place.

What SaaS founders should share in public

What should SaaS founders share while building in public?

SaaS founders should share the customer-safe problem, decision, experiment, evidence, tradeoff, lesson, and next step. Useful updates include decision logs, failed tests, bounded metrics, product changes, launch context, and specific requests. Remove customer identities, credentials, private conversations, sensitive architecture, negotiations, and unsupported conclusions. Specific context makes an update useful; total disclosure is neither required nor wise.

SaaS founder communities for feedback

Where SaaS founders can get useful product feedback

Choose the feedback community by the evidence you need. Use a target-user community for problem language, Buildside or a defined beta group for observed product use, DEV or Hacker News for technical scrutiny, Indie Hackers or MicroConf Connect for founder operating decisions, and Product Hunt for launch reactions. Ask one bounded question and report what changed afterward.

Inspect the relevant platforms

Keep the public journey connected

Give useful progress a durable home.

Create a founder profile, connect your SaaS product, publish the evidence behind the work, and make the next useful action clear.

Join Buildside