Where to post your startup on Reddit

Posts that showcase a specific, useful tool the creator built to solve a real problem they had. The framing is casual and problem-focused ("I got tired of...", "I built this because...") rather than salesy, and often includes the backstory of why it exists.

Posts that share hard-won lessons, contrarian takes, or transparent failures from the author's own experience, framed as educational advice for the community rather than product promotion. The winning pattern is credibility + vulnerability + actionable insight.

Posts succeed by leading with a unique angle or story—either a clever creative concept (turning walks into maps, losing a character in a village), a personal narrative (building out of frustration, investing 1000+ hours), or a genuine technical achievement. The best posts show *why* the project exists before showing *what* it does.

Posts that share personal struggles, lessons learned, or observations about the SaaS industry itself—especially about AI trends, company culture, founder experiences, or operational challenges. The tone is candid and relatable rather than polished.

Personal stories about real entrepreneurial journeys—the struggle, the pivot, the unexpected solution—with honest metrics and lessons learned. Posts that share what didn't work or unconventional tactics resonate more than polished success stories.

Posts that offer something of value to the community first (feedback, customer research, newsletter features, expertise) while naturally mentioning the founder's own project. The winning angle is positioning yourself as a helper or connector rather than a salesperson.

Posts that lead with a personal problem or frustration the developer experienced, then explain how they built an app to solve it. The tone is conversational and problem-focused, not sales-focused. Developers share their journey and reasoning rather than features.

Genuine advice-seeking posts and personal stories about side hustle ideas in progress. Posts that ask for feedback on a nascent idea, share struggles/failures, or describe a side hustle concept the poster is exploring (not yet selling) get traction.

Posts that share concrete milestones, revenue numbers, or specific lessons learned while building in public. The winning angle is showing real traction (users, revenue, growth) with honest process details or unexpected discoveries—not just "I built something cool."

Posts that tell a genuine origin story (why the maker built it, what problem they solved) or frame the app as answering a real pain point, rather than hard-selling features. Community also responds well to comparison posts ("why doesn't existing tool do X?") and discussions asking what people *actually* use.

Posts sharing specific milestones (user counts, revenue, timelines) with honest lessons learned or the actual problem that got solved. The angle is transparency and tactical insight, not hype—showing the journey and what concretely worked.

Personal war stories and counterintuitive lessons. Posts that work here are honest reflections on mistakes, tough decisions, or surprising findings from real business experience—told with specific detail and vulnerability, not hype.

Genuine questions about business problems and challenges (customer acquisition, scaling tactics, vendor issues, sales training). Posts that ask the community for advice or shared experiences without pitching anything perform best.

Practical problem-solving posts that ask genuine questions or share real workflow challenges. Titles are conversational and specific, focusing on user pain points (maintenance burden, choosing tools, debugging issues) rather than announcing products. The tone is relatable and exploratory.

Posts that share concrete revenue/user milestones with personal narrative and transparency about the building process. The winning angle is showing real metrics (ARR, user count, time elapsed) combined with either a success story or a candid failure/lesson learned, making it relatable and inspiring rather than salesy.

Personal narrative + concrete wins: posts that share the founder's emotional/career journey alongside specific metrics (downloads, revenue, timeline), with emphasis on persistence and learning over pure product pitching.

Posts that share the founder's personal journey, honest challenges, or lessons learned from launching—not hard product pitches. People upvote vulnerability (layoffs, struggles) and data-driven insights about Product Hunt itself, mixed with authentic product context.

Posts that invite participation, ask genuine questions about building/validation, or offer value to others (beta testing, feedback) perform best. The winning angle is conversational and community-focused—treating the subreddit as a place to get honest help and find collaborators, not as a billboard.

Posts that lead with a relatable problem the creator faced, then explain the solution they built to solve it. The tone is casual and personal—often with a touch of humor or self-awareness—rather than polished marketing. Success comes from showing the *why* behind the project, not just the *what*.

Posts that lead with a specific insight, surprising data point, or lesson learned from building—with the product mentioned as context rather than the headline. Upvoted posts answer implicit questions like 'what did I learn?' or 'what surprised me?' rather than 'buy my thing.'

Posts that frame self-promotion as a request for help, feedback, or community collaboration (cofounder searches, idea validation, takeover offers) perform better than straightforward product announcements. Personal stories about the building process and honest discussions about founder challenges also gain traction.

Posts that share a genuine milestone, win, or progress moment resonate best. Top posts celebrate early customers, revenue milestones, or user growth—often with a personal, authentic tone rather than a polished pitch.

Posts that frame a genuine problem or bottleneck the founder is facing, often seeking advice or sharing lessons learned. The angle is vulnerability and specificity about a real challenge, not showcasing a finished product.

Authentic founder/salesperson stories and genuine questions seeking advice. Posts that share struggles (customer acquisition, pricing feedback, sales scaling challenges) or ask for community insight on common SaaS problems get engagement. People respond to vulnerability and real problems, not pitches.

Posts that invite brutal feedback by admitting a mistake, wasted time, or a risky decision. The founder sets up the vulnerability ("I spent 8 months building something nobody asked for") and asks the community to roast the product or business model honestly.

Posts that either solve a personal problem the founder faced (sharing the origin story) or offer genuine value/opportunity to the community (like paid research studies or asking for feedback). Upvoted posts feel like peer-to-peer advice or authentic problem-sharing, not hard sales pitches.

Authentic problem-solving posts that ask real questions about PM challenges, share data-driven insights, or reflect on practical dilemmas PMs face. These succeed by being specific, vulnerable, and inviting peer discussion rather than positioning the author as an expert.

Posts that lead with a genuine insight or problem statement, then casually mention a tool/product as a practical example or solution. The angle is educational and narrative-driven, not sales-focused.

Posts sharing specific, battle-tested tactics and lessons learned from real SaaS experiences. The winning angle is providing concrete advice or insights that solve problems for other founders, presented conversationally rather than as marketing.

Genuine problem-solving questions framed from a founder's perspective, asking for advice or alternatives from the community. Posts that acknowledge a real constraint (budget, resources, skills) and seek input tend to perform well.

Unable to determine from available data—no recent top posts were fetched. Recommend reviewing the subreddit directly to identify current engagement patterns.