Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getcore.me/llms.txt

Use this file to discover all available pages before exploring further.

Goal: Plan launches that build momentum, capture attention, and convert interest into users.

Tools Required

This skill runs using CORE memory only. No integrations required.

Trigger

Run on demand when the user wants to plan a launch or feature announcement.

Setup

Search memory for:
  • “What’s being launched?”
  • “Who’s the target audience?”
  • “What channels are you using?”
  • “Have you launched before?”
If nothing found, ask once:
“What are you launching? (1) Is this a new product, major feature, or minor update? (2) Who’s the primary audience? (3) What channels do you have? (Email list size? Blog traffic? Social following?)”
Store the response in memory. Do not ask again in future runs.

Step 1: Assess Your Launch Type and Resources

Determine what you’re launching:
  • New product → Full five-phase launch
  • Major feature → Extended announcement across channels
  • Minor update → Changelog + targeted announcement
Identify your channel resources:
  • Owned: Email list, blog, product, community
  • Rented: Social media, marketplaces, app stores
  • Borrowed: Press, influencers, partnerships
Strongest launches start with owned channels. Focus on building 1-2 owned channels first.

Step 2: Plan the Five-Phase Launch

Phase 1: Internal Launch

  • Recruit early users to test for free
  • Collect usability feedback
  • Iron out major issues
  • Goal: Validate core functionality with friendly users

Phase 2: Alpha Launch

  • Create landing page with early access signup
  • Announce the product exists
  • Invite users individually to testing
  • Goal: First external validation and initial waitlist

Phase 3: Beta Launch

  • Scale up early access
  • Start marketing with teasers
  • Recruit friends, investors, influencers to test and share
  • Goal: Build buzz and refine with broader feedback

Phase 4: Early Access Launch

  • Leak product details: screenshots, GIFs, demos
  • Run user research
  • Expand access in batches or open to all under “early access” label
  • Goal: Validate at scale and prepare for full launch

Phase 5: Full Launch

  • Open self-serve signups
  • Start charging (if applicable)
  • Announce across all channels
  • Goal: Maximum visibility and conversion

Step 3: Build Your Launch Moment

Use the ORB framework: Owned Channels — Email list, blog, product, community
  • Most effective over time
  • Direct relationship with audience
  • Build 1-2 before relying on others
Rented Channels — Social media, YouTube, Reddit, marketplaces
  • Gives speed but not stability
  • Use to drive traffic back to owned channels
  • Don’t rely as sole strategy
Borrowed Channels — Guest posts, podcast interviews, influencers, speaking
  • Taps into existing audiences
  • Requires proactive outreach and win-win pitches
  • Highest credibility but limited control

Step 4: Product Hunt (If Using)

If launching on Product Hunt: Before launch day:
  • Optimize listing with compelling tagline and visuals
  • Build relationships with potential upvoters
  • Create demo video
  • Engage in communities first (add value before asking)
On launch day:
  • Treat as all-day engagement event
  • Respond to every comment in real-time
  • Spark discussions
  • Direct traffic back to your site to capture signups
After launch day:
  • Follow up with engaged users
  • Convert Product Hunt traffic to owned relationships
  • Continue momentum with post-launch content

Step 5: Post-Launch Actions

Immediate:
  • Onboarding email sequence for new users
  • Feature education on what’s new
  • Competitor comparison pages
  • In-app announcements for existing users
Sustained:
  • Weekly/biweekly roundup mentioning the launch
  • Case studies from early users
  • Updates signaling active development
  • Plan next launch moment

Step 6: Define Launch Channels and Messaging

Document your launch plan:
ChannelWhatWhenOwner
EmailLaunch announcementDay 1Marketing
BlogFeature postDay 1Content
In-appNotificationDay 1Product
SocialPosts + threadDays 1-7Social
Product HuntListingDay 1CEO
Ensure message consistency across channels while adapting format to each platform.

Output Format


Launch Strategy — [Product/Feature Name] What’s Launching
  • Type: [New product / Major feature / Minor update]
  • Target audience: [Primary persona]
  • Launch date: [Planned date]
Five-Phase Timeline
  • Phase 1 (Internal): [Dates and goals]
  • Phase 2 (Alpha): [Dates and goals]
  • Phase 3 (Beta): [Dates and goals]
  • Phase 4 (Early Access): [Dates and goals]
  • Phase 5 (Full Launch): [Dates and goals]
ORB Channel Plan
  • Owned: [Email, blog, community — sizes and strategy]
  • Rented: [Social, marketplaces — audience and tactics]
  • Borrowed: [Influencers, partners — outreach plan]
Product Hunt Plan (If Using)
  • Preparation: [Timeline and tasks]
  • Launch day: [Team roles and schedule]
  • Post-launch: [Follow-up sequence]
Launch Day Checklist
  • Announcement email sent
  • Blog post published
  • Social posts scheduled
  • In-app notification live
  • Product Hunt listing live (if using)
  • Team ready to engage
  • Analytics tracking configured
Post-Launch Plan
  • Onboarding email sequence: [Timeline]
  • Feature comparison pages: [Topics]
  • Update frequency: [Blog, changelog, email]

Edge Cases

  • Small email list (< 1K): Focus on owned channels with high engagement; build list before relying on email
  • No existing community: Borrow audience first through partnerships; build owned audience in parallel
  • B2B with long sales cycle: Early access phase extends longer; nurture with education, not sales
  • Marketplace/platform limitation: Product Hunt and BetaList matter more; coordinate timing
  • Competitive category: Differentiation in messaging critical; show why you’re different, not just new
  • Launch is actually a re-launch: Communicate improvement narrative; highlight what changed and why