Build in public privacy
Building in public does not require a public revenue dashboard. Many founders hold back numbers for good reasons: a contract, a competitor, a nervous investor, or plain preference. You can share a great deal and keep all of that private.
Decide what is private before you post
Make a short list once, and keep it. Put on it anything that would hurt you if it were known: revenue, runway, exact user counts, pricing under negotiation, customer names without permission, and anything covered by a contract or an employer’s rules. Write it where you can see it when you are about to post.
A list removes the in-the-moment decision, which is when people overshare. Late on a Friday after a good week, a number can feel harmless. If it is on the list, it stays out. If it is not on the list and you still feel a flinch, wait a day. Deleting a post does not unpublish a screenshot.
Share direction instead of figures
A number is one way to be specific, and there are others. Compare “we grew a lot” with “we went from hearing about the product by word of mouth to hearing from strangers for the first time.” The second has no figure and says something real. Direction, order of events, and what changed are all specific.
Use ratios and ranges when you want a sense of scale. “More than doubled” says something without revealing a base. “Our slowest day is still better than our best day in March” gives readers a feel without a figure. Say “a handful” or “dozens” when it is true and the exact count adds nothing.
Customer stories with permission
Customer quotes are some of the best posts a founder can write, and they carry a privacy cost, because someone else is involved. Ask first. A short message works: you would like to share what they said, here is the exact sentence, and are they happy to be named or would they prefer to be described. Most people say yes, and some say yes with a different company name or a first name only.
If the answer is no, you can still use the lesson. Describe the person by role, such as a bookkeeper at a small agency, if that does not identify them. Change details that do not matter to the point. Never invent a person. If you are describing a composite or a hypothetical, say so.
Share the process, mistakes and decisions
Most of what makes build in public worth following contains no figures. The decision you cannot make. The feature you built and removed. The email you sent that got no reply. The assumption you held for a year that turned out wrong. These are specific, they are honest, and they cost you nothing in secrecy.
Mistakes also build trust faster than wins. A founder who says what went wrong, plainly, is easy to believe when they later say something went right. Keep the account of the mistake free of blame for named people and free of anything legally sensitive, and you have a safe, useful post.
Handling questions you do not want to answer
Sooner or later someone asks for your revenue in a reply. You do not owe them an answer. A short, friendly line works: you keep the figures private, and you are happy to talk about anything else, such as how you found your first customers or what you would do differently. People rarely push after a polite and relaxed reply.
The pressure feels larger than it is. Readers of build in public posts tend to want honesty and usefulness, and they get both without a spreadsheet. If a few people leave because you do not share a figure, they were probably there for the figure and not for you.
Be consistent. If you share a number once, people will expect it again, and silence the next time will read as bad news. Decide your policy early. Either you share a certain category of figure regularly, or you never do. Having a rule keeps you from drifting into sharing something you regret.
Finally, remember that your future self reads your old posts. Something harmless today can look different when you raise money, sell the company, or negotiate with a larger customer. When in doubt, describe it and leave the figure out.
There is a middle road for people who want to share progress without a figure. Share milestones as events: your first paying customer, your first customer from another country, the first time someone you did not know recommended you. Each is a real moment, each is specific, and none reveals a number that matters to a competitor.
You can also share the shape of your numbers without the scale. Say that signups doubled after you changed the onboarding, or that churn fell once you added a welcome email. Readers learn what worked, and your base stays private. This kind of post is often more useful than a screenshot of a dashboard, because it explains why something moved.
Measure the effect without publishing it
You can track your own numbers closely and still keep them private. Count replies, clicks and sign-ups from each post, with names where you can see them, and keep that record for yourself. Public sharing and private measurement are separate, and the second is what helps you decide what to post next.
The habit that makes this easy is a daily question with an answer you are comfortable giving. Quant100 sends one question a day, and the answer is yours to shape. You choose what you say on camera, and the receipt that comes back the next morning is private to you.