To build in public without losing your week, give it one fixed hour. Spend ten minutes on Monday noting what happened, thirty minutes midweek writing one honest update, and twenty minutes on Friday replying and checking what it brought. Share real numbers, decisions and mistakes. Post the same core update on two channels at most. Then make sure every update gives readers one easy way to try what you are building.

Why most build in public efforts stall

Building in public sounds easy: just share what you are doing. In practice, it competes with the building itself. A founder in an r/microsaas thread on balancing the two admitted that “it’s more like 80% development and 20% marketing”. Another described posting on X for two days and then forgetting about LinkedIn entirely.

Two things make it stick: a small, fixed time box, and a template so you never start from a blank page.

The best updates have something a reader can learn from or react to.

Share:

Numbers, with dates. Sign-ups, paying users, revenue if you are comfortable, conversion from trial to paid. Small numbers are fine. Honest small numbers get more trust than vague big claims.
Decisions and why. “We dropped the free plan. Here is the reasoning.”
Mistakes. What you tried, what broke, what you changed.
Lessons from users. What a customer said that changed your roadmap, with their permission or anonymized.
Work in progress. A screenshot of a new screen, a before and after.

Keep private:

anything about a specific customer without their permission;
security details and anything that would help someone attack your product;
numbers your partners or investors asked you to keep confidential.

The one-hour weekly plan

Put three blocks on your calendar and treat them like meetings.

Monday, 10 minutes: capture. Open a note and write five bullets about last week: one number, one thing shipped, one problem, one thing a user said, one decision. You will not use all five.

Wednesday, 30 minutes: write and post. Pick the most interesting bullet and turn it into one update with the template below. Post it on your main channel, then adapt it for one more. Done.

Friday, 20 minutes: reply and check. Answer every comment and question. Then check what the update brought: profile visits, sign-ups, replies from people who could become users. Write the number in your Monday note for next week.

That is one hour. On a heavy week, skip the second channel. On a very heavy week, post just the number and one sentence. Consistency over months matters more than any one post.

A build in public post template

Use this shape and fill it in:

The hook: the number or the surprise. “We went from 3 to 11 paying users this month, and none came from the launch.”
The context: one or two sentences on what you are building and for whom.
What happened: the story, in three to five short lines.
What you learned: one takeaway someone else can use.
What is next: your plan for the coming week.
One soft ask: “If you run a bookkeeping practice, I’d love your take,” with a link in your profile or the first reply.

Write it in your own voice. If you use AI to draft, start from your Monday note so the facts are yours, and rewrite the hook yourself.

A month of updates, as an example

If you are not sure what to post, here is what four weeks could look like for a small invoicing tool:

Week 1, a number: “12 sign-ups this week, 2 paid. Both paid after the reminder email, not the landing page.”
Week 2, a decision: “We removed the free plan. Free users never sent a second invoice. Here is what we tried first.”
Week 3, a mistake: “Our onboarding asked for a logo before anything else. Half of new users stopped there. We moved it to the end.”
Week 4, a lesson from a user: “A bookkeeper told us she only cares about one screen. We are rebuilding the dashboard around it.”

The figures here are made up for the example. Yours should be real, and dated.

Where to build in public

Pick one main channel and at most one second channel:

X: quick updates and screenshots; popular with founders.
LinkedIn: longer posts, and better if your buyers are professionals.
Indie Hackers: milestone posts and lessons, read mostly by other founders.
Your own newsletter: a monthly summary of your updates, which you own.
Reddit: only where the subreddit allows progress posts, and never as a link drop. Read Reddit marketing for SaaS without getting banned first.

A warning from an r/microsaas thread: many micro SaaS products fail because founders build for other founders. If your buyers are not founders, building in public among founders will bring encouragement, not customers. Post where your buyers are too, even if that audience is smaller.

Turn readers into users

Put one clear link in your profile, to a page that says what the product does and who it is for.
Use a tracked link for each channel so you can see which updates bring sign-ups.
Invite readers to your list once a month, with a reason: early access, a founding price, a beta.
Answer every reply. The people who comment are your warmest leads.

Your weekly updates can also feed your other content. One good update can become a blog post, as in SaaS content marketing for a solo founder’s week.

Where Tamarind fits

Tamarind can take your Monday notes and product data, plan the week and draft the update for each channel. You edit and approve each draft, and it shows which update led to sign-ups and payments.

Building in public before a launch also gives you an audience to tell on the day. See the Product Hunt launch checklist and how to get your first customers.

Tamarind is in early access. Join the early list to hear when it opens.

Build in public: a one-hour weekly plan