tomevault-io Product Hunt Relaunch Strategy
This skill helps you plan and execute successful relaunches on Product Hunt, building on your previous launch experience.
When to Use This Skill
- Evaluating if you should relaunch
- Understanding relaunch rules
- Preparing for a version 2.0 launch
- Maximizing relaunch impact
- Timing your next launch
Relaunch Rules
Official Guidelines
Standard Rule:
- Can relaunch after 6 months
- Must have significant updates
Exceptions:
- Major product pivot (can be sooner)
- New product with different name/URL (anytime)
- V2 with substantial changes (request approval)
What Counts as "Significant"
Qualifies for Relaunch:
- Major version release (v2.0)
- Complete redesign
- New core features
- Platform expansion
- Pivot/rebrand
Does NOT Qualify:
- Minor bug fixes
- Small feature additions
- UI tweaks
- Pricing changes
- New integrations alone
Should You Relaunch?
Relaunch Decision Matrix
| Question | Yes = Relaunch | No = Wait |
|---|---|---|
| 6+ months since last launch? | ✓ | Need approval |
| Major new features/version? | ✓ | Need more changes |
| Compelling new story to tell? | ✓ | Need better angle |
| Bigger audience now? | ✓ | Build audience first |
| First launch was learning? | ✓ | Optimize first |
When to Relaunch
Good Reasons:
- V2 with major improvements
- Expansion to new platform
- Major feature launch
- Significant pivot
- Acquired large user base
Bad Reasons:
- First launch underperformed
- Want more upvotes
- Nothing new, just want attention
- Gaming the system
Relaunch Strategy
Timing Your Relaunch
Wait Until You Have:
- 2-3 major new features minimum
- Clear differentiation from v1
- Compelling new story
- Larger support network than before
- Lessons applied from first launch
Bundle Updates: Instead of launching each feature separately, combine:
- Feature A + Feature B + Feature C = "Major Update Launch"
Positioning the Relaunch
Approach 1: "Version 2.0"
[Product] 2.0: Now with [major improvement]
We listened to your feedback. Here's everything new:
• [Feature 1]
• [Feature 2]
• [Feature 3]
Approach 2: "Complete Redesign"
[Product] — Completely Rebuilt
Same mission, totally new experience:
• [Improvement 1]
• [Improvement 2]
• [Improvement 3]
Approach 3: "Platform Expansion"
[Product] for [New Platform]
By popular demand: [Product] is now on [Platform]
• [Platform-specific feature]
• [Platform-specific feature]
What's Different This Time
Learn from First Launch:
| First Launch Issue | Second Launch Fix |
|---|---|
| Weak tagline | Test tagline beforehand |
| Low engagement | Build bigger supporter network |
| Poor timing | Choose optimal day |
| Rushed assets | Professional design |
| No video | Compelling demo video |
Preparing for Relaunch
3-Month Preparation
Month 1: Foundation
- Analyze first launch performance
- Identify what to improve
- Start building new features
- Grow email list/community
Month 2: Building
- Complete major updates
- Prepare new assets
- Build support network
- Test with beta users
Month 3: Launch Prep
- Finalize all assets
- Coordinate supporters
- Schedule launch day
- Pre-launch marketing
Asset Updates Needed
Always Update:
- Tagline (reflect new value)
- Description (highlight what's new)
- Gallery images (show new features)
- Video (demo new capabilities)
- Maker comment (new story)
Consider Updating:
- Thumbnail (refresh or keep for recognition)
- Website (new landing page for v2)
- Email templates (reflect changes)
Relaunch Messaging
Tagline Formula for Relaunch
Version 2 Format:
[Product] 2.0: [Key improvement]
Evolution Format:
[Product], now with [game-changing feature]
Expansion Format:
[Product] for [New platform/audience]
Maker Comment for Relaunch
Structure:
Hey Product Hunt! 👋
Some of you might remember us from [timeframe] ago.
We're back with [Product] 2.0, and a lot has changed.
WHAT WE HEARD
After our first launch, the community told us:
• [Feedback 1]
• [Feedback 2]
• [Feedback 3]
WHAT WE BUILT
We went back to work and:
• [New feature 1]
• [New feature 2]
• [New feature 3]
THE RESULTS
Since v1, [X users] have [used/joined], and they've
helped us build something much better.
WHAT'S NEXT
We're just getting started. [Future vision]
Would love your feedback on the new version!
[CTA]
Thanks for the support 🙏
[Name]
Request for Early Relaunch
When to Request
If less than 6 months but have:
- Major version update
- Significant pivot
- Complete redesign
How to Request
- Go to Product Hunt support
- Explain the significant changes
- Provide evidence of major updates
- Wait for approval
Request Template
Subject: Relaunch Request for [Product Name]
Hi Product Hunt Team,
We launched [Product] on [date]. We'd like to request
permission to relaunch before 6 months because we've
made significant changes.
WHAT'S NEW:
1. [Major change 1] — [Brief explanation]
2. [Major change 2] — [Brief explanation]
3. [Major change 3] — [Brief explanation]
EVIDENCE:
• [Link to changelog or blog post]
• [Screenshots of changes]
• [User feedback on improvements]
We believe this qualifies as a significant update under
your relaunch guidelines.
Thank you for considering our request.
Best,
[Your Name]
[Product URL]
Relaunch vs New Product
When It's a Relaunch
- Same product, improved
- Same URL
- Same core purpose
- Evolution of original
When It's a New Product
- Different name
- Different URL
- Different purpose
- Spin-off or new direction
New Product Advantage:
- Can launch anytime
- No 6-month wait
- Fresh start
- Different audience possible
Relaunch Success Metrics
Compare to First Launch
| Metric | Launch 1 | Launch 2 | Goal |
|---|---|---|---|
| Ranking | Higher | ||
| Upvotes | +50% | ||
| Comments | More quality | ||
| Signups | +100% | ||
| Conversion | Higher |
Key Questions
After relaunch, assess:
- Did new features resonate?
- Was timing better?
- Did larger network help?
- What would you do differently for v3?
Relaunch Checklist
Pre-Relaunch (1 Month)
- 6 months elapsed OR approval received
- Major updates completed
- New story/angle prepared
- Assets updated
- Support network expanded
Launch Prep (1 Week)
- All new assets finalized
- Supporters briefed
- Emails scheduled
- Social posts ready
- Launch date confirmed
Relaunch Day
- Apply all lessons from first launch
- Execute improved strategy
- Compare metrics in real-time
- Document learnings
Post-Relaunch
- Analyze vs first launch
- Document improvements
- Plan for potential v3
- Maintain momentum
Output Format
RELAUNCH STRATEGY: [Product Name]
FIRST LAUNCH:
Date: [Date]
Results: #[X], [X] upvotes, [X] signups
Lessons: [Key learnings]
RELAUNCH ELIGIBILITY:
Time since launch: [X months]
Status: [Eligible / Need approval / Too soon]
SIGNIFICANT UPDATES:
1. [Update 1]: [Description]
2. [Update 2]: [Description]
3. [Update 3]: [Description]
RELAUNCH POSITIONING:
Angle: [v2.0 / Redesign / Expansion / etc.]
Tagline: "[New tagline]"
Key message: [Core message]
IMPROVEMENTS FROM V1:
| Area | V1 | V2 |
|------|-----|-----|
| [Area] | [Old] | [New] |
TARGET METRICS:
| Metric | V1 | V2 Target |
|--------|-----|-----------|
| Ranking | #[X] | #[X] |
| Upvotes | [X] | [X] |
| Signups | [X] | [X] |
TIMELINE:
[Date]: [Milestone]
[Date]: [Milestone]
[Date]: RELAUNCH DAY
Converted and distributed by TomeVault — claim your Tome and manage your conversions.