skills/marketing/launch-plan/SKILL.md
Use this skill when the user says 'launch plan', 'product launch', 'go-to-market', 'launch calendar', or needs a day-by-day launch timeline with pre-launch, launch week, and post-launch task checklists. Do NOT use for ongoing funnel design or ad copy alone.
npx skillsauth add cwinvestments/memstack memstack-marketing-launch-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Develops a day-by-day launch timeline with pre-launch buildup, launch week execution, post-launch optimization, channel strategy, PR outreach templates, and metrics tracking.
When this skill activates, output:
Launch Plan — Planning product launch...
Then execute the protocol below.
| Context | Status | |---------|--------| | User says "launch plan", "product launch", "go-to-market" | ACTIVE | | User says "launch calendar" or "launch timeline" | ACTIVE | | User is preparing to release a new product or feature | ACTIVE | | User wants an ongoing sales funnel (not time-bound) | DORMANT — use Sales Funnel | | User wants ad copy only | DORMANT — use Facebook Ad or Google Ad |
| Mistake | Why It's Wrong | |---------|---------------| | "Launch day IS the marketing plan" | 80% of launch success happens in the pre-launch phase. The launch day is execution, not strategy. | | "Tell everyone at once" | Tiered reveals (insiders → waitlist → public) create momentum and social proof. | | "No deadline on the launch offer" | Open-ended launches have no urgency. Set a clear close date for the launch price/bonus. | | "Skip the waitlist" | A waitlist of 500+ people means launch day revenue, not crickets. | | "Go dark after launch day" | Post-launch follow-up (days 2-7) often generates more revenue than day 1. |
If the user hasn't provided details, ask:
- Product/service — what are you launching? (name, description, price)
- Launch date — when does it go live?
- Audience size — email list, social followers, existing customers?
- Launch type — new product, major update, beta → GA, or seasonal promotion?
- Channels — email, social, ads, PR, partnerships, affiliates?
- Launch offer — special pricing, bonus, or early-bird deal?
| Launch Type | Pre-Launch | Launch Window | Post-Launch | |------------|-----------|--------------|-------------| | Product Hunt launch | 2-4 weeks | 1 day | 1 week | | SaaS launch | 4-6 weeks | 1 week | 2-4 weeks | | Course/info product | 2-4 weeks | 3-5 days (open cart) | 1 week | | E-commerce product | 2-3 weeks | 1-2 weeks | Ongoing | | Feature launch | 1-2 weeks | 1-3 days | 1 week |
Week 4-3: Foundation
| Day | Task | Channel | Owner | |-----|------|---------|-------| | T-28 | Finalize launch offer (pricing, bonuses, deadline) | Internal | Product | | T-27 | Create landing page with waitlist signup | Web | Marketing | | T-26 | Set up email sequences (pre-launch + launch) | Email | Marketing | | T-25 | Prepare PR/media list (50+ relevant contacts) | PR | Marketing | | T-24 | Create social content calendar (14 posts minimum) | Social | Content | | T-23 | Record demo video or product walkthrough | Video | Product | | T-22 | Brief affiliates/partners with swipe copy | Partners | Marketing |
Week 2-1: Build Anticipation
| Day | Task | Channel | Owner | |-----|------|---------|-------| | T-14 | Send teaser email #1 — "Something's coming" | Email | Marketing | | T-12 | Behind-the-scenes social post (product development) | Social | Content | | T-10 | Send PR pitch to media list | PR | Marketing | | T-8 | Teaser email #2 — reveal a feature/benefit | Email | Marketing | | T-7 | Publish blog post related to the problem you solve | Blog | Content | | T-5 | Social proof post (beta user testimonial or preview) | Social | Content | | T-3 | Teaser email #3 — "Launching in 3 days" with preview | Email | Marketing | | T-2 | Notify affiliates/partners: "Go live in 48 hours" | Partners | Marketing | | T-1 | Final prep — test checkout, verify tracking, stage all content | Internal | All |
Pre-launch email sequence:
Email 1 (T-14): [Teaser]
Subject: Something big is coming...
Body: Hint at the problem you're solving. Don't reveal the product yet.
CTA: "Want early access? Join the waitlist"
Email 2 (T-8): [Reveal]
Subject: Here's what we've been building
Body: Show one key feature/benefit. Share the "why" story.
CTA: "Reply and tell me — would this help you?"
Email 3 (T-3): [Countdown]
Subject: 3 days until launch (and a special deal)
Body: Reveal the launch offer. Create urgency with deadline.
CTA: "Mark your calendar — [launch date] at [time]"
Day 1 — Launch Day:
| Time | Task | Channel | |------|------|---------| | 6:00 AM | Activate landing page / checkout | Web | | 7:00 AM | Send launch email to full list | Email | | 8:00 AM | Publish all social posts (feed + stories) | Social | | 9:00 AM | Go live on Product Hunt (if applicable) | PH | | 10:00 AM | Activate paid ads (if planned) | Ads | | 12:00 PM | Share in communities (Reddit, Slack, Discord) | Community | | 3:00 PM | Send affiliate notification — "We're live!" | Partners | | 6:00 PM | Evening social post — first results/reactions | Social | | 9:00 PM | Check metrics: traffic, signups, revenue | Analytics |
Launch email template:
Subject: It's live — [Product Name] is here
Preview: [One-line benefit + launch offer]
[Name],
[Product] is officially live.
[1-2 sentences: what it is and who it's for]
Here's what you get:
→ [Benefit 1]
→ [Benefit 2]
→ [Benefit 3]
Launch special: [Offer details — discount, bonus, early-bird price]
This offer expires [deadline].
[CTA Button: Get [Product] Now →]
[Social proof: "Already [X] people signed up in the first hour"]
[Signature]
P.S. [Restate urgency — "This price goes up on [date]"]
Days 2-5 — Momentum:
| Day | Email | Social | Other | |-----|-------|--------|-------| | Day 2 | Social proof email — first customer results | Share customer reactions | Respond to all comments/questions | | Day 3 | FAQ/objection handling email | Demo video or walkthrough | Track and fix any UX issues | | Day 4 | Case study or deep-dive on one feature | User testimonial post | Re-engage waitlist non-openers | | Day 5 | Scarcity email — "X spots left" or "3 days left" | Countdown post | Activate retargeting ads |
Days 6-7 — Close:
| Day | Email | Social | |-----|-------|--------| | Day 6 | "Last chance" — 24 hours remaining | Urgency stories/posts | | Day 7 | Final email — "Doors close at midnight" (send twice: AM + PM) | "Final hours" post |
| Day | Task | Channel | |-----|------|---------| | Day 8 | "Thank you" email to buyers + what's next | Email | | Day 8 | Analyze launch metrics (see Step 7) | Analytics | | Day 10 | Collect testimonials from early customers | Email | | Day 14 | Publish launch retrospective blog post | Blog | | Day 14 | Send re-engagement offer to non-buyers | Email | | Day 21 | Begin evergreen funnel setup (automated version) | Email + Ads | | Day 30 | Full post-mortem: what worked, what didn't, next launch improvements | Internal |
Media pitch template:
Subject: [Product Name]: [One-line news hook]
Hi [Name],
I'm [Your Name], [title] at [Company].
We just launched [Product Name] — [one sentence: what it does and why it matters].
This is relevant to your audience because:
• [Angle 1: trend, problem, or market shift]
• [Angle 2: unique approach or notable result]
• [Angle 3: human interest or founder story]
Key facts:
• [Stat or metric: waitlist size, beta results, market size]
• [Price point and availability]
• [Notable backers, partners, or early customers]
I'd love to offer you [exclusive early access / a demo / an interview].
Press kit: [link]
Product: [URL]
Best,
[Your Name]
[Contact info]
Outreach targets:
| Metric | Pre-Launch Target | Launch Target | Track With | |--------|------------------|--------------|------------| | Waitlist signups | 500+ | — | Email platform | | Email open rate | 35%+ | 40%+ | Email platform | | Email click rate | 5%+ | 8%+ | Email platform | | Landing page visitors | — | 5,000+ (day 1) | Google Analytics | | Conversion rate | — | 2-5% | Checkout analytics | | Revenue | — | $[target] | Payment processor | | Social mentions | 10+/week | 50+/day | Social monitoring | | Press coverage | — | 3+ articles | Manual tracking | | Customer satisfaction | — | 4.5+ stars | Survey/reviews | | Refund rate | — | <5% | Payment processor |
# Launch Plan — [Product Name]
## Launch Overview
- **Product:** [Name and one-line description]
- **Launch date:** [Date]
- **Launch window:** [X days]
- **Launch offer:** [Special pricing/bonus + deadline]
- **Revenue target:** $[amount]
## Timeline
### Pre-Launch (T-[X] to T-1)
[Day-by-day task table]
### Launch Week (Days 1-7)
[Day-by-day task table with times for Day 1]
### Post-Launch (Days 8-30)
[Task table with milestones]
## Channel Strategy
[Per-channel plan: email, social, ads, PR, partners]
## Email Sequences
[Pre-launch (3 emails) + Launch (7 emails) + Post-launch (3 emails)]
## PR Plan
[Media list categories + pitch template]
## Metrics Dashboard
[Tracking table with targets]
Launch Plan — Complete!
Launch date: [Date]
Pre-launch duration: [X weeks]
Launch window: [X days]
Total emails planned: [Count]
Social posts planned: [Count]
PR targets: [Count]
Next steps:
1. Set up waitlist landing page immediately
2. Build email sequences in your platform
3. Schedule social content calendar
4. Send PR pitches at T-10
5. Brief team on Day 1 timeline
tools
Use when the user says 'save diary', 'log session', 'wrapping up', or at end of a productive session.
tools
Use when the user says 'submit to marketplace', 'publish my skill', 'share this skill', 'list on marketplace', 'submit plugin', 'publish to community', or needs to submit a skill or plugin to a community marketplace via PR. Do NOT use for building skills or writing plugin code.
development
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
development
Use when the user says 'teach me', 'explain as you go', 'mentor mode', 'walk me through', 'help me learn', 'explain why', 'learning mode', or wants real-time plain language narration of decisions and tradeoffs while building. Do NOT use for code review or debugging.