Reddit Community Analysis: r/SideProject

1. Data Sources & Methodology

• 292 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: 672,061
• Score range: 182 to 6,241
• Median score: ~1,207 (estimated from ~146th ranked post)
• Top 25 threshold: ~2,157
• Top 50 threshold: ~1,488
• Top 100 threshold: ~1,011

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

Cross-subreddit calibration: r/SideProject peaks at ~6,241 vs r/ClaudeAI's ~8,084, r/macapps's ~2,029, and r/ChatGPT's ~84,058. With 672K subscribers, r/SideProject sits between r/macapps (218K) and r/ClaudeAI (unknown but smaller subscriber base, higher engagement). A score of 1,000 on r/SideProject is a strong post; 2,000+ is exceptional; 3,000+ is rare territory. The median score (~1,207) is comparable to r/ClaudeAI's median (~1,876) despite having roughly 3x the subscribers, reflecting that r/SideProject's content is more diluted by high-volume low-engagement launches.

2. Subreddit Character

r/SideProject is a show-and-tell stage for builders who want validation, not a marketplace. Unlike r/macapps where users come to discover software, or r/ClaudeAI where users discuss a shared tool, r/SideProject is where indie developers, hardware tinkerers, and aspiring entrepreneurs come to say "look what I made" and hear "that's cool" back. The community's purpose is encouragement and feedback, not consumer evaluation.

Product launches are the entire point. Every post is some form of "I built X." But the community has strong preferences about how you present that. The posts that dominate are not polished marketing pitches -- they are personal stories with vulnerability, humor, or technical novelty. The community rewards authenticity above polish.

The audience is overwhelmingly developers and aspiring indie hackers. They understand tech stacks (mentioning Next.js, Supabase, SwiftUI is common and not frowned upon). They appreciate technical depth but primarily respond to the story -- why you built it, what went wrong, what surprised you. Non-technical users are rare.

Core cultural values, ranked by intensity:

1. Authenticity and vulnerability -- The highest-performing posts reveal personal struggle: job loss ("Lost my job after 20 years" at 2,512), grief ("I lost my job and my Dad" at 1,007), relationship pain ("After quitting my job and a 5 year relationship heartbreak" at 1,516). Revenue brags without context generate suspicion. Self-deprecating humor performs exceptionally well ("I did it! $0 in 30 days!" at 1,541; "Built an AI that teaches dolphins to code" at 2,464).
2. Visual demos over descriptions -- VIDEO format dominates the top 25 (14 of 25 posts). The community wants to see your project work, not read about it. A 30-second screen recording outperforms any wall of text.
3. Novelty and "wow factor" -- Creative, unexpected, or delightfully weird projects massively outperform utility tools. A cat-a-log app (4,730), a Tinder clone for your wife (3,608), a fake smoke detector to annoy neighbors (3,218), a pigeon defense system (1,747) -- the community upvotes things that make them smile or say "wait, what?"
4. Anti-hustle-culture skepticism -- Posts that feel like LinkedIn-style bragging get called out. "My app made 17k this month" (1,069, 0.83 ratio) and "I made $54k in 10 months" (1,141, 0.91 ratio) generate friction. The community prefers "I built this weird thing" over "I'm crushing it financially."
5. Free and open-source preference -- Posts explicitly mentioning "free," "open source," "no signup," or "no watermark" consistently score well with high ratios (0.98-0.99). The community is sympathetic to paid products but instinctively rewards generosity.

No formal rules or enforcement. The subreddit sidebar simply suggests using "[Project name] - [Short description]" format, but almost nobody follows it. There are no flairs, no mandatory formats, no blacklists, no karma requirements, and no posting frequency limits. Moderation is extremely light. The community self-polices through downvotes on perceived spam or self-promotion without substance.

Humor works extremely well here -- unlike r/macapps where humor falls flat. Meme posts ("why am i like this" at 3,147, 1.0 ratio; "Easy to say" at 3,561, 0.99 ratio; "We all start somewhere" at 1,393, 1.0 ratio) consistently rank in the top tier. Self-aware satire of the indie hacker culture ("Built an AI that teaches dolphins to code. Hit $12M ARR this morning. I am 9 years old" at 2,464) is beloved.

How this sub differs from r/macapps and r/ClaudeAI: On r/macapps, you present your product like a pitch to consumers, following strict PCP format. On r/ClaudeAI, you tell a story about using Claude. On r/SideProject, you tell a story about being a builder. The product is secondary; the person behind it is primary. This is why personal backstories ("my silly app got its first paying user" at 4,596) outperform polished product announcements every time.

3. The All-Time Leaderboard

Dataset median: ~1,207. Top-25 threshold: ~2,157.

Notable patterns: 12 of the top 25 are VIDEO format. None use any flair (r/SideProject has no flair system). Average ratio across top 25 is 0.97 -- very high, indicating the top content is nearly universally liked. Only one post (#6, "No shortcuts. Only hard work" at 0.90) shows meaningful friction, likely because it reads as hustle-culture posturing with a joke about exposing .env files.

4. Content Type Dominance at Scale

Since r/SideProject has no flair system, content types are best categorized by what the post is about rather than by flair tags.

The surprising finding: Memes and humor posts average ~2,200 score with near-perfect ratios despite being only ~8% of all posts. They punch far above their weight. Revenue/growth reports average only ~1,350 with the worst average ratio (0.92) of any category -- the community is skeptical of money posts.

5. Content Archetypes That Work

Archetype 1: "The Delightfully Unnecessary" (Score ceiling: 4,730)

Examples:

• "I made an app where you collect every cat you meet as stickers in your own cat-a-log" (4,730)
• "I made tinder but it's only pictures of my wife and I can only swipe right" (3,608)
• "Smoking neighbors hate this little trick" (3,218)
• "I built real dark mode for my website - your cursor is now a flashlight" (1,301)
• "I am a lazyfck so i am building this" (1,544)

The pattern: Projects that are whimsical, personal, slightly absurd, or solve a "problem" that makes people laugh. The project doesn't need to be commercially viable -- it needs to be charming. The cat-a-log app works because it combines a pun, a relatable love for cats, and a polished video demo. The Tinder-for-wife works because it's both funny and sweet.

Why it matters for distribution: If your product has any element of whimsy, lead with it. Even serious products can use a lighthearted framing to stand out. "I built X because I'm too lazy to Y" consistently outperforms "I built X to solve Y."

Archetype 2: "The Technical Marvel" (Score ceiling: 6,241)

Examples:

• "I wrote a 680-page Interactive Book on Computer Science Algorithms" (6,241)
• "Training a custom neural network to erase the cage from fight footage" (3,834)
• "I built a wallpaper that shifts perspective when you move your head" (3,420)
• "I build a visual Wikipedia Browser because I got sick of tabs" (3,035)
• "LLM running locally on a business card" (1,783)

The pattern: Projects that demonstrate impressive technical skill or produce visually stunning results. These almost always require video demos. The community respects craft -- a well-made demo video of something technically sophisticated is the single highest-scoring content type. The key differentiator: these projects show something you haven't seen before, not just "another SaaS."

Why it matters for distribution: If your project has any technically impressive element, make a video showing it in action. Even if the business model is boring, the tech demo can carry the post.

Archetype 3: "The Origin Story" (Score ceiling: 4,596)

Examples:

• "My silly 'secret chat' app got its first paying user... using it in a way I never imagined" (4,596)
• "Lost my job after 20 years... decided it was time to take control" (2,512)
• "I invented a timelapse camera for houseplants and brought it to market" (2,326)
• "My App surpassed $100k in revenue" (2,178)
• "After quitting my job and a 5 year relationship heartbreak..." (1,516)

The pattern: Personal narratives with emotional stakes. The product is almost secondary -- the community is investing in you. Key ingredients: adversity (job loss, relationship breakup, years of failure), a turning point, and honest emotion. The MojiCode story (4,596) works because the unexpected use case is genuinely delightful, and the founder's surprise feels authentic.

Why it matters for distribution: Your launch post should include your backstory. Where were you when you started? What made you build this? What surprised you? This community rewards the human behind the code.

Archetype 4: "The Relatable Meme" (Score ceiling: 3,561)

Examples:

• "Easy to say" (3,561, meme image)
• "why am i like this" (3,147, meme image)
• "Looking for a co-founder" (3,550, meme image)
• "I did it! $0 in 30 days!" (1,541, satirical text)
• "99.9% of posts here daily" (1,065, meme image)

The pattern: Images or short text that capture the universal experience of being a side project builder. Buying domains you never use, starting projects and never finishing them, making $0, scrolling r/SideProject instead of building. These require zero product -- just shared experience and good comedic timing.

Why it matters for distribution: Memes build your presence in the community without "spending" a launch post. Post a relatable meme, build karma and recognition, then launch your product in a separate post. This is a legitimate warm-up strategy.

Archetype 5: "The Free Gift to the World" (Score ceiling: 2,750)

Examples:

• "Created a Chrome extension to practice typing on any website" (2,750)
• "I built a free tool that turned my 15 PTO days into 53 days off" (1,616)
• "Built a free passport photo tool because I got charged 15 euros" (1,957)
• "I made an AI subtitles generator that works fully client-side. For free, no signup, no watermarks" (1,188)
• "I built a fully client-side map poster generator" (966)

The pattern: Free tools solving specific annoyances, with emphasis on "no signup, no tracking, runs locally." The community rewards generosity. These posts consistently achieve 0.98-0.99 ratios. The more friction you remove (no accounts, no cloud, no watermarks), the better the reception.

Why it matters for distribution: If you have a freemium product, lead with the free part. Make a genuinely useful free tool, launch it here with "no signup, no BS" messaging, and let the community come to you for the paid version organically.

Archetype 6: "The Meta Commentary" (Score ceiling: 2,464)

Examples:

• "Built an AI that teaches dolphins to code. Hit $12M ARR. I am 9 years old" (2,464)
• "Stop building useless sh*t" (1,479)
• "This sub is a perfect representation of dead internet theory" (259)
• "Hot take: Side project teaches you more than any college" (1,799)
• "User review: I've already paid for iPhone. Why do I have to pay for your app" (2,189)

The pattern: Posts that comment on the culture of building, launching, or the subreddit itself. The "dolphins to code" post is pure satire of hustle-culture launch posts and the community loved it. "Stop building useless sh*t" articulates frustrations about AI-generated SaaS spam that many feel but few say.

Why it matters for distribution: Understanding what the community criticizes helps you avoid those patterns in your own launch. Don't lead with revenue numbers. Don't use AI-generated marketing copy. Don't claim things happened "overnight."

6. Format Analysis

VIDEO dominates the top tier. 48% of the top 25 and top 50 are video posts. Average score for video posts: ~1,650. Average score for image posts: ~1,350. Average score for text posts: ~1,100.

What Format to Use For What

• App/tool launches -- VIDEO. A 15-45 second screen recording showing the core feature in action. The top 3 posts in the dataset are all videos. No talking head needed; just show the product working.
• Personal stories/milestones -- IMAGE (screenshot of dashboard, analytics, or a photo) + detailed selftext. The story is in the text; the image is proof.
• Memes/humor -- IMAGE. Simple, clean, instantly readable. No video needed.
• Hardware projects -- VIDEO is mandatory. Hardware needs to be seen in motion to generate excitement. Every hardware post in the top 100 is video.
• Open-source launches -- VIDEO demo + GitHub link in selftext. The community wants to see it work before they'll star the repo.

What Makes a Good Demo Video

Based on the top-performing video posts:

1. Start with the "wow moment" -- Don't build up. Show the coolest feature in the first 3 seconds. The cat-a-log video opens with a cat being photographed and turning into a sticker immediately.
2. Keep it under 45 seconds -- Most top videos are 15-45 seconds. The 680-page book video is an outlier; most successful demos are snappy.
3. Screen recording over talking head -- Not a single top-25 video is a talking-head format. They're all screen recordings, product demos, or physical product demonstrations.
4. Show the before/after -- "I got tired of X, so I built Y" is the implicit narrative. The passport photo tool shows the crappy studio experience vs. the free tool.
5. No music over narration -- Clean audio or silence. The community watches on mute in many cases, so visual clarity matters more than audio.

7. Flair/Category Strategy

r/SideProject has no flair system at all. Every single post in the 292-post dataset has an empty flair field. This means:

• No flair selection is needed -- just post.
• Your title IS your flair -- it must signal what the post is (launch, meme, advice, milestone) within the first few words.
• No pricing-model hierarchy to navigate -- unlike r/macapps where "Subscription" flair is a death sentence, r/SideProject has no formal pricing biases baked into the system.

Pricing Model Reception (Inferred from Post Performance)

Despite no flairs, the community has clear pricing preferences visible in post reception:

The community is less hostile to subscriptions than r/macapps, but posts that lead with revenue from subscription models generate more skepticism. Leading with the product (not the revenue) helps.

Title-Prefix Tags

While no formal tag system exists, certain phrases in titles function as de facto tags:

• "I built" / "I made" -- The standard opener. ~60% of all posts start with this. Safe, expected, unremarkable.
• "free" / "open source" / "no signup" -- Positive signals. Posts containing these in the title average 0.98 ratio.
• Revenue figures -- Divisive. "$100k revenue" (2,178, 0.98) works when wrapped in a genuine story. "$54k in 10 months" (1,141, 0.91) and "$17k this month" (1,069, 0.83) generate friction when they feel like humble-brags.
• "Looking for feedback" -- Neutral-to-positive. Signals humility but can read as formulaic.

8. Title Engineering

Top 10 Title Deconstruction

1. "I wrote a 680-page Interactive Book on Computer Science Algorithms" (6,241) -- Specific number (680), unexpected scale, clear topic. The specificity makes it credible.
2. "just made my first SaaS!" (5,778) -- Lowercase, casual excitement, "first" implies beginner energy. Feels authentic, not polished.
3. "I made an app where you collect every cat you meet as stickers in your own cat-a-log" (4,730) -- Pun in the product name. Clear, whimsical description. The pun does heavy lifting.
4. "My silly 'secret chat' app got its first paying user... using it in a way I never imagined" (4,596) -- Open loop (what way?). "Silly" and "first paying user" are humble. The ellipsis creates intrigue.
5. "Jelly Slider" (4,306) -- Two words. Let the video do the talking. Works ONLY with video format.
6. "No shortcuts. Only hard work." (3,950) -- Provocative motivational statement. Works because the image provides ironic context (coding on a train with .env visible).
7. "Training a custom neural network to erase the cage from fight footage" (3,834) -- Technical specificity + unexpected application. "Custom neural network" signals skill; "fight footage" signals novelty.
8. "I made tinder but it's only pictures of my wife and I can only swipe right" (3,608) -- Subverts a well-known product. The constraint is the joke. Instantly communicates the concept.
9. "Easy to say" (3,561) -- Three words. Cryptic. Only works because the image delivers the punchline.
10. "Looking for a co-founder" (3,550) -- Plays on a common serious post type but the image reveals it's a meme/joke.

Title Formulas That Work

"I built [unexpected thing] because [relatable frustration]" -- The dominant formula. Examples: "Built a free passport photo tool because I got charged 15 euros" (1,957), "I build a visual Wikipedia Browser because I got sick of tabs" (3,035), "I am a lazyfck so i am building this" (1,544).

"[Specific number] + [surprising result]" -- Numbers create credibility. "680-page Interactive Book" (6,241), "I built a Chrome extension that converts prices into time - 700 people already use it" (2,346), "5 years, 30+ failed projects... and finally one that's growing" (1,687).

"[Self-deprecating setup] + [product reveal]" -- "I did it! $0 in 30 days!" (1,541), "just made my first SaaS!" (5,778), "My silly 'secret chat' app" (4,596). Downplaying your achievement invites the community to celebrate it for you.

"[Subverted expectation]" -- "I made tinder but it's only pictures of my wife" (3,608), "Microsoft Rejected Me, So I Built My Own Excel" (1,978), "Cluely raised $15M to build this, I just open sourced it" (1,414).

Title Anti-Patterns

• Revenue-forward titles without story context generate the lowest ratios. "My app made 17k this month" (0.83), "I made $54k in 10 months" (0.91). The community interprets these as self-promotion disguised as sharing.
• Generic AI SaaS descriptions get ignored or downvoted. "I built an AI that [does common thing]" without a novel angle is the most oversaturated title pattern. The "stop building useless sh*t" meta-post (1,479) specifically calls out "I created an AI-powered chatbot" as the archetype of worthless content.
• "Looking for feedback" as the entire hook is weak. Compare "Looking for feedback" in a title (mid-range scores) vs. titling with the thing itself and asking for feedback in the selftext (top-tier scores).
• Emoji-heavy titles appear in lower-performing posts. The top 25 has minimal emoji usage. The community reads emoji as marketing polish, which triggers skepticism.

9. Engagement Patterns

If your goal is VISIBILITY, use the Technical Marvel or Delightfully Unnecessary archetype with VIDEO format. These generate the highest scores with broad appeal.

If your goal is RELATIONSHIPS and discussion, use the Origin Story archetype or offer something to the community (free codes, feedback offers, AMAs). The post "Drop your project link. I'll write you a one-liner that actually sells it" (262 score) generated 1,244 comments -- the highest in the entire dataset -- by offering value first.

Highest-Discussion Topics

1. Marketing/growth struggles -- Posts about failed marketing, $0 revenue, and "how do I get users" generate 150-250 comments of advice
2. Pricing decisions -- "How should I price this?" or showing pricing generates intense debate
3. App Store rejections/struggles -- Apple rejection stories generate solidarity comments
4. NSFW projects -- Consistently generate 200+ comments due to curiosity and novelty
5. "What should I build next?" -- Community participation posts where people suggest ideas

10. What Gets Downvoted

Ratio Tiers

Notable Low-Ratio Posts

Anti-Patterns (Named and Explained)

1. "The Hustle Bro" -- Posts that lead with revenue figures and read like a LinkedIn humblebrag. "My app made 17k this month" (0.83 ratio) is the clearest example. The community dislikes being used as an audience for someone's self-congratulation. Include revenue if it serves the story; don't make it the headline.

2. "The Tasteless Trend-Jacker" -- Building something that capitalizes on real-world tragedy or conflict. The Iran/Hormuz browser game (0.71 ratio) is the lowest in the dataset. Making a game about an active military conflict reads as exploitative.

3. "The AI Slop Launch" -- Generic AI-powered tools without genuine differentiation. "I built an AI that turns photos into X" generates friction when the underlying tech is just a thin wrapper around an existing API. The "stop building useless sh*t" post (1,479) was a direct community response to this pattern.

4. "The Repeat Poster" -- Author "Alex-grow" appears twice with nearly identical "failed projects, finally growing" narratives (1,901 and 1,687). Author "felix-heikka" posts revenue updates that get progressively worse ratios (0.91 then 0.83). Repeat self-promotion wears thin.

5. "The Stealth Price Tag" -- Posts that present as free/helpful but reveal a $199 price point or subscription in the fine print. The vestaboard alternative (0.78) led with "no subscription, one time fee $199" and still got friction -- the community expected free from the framing.

6. "The Homework Assignment" -- Posts that are clearly course projects or tutorial outputs presented as "side projects." The community can tell when something was made in 2 hours following a YouTube tutorial vs. genuine personal investment.

11. The Distribution Playbook

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

Build community presence first. Post a relatable meme about the builder experience. Comment helpfully on other people's launches. The community remembers usernames -- accounts with zero history that suddenly post a launch get less traction.

Prepare your video demo. Based on the data, VIDEO format has a ~22% higher average score than IMAGE and ~50% higher than TEXT. Record a 20-40 second screen recording or physical product demo. Show the "wow moment" first.

Study what's currently trending. Check the subreddit's front page the week before your launch. If the top posts are all memes about failed projects, lean into self-deprecation in your title. If technical demos are trending, lead with your tech.

Phase 2: Launch Day

Title formula: Use "[I built/made] [specific description] [because personal reason]" or "[Self-deprecating hook] + [product reveal]." Avoid revenue numbers in the title. Avoid emoji in the title.

Post format: VIDEO with a link to your project in the selftext. If no video, use IMAGE (screenshot or product photo). Include 3-5 sentences of backstory in the selftext -- why you built it, how long it took, what's unique about it.

Flair: None needed (no flair system exists).

Timing: Most top posts in the dataset were created during US business hours (roughly 13:00-20:00 UTC). The top 3 posts were posted on weekdays.

Pricing transparency: If your product is free, say so explicitly in the title or first line of selftext. If it's paid, mention the model honestly but don't lead with it.

Phase 3: First 24-48 Hours

Respond to every comment in the first 2 hours. This community rewards engaged founders. Answer technical questions with specificity. Accept criticism graciously -- the community is watching how you handle pushback.

Common questions you'll receive and how to answer them:

• "Is this vibe-coded / built with AI?" -- Be honest. If you used AI assistance, say so. "I used Cursor for X but wrote the core logic myself" is perfectly acceptable. Lying and getting caught is fatal. The community is suspicious of "6 months of work" claims on simple apps.
• "Why not just use [existing tool]?" -- Acknowledge the alternative and explain your specific frustration with it. "I tried X but it didn't do Y" is the gold-standard response.
• "What's the pricing?" -- Be upfront. If free, say "completely free, no catch." If freemium, explain the split. If paid, lead with the value, not the price. One-time purchases are received better than subscriptions.
• "When is the Android/iOS/web version coming?" -- If it's planned, give a rough timeline. If not, say "if there's enough demand." Don't promise what you can't deliver.
• "Source code?" -- If open source, link it immediately. If not, explain why without being defensive. "I'm a solo developer and this is how I pay rent" is a valid answer.

Phase 4: Ongoing Presence

Post updates, not reposts. The community tolerates re-posts if they show genuine progress. "I built X" (first post) -> "[Update] X now has Y feature" (second post) works. Reposting the same content with a slightly different title does not.

Contribute to other threads. Answer questions about your tech stack in other people's launch threads. Share genuine advice in "how do I market" threads. The community rewards people who give more than they take.

Cross-post strategically. If your project is relevant to r/macapps, r/webdev, r/gamedev, or niche subreddits, cross-post with reframed titles appropriate to each community. A post framed as "I built this cool thing" on r/SideProject should be reframed as "macOS tool that solves X" on r/macapps with PCP format.

Score-Tier Calibration

• 200-500: Typical for a decent launch post from a new account with moderate engagement. This is your realistic floor.
• 500-1,000: Strong post. Your project resonated with the community. Good for driving initial users.
• 1,000-2,000: Excellent. Top ~30% of all posts in the dataset. Will appear on many people's feeds.
• 2,000-4,000: Exceptional. Requires either a genuinely novel project, a compelling personal story, or a viral-quality video demo.
• 4,000+: Rare. Only 6 posts in our dataset hit this level. Requires a combination of novelty, emotional resonance, and perfect execution.

Tool launches on r/SideProject realistically peak at 1,000-2,500. If you need 4,000+, you need the Delightfully Unnecessary or Technical Marvel archetype, not a standard product launch.

Post-Publication Measurement

• Ratio above 0.95 in the first hour: You're safe. The community likes it.
• Ratio 0.85-0.95: Mixed reception. Check comments for criticism and respond constructively.
• Ratio below 0.85: Something went wrong. Read the comments carefully -- the community is telling you what they don't like.
• Comments-to-upvotes above 0.15: High engagement. You're generating discussion, which means the post has legs.
• No traction in 4 hours: The post likely won't recover. Don't delete it (that looks suspicious), but plan a differently-angled post for next week.

12. Applying This to Any Project

Quick-Reference Checklist

1. Record a 20-40 second video demo showing the best feature first
2. Write a title using the "[I built X] [because personal reason]" formula
3. Include 3-5 sentences of honest backstory in the selftext
4. Mention if it's free, open-source, or one-time purchase in the first paragraph
5. Don't put revenue numbers in the title
6. Don't use emoji in the title
7. Post during US business hours (13:00-20:00 UTC) on weekdays
8. Respond to every comment in the first 2 hours
9. Be honest about AI usage in building the project
10. Include a direct link to try/download/view the project
11. If you have a personal story, tell it -- vulnerability outperforms polish
12. Check the sub's current front page and match the energy

Scenario-Based Launch Guides

If your product is free / open-source:

• Optimal launch formula: VIDEO demo + title emphasizing "free, no signup, open source" + GitHub link. Lead with the problem you solved, not the tech stack.
• Key risk: Almost none. Free/open-source posts achieve 0.98-0.99 ratios consistently. The only risk is the project being too simple or unoriginal.
• Expected score range: 500-2,750 if the demo is good.

If your product uses one-time / lifetime pricing:

• Optimal launch formula: VIDEO or IMAGE demo + personal story about why you built it + mention pricing only in selftext, not title. Frame as "I built this for myself and now I'm sharing it."
• Key risk: Price sensitivity. Keep it under $25 for best reception. If higher, justify with detailed features and comparison to expensive alternatives ("because I can't pay $200 for a DAW just to record voiceover" at 1,304).
• Expected score range: 400-2,500.

If your product uses subscription pricing:

• Optimal launch formula: Lead with the product and the story, not the business model. Mention a free tier prominently. If possible, offer lifetime access or a generous trial. Never lead with MRR in the title.
• Key risk: The community's reflex suspicion of SaaS. Posts that feel like "look at my recurring revenue" rather than "look at what I built" generate 0.83-0.91 ratios. Counter this by being genuinely humble and focused on the product's utility.
• Expected score range: 300-1,500. Subscription products rarely break into the top 50 unless the story is exceptional.

If your product was built with AI:

• Optimal launch formula: Be transparent about AI usage but lead with the result, not the tool. "I built X" not "I vibe-coded X." If AI was genuinely helpful, frame it as one tool among many. Show genuine technical depth in comments.
• Key risk: The community has growing "AI slop" fatigue. "Stop building useless sh*t" (1,479) specifically calls out AI-generated chatbots and Cursor-built SaaS as worthless. Your post must demonstrate that your project is NOT just a thin AI wrapper. Show something AI can't easily replicate: domain expertise, design taste, personal story, or novel application.
• Expected score range: 200-1,500. AI-built projects need to work twice as hard to earn trust.

Cross-Posting Guidance

The same project should be framed differently across subreddits:

• r/SideProject: "I built [X] because [personal frustration]. Here's the story." Lead with the builder journey.
• r/macapps: "[Product Name] - [Problem it solves]. [Pricing model]. [PCP format required]." Lead with the product's utility to macOS users. Follow mandatory post formatting rules.
• r/ClaudeAI: "I used Claude Code to build [X] - here's what I learned." Lead with the Claude-specific building experience. Include what worked and what didn't.
• r/webdev or r/programming: "[Technical approach] for [problem domain]." Lead with the tech stack and architecture decisions. Include source code or technical details.

The core difference: r/SideProject rewards who you are. Other subs reward what you built or how you built it. Adjust your framing accordingly.