Check whether the discussion belongs in the community

Reddit marketing works best as participation in a relevant discussion. Before drafting a product post, read the community’s rules, recurring threads, and recent conversations. Look for the problems people describe and the kinds of contributions they welcome. A community for sharing software can be an appropriate place for a product introduction; another community may allow introductions only in a designated thread. Our vibe coder Reddit guide includes a specific product-post outline and explains when the building process belongs in the introduction.

Do not assume that the same format belongs everywhere. A builder community may want to discuss how the product was made, while a professional community may care about a workflow and its limitations. Choose the angle that serves the people in that space. If the rules leave a material question unresolved, clarify the allowed format before posting.

Write a post that provides value before the link

Use a concrete problem, the approach you tried, and an honest account of what it does well. Include enough substance for someone to respond without visiting another website. In a hypothetical example, the maker of a meeting-notes tool might share a template for turning decisions into assigned tasks and explain the part their software automates.

A useful draft could read: I built a small tool because our action items kept losing their owners. Here is the template behind it, the workflow it supports, and the part that still needs manual review. How do you handle actions that span two teams? Adapt that structure to real experience and the community’s rules. It invites a specific discussion without inventing customer evidence.

Make the relationship and limitations easy to understand

Say that you built, work on, or are publishing coverage of the product. Do not pose as an unrelated customer. Explain important conditions near the claim: supported platforms, a required account, a usage limit, or an unfinished feature. Readers can give more useful feedback when they know what they are evaluating and who is presenting it.

If someone asks a difficult question, answer what you know and investigate what you do not. A correction can improve the linked product article as well as the thread. Avoid turning every response into a new invitation to sign up. The discussion itself should remain useful even to people who conclude that another approach fits them better.

Keep distribution compatible with Reddit’s rules

Reddit’s spam policy prohibits repeated or unsolicited activity that harms users or communities, including repetitive mass posting for exposure. Prepare a relevant contribution for the chosen place, and follow that community’s specific rules. Copying the same promotional text into many communities is a poor foundation for a relationship with readers.

Keep editorial help separate from moderation privileges. Reddit’s Moderator Code of Conduct prohibits moderation actions in exchange for compensation. A service can help prepare useful copy, but payment must not buy approval, a pin, or preferential moderation. A ShowMeYourSaaS spotlight should be evaluated under the same applicable community and platform rules as other content.

Plan to answer the questions your post creates

Have someone available to respond after publication. Save recurring product questions, objections, and requests for examples in a simple research log. Ask permission before turning an identifiable comment into a testimonial or case study. Summarize general patterns without exposing personal details or presenting one person’s preference as a market-wide conclusion.

If the conversation identifies a missing explanation, improve the destination page and share the clarification when appropriate. For the meeting-notes example, questions about permissions might justify a short access-control explanation. Questions about exporting might belong in the existing setup guide. Let the actual decision determine the content format. The feedback-to-content workflow helps turn those questions into verified explanations.

Judge results by fit and learning

Record the public post URL, relevant questions, available visits, and meaningful product actions over a defined period. A subreddit’s members are its potential community, not the number of people who saw your post. Likewise, a comment count does not establish how many people became users. Keep each observation named accurately.

For builders, r/ShowMeYourSaaS offers a focused context for discussing software and the work behind it. Bring an explanation that others can learn from, use your reviewed directory profile as a place for product detail, and remain involved in the discussion. The most useful result may be a better understanding of why someone would try the product in the first place.

How can a solopreneur build in public without making every post a promotion?

Share one real decision, the evidence available, and a question the community can help answer. For a fictional revision organizer, explain why the first version supports one input format and ask about the tradeoff only where such discussion is allowed. State that you are building the product. A recurring task diary can be useful, while repeated links with slightly different introductions can still be spam.

Reddit prohibits repeated or unsolicited mass engagement, whether manual or automated. Individual community rules may be stricter. Read them before contributing and keep prospective-customer feedback separate from fellow-builder encouragement. For a working product’s public introduction, the promotion guide compares a profile, launch, tutorial, and discussion.

Should you lead with the fact that the app was vibe coded?

Lead with it when the building process is the topic of the community or the lesson you want to share. In a development discussion, explaining an AI-assisted build decision and what you learned can be relevant. In a user community, the task and result may deserve the first sentence.

Be accurate about the product and your experience in either setting. Do not claim expertise, testing, or customer outcomes you do not have. You can say what you built, what you checked, and what remains uncertain. A precise account gives readers a better way to judge the app than either hiding the process or treating the process as the whole value proposition.