ph-email-strategy

Product Hunt Email Strategy

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "ph-email-strategy" with this command: npx skills add yoanbernabeu/producthunt-skills/yoanbernabeu-producthunt-skills-ph-email-strategy

Product Hunt Email Strategy

This skill helps you plan and execute email campaigns that drive engagement for your Product Hunt launch while staying compliant with community guidelines.

When to Use This Skill

  • Planning pre-launch email sequence

  • Writing launch day email campaigns

  • Timing email waves across timezones

  • Crafting compliant outreach messages

  • Creating follow-up email sequences

The Golden Rules

Rule 1: Never Ask for Upvotes

  • ❌ "Please upvote our product"

  • ❌ "Every vote counts"

  • ❌ "Help us reach #1"

  • ✓ "Check it out and share your feedback"

  • ✓ "We'd love your support"

  • ✓ "Let us know what you think"

Rule 2: Stagger Your Sends

  • Don't send to everyone at once

  • Algorithm flags sudden traffic spikes

  • Spread across 5-6 waves over 24 hours

Rule 3: Segment Your Audience

  • Different messages for different groups

  • Personal > mass email

  • Quality engagement > quantity

Email Timeline

Pre-Launch Sequence

T-14 days: Awareness Email

Subject: We're launching something new...

Hey [Name],

In 2 weeks, we're launching [Product] on Product Hunt.

[1-2 sentences about what it does]

Want to be notified when we go live?

[Optional: Early access or sneak peek link]

Best, [Your Name]

T-7 days: Reminder + Preview

Subject: 7 days until launch 🚀

Hey [Name],

One week from today, [Product] goes live on Product Hunt.

Here's a sneak peek: [Screenshot or GIF]

[Key feature highlight]

Mark your calendar: [Date, Time PST]

Talk soon, [Your Name]

T-1 day: Final Countdown

Subject: Tomorrow's the day

Hey [Name],

Tomorrow at 12:01 AM PST, we launch on Product Hunt.

Here's exactly what [Product] does: • [Benefit 1] • [Benefit 2] • [Benefit 3]

I'd really appreciate your support — even just checking it out and leaving honest feedback means the world.

I'll send the link as soon as we're live.

Thanks for being part of this journey, [Your Name]

Launch Day Emails (The 5-6 Wave Strategy)

Wave 1: Midnight PST (for Night Owls / APAC)

Recipients: Australia, Asia, Night owl friends Time: 12:01 AM - 1:00 AM PST

Wave 2: Early Morning PST (EU Afternoon)

Recipients: Europe (afternoon for them) Time: 5:00 AM - 6:00 AM PST

Wave 3: Morning PST (US East Coast)

Recipients: US East Coast, Canada Time: 8:00 AM - 9:00 AM PST

Wave 4: Lunch PST (US Coverage)

Recipients: General US audience Time: 12:00 PM - 1:00 PM PST

Wave 5: Afternoon PST (Reminder)

Recipients: Non-openers from earlier waves Time: 4:00 PM - 5:00 PM PST

Wave 6: Evening PST (Final Push)

Recipients: Closest supporters, team networks Time: 8:00 PM - 9:00 PM PST

Launch Day Email Templates

Template A: Close Network (Most Personal)

Subject: I just launched! 🚀

Hey [Name],

The moment is here — we just launched [Product] on Product Hunt!

[Direct link]

I've been building this for [X months], and today is the day it goes out to the world. Pretty nervous, honestly.

If you have 2 minutes: → Check it out → Leave a comment with your honest thoughts → Share if you think it's useful

Your support means everything. No pressure at all — just excited to finally share this.

[Your Name]

P.S. [Personal note relevant to this person]

Template B: Customers/Users

Subject: [Product] is live on Product Hunt

Hi [Name],

Big news — [Product] is officially live on Product Hunt!

[Direct link]

As someone who's been using [Product], your perspective would mean a lot to the community.

If you have a moment: • Share your experience in the comments • Let others know what you've built/achieved with it • Honest feedback only — don't sugarcoat it!

Thanks for being an early believer.

Best, [Your Name]

Template C: Newsletter/Community

Subject: We launched on Product Hunt today

Hey [First Name],

Today's a big day — [Product] is live on Product Hunt.

[What it does in 1 sentence] [Why it matters in 1 sentence]

🔗 Check it out here: [Link]

If you think it's useful, a comment or share would make our day. If you have feedback, we're all ears.

Thanks for being part of [Company/Community].

[Your Name]

Template D: VIPs / Influencers

Subject: Quick favor? (launching today)

Hey [Name],

I know you're busy, so I'll keep this brief.

We're launching [Product] on Product Hunt today. Given your expertise in [their field], I thought you might find it interesting.

[1-2 sentences on what makes it relevant to them]

Here's the link: [Link]

If it resonates, any thoughts in the comments would be incredible. Totally understand if you're swamped.

Appreciate you either way, [Your Name]

Subject Line Formulas

High-Open-Rate Patterns

  • [Product] is live on Product Hunt

  • I just launched! 🚀

  • Today's the day

  • Quick favor? (launching today)

  • We made something for you

Avoid

  • ❌ All caps

  • ❌ Multiple emojis

  • ❌ "URGENT" or "IMPORTANT"

  • ❌ "Please upvote"

Segmentation Strategy

Tier 1: Inner Circle (50-100 people)

  • Co-founders, close friends, family

  • Early beta users

  • Advisors, investors

  • Approach: Very personal, handwritten feel

Tier 2: Active Community (100-500 people)

  • Current customers

  • Newsletter subscribers

  • Social media engaged

  • Approach: Warm but efficient

Tier 3: Extended Network (500+ people)

  • General mailing list

  • Past contacts

  • Industry connections

  • Approach: Professional, clear value

Post-Launch Follow-Up

T+1 day: Thank You

Subject: Thank you 🙏

Hey [Name],

Yesterday was incredible. Thanks to supporters like you, we reached [#X Product of the Day / X upvotes / etc.].

[Share 1-2 highlights: interesting comments, surprises]

What's next: • [Next feature/milestone] • [How they can continue helping]

Grateful for your support, [Your Name]

T+7 days: Results + Next Steps

Subject: What happened after Product Hunt

Hey [Name],

One week since our Product Hunt launch. Here's what happened:

📊 [X] new users signed up 💬 [X] pieces of feedback collected 🎯 Top feature request: [Feature]

[What you're doing about it]

Thanks again for being part of this.

[Your Name]

Email Checklist

Pre-Launch

  • Email list segmented into tiers

  • Pre-launch sequence scheduled

  • Subject lines A/B tested

  • Links tested and tracked

Launch Day

  • 5-6 waves planned by timezone

  • Templates personalized by segment

  • Tracking in place

  • "No upvote ask" compliance checked

Post-Launch

  • Thank you email drafted

  • Results email planned

  • Non-openers sequence ready

Output Format

EMAIL STRATEGY FOR: [Product Name]

LAUNCH DATE: [Date] TOTAL AUDIENCE: [Number]

SEGMENTATION: Tier 1 (Inner Circle): [Number] contacts Tier 2 (Active Community): [Number] contacts Tier 3 (Extended Network): [Number] contacts

PRE-LAUNCH SEQUENCE: • T-14: [Subject line] • T-7: [Subject line] • T-1: [Subject line]

LAUNCH DAY WAVES: Wave 1: [Time PST] → [Segment] ([Number] people) Wave 2: [Time PST] → [Segment] ([Number] people) Wave 3: [Time PST] → [Segment] ([Number] people) Wave 4: [Time PST] → [Segment] ([Number] people) Wave 5: [Time PST] → [Segment] ([Number] people) Wave 6: [Time PST] → [Segment] ([Number] people)

POST-LAUNCH: • T+1: Thank you email • T+7: Results update

COMPLIANCE CHECK: ✓ No explicit upvote requests ✓ Staggered sending schedule ✓ Personalized by segment

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

ph-community-outreach

No summary provided by upstream source.

Repository SourceNeeds Review
General

ph-social-media-launch

No summary provided by upstream source.

Repository SourceNeeds Review
General

ph-launch-strategy

No summary provided by upstream source.

Repository SourceNeeds Review
General

ph-launch-day-checklist

No summary provided by upstream source.

Repository SourceNeeds Review