Product Hunt launch

# ZajLibrary — guide

You are a **technical tutor**. You help the user understand the guide below and apply it to their own situation.

**Mission:** Explain the guide below and help the user apply it to what they are building.

## Metadata
- title: Product Hunt launch
- url: https://library.zajapps.com/tech-stack/laravel/codecanyon/learn/guides/post-launch/product-hunt-launch/
- shelf: Learn & Understand
- doc_type: guide
- status: current
- kind: guide
- category: tech-stack
- subcategory: laravel
- topic: codecanyon
- description: Strategy, launch assets, launch-day execution, directory submissions, and post-launch follow-up for a Product Hunt ship.
- tags: codecanyon, laravel, post-launch, product-hunt, launch

## How to use this page
- Use the body as the source of truth: explain the ideas, then help the user apply them to their own situation.
- Surface trade-offs, decisions, and prerequisites — not just definitions.
- Cite section headings (`##`, `###`) when quoting or referring to specific parts.

---

# Product Hunt launch

:::summary[TL;DR]
**Objective** — Ship a coordinated **launch day** with assets ready, hunters lined up, and follow-up that converts spike traffic into signups.

## Launch timeline

```mermaid
graph LR
  S1["Strategy + date"] --> S2["Assets"]
  S2 --> S3["Launch day"]
  S3 --> S4["Directories"]
  S4 --> S5["Follow-up"]
```

## Strategy 👤

- Pick launch date (Tuesday–Thursday US morning often works); avoid major vendor holidays.
- Define one-sentence positioning and three proof points (screenshot, testimonial, metric).
- Recruit hunters and team comments — authentic, not spam.

## Launch assets 👤/💻

- Gallery images, logo, tagline, maker comment draft, demo video or GIF.
- Landing page UTM `?ref=producthunt` for attribution.
- Support inbox staffed launch day.

## Launch day execution 🔀

- [ ] Post goes live at scheduled time
- [ ] Maker comment published within 15 minutes
- [ ] Team shares to owned channels (once each)
- [ ] Respond to every comment same day
- [ ] Monitor Sentry + analytics for traffic spike errors

## Directories & follow-up

- Submit to complementary directories (see source S04 list) — batch after PH spike.
- Email waitlist with launch offer; retarget PH visitors who did not convert.
- Write retrospective: traffic, signups, top objections.

:::next[Next]
[Thought leadership](/tech-stack/laravel/codecanyon/learn/guides/post-launch/thought-leadership/) sustains momentum after launch day traffic fades.
:::

# Product Hunt launch

> Source: https://library.zajapps.com/tech-stack/laravel/codecanyon/learn/guides/post-launch/product-hunt-launch/

:::summary[TL;DR]
**Objective** — Ship a coordinated **launch day** with assets ready, hunters lined up, and follow-up that converts spike traffic into signups.

## Launch timeline

```mermaid
graph LR
  S1["Strategy + date"] --> S2["Assets"]
  S2 --> S3["Launch day"]
  S3 --> S4["Directories"]
  S4 --> S5["Follow-up"]
```

## Strategy 👤

- Pick launch date (Tuesday–Thursday US morning often works); avoid major vendor holidays.
- Define one-sentence positioning and three proof points (screenshot, testimonial, metric).
- Recruit hunters and team comments — authentic, not spam.

## Launch assets 👤/💻

- Gallery images, logo, tagline, maker comment draft, demo video or GIF.
- Landing page UTM `?ref=producthunt` for attribution.
- Support inbox staffed launch day.

## Launch day execution 🔀

- [ ] Post goes live at scheduled time
- [ ] Maker comment published within 15 minutes
- [ ] Team shares to owned channels (once each)
- [ ] Respond to every comment same day
- [ ] Monitor Sentry + analytics for traffic spike errors

## Directories & follow-up

- Submit to complementary directories (see source S04 list) — batch after PH spike.
- Email waitlist with launch offer; retarget PH visitors who did not convert.
- Write retrospective: traffic, signups, top objections.

:::next[Next]
[Thought leadership](/tech-stack/laravel/codecanyon/learn/guides/post-launch/thought-leadership/) sustains momentum after launch day traffic fades.
:::

Objective — Ship a coordinated launch day with assets ready, hunters lined up, and follow-up that converts spike traffic into signups.

Launch timeline

graph LR
  S1["Strategy + date"] --> S2["Assets"]
  S2 --> S3["Launch day"]
  S3 --> S4["Directories"]
  S4 --> S5["Follow-up"]

Strategy 👤

Pick launch date (Tuesday–Thursday US morning often works); avoid major vendor holidays.
Define one-sentence positioning and three proof points (screenshot, testimonial, metric).
Recruit hunters and team comments — authentic, not spam.

Launch assets 👤/💻

Gallery images, logo, tagline, maker comment draft, demo video or GIF.
Landing page UTM ?ref=producthunt for attribution.
Support inbox staffed launch day.

Launch day execution 🔀

Post goes live at scheduled time
Maker comment published within 15 minutes
Team shares to owned channels (once each)
Respond to every comment same day
Monitor Sentry + analytics for traffic spike errors

Directories & follow-up

Submit to complementary directories (see source S04 list) — batch after PH spike.
Email waitlist with launch offer; retarget PH visitors who did not convert.
Write retrospective: traffic, signups, top objections.

Thought leadership sustains momentum after launch day traffic fades.

# ZajLibrary — guide

You are a **technical tutor**. You help the user understand the guide below and apply it to their own situation.

**Mission:** Explain the guide below and help the user apply it to what they are building.

## Metadata
- title: Product Hunt launch
- url: https://library.zajapps.com/tech-stack/laravel/codecanyon/learn/guides/post-launch/product-hunt-launch/
- shelf: Learn & Understand
- doc_type: guide
- status: current
- kind: guide
- category: tech-stack
- subcategory: laravel
- topic: codecanyon
- description: Strategy, launch assets, launch-day execution, directory submissions, and post-launch follow-up for a Product Hunt ship.
- tags: codecanyon, laravel, post-launch, product-hunt, launch

## How to use this page
- Use the body as the source of truth: explain the ideas, then help the user apply them to their own situation.
- Surface trade-offs, decisions, and prerequisites — not just definitions.
- Cite section headings (`##`, `###`) when quoting or referring to specific parts.

---

# Product Hunt launch

:::summary[TL;DR]
**Objective** — Ship a coordinated **launch day** with assets ready, hunters lined up, and follow-up that converts spike traffic into signups.

## Launch timeline

```mermaid
graph LR
  S1["Strategy + date"] --> S2["Assets"]
  S2 --> S3["Launch day"]
  S3 --> S4["Directories"]
  S4 --> S5["Follow-up"]
```

## Strategy 👤

- Pick launch date (Tuesday–Thursday US morning often works); avoid major vendor holidays.
- Define one-sentence positioning and three proof points (screenshot, testimonial, metric).
- Recruit hunters and team comments — authentic, not spam.

## Launch assets 👤/💻

- Gallery images, logo, tagline, maker comment draft, demo video or GIF.
- Landing page UTM `?ref=producthunt` for attribution.
- Support inbox staffed launch day.

## Launch day execution 🔀

- [ ] Post goes live at scheduled time
- [ ] Maker comment published within 15 minutes
- [ ] Team shares to owned channels (once each)
- [ ] Respond to every comment same day
- [ ] Monitor Sentry + analytics for traffic spike errors

## Directories & follow-up

- Submit to complementary directories (see source S04 list) — batch after PH spike.
- Email waitlist with launch offer; retarget PH visitors who did not convert.
- Write retrospective: traffic, signups, top objections.

:::next[Next]
[Thought leadership](/tech-stack/laravel/codecanyon/learn/guides/post-launch/thought-leadership/) sustains momentum after launch day traffic fades.
:::

# Product Hunt launch

> Source: https://library.zajapps.com/tech-stack/laravel/codecanyon/learn/guides/post-launch/product-hunt-launch/

:::summary[TL;DR]
**Objective** — Ship a coordinated **launch day** with assets ready, hunters lined up, and follow-up that converts spike traffic into signups.

## Launch timeline

```mermaid
graph LR
  S1["Strategy + date"] --> S2["Assets"]
  S2 --> S3["Launch day"]
  S3 --> S4["Directories"]
  S4 --> S5["Follow-up"]
```

## Strategy 👤

- Pick launch date (Tuesday–Thursday US morning often works); avoid major vendor holidays.
- Define one-sentence positioning and three proof points (screenshot, testimonial, metric).
- Recruit hunters and team comments — authentic, not spam.

## Launch assets 👤/💻

- Gallery images, logo, tagline, maker comment draft, demo video or GIF.
- Landing page UTM `?ref=producthunt` for attribution.
- Support inbox staffed launch day.

## Launch day execution 🔀

- [ ] Post goes live at scheduled time
- [ ] Maker comment published within 15 minutes
- [ ] Team shares to owned channels (once each)
- [ ] Respond to every comment same day
- [ ] Monitor Sentry + analytics for traffic spike errors

## Directories & follow-up

- Submit to complementary directories (see source S04 list) — batch after PH spike.
- Email waitlist with launch offer; retarget PH visitors who did not convert.
- Write retrospective: traffic, signups, top objections.

:::next[Next]
[Thought leadership](/tech-stack/laravel/codecanyon/learn/guides/post-launch/thought-leadership/) sustains momentum after launch day traffic fades.
:::