메뉴
Plan and execute go-to-market from pre-launch waitlist through first 100 customers—B2C tactics from Lenny Rachitsky's research, B2B motion selection, Product Hunt playbook, and the Racecar Growth Framework. Use when launching a product, choosing growth channels, or planning initial customer acquisition.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | go-to-market |
| description | Plan and execute go-to-market from pre-launch waitlist through first 100 customers—B2C tactics from Lenny Rachitsky's research, B2B motion selection, Product Hunt playbook, and the Racecar Growth Framework. Use when launching a product, choosing growth channels, or planning initial customer acquisition. |
Distribution beats product. The best product nobody hears about loses to the average product with great distribution every time.
Stage 1: Personal network (customers 1-10)
→ Founders selling 1:1, leveraging existing relationships
Stage 2: Community seeding (customers 10-30)
→ Targeted communities, content in niche forums, early adopter programs
Stage 3: Channel discovery (customers 30-100)
→ Test 2-3 channels, find the one that works, double down
Stage 4: Channel optimization (customers 100-1,000)
→ Systematize the winning channel, add one more
From studying 40+ successful companies:
| Growth Channel | Example Companies | How They Started |
|---|---|---|
| Word of mouth | Slack, Dropbox, Figma | Built something people couldn't stop talking about |
| Virality (built-in) | WhatsApp, Venmo, Calendly | Product is better when you invite others |
| Content / SEO | HubSpot, Zapier, Canva | Created tools/content people search for |
| Paid acquisition | DoorDash, Instacart | Unit economics supported paid from day 1 |
| Community | Notion, Loom, dbt | Invested in user communities before scaling |
| Sales | Salesforce, Workday | High-touch enterprise from the start |
| Partnerships | Ramp, Plaid | Integrated into existing workflows |
Spend 2 weeks on each of 3 channels.
Track: CAC, conversion rate, time to first value.
Kill channels where CAC > target within 2 weeks.
Double down on the channel with lowest CAC and fastest conversion.
| Signal | PLG | Sales-Led |
|---|---|---|
| ACV | < $5K/year | > $25K/year |
| Buyer | End user | Executive / committee |
| Decision speed | Days | Weeks to months |
| Try-before-buy | Expected | Not always possible |
| Expansion | Usage-based upgrades | Contract negotiations |
Can a user get value in under 5 minutes without talking to anyone?
├── YES → Product-Led Growth
│ Examples: Slack, Notion, Figma
│ Playbook: Free tier → team adoption → enterprise upgrade
│
└── NO → Sales-Led (or Sales-Assisted PLG)
Examples: Salesforce, Snowflake
Playbook: Targeted outbound → demo → POC → contract
- Build a "hunter" relationship (top hunters get more visibility)
- Collect 200+ upvotes worth of supporters — email list, community, friends
- Prepare assets: 5 images, 240-char tagline, first comment with story
- Have a special launch offer ready
- Launch at 12:01 AM PT (Product Hunt resets daily at midnight PT)
- Post your "maker comment" immediately — tell the origin story
- Respond to every comment within 15 minutes for the first 4 hours
- Notify your supporters between 7-9 AM PT (prime upvote window)
- Share on Twitter/X, LinkedIn, and communities throughout the day
- Day 2-3: Follow up with everyone who engaged
- Week 1: Email all upvoters with exclusive offer
- Week 2: Write a "lessons learned" post (content from launch → SEO)
KICKSTARTS — One-time pushes that spike growth
→ PR hits, Product Hunt launch, conference talks, viral content
→ Valuable but not sustainable alone
ENGINES — Repeatable growth loops
→ SEO → content → traffic → signups (content engine)
→ User invites → new users → more invites (viral engine)
→ Revenue → paid ads → customers → revenue (paid engine)
TURBO BOOSTS — Optimizations that multiply existing engines
→ Conversion rate optimization
→ Referral program improvements
→ Onboarding flow tightening
Most startups over-invest in kickstarts and under-invest in engines.
Priority order:
1. Get one engine working (even at small scale)
2. Use kickstarts to feed fuel into the engine
3. Apply turbo boosts once the engine is proven
| GTM Theater | Real GTM |
|---|---|
| "We'll grow organically" | Choosing a specific channel and testing it |
| Launching on Product Hunt with no preparation | 2 weeks of community building first |
| Testing 10 channels simultaneously | Testing 3, killing 2, doubling down on 1 |
| "Our product is so good it sells itself" | Great products still need distribution |
| Waiting until the product is "ready" | Launching when it solves one problem well |
"Map out a 90-day GTM plan for [product] targeting [customer segment]. Identify the top 3 channels to test, design a 2-week experiment for each, and define the Racecar Growth Framework components: kickstarts for launch, the engine I should build first, and turbo boosts for month 3."
The agent becomes your growth strategist — building a repeatable acquisition engine, not just a launch moment.
Create, update, close, and report on Jira tickets. Reads JIRA_URL and JIRA_TOKEN from environment variables or .env file. Provides comprehensive guidance for Jira ticket lifecycle management, API integration, and automation workflows.
AI-powered clarity engine for job seekers and founders. Not a resume fixer — a thinking partner. Helps you find your north star sentence: who you are, what you do, and why it matters to someone else. Produces one core version and targeted variations for different audiences. Use before interviews, investor conversations, networking events, or any moment where you need to introduce yourself under pressure.
Review code for bugs, security issues, and improvements. Use when the user asks to: (1) review code or a diff, (2) check code quality, (3) find bugs or issues, (4) audit for security problems. Trigger on phrases like 'review this', 'check my code', 'any issues with this', 'code review'.
Full-lifecycle career advisor — self-discovery through career growth. Use when the user wants to: (1) discover identity, values, ikigai, or skills inventory, (2) define dream job or analyze career gaps, (3) close gaps via learning, certifications, portfolio, or personal branding, (4) build narrative hats or role-specific positioning, (5) search for jobs, generate resumes, or prepare for interviews, (6) onboard into a new role, track achievements, or generate self-reviews, (7) backfill past roles, run weekly recall, or check career readiness. Proactively nudges users to document achievements NOW — not when they need a resume. Consolidates the former career-resume, career-tracker, portfolio-strategy, and github-profile skills.
Synthesizes professional accomplishments into high-converting landing page content. Triggers when a user wants to build a landing page, launch a consulting service, productize their career expertise, create a service page, or monetize their skills. Also triggers on: "freelance", "consulting offer", "offer page", "service offering", "turn my experience into a business". Uses career-advisor data as the foundation.
Query Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers. Use when user mentions NotebookLM, shares a notebooklm.google.com URL, asks to query their notebooks/docs, or says "ask my NotebookLM", "check my docs", "query my notebook". Provides browser automation, notebook library management, and persistent auth. Drastically reduced hallucinations through document-only responses from Gemini.