- Home
- Skills
- Yoanbernabeu
- Producthunt Skills
- Ph Relaunch Strategy
ph-relaunch-strategy_skill
6
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill yoanbernabeu/producthunt-skills --skill ph-relaunch-strategy- SKILL.md7.8 KB
Overview
This skill helps you plan and Product Hunt relaunch from eligibility checks through execution and analysis. It guides decision-making about whether to relaunch, how to craft a compelling relaunch story, and which assets and metrics to prepare. Use it to turn learnings from your first launch into a higher-impact second (or third) launch.
How this skill works
The skill inspects your prior launch date, feature changes, user growth, and public assets to determine relaunch eligibility under Product Hunt rules. It then recommends a relaunch angle (v2.0, redesign, or platform expansion), required asset updates, a three-month preparation timeline, and a checklist for launch day and post-launch analysis. It also provides templates for maker comments and support requests if you need early approval.
When to use it
- You released on Product Hunt 6+ months ago and built major new features.
- You completed a complete redesign, platform expansion, or product pivot.
- You want a structured prep plan to improve outcomes after a first launch.
- You need to decide whether to request early relaunch approval from Product Hunt.
- You want concrete asset and messaging templates for a stronger relaunch.
Best practices
- Only relaunch with significant, bundled updates (multiple major features or a full redesign).
- Build a larger supporter network before launch: beta users, email list, and allies.
- Refresh tagline, maker comment, gallery, and demo video to tell a new story.
- Test and iterate your tagline and demo with users beforehand.
- Document metrics and lessons from the first launch and set measurable targets for V2.
Example use cases
- A SaaS product shipping v2.0 with three major features wants a higher-ranked relaunch.
- A team that rebuilt the product UX and added platform support plans a complete redesign relaunch.
- A startup that pivoted core functionality seeks approval to relaunch before six months.
- An indie maker aiming to double signups uses the checklist to coordinate supporters and assets.
- A product with a larger user base prepares a stronger story and demo to convert new visitors.
FAQ
Yes, but only with Product Hunt approval and clear evidence of significant changes like a major version, pivot, or complete redesign.
What counts as a significant update?
Major version releases, new core features, platform expansion, full redesigns, or pivots qualify. Minor fixes, UI tweaks, pricing changes, or single integrations do not.
Should I change the product URL or name for a relaunch?
If you change name or URL and the product is different enough, treat it as a new product launch (no 6-month wait). Otherwise keep the same URL and relaunch as V2.