Build in public posts come with numbers attached: revenue, users, days in a row, hours spent. Replying to them well is mostly about treating those numbers with care. The person posted a vulnerable thing in public, often a small or a bad one, and the replies decide whether they do it again.
The best replies ask the question behind the number, share the matching moment from your own project, or simply acknowledge the kind of week it was. Below are 14 of them, grouped by the kind of update: growth, a bad month, a small ship, a hard decision. If you are the one posting updates, the formats that draw good replies are in build in public post ideas.
The etiquette of other people's numbers
A revenue number in a post is an invitation to talk about the work, not about the number. Replies that compare it to your own, bigger number, or that calculate what it means per hour, or that explain why it is not that impressive, are the fastest way to make a thread go quiet. The person knows what their number is. They are telling you how they got there, or how it felt.
- Ask about the change, not the level. "What moved between month three and four?" is a conversation. "Only $800?" is not.
- Match the mood. A flat month wants a question or a shared experience, not a motivational line.
- Offer your own number only as context. "Mine stayed flat for five months before it moved" helps. "I did $20k my first month" does not.
- Do not ask for the stack, the link or the audience size unless it is the subject. The repeated "what's your tech stack" under a revenue post is the build in public version of "nice post".
Revenue and growth updates
Monthly revenue is up
Congrats. What changed between month 3 and 4? The jump is bigger than the trend, so I'm guessing pricing or a new channel, and I'd like to learn which.
- Why it works:
- Reads the chart carefully, makes a guess, and asks. The author has a specific thing to answer and the readers get the lesson.
First paying customer
The first one is the hardest number you will ever post. Did they come from here or from somewhere else? Trying to learn where the first ones come from.
- Why it works:
- Honours the milestone, then asks the question every pre-revenue reader wants answered.
A flat month, posted anyway
Flat after a growth run is normal and almost nobody posts it, so thank you. What's the one thing you're changing this month, if anything?
- When:
- The update is honest about nothing moving.
- Why it works:
- Rewards the honesty explicitly and asks a forward question that does not assume they must change something.
A big number from a bigger account
Huge. Genuine question from a smaller account: at this size, how much of your week is still writing posts versus running the thing?
- Why it works:
- Names your own position, which makes the question safe to ask, and asks about the work rather than the money.
Failures and bad months
A post about churn, a flopped launch or a shutdown is the hardest kind to write and the easiest to reply to badly. Skip the advice unless they asked for it. Skip "you've got this". Say the thing you went through that matches, or ask a question that treats them as someone who still knows what they are doing.
A churn spike
Sorry, that stings. Did the people who left say anything? In my case the silent ones were the ones who never got set up; the loud ones mostly stayed.
- Why it works:
- Sympathy in three words, then a question with your own pattern attached. The pattern is the useful part.
A shutdown post
Thank you for writing this one. Most people just disappear. What would you tell the version of you who wrote the first post about this project?
- When:
- Someone announces they are closing the project.
- Why it works:
- Honours the act of posting it and asks a reflective question that lets them end on a lesson instead of a loss.
The launch flopped
Been there in March. The post that saved mine was the one a week later where I wrote exactly who the product was for. The launch wasn't the problem, the aim was.
- Why it works:
- Shared failure with a date, and a concrete next step that worked for you. Offered, not prescribed.
Burnout
Take the week. The dashboard will be there. The people who replied to your first ten posts will be too.
- Why it works:
- No advice, no question, just permission and a reminder of who is still around. Sometimes that is the whole reply.
Ship logs and small wins
A small feature shipped
Small ships are the whole game. How long between the first request for this and today? Trying to get my own number down.
- Why it works:
- Validates the size of the win and asks a question with a number for an answer. Builders love comparing that number.
Day 47 of a daily log
Day 47 is further than most of the people who announced day 1 ever got. What's the most boring thing you've kept doing?
- Why it works:
- Puts the streak in context and asks about the unglamorous part, which is what daily loggers actually want to talk about.
A screenshot of new UI
That empty state is doing a lot of work. Did you write the copy first or design the layout first?
- Why it works:
- Notices a specific detail and asks about process. Designers and developers both have an opinion on the order.
Pivots, prices and other hard decisions
A pivot announcement
Makes sense from the outside. Did the old users come with you, or is this effectively a new start? Either answer is useful to the rest of us.
- Why it works:
- Endorses without flattering and asks the question other founders are quietly wondering about.
Raising prices
Good. The question I'd ask: did you grandfather the existing customers? I didn't, got three angry emails, and I'd still do it the same way.
- Why it works:
- Supports the decision, asks the practical follow-up, and shares your own call with its cost attached.
First hire
Congrats, that's a bigger milestone than the revenue one. What did you stop doing the week after they started?
- Why it works:
- Reframes the milestone and asks about the real change, which is what the author is still figuring out.
Writing your own
- 01Read the whole update including the chart or screenshot. Half the good questions are in the detail the text skipped.
- 02Decide what the author needs: a question to answer, company in a bad week, or a witness for a small win.
- 03Ask about the change, the decision or the process. Never about the level of the number.
- 04If you add your own experience, attach a cost or a date so it reads as a story, not a brag.
- 05Keep it to two lines, and come back when they answer. Updates are a series; the reply relationship is too.
Do
- Ask what changed, what they stopped doing, what surprised them.
- Thank people explicitly for posting the bad months.
- Reply to the same person's updates over time. That is how the community forms.
Don't
- Do not compare their number to yours unless yours is the smaller one and the point is encouragement.
- Do not give advice under a failure post unless they asked for it.
- Do not ask for the tech stack under a revenue post. Ask it under the post about the tech stack.
Build in public threads are where founders meet other founders, and the replies are the introductions. If you want to be a regular in them rather than a visitor, the longer plan is in X growth for founders, and the replies that work on a launch day specifically are in what to comment on a launch post.
BuzzyX · X growth workspace
Grow on X with posts that sound like you.
Compose in your voice, schedule the week, find posts worth replying to and read real analytics from the X API. $29/mo after the trial, everything included.
Frequently
asked questions
Something else on your mind? Get in touch.
Is it rude to ask how much money someone makes?
If they posted the number, they want to talk about it, so asking about how it moved or what drove it is welcome. If they did not post it, do not ask. Asking for a number someone chose not to share is the one question that reliably gets ignored.
Should I share my own numbers in a reply?
Only as context for a point, and only when your number is comparable or smaller. Dropping a bigger number under someone else's update reads as a brag no matter how it is phrased.
What do I say under a shutdown or failure post?
Thank them for posting it, share a matching moment of your own if you have one, or ask a reflective question. Skip advice unless they asked for it, and skip motivational lines. A short, honest reply is enough.
How do I reply to a daily streak post without being repetitive?
Ask about the part that changed since last time, or about the boring habit that keeps the streak going. If you reply to every day, you will run out of things to say; reply to the days where something actually happened.
Can I ask about their tech stack or tools?
Yes, under a post about the product or the build. Under a revenue or a failure post it changes the subject, and the author usually skips it. Timing the question to the right post is most of the etiquette.