A developer launched his ambient music app on Reddit.
It flopped.
He tried again.
Rejected by mods.
Third attempt?
Mods seemed to take a day off and his post auto-approved.
That "lucky" third try reached 600,000 people on Reddit, hit #2 on HackerNews, and took him from 2 customers to over 40.
The lesson?
The difference between failure and success is often just trying one more time.
📍 What It Is
The Multiple Attempts Strategy: Treating launch failures as data points rather than final verdicts, systematically adjusting variables (timing, titles, signup requirements), and persisting through rejections until you find the combination that works.
🎯 Why It Works
Timing is unpredictable - Same post, different time = completely different results
Mod approval is inconsistent - What gets rejected one day might pass the next
Each failure teaches something - Wrong title? Wrong format? Wrong subreddit rules?
Platforms allow retries - HackerNews explicitly permits reposting low-scoring content
Luck multiplies with attempts - More tries = more chances for timing/algorithm alignment
Removing friction increases viral potential - Accountless access means more upvotes
Most founders quit after one failed launch. Winners treat the first attempt as Experiment #1.
⚙️ How It Works
The Core Principle: Try, Adjust, Repeat
Attempt #1: Reddit r/internetisbeautiful
Title: "I made a bunch of algorithms that make ambient music for you"
Problem: Too technical, confusing for average users
Questions it raised: "Do I need to download algorithms? What's an algorithm?"
Result: Zero traction
Learning: Title didn't match audience understanding level
Attempt #2: Reddit (same subreddit)
Adjustment: Removed forced signups, simplified language
New Problem: Mod denied post - "not enough you can do without an account"
Result: Rejected by moderator
Learning: Still had "obvious references to premium section" that signaled paywalls
Attempt #3: Reddit (same subreddit)
Adjustment: Removed all premium references, made everything accessible
Lucky Break: Mods seemingly took day off, post auto-approved
Result: 600K reach, viral success
Learning: Persistence + timing luck = breakthrough
HackerNews Attempts:
Failed titles: Too generic or unclear
Winning title: "I made a website with 100+ ambient music generators (works in browser)"
Why it worked: Technical audience understood "generators," loved "works in browser"
Result: #2 on HackerNews
Step-by-Step Implementation:
Embrace accountless access - Reddit and HN communities want instant usability. No signup walls. Make your core value accessible immediately. This isn't viable for all SaaS, but it's essential for viral launches.
Study failed posts in /new sections - Spend time watching what dies in "new." Posts requiring signups consistently get zero upvotes. Learn from others' failures.
Title for your specific audience - Reddit: Simple, non-technical ("I made ambient music you can use right now"). HackerNews: Technical details matter ("100+ generators, works in browser"). Same product, different framing.
Use "I made a..." opening - Personal element resonates. People love the human story behind the product.
Find optimal posting times - Use tools like laterforreddit.com to identify peak activity hours for your target subreddit.
Adjust one variable at a time - Changed title? Keep everything else the same. Changed signup flow? Keep title same. This way you know what actually made the difference.
Document every attempt - Track: title used, time posted, which features were accessible, mod response, upvotes in first hour. Patterns emerge.
Build re-engagement mechanism - Drew created Discord (150 members). Email signups work too. You need a way to contact people after the viral moment fades.
Pro Tips:
HackerNews explicitly allows reposting low-scoring submissions
Reddit is trickier but allows reposts if you make genuine changes
Mods can reject for vague reasons ("no generators rule" - seriously?)
Sometimes you just need luck (mods taking a day off)
Don't overthink - launch, learn, adjust, repeat
The Mindset: "There were 1000 more things I could have done before launch but I am glad I have this under my belt and can keep working from here." - Drew
🏆 Real Example
Developer: Drew (Flowful - ambient music generator web app)
Starting point: 2 paying customers before launch
Timeline of Attempts:
Attempt #1 - Reddit Fail:
Title too technical for general audience
Required signup
Zero traction
Learning: Simplify language, remove friction
Attempt #2 - Reddit Rejection:
Removed signups
Mod rejected: "not enough you can do without an account"
Learning: Premium features still too visible
Attempt #3 - Reddit Success:
Removed all premium references
Simplified title
Lucky timing (mods auto-approved)
Result: 600K reach
HackerNews Success:
Multiple attempts with different titles
Winning title: Technical but clear
Result: #2 position on HackerNews
Combined Results:
20,000+ visitors across platforms
70+ sales (mostly lifetime deals)
2 → 40+ paying customers (20x growth)
150 Discord members for ongoing engagement
Only $20 MRR but massive validation
#2 on HackerNews
600K Reddit reach
What Made It Work:
Removed signup requirement - Made product instantly usable
Audience-appropriate titles - Technical for HN, simple for Reddit
Persistence through rejections - Nearly gave up before breakthrough
Lucky timing - Third attempt when mods were less active
Discord for retention - 150 people he can now re-engage
Lifetime deals - Got validation + revenue without MRR pressure
Key insights:
"I almost overlooked Discord" - Built-in re-engagement saved the launch value
Lifetime deals worked better than MRR for his audience (techies who appreciate craft)
Multiple failed titles taught him what resonates with each platform
Mod rules are sometimes arbitrary - don't take rejections personally
Setting launch date and committing matters more than perfect preparation
The Reality Check: Drew was "very close to giving up" before the third attempt worked.
The difference between failure and 40 customers was literally one more try when mods happened to be less strict.
💡 Your Turn If you've had a failed launch, change one variable (title, timing, or access requirements) and try again this week. Reply with what you're changing and why—best strategy gets featured Friday!