Reddit Community Analysis: r/buildinpublic

1. Data Sources & Methodology

• 269 unique posts after deduplication across 4 time periods (all-time, year, month, week), 4 pages each (16 raw JSON files)
• Date collected: April 2, 2026
• Subreddit subscribers: 76,843
• Score range: 27 to 2,072
• Median score: ~121 (estimated from mid-ranked post)
• Top 25 threshold: ~272
• Top 50 threshold: ~136
• Top 100 threshold: ~96

This is a content strategy guide for distributing through r/buildinpublic. The dataset skews toward high-performing posts since it draws from "top" sorting.

Cross-subreddit calibration: r/buildinpublic peaks at ~2,072 with only 77K subscribers. Compare to r/SideProject (~6,241 peak, 672K subs), r/SaaS (~2,741 peak, 645K subs), r/macapps (~2,029 peak, 218K subs), r/ClaudeAI (~8,084 peak). Despite having roughly 1/9th the subscribers of r/SideProject, r/buildinpublic's ceiling is about 1/3 of r/SideProject's -- reflecting a tighter, more engaged community. A score of 100 on r/buildinpublic is a solid post; 300+ is strong; 500+ puts you in the top 10 all-time. The median score (~121) is lower than r/macapps (198) and r/SaaS (136), reflecting the community's smaller size and the sheer volume of "I built X" posts competing for attention.

2. Subreddit Character

r/buildinpublic is an emotional support group for solo founders disguised as a product showcase. It is not a product discovery forum, not a technical community, and not a business advice hub. It is where aspiring indie hackers, first-time founders, and solo developers come to celebrate small wins, process the loneliness of building alone, and receive encouragement from people who understand their journey. The product is always secondary to the person behind it.

Product launches are not just welcome -- they are the entire point. But the community has a very specific filter: it rewards vulnerability and journey-sharing over polished pitches. Rule 3 explicitly states "No Self-Promotion Without Context" -- you must share progress, lessons learned, or ask for feedback, not just drop a link. Posts that lead with revenue screenshots, emotional confessions, or humble origin stories dramatically outperform posts that lead with feature lists.

The audience is overwhelmingly solo developers and aspiring indie hackers. Most are building mobile apps or SaaS tools. Technical depth is moderate -- users mention Cursor, Claude Code, Next.js, Supabase, RevenueCat, and SwiftUI casually. But the community responds to the story far more than the stack. "I quit my 9-5" resonates more than "I used SwiftUI."

Core cultural values, ranked by intensity:

1. Celebration of small wins -- The community's beating heart. Posts celebrating $3.60 in ad revenue (106 upvotes), a single first sale (171 upvotes, 1.0 ratio), or "I got rich" about a $0.99 subscriber (203 upvotes, 1.0 ratio) consistently outperform polished launch announcements. The community LOVES underdog energy.

2. Authenticity and vulnerability -- "My first month after quitting my 9-5 to be a full time indie hacker" (932, 0.97 ratio). "I am that introvert guy who finally show my product after quitting job" (469, 0.94 ratio). "Giving myself 6 months to build my way out of my marriage" (37, 0.93 ratio). Personal struggle is currency here.

3. Anti-fake-revenue skepticism -- "'I earned 50k from an app I made in 1 day'" (321, 0.96 ratio) was a meta-callout of fake revenue posts. "I vibe coded this very illegal app and hit $1500 MMR!" (218, 0.91 ratio) was satirical. The community is increasingly skeptical of MRR screenshots and rewards self-awareness about this tension.

4. Free resources and generosity -- "Made a list of 188 free places to list your app" (415, 1.0 ratio). "No Audience, No Budget? This GitHub Repo Will Help You Get Your First Users" (198, 0.99 ratio). Resource-sharing posts consistently hit high ratios.

5. Practical distribution advice -- The community craves actionable marketing guidance over product feedback. Posts detailing Reddit DM strategies, cold email playbooks, and growth tactics generate high engagement.

Enforcement mechanisms: Rules are light. 7 rules total, all focused on basic civility and transparency. No blacklist, no karma requirements, no posting frequency limits, no mandatory flair, no required post format. The community self-polices through downvotes. The most notable enforcement pattern: posts by repeat authors promoting the same product (Tydal.co appears in 7+ posts by Lopsided_Funny_6397 and ExcellentLake4440) see diminishing ratios over time (from 0.98 to 0.77), suggesting the community eventually tires of serial self-promoters.

No flair system exists. Every single post in the 269-post dataset has an empty flair field. This is a flat, unstructured community where post types are distinguished entirely by title and content.

How this sub differs from similar subs: On r/SideProject, you show your product and the story is optional. On r/SaaS, you share business lessons and failure post-mortems. On r/buildinpublic, you share your emotional journey -- the product is proof of the journey, not the point. This is the most emotionally intimate of the three founder communities. It is also the smallest and most encouraging. Critical feedback is rare; supportive comments dominate.

3. The All-Time Leaderboard

Context: The median score for the full dataset is ~121. The top-25 threshold is ~272. The #1 post at 2,072 is an outlier -- an open-source creative tool (TerraInk) that is visually stunning, completely free, and solves a universal desire (personalized map art). The top 25 is dominated by IMAGE format (15 of 25, 60%) with GALLERY and VIDEO each claiming 3 slots. TEXT posts are rare at the top (only 3 of 25).

4. Content Type Dominance at Scale

Since r/buildinpublic has no flair system, content types are categorized by archetype rather than flair:

Most surprising finding: MRR/revenue milestone posts are the MOST frequent content type (~60 posts, ~22% of the dataset) but have a relatively low average score (~150). The community is saturated with "$X MRR" posts. What separates the high-performing ones (455 score) from the baseline (50-80 score) is exclusively the narrative quality -- humble self-awareness, specific tactical details, and emotional honesty. Generic "I just hit $X MRR" with a Stripe screenshot and a link gets diminishing returns.

5. Content Archetypes That Work

Archetype 1: "The Underdog Origin Story"

Score range: 294-932 Examples:

• "My first month after quitting my 9-5 to be a full time indie hacker" (932)
• "No funding, no team, just a laptop in a corner" (596)
• "Quit my corporate job 6 months ago to build something meaningful" (552)
• "From the corner of my 9-5 office - my project just crossed 2,600 signups" (294)
• "I'm 16 and built an iPad browser that hit #1 in the US, UK and Canada" (272)

The pattern: A personal transformation narrative where the builder's circumstances (quitting a job, being young, working from a corner desk, being an introvert) create dramatic contrast with the outcome. The product is mentioned but framed as proof of the journey, not the hero. These posts always include specific numbers (users, revenue, days since launch) and end with encouragement to others.

Why it matters for distribution: If you are launching a product on r/buildinpublic, your personal backstory IS the launch strategy. Frame your post as "here is my journey" not "here is my product." Include your origin (what you were doing before), your constraints (no funding, solo, side project), and your honest results (even if small). This archetype has the highest ceiling on the subreddit.

Archetype 2: "The Beautiful/Novel Demo"

Score range: 207-2,072 Examples:

• "I built a tool to turn any coordinate into minimalist map art" (2,072)
• "I built an offline survival AI [Update]" (1,080)
• "I made a weather app that generates a live 3D AI diorama of your city" (467)
• "I built something to help with your presentation skills!" (493)
• "I built a weather app that turns real forecasts into AI-generated 3D miniature scenes" (207)

The pattern: A product that is visually impressive or conceptually novel. GALLERY and VIDEO formats dominate here because the product speaks through its visuals. The #1 post of all time (TerraInk, 2,072) was a gallery of stunning map art. The key differentiator: these products make people say "that's beautiful" or "that's actually cool," not "that's useful."

Why it matters for distribution: If your product has strong visual appeal, lead with GALLERY format showing 4-6 stunning screenshots. If it has motion (animation, real-time features), use VIDEO. Do NOT bury the visual payoff behind a wall of text. The #1 post had both gallery images AND a detailed selftext explaining the tech -- but the images hooked people first.

Archetype 3: "The Humble First Dollar"

Score range: 92-455 Examples:

• "I woke up to $500 MRR. I can't even believe it." (455)
• "Hello! I made my first $1000" (437)
• "I got rich" [first subscriber on Android app] (203)
• "My app got its first sell!" (171)
• "Earned $3.6 last month. Excited for this month." (106)

The pattern: Celebrating a small revenue milestone with genuine disbelief and gratitude. The smaller the number, the more authentic it feels. "I got rich" about a single subscriber at 203 upvotes with 1.0 ratio is the purest expression of this archetype. These posts consistently achieve 0.97-1.0 ratios because they are impossible to criticize -- you cannot downvote someone's genuine happiness about their first dollar.

Why it matters for distribution: After your first sale or first meaningful metric, post it here immediately. Frame it as emotional, not strategic. "I can't believe it" > "Here's my growth strategy." Include a screenshot of the payment notification or dashboard. Keep the product pitch to 1-2 sentences at the end. The community will ask about your product in comments -- that is where you pitch, not in the post body.

Archetype 4: "The Free Resource Gift"

Score range: 147-415 Examples:

• "Made a list of 188 free places to list your app or startup" (415)
• "i made a free list of 80 places where you can promote your app" (324)
• "No Audience, No Budget? This GitHub Repo Will Help You Get Your First Users" (198)
• "YouTube is the best startup accelerator" (151)
• "i made a free list of 100 places where you can promote your app" (147)

The pattern: Providing a genuinely useful resource (directory, list, guide) that helps other builders with their biggest pain point: distribution and visibility. These posts achieve near-perfect ratios (0.97-1.0) because they provide immediate value with no ask. The same author (Ok_Cartoonist2006) posted the "free list" multiple times with slight variations and each post performed well.

Why it matters for distribution: If you are building a tool related to launch/marketing/growth, create a free resource and share it here. Your product should be the infrastructure behind the resource, not the pitch itself. "I made a free list" with a link to your site that hosts the list > "I built a launch directory tool."

Archetype 5: "The Meta-Critique / Satire"

Score range: 116-321 Examples:

• "'I earned 50k from an app I made in 1 day'" (321)
• "I vibe coded this very illegal app and hit $1500 MMR!" (218)
• "AI is creating a huge skill gap" (137)
• "Reality: AI is creating two types of developers" (116)

The pattern: Posts that critique the culture of build-in-public itself -- fake revenue claims, vibe coding hype, AI skill gaps. The satirical FakeMRR tool (218 upvotes) is peak meta-commentary: it turns the community's biggest frustration (fake screenshots) into a product. These posts generate high discussion with strong comment-to-upvote ratios.

Why it matters for distribution: If your product addresses a meta-problem (detecting fake reviews, verifying revenue, improving code quality), frame it as community critique first, product second. The community rewards self-awareness about its own flaws.

Archetype 6: "The Serial Journey Update"

Score range: 49-455 Examples: Lopsided_Funny_6397's Tydal.co series: $500 MRR (455), $500 MRR again (191), $684/month (136), $1000 MRR (124), $1700 MRR (162). Also ExcellentLake4440's identical copies at lower scores (86, 49). Old-Storage1099's Monee budget app: 12K DAU (430), 1770 euros donations (159), 6088 euros update (87).

The pattern: Multi-post narrative arcs where the same builder shares periodic updates on the same product. Early posts in the series score highest because the story is fresh. Later updates see declining engagement and ratios (Lopsided_Funny_6397 went from 0.98 ratio to 0.77 as ExcellentLake4440). The community rewards the first few updates but grows suspicious of serial posting.

Why it matters for distribution: You get 2-3 strong "milestone update" posts before the community tires of you. Make them count. Space updates at least 4-6 weeks apart. Each update must add genuinely new information (not just an incremented MRR number). The best serial posters (Old-Storage1099 with Monee) change the narrative angle each time: first post was about DAU, second was about donations as a business model experiment, third was about the donation curve data.

6. Format Analysis

What Format to Use For What

• Revenue milestones / first sale celebrations --> IMAGE (screenshot of Stripe dashboard, RevenueCat, or TrustMRR). This is by far the dominant format. A single revenue screenshot with a personal story in selftext is the template.
• Product with visual appeal (design tools, weather apps, creative tools) --> GALLERY (4-6 screenshots showing the product in action). The #1 all-time post used GALLERY. Show multiple angles/use cases.
• Product with motion/interaction (survival AI, video editor, scroll blocker) --> VIDEO. Keep under 60 seconds. Show the product working, not a talking head.
• Meta-commentary, distribution playbooks, long-form advice --> TEXT. Only use TEXT when the ideas are the product. TEXT posts average fewer upvotes but generate more discussion per upvote.
• Community engagement threads --> TEXT. "What are you building?" threads score low (30-76) but generate 100-327 comments, making them high-engagement but low-visibility.

What Makes a Good Demo Video

Based on top-performing VIDEO posts (1,080; 493; 137; 136):

1. Show the product working immediately -- do not start with a logo animation or backstory. The offline survival AI video (#3 all-time) leads with the device in action.
2. Keep it under 60 seconds -- the community scrolls fast. The highest-performing videos are short and punchy.
3. Screen recording over talking head -- this community wants to SEE the software, not watch someone talk about it.
4. Show a real-world use case, not a feature tour -- "I built a Waze for safe walking" works because it shows the problem scenario, not the settings menu.
5. End with a clear call to action -- "demo it" comment prompts (92 upvotes, 130 comments for ChatGPT video editor) drive engagement.

7. Flair/Category Strategy

r/buildinpublic has no flair system. Every post in the 269-post dataset has an empty flair field. There are no tags, no categories, and no required formatting.

This means your post title is your only categorization mechanism. Title choice is everything.

Pricing Model Hierarchy (Community Preferences)

Based on community response patterns across the dataset:

1. Free / Open-Source (most community-friendly): TerraInk at #1 all-time (2,072, 1.0 ratio) is free and open-source. Monee budget tracker (430, 0.94) is completely free. Posts emphasizing "no paywall, no ads, no tracking" consistently achieve 0.97+ ratios. The 15-year-old who built Telic as "totally free, zero ads, no paywalls" (88, 0.91) -- community loves generosity.

2. One-time / Lifetime purchase: Beam Browser's $4.99 one-time (272, 0.96 ratio). AfterCut screen recorder with one-time license: "Not everything must be a subscription" (28, 0.96 ratio). The community explicitly celebrates anti-subscription pricing.

3. Freemium: Deck Figma plugin's freemium pivot (159, 0.96 ratio). Acceptable when the free tier is generous and the paid upgrade feels fair.

4. Subscription (least community-friendly): Posts mentioning subscription pricing don't get penalized directly, but they don't get bonus points either. The community's pricing radar is less aggressive than r/macapps but still tilts toward ownership. The Video-to-MP3 app with hard paywall at $12.99/year (136, 0.89 ratio) had a notably lower ratio than similar posts without subscription mention.

8. Title Engineering

Deconstructing the Top 10 Titles

1. "I built a tool to turn any coordinate into minimalist map art" (2,072) -- Concrete outcome framing. Tells you exactly what it does in one line. "Minimalist map art" is instantly evocative.

2. "I cant stop thinking about this...." (1,093) -- Curiosity gap. Vague on purpose. Works because it's an IMAGE post -- the image IS the payoff.

3. "I built an offline survival AI [Update]" (1,080) -- Novel concept + update tag. "Offline survival AI" is intrinsically interesting. [Update] signals a journey the community can follow.

4. "My first month after quitting my 9-5 to be a full time indie hacker" (932) -- Personal transformation narrative. Hits the quit-my-job archetype directly. "First month" signals a fresh beginning story.

5. "Grok + LinkedIn = 82 Interviews in a week [AMA]" (728) -- Equation formula + specific number. The math-style title is unusual and eye-catching. 82 is specific enough to be credible.

6. "No funding, no team, just a laptop in a corner" (596) -- Constraint stack. Lists what you DON'T have. The community loves underdog framing.

7. "Quit my corporate job 6 months ago to build something meaningful" (552) -- Same quit-my-job formula. "Something meaningful" adds emotional weight.

8. "I built something to help with your presentation skills!" (493) -- I built + benefit. Simple, direct, tells you WHO it helps.

9. "I am that introvert guy who finally show my product" (469) -- Identity admission. "That introvert guy" creates relatability. "Finally" signals a triumph over fear.

10. "I made a weather app that generates a live 3D AI diorama of your city" (467) -- I made + specific description. Technical specificity ("3D AI diorama") creates curiosity.

Title Formulas That Work

Formula 1: "I built/made X that does Y" (most reliable)

• "I built a tool to turn any coordinate into minimalist map art" (2,072)
• "I built an offline survival AI" (1,080)
• "I built something to help with your presentation skills!" (493)
• Why: Simple, direct, promises a concrete thing to look at.

Formula 2: "I quit my job / No funding / Solo + outcome" (highest emotional ceiling)

• "My first month after quitting my 9-5" (932)
• "No funding, no team, just a laptop in a corner" (596)
• "Quit my corporate job 6 months ago" (552)
• Why: Underdog framing is this community's love language.

Formula 3: "I just hit $X [MRR/revenue/users]" (most common, diminishing returns)

• "I woke up to $500 MRR" (455)
• "Hello! I made my first $1000" (437)
• "I got rich" (203)
• Why: Works when the number is either impressively large OR amusingly small. The $3.60 revenue post (106 upvotes) outperformed many $10K+ revenue posts.

Formula 4: "I made a free list of X" (high ratio, moderate score)

• "Made a list of 188 free places to list your app" (415)
• "i made a free list of 80 places where you can promote your app" (324)
• Why: Immediate, obvious value. "Free" is a magic word here.

Title Anti-Patterns

• Generic revenue brags without narrative: "I just crossed $2400 MRR. I can't believe it." posted twice by different accounts (ExcellentLake4440: 86 and 49 scores, 0.88 and 0.77 ratios) with near-identical selftext for Tydal.co. The community detected and punished the repetition.
• LinkedIn-style motivational framing: "Tonight I'll be out promoting my app" (85, 0.77 ratio) with "Can I get a Hoorah!!!!!!". The hustle-culture energy feels out of place.
• "I just got into Y Combinator" (102, 0.80 ratio) -- bragging about institutional validation generates friction. The community celebrates bootstrapped wins, not credential collection.
• Over-polished marketing language: Posts with professional marketing copy in the title consistently underperform raw, informal language. "I cant stop thinking about this...." (1,093) with a typo outperforms any perfectly crafted headline.

9. Engagement Patterns

Community threads are outliers: "What are u building this week" (76 score, 327 comments, C/U ratio 4.3). "Pitch your product in 1 line" (36 score, 280 comments). "What are you building? Share your project!" (37 score, 190 comments). These are the highest-discussion posts by far but score poorly because they generate self-promotional comment threads rather than organic engagement.

If your goal is VISIBILITY: Post an IMAGE or GALLERY with an underdog origin story. This maximizes upvotes and front-page time.

If your goal is RELATIONSHIPS and discussion: Post a TEXT advice/lesson post or ask a genuine question. TEXT posts generate nearly 2x the C/U ratio of IMAGE posts, meaning each upvote comes with more conversation.

If your goal is PRODUCT TRIALS: Comment in community threads ("What are you building?") which consistently generate 100-300+ comments. Your comment will be seen by dozens of other builders who are actively looking at products.

Highest-Discussion Topics (regardless of score)

1. "What are you building" threads -- 117-327 comments. Pure engagement magnets.
2. Marketing/distribution strategy -- "From the corner of my 9-5 office" (132 comments), "How I found real demand" (15 comments but extremely actionable).
3. Quit-my-job emotional stories -- "My first month after quitting my 9-5" (333 comments). People share their own stories.
4. First sale/revenue celebrations -- "Hello! I made my first $1000" (152 comments). People congratulate and ask questions.
5. AI/vibe coding discourse -- "AI is creating a huge skill gap" (88 comments). Opinion posts generate debate.

10. What Gets Downvoted

Ratio Tiers

Notable Low-Ratio Posts

Named Anti-Patterns

1. "The Serial Carpet-Bomber": Same product promoted repeatedly with near-identical post structure. Lopsided_Funny_6397 and ExcellentLake4440 posted about Tydal.co 7+ times. Early posts scored well (455, 0.98 ratio); later posts dropped to 49 with 0.77 ratio. The community has collective memory. Limit yourself to 2-3 posts about the same product.

2. "The YC Name-Dropper": Posts that lead with institutional credentials (YC, Product Hunt #1, acquisition offers) instead of personal journey. "I just got into Y Combinator" (102, 0.80) was from Ecstatic-Tough6503 who had already posted about GojiberryAI multiple times. The community rewards bootstrapping pride, not pedigree.

3. "The Hustle Preacher": Posts that adopt LinkedIn motivational energy. "Tonight I'll be out promoting my app. This is wartime! Can I get a Hoorah!!!!!!" (85, 0.77). This community is supportive but allergic to performative aggression.

4. "The Revenue Screenshot Recycler": Posts that are just a revenue dashboard screenshot with minimal narrative. As the dataset shows, at least 60 posts follow this template. The ones that score well include genuine narrative; the ones that don't are just Stripe screenshots with "I can't believe it."

5. "The Hidden Upsell": Posts that appear to share something free but pivot to a premium ask at the end. The weather diorama app (467, 0.84) dropped to this ratio because the post ended with "If you want to be one of the first founders and get Lifetime Pro join us." The community felt the bait-and-switch.

6. "The SF Flex": Posts about moving to San Francisco, YC batch experiences, or high-cost-of-living lifestyle updates. "The real cost of moving to San Francisco" (28, 0.73) was the lowest-ratio post in the dataset. The community identifies as scrappy bootstrappers, not VC-funded founders.

7. "The Bot/Copy-Paste Duplicate": Near-identical posts by what appear to be different accounts promoting the same product. ExcellentLake4440's Tydal posts used identical selftext to Lopsided_Funny_6397's earlier posts, just with updated numbers. The community detects and punishes this aggressively.

11. The Distribution Playbook

Phase 1: Pre-Launch (2-4 weeks before posting)

Build presence first. r/buildinpublic is a small community (77K). Regulars notice new accounts that only show up to promote. Before your launch post:

• Comment genuinely on 10-15 posts over 2 weeks. Give real feedback on other builders' products. The community tracks who contributes vs. who extracts.
• Engage in community threads: "What are you building?" threads appear weekly and get 100-300 comments. Drop your project description in these threads to build familiarity. These threads have low scores but high readership among active community members.
• Understand the emotional tone: Read the top 25 posts. Notice how they lead with personal story, not product features. Draft your post in this voice, not in marketing voice.

Phase 2: Launch Day

Post format: IMAGE (screenshot of your product or dashboard) or GALLERY (4-6 product screenshots) with a detailed selftext.

Title template: Use Formula 1 ("I built X that does Y") or Formula 2 ("I quit/no funding/solo + built X"). Do NOT use Formula 3 ("I just hit $X") on launch -- save that for your first milestone.

Selftext structure (based on top-performing posts):

1. Personal hook (2-3 sentences): Why you built this. What was happening in your life. What problem frustrated you personally.
2. What it does (3-5 bullet points): Features, but framed as benefits. Keep technical.
3. Honest numbers (1-2 sentences): Users, downloads, days since launch. Even "0 users, launching today" works here.
4. The ask (1-2 sentences): "Would love your feedback" or "Happy to answer questions." Never "please upvote" or "check it out."
5. Link (at the end): One link. Not five. App Store or website, not both unless genuinely useful.

Timing: The community is most active during US morning/afternoon hours. Posts from the top 25 were created throughout the day, but US timezone posting correlates with higher initial engagement.

Phase 3: First 24-48 Hours

Reply to EVERY comment. This community is small enough that comment-level engagement directly impacts your post's performance. Every reply creates a notification that brings someone back to your post.

Comment strategy -- pre-written replies for common questions:

• "Is this vibe-coded?" --> "I used [tool] for [specific part], but the core logic and architecture are hand-built. Here's what I learned about when AI helps vs. when it doesn't..." (Be honest. The community respects transparency about AI usage more than denial.)

• "Why not just use [existing tool]?" --> "Great question -- I actually used [tool] for months. The specific thing that broke for me was [specific pain point]. That's the one problem I'm solving better." (Show you know the competition.)

• "What's your pricing model?" --> Lead with the most community-friendly aspect. If you have a free tier, lead with that. If lifetime, mention it. If subscription, explain why it's necessary (server costs, API costs) rather than just stating the price.

• "How did you get users?" --> Share your actual distribution strategy with specific numbers. This community rewards tactical transparency. "Reddit DMs with a 30% reply rate" (like GuidanceSelect7706 shared at 294 upvotes) is the kind of detail people love.

• "This is just another [category] app" --> Don't get defensive. "You're right there are a lot of [category] apps. The specific thing I'm doing differently is [one specific differentiator]." Humility wins here.

Phase 4: Ongoing Presence

Space your milestone updates 4-6 weeks apart. The serial-posting trap is the #1 way to destroy your community goodwill. Tydal.co went from 455 upvotes to 49 over 7 posts.

Vary your narrative angle each time. Don't just increment the MRR number:

• Post 1: "I built X" (launch)
• Post 2: "I hit first $X" (milestone, 4-6 weeks later)
• Post 3: "Here's the exact strategy that worked" (distribution playbook, another 4-6 weeks)
• Post 4: "What I learned from [specific failure/challenge]" (lesson, 2-3 months later)

Contribute free resources. The resource-sharing archetype (lists, guides, tools) generates the highest ratios in the dataset. If you can create a free tool, list, or guide related to your domain, post it. The resource builds goodwill; your profile and post history lead people to your product.

Participate in community threads consistently. The "What are you building?" weekly threads generate 100-300 comments. Each one is a chance to describe your product to an actively engaged audience.

Score-Tier Calibration

If your post doesn't gain traction in the first 4 hours: Don't delete and repost. The community notices duplicate attempts. Instead, engage in comments on other posts and try a different angle in 2-3 weeks.

Post-Publication Measurement

• Ratio above 0.95: Your post resonated authentically. The community felt your sincerity.
• Ratio 0.90-0.95: Good reception with minor friction. Likely some skepticism about revenue claims or pricing.
• Ratio 0.85-0.90: Notable friction. Check if your post felt too promotional or if you're posting too frequently.
• Ratio below 0.85: Community rejection. Your post felt like marketing, bragging, or astroturfing. Diagnose what triggered the reaction and course-correct.

12. Applying This to Any Project

Quick-Reference Checklist

• Read the top 10 posts before writing yours -- absorb the emotional tone
• Lead with your personal story, not your product features
• Include a screenshot or gallery -- IMAGE posts dominate the leaderboard
• Be honest about your numbers, even if they're small ($3.60 revenue scored 106 upvotes)
• Put your link at the END, not the beginning
• Reply to every comment within the first 24 hours
• Do NOT repost the same product more than 3 times total
• Vary your narrative angle with each post
• If you have something free, lead with that
• Ask for feedback, not downloads
• Avoid LinkedIn motivational energy and hustle-culture language
• Space milestone posts 4-6 weeks apart minimum

Scenario-Based Launch Guides

If your product is free/open-source

Optimal launch formula: GALLERY format with 4-6 beautiful screenshots. Title: "I built [specific thing] -- it's completely free and open-source." Selftext: personal motivation, what it does, GitHub link, "what should I add next?" The #1 post of all time (2,072) followed this exact formula. Key risk: None. Free + open-source is the highest-performing combination on this subreddit. Lean into it aggressively.

If your product uses one-time/lifetime pricing

Optimal launch formula: IMAGE format with product screenshot. Title: "I built [thing] because I was frustrated with [problem]." Selftext: personal story, what it does, "$X one-time, no subscription" (the community will cheer). Reference Beam Browser (272 upvotes): "$4.99 one-time. No subscription. If I was maximizing revenue, I'd probably do a subscription... instead I thought: what would I want to pay?" Key risk: If the one-time price feels high ($50+), justify it with the value delivered. The community is price-sensitive but rational.

If your product uses subscription pricing

Optimal launch formula: Lead with your free tier or trial. Never put subscription pricing in the title. Title: "I built [thing] -- it's free to start." Selftext: describe the free experience first, mention premium as a secondary note. The Habitum developer (73 upvotes, 0.94 ratio) handled this well: "It has a free tier, premium is 1.99/month." Key risk: Hard paywalls generate friction. The Video-to-MP3 app with a hard paywall (136, 0.89 ratio) had a lower ratio than comparable posts. If you must use a hard paywall, don't describe it as "hard paywall" -- describe it as "free to try, [price] to unlock everything."

If your product was built with AI

Optimal launch formula: Be transparent about AI usage but don't make it the headline. The 16-year-old Beam Browser builder (272 upvotes) disclosed: "DISCLOSURE: I used AI to polish the writing." The Telic developer (88, 0.91) mentioned "no AI slop or vibe coded, though Claude code helped with some tricky features." The community's sweet spot: use AI as a tool, not as the builder. Key risk: "I vibe coded this in 3 days" generates skepticism. Posts framing AI as the primary builder (not the human) see ratio drops. If you used AI heavily, frame it as "I used [tool] to move fast" not "AI built this for me."

Cross-Posting Guidance

Based on existing analyses across r/SideProject, r/SaaS, r/macapps, r/ClaudeAI, and others:

• On r/buildinpublic: Frame as "here is my journey building this." Lead with personal story, end with product.
• On r/SideProject: Frame as "look what I made." Lead with a demo video or visual. Personal story is optional but helpful. Humor and novelty are rewarded even more than on r/buildinpublic.
• On r/SaaS: Frame as "here's what I learned building and selling." Lead with business lessons, distribution strategy, or failure post-mortem. The product is secondary to the tactical insight.
• On r/macapps: Frame as "macOS is missing X, so I built it." Follow PCP format (Problem-Comparison-Pricing). Zero personal story -- pure product evaluation. Anti-subscription, pro-privacy.
• On r/ClaudeAI: Frame as "I built this with Claude." Lead with how Claude was used in the process. The community wants AI-usage details, not product marketing.

The same product can be presented in 5 completely different ways across these subreddits. Never cross-post the same text. Rewrite entirely for each community's values and expectations.