Gtm 0 To 1 Launch
Run a structured 0-to-1 launch when you need first customers and real adoption signals—not vanity press metrics.
Overview
gtm-0-to-1-launch is an agent skill most often used in Launch (also Validate, Grow) that guides solo builders from launch planning through first-customer acquisition with experiment cycles and adoption diagnostics.
Install
npx skills add https://github.com/github/awesome-copilot --skill gtm-0-to-1-launchWhat is this skill?
- Three-layer diagnosis for why early traction stalls after a launch
- 2-week experiment cycle for testing acquisition hypotheses quickly
- Press ≠ growth framework (50K impressions vs 12 signups case study)
- Triggers for “nobody’s using it” and awareness without conversion
- Aims at 10–50 customers who cannot live without the product
- launch case study: 50K impressions, 12 signups, 2 conversions
Adoption & trust: 1.4k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You shipped or announced something and got buzz, impressions, or curiosity—but almost no paying or retained users and no clear next experiment.
Who is it for?
Solo founders preparing a first launch, feature-as-product release, or post-launch triage when signups do not match attention.
Skip if: Teams that only need technical release checklists, compliance-heavy enterprise rollouts, or launches where positioning and PMF are already proven at scale.
When should I use this skill?
Launching products, finding early adopters, building launch week playbooks, or diagnosing why adoption stalls after press coverage.
What do I get? / Deliverables
You leave with a prioritized launch plan, channel experiments on a two-week cadence, and a diagnostic read on whether the gap is awareness, conversion, or product readiness—so you can iterate toward ten indispensable cus
- Launch experiment backlog
- Channel and messaging hypotheses
- Adoption stall diagnosis
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Launch because the skill centers on coordinated go-to-market execution, launch-week playbooks, and channel choices after you have something to ship. Distribution is the right subphase for outreach vs Product Hunt, awareness-to-conversion gaps, and finding early adopters rather than backend or security work.
Where it fits
Scope a two-week outreach experiment before committing to a big launch-week spend.
Choose between community launch, direct outreach, and press when self-serve is ready.
Diagnose why signups stall after an initial spike using the three-layer framework.
Clarify who the first ten indispensable customers are before picking launch channels.
How it compares
Use instead of treating press coverage or Product Hunt ranking as a substitute for a repeatable first-customer acquisition loop.
Common Questions / FAQ
Who is gtm-0-to-1-launch for?
Indie builders and small teams launching net-new products or major features who own distribution themselves and need frameworks beyond one-off launch tweets or PR.
When should I use gtm-0-to-1-launch?
Use during Validate when scoping first-customer experiments, during Launch when choosing channels and launch-week sequencing, and during Grow when diagnosing stalls between awareness and conversion.
Is gtm-0-to-1-launch safe to install?
Review the Security Audits panel on this Prism page and treat bundled guidance as operational strategy—not legal, financial, or security advice.
SKILL.md
READMESKILL.md - Gtm 0 To 1 Launch
# 0-to-1 Launch Launch new products from idea to first customers. The goal isn't headlines — it's finding 10 customers who can't live without you. ## When to Use **Triggers:** - "How do we launch this product?" - "First customer acquisition strategy" - "We launched but nobody's using it" - "Product Hunt vs direct outreach?" - "We have awareness but no conversion" - "How do I know if this is working?" **Context:** - New product launches - Feature launches that feel like new products - Finding first 10-50 customers - Validating product-market fit - Diagnosing why early traction stalls --- ## Core Frameworks ### 1. Press ≠ Growth (The Launch That Got 12 Signups) **The Pattern:** Coordinated a feature launch with full press tour. TechCrunch, VentureBeat, product blogs. Big announcement day. **Result:** - 50K impressions - 12 signups - 2 conversions **Why It Failed:** Optimized for media buzz, not user value. The feature wasn't ready for self-serve. It needed education, context, hand-holding. Press gives you eyeballs. But eyeballs without activation = vanity. **What Works Better:** Email 50 target customers directly. "We built [feature] because teams like yours struggle with [problem]. Want early access?" Walk them through setup personally. Get feedback, iterate. **Result:** 50 emails → 15 replies (30% reply rate) → 8 trials → 4 conversions (50% trial-to-paid). **The Lesson:** Early customers come from direct outreach, not press coverage. Press matters later (Series A announcement, major milestone). For 0-to-1, it's distraction. --- ### 2. The Three-Layer Diagnosis (Why Launches Stall) **The Pattern:** You launched. You have some awareness. But conversion is weak. The problem lives in one of three layers, and each requires a different intervention. **Layer 1: Positioning Problem** Symptoms: - Messaging sounds like competitors - Differentiation requires explaining complex technical details - Buyers see you as interchangeable with alternatives - Sales conversations get derailed by comparison questions Diagnosis: You're "fighting an asymmetric war on the wrong front" — competing on features against better-funded companies. Map where competitors claim unique value. Find the position they can't easily copy. Fix: Stake a claim you can own structurally (not just through product features). Test with outbound messaging before committing product resources. **Layer 2: Experience Problem** Symptoms: - Strong awareness but weak activation - Users sign up but don't complete first workflow - Multiple entry points creating decision paralysis - Documentation is feature-centric, not outcome-centric Diagnosis: Flexibility without opinionated defaults is a liability, not a feature. Users face the "paradox of choice" — too many options, not enough guidance to the aha moment. Fix: Identify 2-3 "undeniable use cases" that deliver immediate value. Restrict onboarding to those specific use cases. Gate advanced features behind a mastery path. Rewrite help content around jobs-to-be-done, not feature lists. **Layer 3: Alignment Problem** Symptoms: - Team reports being "out of bandwidth" for customers - Different functions optimize for different metrics - Every idea has equal weight (no tiebreaker) - No clear north star connecting activities to outcomes Diagnosis: "Exploratory mode" — where every initiative has equal priority — becomes destructive when resources are constrained. Fix: Define a single shared