0-to-1-launch

Name: 0-to-1-launch
Author: beingsmit

39stars7forks

How to install 0-to-1-launch?

beingsmit/technical-product-gtm/0-to-1-launch

$npx -y skills add beingsmit/technical-product-gtm --skill 0-to-1-launch

Installs into the current project.

Summary

Launch new products from idea to first customers. Use when launching products, finding early adopters, building launch week playbooks, diagnosing why adoption stalls, or learning that press coverage does not equal growth. Includes the three-layer diagnosis, the 2-week experiment

Files · 1

View on GitHub

SKILL.md

1	# 0-to-1 Launch
2
3	Launch new products from idea to first customers. The goal isn't headlines — it's finding 10 customers who can't live without you.
4
5	## When to Use
6
7	Triggers:
8	- "How do we launch this product?"
9	- "First customer acquisition strategy"
10	- "We launched but nobody's using it"
11	- "Product Hunt vs direct outreach?"
12	- "We have awareness but no conversion"
13	- "How do I know if this is working?"
14
15	Context:
16	- New product launches
17	- Feature launches that feel like new products
18	- Finding first 10-50 customers
19	- Validating product-market fit
20	- Diagnosing why early traction stalls
21
22	---
23
24	## Core Frameworks
25
26	### 1. Press ≠ Growth (The Launch That Got 12 Signups)
27
28	The Pattern:
29
30	Coordinated a feature launch with full press tour. TechCrunch, VentureBeat, product blogs. Big announcement day.
31
32	Result:
33	- 50K impressions
34	- 12 signups
35	- 2 conversions
36
37	Why It Failed:
38
39	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.
40
41	What Works Better:
42
43	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.
44
45	Result: 50 emails → 15 replies (30% reply rate) → 8 trials → 4 conversions (50% trial-to-paid).
46
47	The Lesson:
48
49	Early customers come from direct outreach, not press coverage. Press matters later (Series A announcement, major milestone). For 0-to-1, it's distraction.
50
51	---
52
53	### 2. The Three-Layer Diagnosis (Why Launches Stall)
54
55	The Pattern:
56
57	You launched. You have some awareness. But conversion is weak. The problem lives in one of three layers, and each requires a different intervention.
58
59	Layer 1: Positioning Problem
60
61	Symptoms:
62	- Messaging sounds like competitors
63	- Differentiation requires explaining complex technical details
64	- Buyers see you as interchangeable with alternatives
65	- Sales conversations get derailed by comparison questions
66
67	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.
68
69	Fix: Stake a claim you can own structurally (not just through product features). Test with outbound messaging before committing product resources.
70
71	Layer 2: Experience Problem
72
73	Symptoms:
74	- Strong awareness but weak activation
75	- Users sign up but don't complete first workflow
76	- Multiple entry points creating decision paralysis
77	- Documentation is feature-centric, not outcome-centric
78
79	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.
80
81	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.
82
83	Layer 3: Alignment Problem
84
85	Symptoms:
86	- Team reports being "out of bandwidth" for customers
87	- Different functions optimize for different metrics
88	- Every idea has equal weight (no tiebreaker)
89	- No clear north star connecting activities to outcomes
90
91	Diagnosis: "Exploratory mode" — where every initiative has equal priority — becomes destructive when resources are constrained.
92
93	Fix: Define a single shared north star. Use it as tiebreaker for every decision: "Does this help us win a customer?" Cut activities that don't ladder up. Make progress visible weekly, not quarterly.
94
95	How to Use This:
96
97	When a launch stalls, diagnose which layer is broken before throwing resources at it. Fixing experience when the problem is positioning wastes engineering time. Fixing positioning when the problem is internal alignment wastes marketing spend.
98
99	---
100
101	### 3. The First 10 Customers Framework
102
103	Principle: First 10 customers are not for revenue. They're for learning.
104
105	What You're Learning:
106	1. Does the product actually solve the problem?
107	2. What's the activation flow? (How do they get value?)
108	3. What objections come up? (Price, features, integrations?)
109	4. Who's the real buyer? (Title, role, budget authority?)
110	5. What's the sales cycle? (Days, weeks, months?)
111
112	How to Find Them:
113
114	Channel 1: Personal Network (first 2-3)
115	- "I'm building [X], can I get your feedback?"
116	- Convert to paying customers (don't give away for free

People who liked this also viewed

6 picks

Type

0-to-1-launch

39stars7forks

View on GitHub

How to install 0-to-1-launch?

beingsmit/technical-product-gtm/0-to-1-launch

$npx -y skills add beingsmit/technical-product-gtm --skill 0-to-1-launch

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# 0-to-1 Launch
2
3	Launch new products from idea to first customers. The goal isn't headlines — it's finding 10 customers who can't live without you.
4
5	## When to Use
6
7	Triggers:
8	- "How do we launch this product?"
9	- "First customer acquisition strategy"
10	- "We launched but nobody's using it"
11	- "Product Hunt vs direct outreach?"
12	- "We have awareness but no conversion"
13	- "How do I know if this is working?"
14
15	Context:
16	- New product launches
17	- Feature launches that feel like new products
18	- Finding first 10-50 customers
19	- Validating product-market fit
20	- Diagnosing why early traction stalls
21
22	---
23
24	## Core Frameworks
25
26	### 1. Press ≠ Growth (The Launch That Got 12 Signups)
27
28	The Pattern:
29
30	Coordinated a feature launch with full press tour. TechCrunch, VentureBeat, product blogs. Big announcement day.
31
32	Result:
33	- 50K impressions
34	- 12 signups
35	- 2 conversions
36
37	Why It Failed:
38
39	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.
40
41	What Works Better:
42
43	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.
44
45	Result: 50 emails → 15 replies (30% reply rate) → 8 trials → 4 conversions (50% trial-to-paid).
46
47	The Lesson:
48
49	Early customers come from direct outreach, not press coverage. Press matters later (Series A announcement, major milestone). For 0-to-1, it's distraction.
50
51	---
52
53	### 2. The Three-Layer Diagnosis (Why Launches Stall)
54
55	The Pattern:
56
57	You launched. You have some awareness. But conversion is weak. The problem lives in one of three layers, and each requires a different intervention.
58
59	Layer 1: Positioning Problem
60
61	Symptoms:
62	- Messaging sounds like competitors
63	- Differentiation requires explaining complex technical details
64	- Buyers see you as interchangeable with alternatives
65	- Sales conversations get derailed by comparison questions
66
67	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.
68
69	Fix: Stake a claim you can own structurally (not just through product features). Test with outbound messaging before committing product resources.
70
71	Layer 2: Experience Problem
72
73	Symptoms:
74	- Strong awareness but weak activation
75	- Users sign up but don't complete first workflow
76	- Multiple entry points creating decision paralysis
77	- Documentation is feature-centric, not outcome-centric
78
79	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.
80
81	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.
82
83	Layer 3: Alignment Problem
84
85	Symptoms:
86	- Team reports being "out of bandwidth" for customers
87	- Different functions optimize for different metrics
88	- Every idea has equal weight (no tiebreaker)
89	- No clear north star connecting activities to outcomes
90
91	Diagnosis: "Exploratory mode" — where every initiative has equal priority — becomes destructive when resources are constrained.
92
93	Fix: Define a single shared north star. Use it as tiebreaker for every decision: "Does this help us win a customer?" Cut activities that don't ladder up. Make progress visible weekly, not quarterly.
94
95	How to Use This:
96
97	When a launch stalls, diagnose which layer is broken before throwing resources at it. Fixing experience when the problem is positioning wastes engineering time. Fixing positioning when the problem is internal alignment wastes marketing spend.
98
99	---
100
101	### 3. The First 10 Customers Framework
102
103	Principle: First 10 customers are not for revenue. They're for learning.
104
105	What You're Learning:
106	1. Does the product actually solve the problem?
107	2. What's the activation flow? (How do they get value?)
108	3. What objections come up? (Price, features, integrations?)
109	4. Who's the real buyer? (Title, role, budget authority?)
110	5. What's the sales cycle? (Days, weeks, months?)
111
112	How to Find Them:
113
114	Channel 1: Personal Network (first 2-3)
115	- "I'm building [X], can I get your feedback?"
116	- Convert to paying customers (don't give away for free

People who liked this also viewed

6 picks

Type