Where to post your startup on Reddit

Founders share the problem they solved (often frustration-driven) with a casual tone, then briefly mention they built a free tool to fix it. The focus is on usefulness and the personal motivation, not on pitching the product itself.

Posts that share hard-won lessons, contrarian takes, or specific advice from real founder experience—framed as educational content for others, not as a pitch. Vulnerability and data-backed insights get traction. Titles often include disclaimers like "I will not promote" to signal good faith.

Posts that lead with a relatable problem, personal motivation, or specific creative/technical challenge get the most engagement. The best titles avoid hard-sell language and instead invite curiosity ('I made X because...', 'I spent way too long on...', 'Built Y to solve Z'). Founders who share the 'why' and show genuine work win upvotes.

Personal stories and reflections about real SaaS experiences—successes, failures, lessons learned, and candid moments. Posts that share genuine struggles, unexpected wins, or industry observations rather than polished pitches get traction.

Transparent, numbers-backed retrospectives that admit failures and downsides alongside wins. Posts frame themselves as 'here's what actually happened' rather than 'here's how to succeed,' and often include unglamorous details (donuts at supply counters, $3.48/hour, uncomfortable feelings). The angle is humility + specificity, not hype.

Posts that invite community participation work best: asking for feedback on ideas, sharing behind-the-scenes progress/lessons learned, offering to help others, or framing self-promotion as a reciprocal exchange. Vulnerable, educational, or collaborative angles outperform straight product announcements.

Posts that lead with a genuine problem the developer faced, then explain how their app solves it. The tone is personal and relatable—focusing on the 'why I built this' story rather than feature lists. Top posts often highlight a specific pain point or workflow gap before introducing the solution.

Genuine personal questions and failure/learning stories. Posts succeed when they ask for advice, share honest struggles (even failures), or reflect on real experiences—never when they pitch or promote a product or service.

Posts that tell a genuine story (launch journey, real user insight, distribution challenge) or ask an honest question about the craft. Revenue/metrics are fine when paired with the *story* of how you got there, not just the numbers.

Founders share their product by leading with a genuine problem they solved or a personal pain point, then naturally introduce their solution. Posts that frame the app as an answer to a specific workflow gap—rather than a generic pitch—get the most traction. Community discussion posts asking 'what app changed your life?' also perform well.

Milestone-driven posts with honest progress updates, specific numbers (users, revenue, timeline), and actionable lessons learned. The winning angle combines vulnerability (including struggles and zero-revenue phases) with tangible takeaways, often framed as a journey or follow-up to a previous update.

Personal stories + specific lessons learned. Posts that share hard-won failures, counterintuitive insights, or detailed breakdowns of business decisions resonate best. The angle is always 'here's what I discovered' rather than 'here's my solution.'

Genuine questions and vulnerability about business challenges (scaling, sales, ops problems). Posts that ask for perspectives or share lessons learned without a hard sell get engagement. People respond to real struggles and tactical asks, not pitches.

Posts that blend personal experience or genuine problems with casual mentions of tools/solutions. The community responds to reflective, conversational angles—"here's what I'm dealing with"—rather than direct pitches. Vulnerability and authenticity get engagement.

Personal milestone posts that combine genuine excitement with concrete metrics (users, revenue, timelines) and often include a tactical lesson or unexpected insight. The tone is celebratory but authentic—sharing the emotional and practical realities of indie building.

Posts that lead with a personal milestone or struggle-to-success story, then explain the lessons, metrics, or tactical insights gained along the way. The angle is vulnerability + actionable takeaways, not product bragging.

Posts that frame launches as personal stories or lessons learned (e.g., 'I quit my job and built this,' 'we spent 6 months on something nobody wanted') get traction. Meta-questions about distribution, growth strategy, and the PH ecosystem also resonate. The angle is founder transparency and authentic experience-sharing, not polished pitches.

Posts that lead with a problem or question (e.g., 'How do I validate X?' or 'I built this, where does it break?') rather than announcing a finished product. The community responds well to founders who are transparent about their process, actively seeking testers, and inviting critique.

Posts that lead with the problem solved or personal motivation ("I got tired of...", "I built this after work") then quickly explain the core features in simple, benefit-focused bullets. Top posts blend storytelling with practical details and often mention traction or open-source status.

Posts that lead with a personal challenge, unexpected insight, or genuine question—then mention the product as supporting context rather than the main point. The audience responds to vulnerability, data-driven lessons, and contrarian takes on common startup misconceptions.

Posts that frame self-promotion as a genuine ask (looking for cofounders, seeking feedback, offering help) or as a community resource rather than a sales pitch. Question-based and story-driven posts asking for advice or sharing learnings from the startup journey perform well.

Posts that share genuine personal milestones, transparent metrics, or early-stage progress (e.g., 'I just hit X users' or 'my first paying customer'). The winning angle is vulnerable, real, and often includes a specific number or story—not polished sales pitches.

Authentic problem-sharing and lessons-learned posts. Founders ask genuine questions about their struggles (sales, distribution, scaling) or reflect on what they've learned building. The tone is vulnerable, specific, and seeks advice rather than pitches.

Posts that ask genuine questions about SaaS marketing challenges, share specific problems the community can help solve, or demonstrate interesting insights/tools with a breakdown of how they work. The tone is conversational and problem-focused, not promotional.

Posts succeed by framing the startup as a personal problem-solve or a half-baked idea seeking brutal feedback. They include enough detail to roast (the problem, how it works, or a specific business question) and often lead with self-deprecating honesty about the effort or uncertainty involved.

Posts that ask genuine questions about business challenges or share personal experiences and lessons learned from the founder's own journey resonate here. The community responds to vulnerability, relationship-building insights, and requests for advice rather than promotional content.

Genuine, specific questions about PM challenges and career decisions. Posts that invite discussion and advice from the community, often framed as personal dilemmas or real-world trade-offs the author is facing.

Posts that share a technical insight, lesson learned, or problem observation first—with the product/tool mentioned naturally as context or solution, not as the headline. The tone is reflective and educational rather than promotional.

Unable to determine from available data—no recent top posts were fetched. Recommend checking the subreddit's hot/top posts directly to see what resonates with the community.

Unable to determine from available data—no recent top posts were fetched. Recommend checking the subreddit directly to observe what type of posts (lessons-learned, resource guides, questions, case studies) are currently gaining traction.