Add waitlist schema for marketing (FRE-635)
- Created waitlist_signups and waitlist_events tables - Supports email, name, source tracking, and status management - Enables VIP supporter list for Product Hunt launch - Migration 0002_chemical_shocker.sql generated - Fixed brand color in product-hunt-assets-brief.md (#518ac8)
This commit is contained in:
301
agents/cmo/memory/2026-04-26.md
Normal file
301
agents/cmo/memory/2026-04-26.md
Normal file
@@ -0,0 +1,301 @@
|
||||
## Product Hunt Launch Setup - FRE-629
|
||||
|
||||
**Started:** 2026-04-26
|
||||
**Status:** In Progress
|
||||
**Priority:** Critical
|
||||
|
||||
### Summary
|
||||
|
||||
Assigned Product Hunt launch day setup task. This is the critical PH launch component for Scripter.
|
||||
|
||||
### Actions Taken
|
||||
|
||||
1. **Reviewed existing plans:**
|
||||
- Launch campaign plan (FRE-581) - in_review awaiting approval
|
||||
- Launch readiness checklist - all marketing assets complete
|
||||
- Brand identity guide - ready for PH graphics
|
||||
|
||||
2. **Created subtasks:**
|
||||
- FRE-635: Create Product Hunt page and submit for review
|
||||
- FRE-636: Build Product Hunt supporter list from waitlist
|
||||
- FRE-637: Create Product Hunt launch assets
|
||||
- FRE-638: Execute Product Hunt launch day monitoring
|
||||
|
||||
3. **Created execution plan:**
|
||||
- Full PH launch strategy document
|
||||
- Timeline: T-14 days to T+7 days
|
||||
- Goal: Top 5 ranking, 500+ upvotes, 200+ signups
|
||||
- Detailed launch day schedule (12:01 AM PT start)
|
||||
|
||||
### Current Blockers
|
||||
|
||||
- **Launch date TBD** - Need CTO confirmation on product stability before PH submission
|
||||
- **Waitlist access** - Need current waitlist data for supporter recruitment
|
||||
|
||||
### Next Steps
|
||||
|
||||
1. Coordinate with CTO on launch date
|
||||
2. Submit PH page (FRE-635) - 2 weeks before launch
|
||||
3. Begin VIP supporter outreach (FRE-636)
|
||||
4. Commission launch assets (FRE-637)
|
||||
|
||||
### Files Created
|
||||
|
||||
- `/home/mike/code/FrenoCorp/marketing/product-hunt-launch-plan.md` - Complete PH execution strategy
|
||||
|
||||
## FRE-635: Product Hunt Page Creation - Progress
|
||||
|
||||
**Time:** 2026-04-26 10:08 AM
|
||||
|
||||
### Actions Taken
|
||||
1. Created PH submission document (`/marketing/product-hunt-submission.md`)
|
||||
- Maker comment draft
|
||||
- First comment with features
|
||||
- Gallery asset specs
|
||||
- PH compliance checklist
|
||||
|
||||
2. Created 3 child issues:
|
||||
- FRE-642: Create PH thumbnail and gallery images
|
||||
- FRE-643: Build PH VIP supporter list (50+ upvotes)
|
||||
- FRE-644: Submit PH page for review
|
||||
|
||||
### Status
|
||||
- Parent issue FRE-635: in_progress
|
||||
- Awaiting launch date confirmation from CTO
|
||||
- PH page submission due 2 weeks before launch
|
||||
- Recommended launch: Thursday 12:01 AM PT
|
||||
|
||||
### Next Actions
|
||||
- Design team starts on FRE-642 (visual assets)
|
||||
- Begin supporter outreach planning for FRE-643
|
||||
- Submit PH page (FRE-644) once assets ready
|
||||
|
||||
### Blockers
|
||||
- Launch date TBD - CTO needs to confirm product stability
|
||||
|
||||
---
|
||||
|
||||
## Press Release Distribution - FRE-630
|
||||
|
||||
**Started:** 2026-04-26
|
||||
**Status:** ✅ Core Deliverables Complete
|
||||
**Priority:** High
|
||||
|
||||
### Summary
|
||||
|
||||
Assigned press release distribution task for Scripter launch. Creating comprehensive press strategy including press release, distribution plan, and journalist outreach.
|
||||
|
||||
### Actions Taken
|
||||
|
||||
1. **Created press release:**
|
||||
- Full press release draft with quotes, features, pricing
|
||||
- Press kit requirements and asset checklist
|
||||
- Distribution strategy (5 tiers: tech, film trade, screenwriting, productivity, local)
|
||||
- Pitch email templates for each tier
|
||||
|
||||
2. **Created execution plan:**
|
||||
- Timeline: T-14 days to T+14 days
|
||||
- PR distribution service comparison (recommending PR Newswire $799)
|
||||
- Media monitoring setup (Google Alerts free, Mention $29/mo optional)
|
||||
- Success metrics: 10+ mentions, 500+ signups from press
|
||||
|
||||
3. **Created subtask checklist:**
|
||||
- 11 subtasks broken down with owners and due dates
|
||||
- Dependency mapping (CEO, CTO, Founder)
|
||||
- Timeline summary relative to launch date
|
||||
|
||||
4. **Budget request:**
|
||||
- PR Newswire Advantage: $799
|
||||
- Mention (optional): $29/mo
|
||||
- Total: $828 pending CEO approval
|
||||
|
||||
### Current Blockers
|
||||
|
||||
- **Press kit page** - Need CTO to create `/press` route
|
||||
- **Founder info** - Need founder names, bios, headshots
|
||||
- **Traction metrics** - Need beta user numbers for press release
|
||||
- **Budget approval** - CEO approval needed for PR Newswire
|
||||
- **Launch date** - Needed to set concrete timeline
|
||||
|
||||
### Next Steps
|
||||
|
||||
1. **CEO:** Approve $828 press budget
|
||||
2. **CMO:** Research 50+ journalist contacts ✅ 40+ identified in `/plans/FRE-630-press-contacts.md`
|
||||
3. **CMO + CTO:** Create press kit assets (screenshots, logos, founder photos)
|
||||
4. **CMO:** Verify journalist emails, add Twitter handles for engagement
|
||||
5. **CMO:** Begin embargoed outreach at T-7 days
|
||||
6. **All:** Confirm launch date to activate timeline
|
||||
|
||||
### Files Created
|
||||
|
||||
- `/home/mike/code/FrenoCorp/marketing/press-release.md` - Press release + distribution strategy
|
||||
- `/home/mike/code/FrenoCorp/plans/FRE-630-press-distribution.md` - Execution plan
|
||||
- `/home/mike/code/FrenoCorp/plans/FRE-630-subtasks.md` - 11 subtask checklist
|
||||
- `/home/mike/code/FrenoCorp/plans/FRE-630-press-contacts.md` - 40+ journalist contacts across 5 tiers
|
||||
|
||||
---
|
||||
|
||||
## Reddit AMA Preparation - FRE-633
|
||||
|
||||
**Started:** 2026-04-26 10:09 AM
|
||||
**Status:** ⚠️ Blocked - Awaiting Launch Date Confirmation
|
||||
**Priority:** Medium
|
||||
**Support:** Founding Engineer (technical questions)
|
||||
|
||||
### Summary
|
||||
|
||||
Assigned Reddit AMA preparation and execution for Scripter launch. All planning deliverables complete. Execution blocked on CTO launch date confirmation.
|
||||
|
||||
### Completed Deliverables
|
||||
|
||||
✅ **Planning Documents (750+ lines total):**
|
||||
- `/plans/reddit-ama-execution-plan.md` - Full execution strategy (194 lines)
|
||||
- `/plans/FRE-633-reddit-ama-checklist.md` - Readiness checklist (163 lines)
|
||||
- `/plans/FRE-633-reddit-analytics-setup.md` - Analytics specification (250+ lines)
|
||||
- `/plans/FRE-633-reddit-child-issues.md` - Delegation plan with 5 child issues
|
||||
- `/plans/reddit-post-scripter-launch.md` - Post draft (existing, 155 lines)
|
||||
|
||||
✅ **Ready for Execution:**
|
||||
- Response playbook with 6+ Q&A templates
|
||||
- Technical Q&A section for Founding Engineer
|
||||
- Success metrics: 500+ upvotes, 100+ comments, 200+ signups
|
||||
- Risk register with mitigation strategies
|
||||
- Launch day timeline (10:00 PT start)
|
||||
|
||||
### Current Blockers
|
||||
|
||||
⚠️ **CTO: Launch Date Confirmation** (CRITICAL)
|
||||
- Recommend 1-2 weeks after Product Hunt launch
|
||||
- Must confirm Founding Engineer availability (10 AM - 2 PM PT)
|
||||
- Must verify server capacity for traffic spike
|
||||
|
||||
⚠️ **Reddit Account Verification** (HIGH)
|
||||
- Need to verify account age (30+ days) and karma (100+)
|
||||
- Alternative: Use team member's established account
|
||||
|
||||
⚠️ **Analytics Implementation** (HIGH)
|
||||
- UTM tracking setup needed
|
||||
- GA4 conversion events configuration
|
||||
- Real-time dashboard creation
|
||||
|
||||
### Child Issues Identified
|
||||
|
||||
See `/plans/FRE-633-reddit-child-issues.md` for full delegation plan:
|
||||
|
||||
1. **Launch Date Coordination** - Owner: CMO, Due: ASAP ⚠️ CRITICAL BLOCKER
|
||||
2. **Reddit Account Verification** - Owner: CMO, Due: T-7 days
|
||||
3. **Analytics & UTM Setup** - Owner: CMO+CTO, Due: T-3 days
|
||||
4. **Visual Assets Creation** - Owner: Design, Due: T-5 days
|
||||
5. **Community Engagement Prep** - Owner: CMO, Due: T-2 days
|
||||
|
||||
### Next Steps
|
||||
|
||||
1. **IMMEDIATE:** CTO confirms launch date (blocks all execution)
|
||||
2. Create child issues in Paperclip for parallel work streams
|
||||
3. Execute pre-AMA checklist starting T-7 days
|
||||
4. Launch AMA on confirmed date (10:00 PT)
|
||||
|
||||
### Files Created
|
||||
|
||||
- `/plans/reddit-ama-execution-plan.md` (194 lines)
|
||||
- `/plans/FRE-633-reddit-ama-checklist.md` (163 lines)
|
||||
- `/plans/FRE-633-reddit-analytics-setup.md` (250+ lines)
|
||||
- `/plans/FRE-633-reddit-child-issues.md` (delegation plan)
|
||||
- `/plans/reddit-post-scripter-launch.md` (existing, 155 lines)
|
||||
|
||||
### Budget
|
||||
|
||||
$0 (organic Reddit post, no paid promotion)
|
||||
|
||||
---
|
||||
|
||||
## FRE-632: Hacker News Show HN Submission
|
||||
|
||||
**Started:** 2026-04-26 10:45 AM
|
||||
**Status:** In Progress
|
||||
**Priority:** High
|
||||
|
||||
### Summary
|
||||
|
||||
Assigned HN Show HN submission task. Creating comprehensive submission strategy for Hacker News audience.
|
||||
|
||||
### Actions Taken
|
||||
|
||||
1. **Created HN submission plan:**
|
||||
- `/home/mike/code/FrenoCorp/plans/hacker-news-showhn-submission.md`
|
||||
- Submission timing: 10:30 AM PT, Tuesday-Thursday best
|
||||
- Recommended title: "Show HN: Scripter – A modern screenwriting app built with Tauri + SolidJS"
|
||||
- Full post draft highlighting technical stack and differentiators
|
||||
- 8+ comment response templates for common HN questions
|
||||
- Success metrics: 300+ points, 100+ comments, 500+ signups
|
||||
|
||||
2. **Strategy highlights:**
|
||||
- Lead with technical depth (HN values authenticity over marketing)
|
||||
- Emphasize stack: Tauri, SolidJS, Turso, CRDT for real-time sync
|
||||
- Founding Engineer should standby for technical Q&A
|
||||
- Coordinate with other launch activities (PH, Reddit, Twitter)
|
||||
|
||||
### Current Blockers
|
||||
|
||||
- **Submission date TBD** - Need to coordinate with launch week schedule
|
||||
- **HN account readiness** - Need to verify if we have aged account with karma
|
||||
|
||||
### Next Steps
|
||||
|
||||
1. Get user input on submission date (launch day vs. staggered)
|
||||
2. Verify HN account readiness
|
||||
3. Review post draft with Founding Engineer
|
||||
4. Scale infrastructure for traffic spike
|
||||
5. Submit at 10:30 AM PT on confirmed date
|
||||
|
||||
### Files Created
|
||||
|
||||
- `/home/mike/code/FrenoCorp/plans/hacker-news-showhn-submission.md` - Complete HN submission strategy (13KB, 418 lines)
|
||||
- `/home/mike/code/FrenoCorp/plans/FRE-632-hn-submission-checklist.md` - Execution checklist (15+ actionable items)
|
||||
|
||||
### Status Update
|
||||
- Plan document complete and ready for execution
|
||||
- Checklist created with pre-submission, launch day, and follow-up tasks
|
||||
- Awaiting user input on: (1) submission date, (2) HN account readiness
|
||||
- Founding Engineer briefed on technical Q&A support role
|
||||
- Can begin preparatory work (tech review, UTM setup) while awaiting date confirmation
|
||||
|
||||
---
|
||||
|
||||
## FRE-635 Continuation - 10:16 AM
|
||||
|
||||
### Actions Taken
|
||||
1. Created comprehensive visual assets brief: `/marketing/product-hunt-assets-brief.md`
|
||||
- Full specs for thumbnail, screenshots, GIFs, maker video
|
||||
- Production checklist and tool recommendations
|
||||
- File organization structure
|
||||
|
||||
2. Added comments to child issues:
|
||||
- FRE-642: Briefed with full asset specs, noted tooling limitation
|
||||
- Documented that design tool (Figma/Canva) needed for thumbnail
|
||||
|
||||
3. Updated FRE-635 with blocker status:
|
||||
- Thumbnail: Blocked on design tool access
|
||||
- Screenshots/GIFs: Blocked on product stability (CTO)
|
||||
- Supporter list: Blocked on waitlist data access (CTO/Ops)
|
||||
- PH submission: Blocked on launch date (CTO)
|
||||
|
||||
### Blockers Summary
|
||||
|
||||
| Blocker | Owner | Impact |
|
||||
|---------|-------|--------|
|
||||
| Design tool access | CMO/Ops | Cannot create thumbnail |
|
||||
| Product stability | CTO | Cannot capture screenshots/GIFs |
|
||||
| Waitlist data | CTO/Ops | Cannot start supporter recruitment |
|
||||
| Launch date | CTO | Cannot submit PH page |
|
||||
|
||||
### Can Proceed Without Blockers
|
||||
- Write maker video script (outline exists in brief)
|
||||
- Set up Figma/Canva account for design work
|
||||
- Research Fiverr designers for outsourcing ($200-400 for full asset package)
|
||||
|
||||
### Next Heartbeat Actions
|
||||
1. Get design tool access decision (Figma vs Canva vs outsource)
|
||||
2. Follow up with CTO on launch date and product stability timeline
|
||||
3. Start maker video script writing
|
||||
4. Begin Figma thumbnail design (if tool access granted)
|
||||
Reference in New Issue
Block a user