Build in Public
How to Build in Public Without Sounding Like a Sales Pitch
Use real startup work, useful lessons, a short product bridge, and one relevant invitation to build in public without making every post feel like a pitch.
By Uriel Bitton · 4 min read
The short answer
To build in public without sounding promotional, lead with real startup work, extract a useful lesson, connect that lesson to your product briefly, and make one relevant invitation. Do not hide the fact that you are building a company, but avoid making every paragraph about the product. The goal is useful evidence first and promotion in proportion to the reader’s context.
To build in public without sounding promotional, start with real startup work, extract a useful lesson, connect it to your product briefly, and make one relevant invitation. You do not need to hide that you are building a company. Make the post useful enough that the product mention feels like context rather than the entire reason it exists.
Why build-in-public posts start sounding like ads
The problem is usually not that a founder mentions the product. It is that the product becomes the subject of every sentence. LinkedIn’s B2B thought-leadership guidance notes that buyers are turned off by content that is overly promotional or sales-driven, while useful information can demonstrate capability without a direct pitch.
A feature announcement only says what shipped. A useful build-in-public post explains the decision or evidence behind it. The product stays visible, but the reader can learn something even without clicking.
Use the Work–Lesson–Bridge–Invitation structure
1. Start with the work
Lead with something that actually happened: a product decision, failed experiment, customer-safe observation, technical constraint, launch result, or change in your thinking. Specific work is more credible than generic claims about the product.
Buffer’s guide to building in public includes founders sharing experiences, roadmaps, screenshots, roadblocks, wins, and failures. One contributor describes building in public as a continuum rather than an all-or-nothing disclosure exercise. That gives founders plenty of material besides repeated launch announcements.
2. Extract the lesson for the reader
Ask what someone can understand or decide differently because of the update. If you changed onboarding, explain the mistaken assumption. If an outreach experiment failed, explain what was wrong. This turns a founder diary into useful public work.
3. Add a short product bridge
Do not remove the product from the story. Instead, use one or two sentences to connect the lesson back to the SaaS: “That is why we changed our onboarding this week,” or “This is the problem our product is trying to make easier.”
Buildside’s founder-brand guide uses the same principle: connect the problem, your point of view, proof from the work, and the product without turning the whole update into a pitch.
4. Make one invitation that fits the post
A useful post can still ask for something. Match the invitation to the evidence: ask for feedback on one decision, invite a relevant buyer to talk, or link the product when it directly solves the issue. Avoid stacking several calls to action at the end of one update.
Match the promotion level to the channel
Context matters. Reddit’s official guidance says promotional content is not inherently spam, but individual communities may restrict it and some expect most participation to be helpful and organic. A post that works on your own founder profile may be inappropriate in a community with stricter self-promotion rules.
Before publishing, ask three questions: Can this help someone without requiring a click? Is the product mention relevant to the conversation? Does the community allow this kind of promotion? If any answer is no, rewrite the post or choose a different channel.
Know when to pitch directly
Avoiding promotional tone does not mean avoiding sales. If someone asks for a tool that solves the exact problem your product addresses, answer clearly. If a qualified prospect wants a demo, give the demo. Building in public becomes weak when readers cannot tell what the company does.
Buildside’s guide to attracting opportunities recommends making the outcome, proof, need, and next action recognizable. The difference is that the ask follows useful context instead of replacing it.
Rewrite your next update before publishing
Take your next planned post and mark four lines: work, lesson, product bridge, invitation. If the product bridge is longer than the useful part, cut it. If there is no lesson or evidence, add the missing context. If the invitation does not fit the reader, remove it.
The goal is not to disguise marketing. It is to make your startup’s public record worth following. Show useful work, keep the product visible, and earn the right to ask for attention instead of demanding it in every post.
Sources
Frequently asked questions
Is it okay to promote my SaaS while building in public?
Yes. Building in public does not require pretending you have nothing to sell. Promotion works best when the post is useful on its own and the product mention explains why the lesson matters or gives a relevant reader a clear next step.
How often should I mention my product in build-in-public posts?
There is no universal ratio. Mention the product when it provides necessary context, proof, or a relevant next action; otherwise let the decision, experiment, or lesson carry the post.
How do I avoid sounding salesy on Reddit or in founder communities?
Read the community rules, contribute something useful without requiring a click, disclose your connection to the product when relevant, and avoid repeating the same promotional message across conversations.
What should a build-in-public call to action ask for?
Ask for one action that matches the post: a reply from someone with the problem, feedback on a specific decision, a conversation with a relevant buyer, or a product visit when the product directly helps with the issue discussed.
A note from Uriel Bitton
I want Buildside’s public-building advice to help founders stay useful without hiding the fact that they are building a business. The best updates show real work first, make the lesson clear, and connect back to the product only where that connection helps the reader.
Keep building with us
Get practical founder lessons and product updates in your inbox.