Launch Strategy V3

Launch Strategy

Overview

This public intake copy packages plugins/antigravity-bundle-startup-founder/skills/launch-strategy from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

Launch Strategy You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Core Philosophy, The ORB Framework, Five-Phase Launch Approach, Product Hunt Launch Strategy, Post-Launch Product Marketing, Ongoing Launch Strategy.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• This skill is applicable to execute the workflow or actions described in the overview.
• Use when the request clearly matches the imported source intent: You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.
• Use when copied upstream references, examples, or scripts materially improve the answer.
• Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: 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

Examples

Example 1: Ask for the upstream workflow directly

Use @launch-strategy-v3 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @launch-strategy-v3 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @launch-strategy-v3 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @launch-strategy-v3 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-bundle-startup-founder/skills/launch-strategy, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @competitive-landscape-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @competitor-alternatives-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @copywriting-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @cpp-pro-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Imported Reference Notes

Imported: 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. Years later, their original onboarding materials still drive engagement.

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

Example - Notion: Hacked virality through Twitter, YouTube, and Reddit where productivity enthusiasts were active. Encouraged community to share templates and workflows. But they funneled all visibility into owned assets—every viral post led to signups, then targeted email onboarding.

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 tools like SparkToro or Listen Notes to find audience overlap
4. Set up affiliate/referral incentives

Example - TRMNL: Sent a free e-ink display to YouTuber Snazzy Labs—not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion.

Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.

Imported: Five-Phase Launch Approach

Launching isn't a one-day event. It's a phased process that builds momentum.

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 (doesn't need to be production-ready)

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 (even if still evolving)

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
• 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
• In-app popups and product tours
• Website banner linking to launch assets
• "New" sticker in dashboard navigation
• Blog post announcement
• Social posts across platforms
• Product Hunt, BetaList, Hacker News, etc.

Goal: Maximum visibility and conversion to paying users.

Imported: Product Hunt Launch Strategy

Product Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation.

Pros

• Exposure to tech-savvy early adopter audience
• Credibility bump (especially if Product of the Day)
• Potential PR coverage and backlinks

Cons

• Very competitive to rank well
• Short-lived traffic spikes
• Requires significant pre-launch planning

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

Case Studies

SavvyCal (Scheduling tool):

• Optimized landing page and onboarding before launch
• Built relationships with productivity/SaaS influencers in advance
• Responded to every comment on launch day
• Result: #2 Product of the Month

Reform (Form builder):

• Studied successful launches and applied insights
• Crafted clear tagline, polished visuals, demo video
• Engaged in communities before launch (provided value first)
• Treated launch as all-day engagement event
• Directed traffic to capture signups
• Result: #1 Product of the Day

Imported: Post-Launch Product Marketing

Your launch isn't over when the announcement goes live. Now comes adoption and retention work.

Immediate Post-Launch Actions

Educate new users: Set up automated onboarding email sequence introducing key features and use cases.

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.

Offer hands-on preview: Create no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.

Keep Momentum Going

It's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch.

Imported: Ongoing Launch Strategy

Don't rely on a single launch event. Regular updates and feature rollouts sustain engagement.

How to Prioritize What to Announce

Use this matrix to decide how much marketing each update deserves:

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
• Don't need full fanfare

Minor updates (bug fixes, small tweaks):

• Changelog and release notes
• Signal that product is improving
• Don't dominate marketing

Announcement Tactics

Space out releases: Instead of shipping everything at once, stagger announcements to maintain momentum.

Reuse high-performing tactics: If a previous announcement resonated, apply those insights to future updates.

Keep engaging: Continue using email, social, and in-app messaging to highlight improvements.

Signal active development: Even small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around.

Imported: Launch Checklist

Pre-Launch

• Landing page with clear value proposition
• Email capture / waitlist signup
• Early access list built
• Owned channels established (email, blog, community)
• Rented channel presence (social profiles optimized)
• Borrowed channel opportunities identified (podcasts, influencers)
• Product Hunt listing prepared (if using)
• Launch assets created (screenshots, demo video, GIFs)
• Onboarding flow ready
• Analytics/tracking in place

Launch Day

• Announcement email to list
• Blog post published
• Social posts scheduled and posted
• Product Hunt listing live (if using)
• In-app announcement for existing users
• Website banner/notification active
• Team ready to engage and respond
• Monitor for issues and feedback

Post-Launch

• Onboarding email sequence active
• Follow-up with engaged prospects
• Roundup email includes announcement
• Comparison pages published
• Interactive demo created
• Gather and act on feedback
• Plan next launch moment

Imported: Questions to Ask

If you need more context:

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?

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.