@jairodri/huckleberry-cli 1.0.1 → 1.1.0

package/skills/launch-strategy/SKILL.md

@@ -0,0 +1,384 @@
+---
+name: launch-strategy
+description: "When the user wants to plan a product launch, feature announcement, release strategy, or go-to-market plan."
+category: growth
+tier: strategy
+reads:
+  - brand/voice-profile.md
+  - brand/positioning.md
+  - brand/audience.md
+writes:
+  - marketing/launch/plan.md
+  - marketing/launch/checklist.md
+triggers:
+  - launch plan
+  - Product Hunt
+  - go-to-market
+  - beta launch
+  - launch checklist
+metadata:
+  version: 1.2.0
+---
+
+# Launch Strategy
+
+You are an expert in product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.
+
+## On Activation
+
+1. Check if `brand/` directory exists in the project root
+2. If it exists, read `brand/voice-profile.md`, `brand/positioning.md`, and `brand/audience.md` for context
+3. Use that context and only ask for information not already covered or specific to this task
+
+### Decision Gate
+
+Before proceeding, determine which skill is appropriate:
+- **This skill (/launch-strategy):** Strategic planning — phased timeline, channel strategy, messaging, positioning. Use when the user needs a PLAN.
+- **/startup-launcher:** Operational execution — submitting to directories, preparing listing assets, launch day ops. Use when the user needs to DO the launch across platforms.
+
+If the user needs operational execution, say: "You need /startup-launcher for platform submissions. This skill builds the strategic plan. Want the plan first, or jump straight to execution?"
+
+---
+
+## Agent Workflow
+
+Follow these phases in order. Do not skip phases.
+
+### Phase 1: Gather Context
+
+Ask these questions (skip any already answered by brand/ files):
+
+1. What are you launching? (New product, major feature, minor update)
+2. What's your current audience size and engagement?
+3. What owned channels do you have? (Email list size, blog traffic, community)
+4. What's your timeline for launch?
+5. Have you launched before? What worked/didn't work?
+6. Are you considering Product Hunt? What's your preparation status?
+
+### Phase 2: Classify the Launch
+
+Based on context, classify:
+
+| Launch Type | Signals | Approach |
+|-------------|---------|----------|
+| New product, no audience | No email list, no social, first launch | Focus on Phase 1-3, borrowed channels, community seeding |
+| New product, existing audience | Has email list or social following | Focus on Phase 3-5, owned channels first |
+| Major feature update | Existing product, significant new capability | Abbreviated timeline, existing user base + expansion |
+| Minor update | Bug fixes, small improvements | Changelog + email segment, skip full campaign |
+
+### Phase 3: Build the Plan
+
+Using the ORB Framework, Five-Phase Approach, and reference files, produce a plan tailored to the classification. Reference:
+- [references/launch-timeline.md](references/launch-timeline.md) for week-by-week timeline
+- [references/launch-checklist.md](references/launch-checklist.md) for the full pre-flight checklist
+
+### Phase 4: Write Deliverables
+
+Write `marketing/launch/plan.md` using this template:
+
+```markdown
+# Launch Plan: [Product/Feature Name]
+
+## Overview
+- **Launch type:** [New product / Major feature / Minor update]
+- **Target date:** [Date]
+- **Audience size:** [Current size]
+- **Primary goal:** [Signups / Revenue / Awareness]
+
+## Positioning
+- **One-line value prop:** [From positioning.md or crafted here]
+- **Launch angle:** [What makes this newsworthy NOW]
+- **Target audience:** [Who, specifically]
+
+## Channel Strategy (ORB)
+
+### Owned Channels
+[List with specific actions and dates]
+
+### Rented Channels
+[List with specific actions and dates]
+
+### Borrowed Channels
+[List with specific targets and outreach plan]
+
+## Timeline
+[Phased timeline using launch-timeline.md reference]
+
+## Success Metrics
+| Metric | Target | Measurement |
+|--------|--------|-------------|
+| [e.g., Day-1 signups] | [number] | [tool/method] |
+
+## If Launch Stalls
+[Contingency plan with specific triggers and responses]
+```
+
+Write `marketing/launch/checklist.md` as a tailored subset of the reference checklist, including only items relevant to this specific launch.
+
+### Phase 5: Handoff
+
+Tell the user: "Launch plan written to `marketing/launch/`. Here's the summary: [2-3 sentences]. Suggested next steps: [specific skills]."
+
+Recommend related skills based on gaps:
+- No email sequences? → /email-sequences
+- Landing page needs work? → /page-cro
+- Need comparison pages? → /competitor-alternatives
+- Need psychology for waitlists/exclusivity? → /marketing-psychology
+- Ready to submit to directories? → /startup-launcher
+
+---
+
+## Core Philosophy
+
+The best companies don't just launch once -- they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.
+
+A strong launch isn't about a single moment. It's about:
+- Getting your product into users' hands early
+- Learning from real feedback
+- Making a splash at every stage
+- Building momentum that compounds over time
+
+---
+
+## The ORB Framework
+
+Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.
+
+### Owned Channels
+You own the channel (though not the audience). Direct access without algorithms or platform rules.
+
+**Examples:**
+- Email list
+- Blog
+- Podcast
+- Branded community (Slack, Discord)
+- Website/product
+
+**Why they matter:**
+- Get more effective over time
+- No algorithm changes or pay-to-play
+- Direct relationship with audience
+- Compound value from content
+
+**Start with 1-2 based on audience:**
+- Industry lacks quality content -> Start a blog
+- People want direct updates -> Focus on email
+- Engagement matters -> Build a community
+
+**Example - Superhuman:**
+Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth -- all through owned relationships.
+
+### Rented Channels
+Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.
+
+**Examples:**
+- Social media (Twitter/X, LinkedIn, Instagram)
+- App stores and marketplaces
+- YouTube
+- Reddit
+
+**How to use correctly:**
+- Pick 1-2 platforms where your audience is active
+- Use them to drive traffic to owned channels
+- Don't rely on them as your only strategy
+
+**Platform-specific tactics:**
+- Twitter/X: Threads that spark conversation -> link to newsletter
+- LinkedIn: High-value posts -> lead to gated content or email signup
+- Marketplaces (Shopify, Slack): Optimize listing -> drive to site for more
+
+Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.
+
+### Borrowed Channels
+Tap into someone else's audience to shortcut the hardest part -- getting noticed.
+
+**Examples:**
+- Guest content (blog posts, podcast interviews, newsletter features)
+- Collaborations (webinars, co-marketing, social takeovers)
+- Speaking engagements (conferences, panels, virtual summits)
+- Influencer partnerships
+
+**Be proactive, not passive:**
+1. List industry leaders your audience follows
+2. Pitch win-win collaborations
+3. Use Exa MCP or firecrawl to find audience overlap
+4. Set up affiliate/referral incentives
+
+Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.
+
+### ORB Prioritization Matrix
+
+| Audience Size | Focus | Why |
+|---|---|---|
+| < 1,000 | Owned channels only (blog, email list) | Build foundation before spending on reach |
+| 1K - 10K | Owned + Rented (social, SEO, ads) | Enough audience to test paid channels |
+| 10K+ | All three: Owned + Rented + Borrowed (partnerships, press) | Use existing reach for maximum amplification |
+
+---
+
+## Five-Phase Launch Approach
+
+### Phase 1: Internal Launch
+Gather initial feedback and iron out major issues before going public.
+
+**Actions:**
+- Recruit early users one-on-one to test for free
+- Collect feedback on usability gaps and missing features
+- Ensure prototype is functional enough to demo
+
+**Goal:** Validate core functionality with friendly users.
+
+### Phase 2: Alpha Launch
+Put the product in front of external users in a controlled way.
+
+**Actions:**
+- Create landing page with early access signup form
+- Announce the product exists
+- Invite users individually to start testing
+- MVP should be working in production
+
+**Goal:** First external validation and initial waitlist building.
+
+### Phase 3: Beta Launch
+Scale up early access while generating external buzz.
+
+**Actions:**
+- Work through early access list (some free, some paid)
+- Start marketing with teasers about problems you solve
+- Recruit friends, investors, and influencers to test and share
+
+**Consider adding:**
+- Coming soon landing page or waitlist
+- "Beta" sticker in dashboard navigation
+- Email invites to early access list (use gws for sending)
+- Early access toggle in settings for experimental features
+
+**Goal:** Build buzz and refine product with broader feedback.
+
+### Phase 4: Early Access Launch
+Shift from small-scale testing to controlled expansion.
+
+**Actions:**
+- Leak product details: screenshots, feature GIFs, demos
+- Gather quantitative usage data and qualitative feedback
+- Run user research with engaged users (incentivize with credits)
+- Optionally run product/market fit survey to refine messaging
+
+**Expansion options:**
+- Option A: Throttle invites in batches (5-10% at a time)
+- Option B: Invite all users at once under "early access" framing
+
+**Goal:** Validate at scale and prepare for full launch.
+
+### Phase 5: Full Launch
+Open the floodgates.
+
+**Actions:**
+- Open self-serve signups
+- Start charging (if not already)
+- Announce general availability across all channels
+
+**Launch touchpoints:**
+- Customer emails (use gws for sending)
+- In-app popups and product tours
+- Website banner linking to launch assets
+- "New" sticker in dashboard navigation
+- Blog post announcement
+- Social posts across platforms (use ply for posting)
+- Product Hunt, BetaList, Hacker News, etc.
+
+**Goal:** Maximum visibility and conversion to paying users.
+
+### Timeline Guidance
+
+| Phase | Duration | Signal to Advance |
+|---|---|---|
+| Internal Alpha | 2-4 weeks | Core flow works, <10 users giving feedback |
+| Beta | 4-8 weeks | 50-500 users, NPS > 30, key bugs fixed |
+| Early Access | 2-4 weeks | Growing waitlist, retention metrics stable |
+| Full Launch | 1 week intense + ongoing | All channels activated, monitoring metrics |
+
+---
+
+## Product Hunt Launch Strategy
+
+### How to Launch Successfully
+
+**Before launch day:**
+1. Build relationships with influential supporters, content hubs, and communities
+2. Optimize your listing: compelling tagline, polished visuals, short demo video
+3. Study successful launches to identify what worked
+4. Engage in relevant communities -- provide value before pitching
+5. Prepare your team for all-day engagement
+
+**On launch day:**
+1. Treat it as an all-day event
+2. Respond to every comment in real-time
+3. Answer questions and spark discussions
+4. Encourage your existing audience to engage
+5. Direct traffic back to your site to capture signups
+
+**After launch day:**
+1. Follow up with everyone who engaged
+2. Convert Product Hunt traffic into owned relationships (email signups)
+3. Continue momentum with post-launch content
+
+---
+
+## Post-Launch Product Marketing
+
+### Immediate Post-Launch Actions
+
+**Educate new users:**
+Set up automated onboarding email sequence introducing key features and use cases (use gws for email automation).
+
+**Reinforce the launch:**
+Include announcement in your weekly/biweekly/monthly roundup email to catch people who missed it.
+
+**Differentiate against competitors:**
+Publish comparison pages highlighting why you're the obvious choice.
+
+**Update web pages:**
+Add dedicated sections about the new feature/product across your site.
+
+---
+
+## Ongoing Launch Strategy
+
+### How to Prioritize What to Announce
+
+**Major updates** (new features, product overhauls):
+- Full campaign across multiple channels
+- Blog post, email campaign, in-app messages, social media
+- Maximize exposure
+
+**Medium updates** (new integrations, UI enhancements):
+- Targeted announcement
+- Email to relevant segments, in-app banner
+
+**Minor updates** (bug fixes, small tweaks):
+- Changelog and release notes
+- Signal that product is improving
+
+---
+
+## Anti-Patterns
+
+| Anti-pattern | Why it fails | Instead |
+|-------------|-------------|---------|
+| Producing a 5-page plan when user needs a quick checklist | Minor updates don't warrant full campaigns — overwrought plans get ignored | Ask the launch type first — minor updates get a checklist, not a strategy doc |
+| Running this skill when user needs operational platform submissions | This skill produces plans, not actions — the user will get frustrated waiting for a strategy when they need directory submissions done | Route to /startup-launcher for directory submissions and launch day ops |
+| Recommending all ORB channels regardless of audience size | A <1K audience spreading across 6 channels dilutes effort to zero — focus compounds, scatter doesn't | Use the prioritization matrix — <1K audience should focus on owned only |
+| Writing a plan without asking key context questions first | A plan built on assumptions wastes the user's time and produces generic advice | Always gather context in Phase 1, even if brand/ files exist |
+| Ignoring existing brand/ context and asking everything fresh | Asking questions already answered in brand/ files annoys users who've invested in brand memory | Read brand files first, only ask what's missing or launch-specific |
+| Creating a generic timeline not adapted to launch type | A solo founder doesn't need an 8-week timeline, and a funded team shouldn't compress to 2 weeks | Classify the launch in Phase 2, then adapt timeline from references |
+
+---
+
+## Related Skills
+
+- **email-sequences**: For launch and onboarding email sequences
+- **page-cro**: For optimizing launch landing pages
+- **marketing-psychology**: For psychology behind waitlists and exclusivity
+- **competitor-alternatives**: For comparison pages mentioned in post-launch
+- **startup-launcher**: For operational multi-platform launch execution

package/skills/launch-strategy/evals/evals.json

@@ -0,0 +1,91 @@
+{
+  "skill_name": "launch-strategy",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "We're launching a new B2B SaaS product for design teams in 6 weeks. It's a design review tool. We have a small audience (500 email subscribers, 2k Twitter followers). Help us plan the launch.",
+      "expected_output": "Should check for product-marketing-context.md first. Should apply the ORB Framework (Owned, Rented, Borrowed channels) with the user's specific resources. Owned: email list (500 subscribers), website. Rented: Twitter (2k followers). Borrowed: partnerships, communities, Product Hunt. Should recommend the five-phase launch approach with a timeline mapped to the 6-week window: Internal prep, Alpha (existing network), Beta (expanded), Early Access, Full Launch. Should provide specific tactics for each phase. Should recommend building up the audience before launch day. Should include a launch day checklist.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Applies ORB Framework (Owned, Rented, Borrowed)",
+        "Maps to user's specific channels and audience sizes",
+        "Recommends five-phase launch approach",
+        "Provides timeline mapped to 6-week window",
+        "Provides specific tactics for each phase",
+        "Recommends audience building before launch",
+        "Includes launch day checklist"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "We want to launch on Product Hunt. Any tips? We've never done it before.",
+      "expected_output": "Should apply the Product Hunt strategy section. Should cover: choosing the right day and time, preparing assets (logo, gallery images, maker video), crafting the tagline and description, building a hunter network, activating supporters on launch day, engaging with comments, and post-launch follow-up. Should recommend preparation timeline (start 2-4 weeks before). Should mention common mistakes to avoid. Should set realistic expectations about outcomes.",
+      "assertions": [
+        "Applies Product Hunt strategy section",
+        "Covers timing (day and time selection)",
+        "Covers asset preparation",
+        "Addresses hunter network and supporter activation",
+        "Recommends preparation timeline",
+        "Mentions common mistakes to avoid",
+        "Sets realistic expectations"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "we just shipped a major feature update. how should we announce it? it's not a full product launch, just a big new feature.",
+      "expected_output": "Should trigger on casual phrasing. Should apply the ongoing launch strategy section, specifically the major/medium/minor update matrix. Should identify this as a major feature update. Should recommend appropriate channels and tactics for a feature launch (less than a full product launch but more than a changelog entry). Should include: announcement email, blog post, social media push, in-app notification, and possibly a mini Product Hunt launch. Should provide a feature announcement framework.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies ongoing launch strategy / update matrix",
+        "Identifies as major feature update",
+        "Scales tactics appropriately (not full launch)",
+        "Recommends announcement channels",
+        "Includes email, blog, social, and in-app notification",
+        "Provides feature announcement framework"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Our launch flopped. We launched 3 weeks ago and only got 50 signups. We expected at least 500. What went wrong and what can we do now?",
+      "expected_output": "Should apply the post-launch product marketing section. Should diagnose potential failure causes: insufficient audience building pre-launch, wrong channels, weak value proposition messaging, poor launch execution, targeting the wrong audience. Should recommend post-launch recovery tactics: iterate on messaging, identify which channels produced the 50 signups and double down, try new distribution channels, leverage early users for testimonials. Should provide a specific 30-day recovery plan.",
+      "assertions": [
+        "Applies post-launch product marketing guidance",
+        "Diagnoses potential failure causes",
+        "Addresses pre-launch audience building gap",
+        "Recommends post-launch recovery tactics",
+        "Suggests analyzing which channels produced signups",
+        "Provides specific recovery plan"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "How do we leverage partnerships and borrowed audiences for our launch? We don't have a big audience of our own.",
+      "expected_output": "Should focus on the Borrowed channel from the ORB Framework. Should provide specific borrowed audience tactics: podcast guest appearances, co-marketing with complementary tools, influencer partnerships, community engagement (relevant Slack groups, Discord servers, Reddit), guest posts, cross-promotions. Should recommend how to identify and approach potential partners. Should note that borrowed audience strategies take time to build and should start well before launch day.",
+      "assertions": [
+        "Focuses on Borrowed channel from ORB Framework",
+        "Provides specific borrowed audience tactics",
+        "Mentions partnerships, communities, guest content",
+        "Recommends how to identify and approach partners",
+        "Notes borrowed strategies take time to build",
+        "Suggests starting well before launch day"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Give me some creative marketing ideas to promote our product. We're bootstrapped and don't have a big budget.",
+      "expected_output": "Should recognize this is a broader marketing ideas request, not specifically a launch strategy task. Should defer to or cross-reference the marketing-ideas skill, which provides 139 marketing ideas organized by category and filtered by budget. May provide some launch-related tactical ideas but should make clear that marketing-ideas is the right skill for a broader brainstorming session.",
+      "assertions": [
+        "Recognizes this as broader marketing ideas request",
+        "References or defers to marketing-ideas skill",
+        "Does not attempt full marketing brainstorm using launch strategy patterns",
+        "May provide some launch-related tactical ideas"
+      ],
+      "files": []
+    }
+  ]
+}

package/skills/launch-strategy/references/launch-checklist.md

@@ -0,0 +1,209 @@
+# Launch Checklist
+
+Comprehensive pre-flight checklist organized by category. Work through each section before, during, and after launch. Items are ordered by priority within each section.
+
+---
+
+## Positioning & Messaging
+
+- [ ] One-sentence value proposition written and tested with 3+ people
+- [ ] Launch angle defined — what makes this newsworthy NOW (not just "we built a thing")
+- [ ] Target audience clearly defined — who this is for and who it is NOT for
+- [ ] Key differentiator articulated — why this over alternatives
+- [ ] Pricing decided and justified (if applicable)
+- [ ] Objection responses prepared for top 3-5 likely pushbacks
+- [ ] Tagline/headline A/B variants ready for testing
+- [ ] "Elevator pitch" version ready: 15 seconds, 60 seconds, 5 minutes
+
+---
+
+## Landing Page & Website
+
+- [ ] Landing page live with clear headline, subheadline, and CTA
+- [ ] Above-the-fold hook communicates value in under 5 seconds
+- [ ] Social proof present: testimonials, logos, user counts, or results
+- [ ] Email capture or signup form working end-to-end
+- [ ] Mobile responsive — tested on actual devices, not just browser resize
+- [ ] Page load under 3 seconds (test with PageSpeed Insights)
+- [ ] Open Graph and Twitter Card meta tags set for link sharing
+- [ ] Favicon and brand assets in place
+- [ ] 404 page customized (people will mistype URLs)
+- [ ] Legal pages present if needed: terms, privacy, cookie policy
+
+---
+
+## Content & Creative Assets
+
+### Written Content
+- [ ] Launch blog post written: problem → solution → proof → CTA
+- [ ] Press release or media kit prepared (if doing PR outreach)
+- [ ] FAQ document covering top 10 anticipated questions
+- [ ] Comparison page drafted (vs top 1-2 competitors)
+- [ ] Product documentation or help center seeded with basics
+
+### Visual Assets
+- [ ] Product screenshots (clean, annotated, showing key features)
+- [ ] Demo video or product walkthrough (60-90 seconds)
+- [ ] Social media graphics: announcement, feature highlights, quote cards
+- [ ] Feature GIFs for social sharing and Product Hunt
+- [ ] Logo files in multiple formats (PNG, SVG, dark/light variants)
+
+### Social Content
+- [ ] Launch day posts drafted for each active platform
+- [ ] Thread/carousel version for long-form social (Twitter thread, LinkedIn carousel)
+- [ ] Community posts drafted (Reddit, Indie Hackers, relevant Slack/Discord groups)
+- [ ] Reply templates for common questions and congratulatory messages
+
+---
+
+## Email
+
+- [ ] Email list segmented: power users, new subscribers, VIPs, lapsed
+- [ ] Pre-launch tease email drafted (send 3-7 days before)
+- [ ] Launch announcement email drafted with clear CTA
+- [ ] Follow-up email for non-openers (different subject line)
+- [ ] Onboarding email sequence ready (3-5 emails over first 2 weeks)
+- [ ] Transactional emails tested: welcome, confirmation, receipt
+- [ ] Unsubscribe link present and working
+- [ ] Email preview tested across clients (Gmail, Apple Mail, Outlook)
+- [ ] Sender domain authenticated (SPF, DKIM, DMARC)
+
+---
+
+## Distribution Channels
+
+### Owned Channels
+- [ ] Blog post scheduled for launch day
+- [ ] Email blast scheduled for launch morning
+- [ ] In-app announcement prepared (banner, modal, or tooltip)
+- [ ] Website banner or notification bar ready to activate
+- [ ] Changelog or release notes updated
+- [ ] Community/forum post drafted (if you have a branded community)
+
+### Rented Channels
+- [ ] Social profiles updated with launch messaging
+- [ ] Posts scheduled across platforms with appropriate timing
+- [ ] Product Hunt listing complete: tagline, description, media, first comment
+- [ ] Directory submissions prepared (BetaList, AlternativeTo, etc.)
+- [ ] App store listing updated (if applicable)
+
+### Borrowed Channels
+- [ ] Influencer/creator outreach sent with clear ask and easy-share assets
+- [ ] Guest post or newsletter feature confirmed with publication date
+- [ ] Podcast appearance scheduled (if applicable)
+- [ ] Cross-promotion partners briefed with share templates
+- [ ] Affiliate/referral incentives communicated to partners
+
+---
+
+## Analytics & Tracking
+
+- [ ] Analytics installed and verified (page views, events firing correctly)
+- [ ] UTM parameter convention defined and documented
+- [ ] Conversion goals configured: signup, activation, purchase
+- [ ] Funnel tracking set up: visit → signup → activate → convert
+- [ ] Referral source tracking working ("How did you hear about us?")
+- [ ] Retargeting pixel installed (for post-launch ad campaigns)
+- [ ] Real-time dashboard ready for launch day monitoring
+- [ ] Baseline metrics recorded (pre-launch numbers for comparison)
+- [ ] Error monitoring active (catch crashes before users report them)
+
+---
+
+## Technical Readiness
+
+- [ ] Production deployment tested — full user journey works end-to-end
+- [ ] Load testing done if expecting significant traffic
+- [ ] CDN configured for static assets and media
+- [ ] SSL certificate valid and not expiring soon
+- [ ] Database backups running and verified
+- [ ] Error alerting configured (PagerDuty, Sentry, etc.)
+- [ ] Rollback plan documented in case of critical issues
+- [ ] Rate limiting in place for signup/API endpoints
+- [ ] Staging environment matches production
+
+---
+
+## Support & Operations
+
+- [ ] Support team briefed on new product/feature and common questions
+- [ ] FAQ or help docs published and linked from product
+- [ ] Support channels ready: email, chat, or ticket system
+- [ ] Escalation path defined for critical issues on launch day
+- [ ] Response time expectations set (aim for <1 hour on launch day)
+- [ ] Feedback collection mechanism in place (survey, feedback widget, email)
+
+---
+
+## Team Coordination
+
+- [ ] Launch day schedule shared — who does what, when
+- [ ] Social media monitoring assignments clear
+- [ ] Real-time communication channel set up (Slack channel, group chat)
+- [ ] Decision-maker available all day for urgent calls
+- [ ] Post-launch debrief scheduled (within 48 hours)
+- [ ] Success metrics defined — what does a "successful" launch look like?
+
+---
+
+## Launch Day Protocol
+
+### Morning (Launch Hour)
+1. Verify landing page, signup flow, and checkout working
+2. Publish blog post
+3. Send announcement email
+4. Post on all social channels
+5. Submit to Product Hunt / directories
+6. Activate in-app announcements
+7. Notify partners to share
+
+### Throughout the Day
+8. Monitor social mentions and respond to every comment
+9. Watch analytics dashboard for conversion and error rates
+10. Engage in community discussions
+11. Share early traction updates with team and supporters
+12. Address any technical issues immediately
+
+### End of Day
+13. Send thank-you messages to top engagers
+14. Compile day-1 metrics snapshot
+15. Identify top-performing channels
+16. Queue follow-up content for day 2
+
+---
+
+## Post-Launch (First 72 Hours)
+
+- [ ] Day-1 metrics reviewed and shared with team
+- [ ] Follow-up email sent to non-openers
+- [ ] User feedback collected and categorized
+- [ ] Top-performing channels identified for doubling down
+- [ ] Critical bugs or UX issues from feedback addressed
+- [ ] "Launch results" content published (transparency builds trust)
+- [ ] Thank-you messages sent to partners and supporters
+- [ ] Retargeting campaigns activated for landing page visitors
+- [ ] Onboarding sequence verified — new users receiving emails
+
+---
+
+## Post-Launch (Week 1-2)
+
+- [ ] Post-signup survey analyzed: acquisition channels, objections, satisfaction
+- [ ] Case study drafted from best early adopter story
+- [ ] Comparison and alternative pages published
+- [ ] Content repurposing started: blog → threads → short video → newsletter
+- [ ] Referral or sharing mechanism added to product
+- [ ] Channel-level CAC calculated — where to invest next
+- [ ] Next launch moment planned (feature update, milestone, re-launch)
+
+---
+
+## If Launch Underperforms
+
+| Symptom | Likely Cause | Fix |
+|---|---|---|
+| High traffic, low signups | Weak landing page or unclear value prop | A/B test headline, add social proof, simplify form |
+| Low traffic overall | Distribution channels not activated | Push harder on borrowed channels, try paid ads |
+| Signups but no activation | Onboarding friction or unclear first step | Simplify first-run experience, add welcome email |
+| Good activation, quick churn | Product gap or wrong audience | Survey churned users, revisit positioning |
+| No social engagement | Wrong platform or weak content | Test different formats, post at different times |