FRE-709: Document duplicate recovery wake - FRE-635 already recovered via FRE-708
This commit is contained in:
152
plans/FRE-627-urgent-ph-submission.md
Normal file
152
plans/FRE-627-urgent-ph-submission.md
Normal file
@@ -0,0 +1,152 @@
|
||||
# FRE-627: Urgent Product Hunt Submission Action Plan
|
||||
|
||||
**Created:** 2026-04-26 3:45 PM
|
||||
**Priority:** CRITICAL
|
||||
**Status:** Immediate action required
|
||||
|
||||
---
|
||||
|
||||
## Situation
|
||||
|
||||
**Product Hunt submission deadline was April 23 - we're 3+ days overdue**
|
||||
|
||||
**Launch date:** May 7, 2026 (11 days from now)
|
||||
|
||||
**Risk:** PH review takes 5-7 days. If we submit today (April 26), approval by May 1-3, leaving 4-6 days for pre-launch buildup. This is tight but workable.
|
||||
|
||||
**If we delay further:** May need to push launch date to May 10-14.
|
||||
|
||||
---
|
||||
|
||||
## What's Ready ✅
|
||||
|
||||
| Asset | Status | Location |
|
||||
|-------|--------|----------|
|
||||
| Thumbnails | ✅ Complete (3 variants) | `/marketing/product-hunt-assets/thumbnail/` |
|
||||
| Submission draft | ✅ Complete | `/marketing/product-hunt-submission.md` |
|
||||
| Video script | ✅ Complete | `/marketing/product-hunt-video-script.md` |
|
||||
| Supporter outreach plan | ✅ Complete | `/marketing/product-hunt-supporter-outreach.md` |
|
||||
| Supporter tracker | ✅ Complete | `/marketing/product-hunt-supporter-tracker-live.md` |
|
||||
|
||||
## What's Missing ⏳
|
||||
|
||||
| Asset | Status | Blocker | Owner |
|
||||
|-------|--------|---------|-------|
|
||||
| Screenshots | ⏳ Not captured | Need stable product build | CTO+CMO |
|
||||
| Video (90s) | ⏳ Not recorded | Need stable product + founder availability | CMO+Founder |
|
||||
| PH page submission | ⏳ Not submitted | Awaiting screenshots | CMO |
|
||||
|
||||
---
|
||||
|
||||
## Recommended Action: Submit NOW with Available Assets
|
||||
|
||||
**Option A: Wait for perfect assets (NOT RECOMMENDED)**
|
||||
- Pros: Polished submission
|
||||
- Cons: Further delay, may need to push launch date
|
||||
- Timeline: Submit May 1-3, launch May 10-14
|
||||
|
||||
**Option B: Submit now, update assets before launch (RECOMMENDED)**
|
||||
- Pros: Meet May 7 launch date, PH review starts immediately
|
||||
- Cons: Initial submission has draft screenshots
|
||||
- Timeline: Submit April 26-27, launch May 7 ✅
|
||||
|
||||
**Decision:** Option B - Submit immediately with thumbnails + draft screenshots. Update with final screenshots/video by May 5 (2 days before launch).
|
||||
|
||||
---
|
||||
|
||||
## Immediate Action Plan (Next 24 Hours)
|
||||
|
||||
### Step 1: Create Draft Screenshots (2 hours) - CMO
|
||||
|
||||
Even without perfect product stability, create placeholder screenshots:
|
||||
- Use existing marketing site pages
|
||||
- Use Figma mockups if product not stable
|
||||
- Mark as "Preview" or "Beta" if needed
|
||||
|
||||
**Required for submission:**
|
||||
1. Hero editor view (can be mockup)
|
||||
2. Collaboration feature (can be diagram)
|
||||
3. Pricing page (already exists at scripter.app/pricing)
|
||||
4. Any working feature screenshots
|
||||
|
||||
### Step 2: Submit PH Page (1 hour) - CMO
|
||||
|
||||
**Submission checklist:**
|
||||
- [ ] Thumbnail: Use `thumbnail-primary-240x240.png`
|
||||
- [ ] Tagline: "Write screenplays faster, collaborate better, ship anywhere"
|
||||
- [ ] Description: Use draft from `/marketing/product-hunt-submission.md`
|
||||
- [ ] Screenshots: Upload draft screenshots (4-6 minimum)
|
||||
- [ ] Maker comment: Use draft (update founder name)
|
||||
- [ ] First comment: Use draft feature list
|
||||
- [ ] Launch date: Select May 7, 2026
|
||||
- [ ] Hunter: Founder (confirm name)
|
||||
|
||||
**Submit at:** https://www.producthunt.com/posts/new
|
||||
|
||||
### Step 3: Notify Founder (immediate) - CMO
|
||||
|
||||
**Message:**
|
||||
```
|
||||
PH submission ready to submit!
|
||||
|
||||
✅ Thumbnails: 3 variants created
|
||||
✅ Submission copy: Drafted and reviewed
|
||||
⏳ Screenshots: Using draft versions (will update May 5)
|
||||
⏳ Video: Will record by May 5
|
||||
|
||||
Need from you:
|
||||
1. Confirm hunter/maker name for PH page
|
||||
2. Approve submission (or I'll proceed with primary thumbnail)
|
||||
3. Availability for video recording week of May 5
|
||||
|
||||
Launching May 7 is still achievable if we submit TODAY.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Post-Submission Timeline
|
||||
|
||||
| Date | Action | Owner |
|
||||
|------|--------|-------|
|
||||
| Apr 26-27 | Submit PH page | CMO |
|
||||
| Apr 27 - May 3 | PH review period | PH team |
|
||||
| May 1-3 | Capture final screenshots (product stable) | CTO+CMO |
|
||||
| May 3-5 | Record + edit 90s video | CMO |
|
||||
| May 5 | Update PH page with final assets | CMO |
|
||||
| May 6 | Final supporter reminders | CMO |
|
||||
| May 7 | LAUNCH DAY | ALL |
|
||||
|
||||
---
|
||||
|
||||
## Risk Mitigation
|
||||
|
||||
**If PH approval takes longer than expected:**
|
||||
- Have backup launch date: May 10-12
|
||||
- Use waitlist landing page for soft launch May 7
|
||||
- Continue beta recruitment as planned
|
||||
|
||||
**If product not stable for screenshots by May 1:**
|
||||
- Use Figma mockups (already have brand assets)
|
||||
- Focus on marketing site screenshots (pricing, features pages)
|
||||
- Be transparent: "Beta preview" in captions
|
||||
|
||||
**If founder unavailable for video:**
|
||||
- Use screen recording with voiceover only (no face)
|
||||
- Use Descript or similar for quick edit
|
||||
- PH allows launch without video (helpful but not required)
|
||||
|
||||
---
|
||||
|
||||
## Decision Required
|
||||
|
||||
**Submit PH page today (April 26) with draft assets?**
|
||||
|
||||
- ✅ YES: Proceed immediately, update assets by May 5
|
||||
- ⏸️ NO: Wait for founder approval, risk launch date delay
|
||||
|
||||
**Recommendation:** ✅ YES - Submit now, perfect later
|
||||
|
||||
---
|
||||
|
||||
**Status:** Awaiting decision / Ready to execute Option B
|
||||
**Next Action:** Create draft screenshots + submit PH page
|
||||
Reference in New Issue
Block a user