Cold start strategy skill
When the user wants to plan cold start, get first users, or launch a new product with zero traction.
by kostja94·MIT license·★ 1,006 Stars on the repo·GitHub ↗
Use now
npx degit kostja94/marketing-skills/skills/strategies/launch/cold-start#main ~/.claude/skills/cold-start-strategyChecked ·commit main
Files of Cold start strategy
SKILL.md
Show the full text123 lines
Strategies: Cold Start
Guides cold start strategy for AI/SaaS products: getting first users and traction when you have zero. The cold start problem is overcoming the chicken-and-egg barrier; most startups fail due to poor distribution, not product quality. For indie hacker context (first 100 users, Build in Public, Pieter Levels tactics), see indie-hacker-strategy.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
Identify:
- Product type: AI tool, SaaS, app, B2B, B2C
- Target audience: Where they spend time
- Budget: Zero, minimal ($500–1K), or moderate
- Timeline: Pre-launch, launch week, post-launch
Cold Start Channels
| Channel | Audience | Use | Notes |
|---|---|---|---|
| Product Hunt | Indie makers, early adopters | Launch-day buzz; community upvotes | ~3% conversion; traffic spike; see product-hunt-launch |
| AppSumo / LTD | Deal seekers, early adopters | Lifetime deal for fast revenue, validation | Quick cash; price-sensitive users; see discount-marketing-strategy for LTD structure, trade-offs |
| Subreddit-specific | r/AlphaAndBetaUsers, r/roastmystartup, r/devops, r/SaaS | 80/20 rule; 5+ months for traction; lead with story | |
| Indie Hackers | Indie makers, founders | Sustained engagement; authentic journey | ~23% conversion; 4–6 months; see indie-hacker-strategy for tactics |
| Hacker News | Tech, startups | Show HN launch | Luck + timing; front page = traffic spike |
| Directory submission | AI tools, product launch | Taaft, G2, niche directories | Validate PMF; seed users; see directory-submission |
| Founder-led outbound | B2B, high ACV | Cold email, LinkedIn; 10–15 personalized outreaches/day | Pre-$5K MRR; only reliable path when ACV >$500/mo |
| Community engagement | Target users | Forums, LinkedIn groups, Discord | 45–90 days; contribute value first |
Finding Users: Demand-Signal Outreach
Low-cost ways to find and reach users who are already expressing need. Use when Product Hunt, directories, or forums are not enough.
Social Platform Search
Search Twitter/X, LinkedIn, Reddit, and niche communities for demand signals:
| Signal | What to seek |
|---|---|
| Keywords | Industry terms, category keywords, "looking for [X] tool," "best alternative to [Y]" |
| Discussion | Industry threads, complaints about competitors, "anyone used…" or "recommend…" posts |
| Platform | Choose where your audience spends time (Twitter/X, LinkedIn, Reddit, Discord, vertical forums) |
Freelance Platforms (Fiverr, Upwork)
| Step | Practice |
|---|---|
| Search | Service requests related to your product (e.g. "need logo design," "looking for video editor") |
| Identify | Buyers in job descriptions or comments who have related needs |
| Reach | Offer help or tool recommendation; introduce product politely |
Users often have clear need and budget; high intent.
Comment Outreach (Twitter/X, etc.)
| Practice | Guideline |
|---|---|
| Search | Brand, category, "looking for AI tool," "best alternative to…" |
| Reply | Comment on posts where users express need; avoid spam |
| Tone | Sincere; honest that it's your product; invite trial and feedback |
| Avoid | Hard sell; copy-paste; repeated posting |
Example outreach: "Hi, I'm building something similar. If you'd like to try it: [link]. Happy to hear any feedback—we're iterating actively."
Feedback collection: DM, email, survey, user interview, in-app feedback—choose by channel and context.
Multi-Channel Launch (6–7 Week)
Coordinated launch across channels yields 5–6× more users than single-channel:
| Week | Focus |
|---|---|
| 1–2 | Audience building (LinkedIn 3×/week) |
| 3–4 | Beta; community engagement |
| 5 | Pre-launch countdown |
| 6 | Product Hunt + Reddit/Indie Hackers |
| 7 | Post-launch follow-up |
Build in public before launch—share progress, validate ideas, create invested audience. For indie hacker first 100 users, Build in Public content framework (40/30/20/10), Pieter Levels tactics → indie-hacker-strategy.
Pre-Launch
- Validate demand: 10–15 target user conversations; 20–30 before launch
- Waitlist: 8–12 weeks before launch; target 200–1,000 signups
- Landing page: Ready; screenshots, description, media kit
- Avoid: Perfectionism; large-scale paid ads before PMF—see paid-ads-strategy. Small-budget Google Ads for PMF testing is valid.
What Doesn't Work Early
- Hiring SDRs before founder has closed 10 customers
- Large-scale paid ads before product-market fit—see paid-ads-strategy. Small-budget PMF testing (e.g., $47–500 Google Ads + landing page) is valid.
- Sporadic execution; "spray and pray" targeting
- Mass submission to low-quality directories
Output Format
- Channel selection (2–3 channels; execute well)
- Timeline (pre-launch, launch, post-launch)
- Readiness checklist
- Platform-specific actions (Product Hunt, Reddit, etc.)
Related Skills
- pmf-strategy: Product-market fit validation; when to scale; avoid large-scale paid before PMF
- gtm-strategy: Full GTM framework; cold start differs (0→1 vs commercialization)
- paid-ads-strategy: Two modes—PMF testing (small budget) vs conversion-driven (post-PMF); when to add paid after cold start
- google-ads: PMF testing setup; small-budget validation
- discount-marketing-strategy: LTD structure, pricing, trade-offs; cold start uses LTD as channel
- product-hunt-launch: Product Hunt preparation and launch
- directory-submission: Taaft, G2, curated lists—directory listings as cold-start channel
- community-forum: Indie Hackers, HN, Reddit—forum/community as cold-start channel
- reddit-posts: Reddit post copy for cold-start posts
- integrated-marketing: Channel mix; cold start is early-stage channel strategy
- media-kit-page-generator: Assets required for Product Hunt and directory submissions
- indie-hacker-strategy: Indie hacker first 100 users; Build in Public; Pieter Levels tactics; channel fit; this skill = generic cold start; indie-hacker = indie-specific
| 1 | |
| 2 | name cold-start-strategy |
| 3 | description When the user wants to plan cold start, get first users, or launch a new product with zero traction. Also use when the user mentions "cold start," "cold start problem," "first users," "seed users," "finding users," "finding early users," "Fiverr Upwork," "comment outreach," "Twitter search users," "product launch strategy," "0 to 1 growth," "early-stage acquisition," "launch channels," "get first customers," "Product Hunt launch," "AppSumo," "LTD," "indie hacker," "bootstrapping," or "solo founder." For directory listing copy and submissions, use directory-submission. For Product Hunt day-of execution, use product-hunt-launch. For GTM motion design, use gtm-strategy. |
| 4 | metadata |
| 5 | version 1.3.0 |
| 6 | |
| 7 | |
| 8 | # Strategies: Cold Start |
| 9 | |
| 10 | Guides cold start strategy for AI/SaaS products: getting first users and traction when you have zero. The cold start problem is overcoming the chicken-and-egg barrier; most startups fail due to poor distribution, not product quality. For **indie hacker** context (first 100 users, Build in Public, Pieter Levels tactics), see **indie-hacker-strategy**. |
| 11 | |
| 12 | **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. |
| 13 | |
| 14 | ## Initial Assessment |
| 15 | |
| 16 | **Project context:** Read root `contextus.md` when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system. |
| 17 | |
| 18 | Identify: |
| 19 | **Product type**: AI tool, SaaS, app, B2B, B2C |
| 20 | **Target audience**: Where they spend time |
| 21 | **Budget**: Zero, minimal ($500–1K), or moderate |
| 22 | **Timeline**: Pre-launch, launch week, post-launch |
| 23 | |
| 24 | ## Cold Start Channels |
| 25 | |
| 26 | | Channel | Audience | Use | Notes | |
| 27 | |---------|----------|-----|-------| |
| 28 | | **Product Hunt** | Indie makers, early adopters | Launch-day buzz; community upvotes | ~3% conversion; traffic spike; see **product-hunt-launch** | |
| 29 | | **AppSumo / LTD** | Deal seekers, early adopters | Lifetime deal for fast revenue, validation | Quick cash; price-sensitive users; see **discount-marketing-strategy** for LTD structure, trade-offs | |
| 30 | | **Reddit** | Subreddit-specific | r/AlphaAndBetaUsers, r/roastmystartup, r/devops, r/SaaS | 80/20 rule; 5+ months for traction; lead with story | |
| 31 | | **Indie Hackers** | Indie makers, founders | Sustained engagement; authentic journey | ~23% conversion; 4–6 months; see **indie-hacker-strategy** for tactics | |
| 32 | | **Hacker News** | Tech, startups | Show HN launch | Luck + timing; front page = traffic spike | |
| 33 | | **Directory submission** | AI tools, product launch | Taaft, G2, niche directories | Validate PMF; seed users; see **directory-submission** | |
| 34 | | **Founder-led outbound** | B2B, high ACV | Cold email, LinkedIn; 10–15 personalized outreaches/day | Pre-$5K MRR; only reliable path when ACV >$500/mo | |
| 35 | | **Community engagement** | Target users | Forums, LinkedIn groups, Discord | 45–90 days; contribute value first | |
| 36 | |
| 37 | ## Finding Users: Demand-Signal Outreach |
| 38 | |
| 39 | Low-cost ways to find and reach users who are already expressing need. Use when Product Hunt, directories, or forums are not enough. |
| 40 | |
| 41 | ### Social Platform Search |
| 42 | |
| 43 | Search Twitter/X, LinkedIn, Reddit, and niche communities for demand signals: |
| 44 | |
| 45 | | Signal | What to seek | |
| 46 | |--------|--------------| |
| 47 | | **Keywords** | Industry terms, category keywords, "looking for [X] tool," "best alternative to [Y]" | |
| 48 | | **Discussion** | Industry threads, complaints about competitors, "anyone used…" or "recommend…" posts | |
| 49 | | **Platform** | Choose where your audience spends time (Twitter/X, LinkedIn, Reddit, Discord, vertical forums) | |
| 50 | |
| 51 | ### Freelance Platforms (Fiverr, Upwork) |
| 52 | |
| 53 | | Step | Practice | |
| 54 | |------|----------| |
| 55 | | **Search** | Service requests related to your product (e.g. "need logo design," "looking for video editor") | |
| 56 | | **Identify** | Buyers in job descriptions or comments who have related needs | |
| 57 | | **Reach** | Offer help or tool recommendation; introduce product politely | |
| 58 | |
| 59 | Users often have clear need and budget; high intent. |
| 60 | |
| 61 | ### Comment Outreach (Twitter/X, etc.) |
| 62 | |
| 63 | | Practice | Guideline | |
| 64 | |----------|-----------| |
| 65 | | **Search** | Brand, category, "looking for AI tool," "best alternative to…" | |
| 66 | | **Reply** | Comment on posts where users express need; avoid spam | |
| 67 | | **Tone** | Sincere; honest that it's your product; invite trial and feedback | |
| 68 | | **Avoid** | Hard sell; copy-paste; repeated posting | |
| 69 | |
| 70 | **Example outreach**: "Hi, I'm building something similar. If you'd like to try it: [link]. Happy to hear any feedback—we're iterating actively." |
| 71 | |
| 72 | **Feedback collection**: DM, email, survey, user interview, in-app feedback—choose by channel and context. |
| 73 | |
| 74 | ## Multi-Channel Launch (6–7 Week) |
| 75 | |
| 76 | Coordinated launch across channels yields 5–6× more users than single-channel: |
| 77 | |
| 78 | | Week | Focus | |
| 79 | |------|-------| |
| 80 | | 1–2 | Audience building (LinkedIn 3×/week) | |
| 81 | | 3–4 | Beta; community engagement | |
| 82 | | 5 | Pre-launch countdown | |
| 83 | | 6 | Product Hunt + Reddit/Indie Hackers | |
| 84 | | 7 | Post-launch follow-up | |
| 85 | |
| 86 | **Build in public** before launch—share progress, validate ideas, create invested audience. For indie hacker first 100 users, Build in Public content framework (40/30/20/10), Pieter Levels tactics → **indie-hacker-strategy**. |
| 87 | |
| 88 | ## Pre-Launch |
| 89 | |
| 90 | **Validate demand**: 10–15 target user conversations; 20–30 before launch |
| 91 | **Waitlist**: 8–12 weeks before launch; target 200–1,000 signups |
| 92 | **Landing page**: Ready; screenshots, description, media kit |
| 93 | **Avoid**: Perfectionism; large-scale paid ads before PMF—see **paid-ads-strategy**. Small-budget Google Ads for PMF testing is valid. |
| 94 | |
| 95 | ## What Doesn't Work Early |
| 96 | |
| 97 | Hiring SDRs before founder has closed 10 customers |
| 98 | Large-scale paid ads before product-market fit—see **paid-ads-strategy**. Small-budget PMF testing (e.g., $47–500 Google Ads + landing page) is valid. |
| 99 | Sporadic execution; "spray and pray" targeting |
| 100 | Mass submission to low-quality directories |
| 101 | |
| 102 | ## Output Format |
| 103 | |
| 104 | **Channel** selection (2–3 channels; execute well) |
| 105 | **Timeline** (pre-launch, launch, post-launch) |
| 106 | **Readiness** checklist |
| 107 | **Platform-specific** actions (Product Hunt, Reddit, etc.) |
| 108 | |
| 109 | ## Related Skills |
| 110 | |
| 111 | **pmf-strategy**: Product-market fit validation; when to scale; avoid large-scale paid before PMF |
| 112 | **gtm-strategy**: Full GTM framework; cold start differs (0→1 vs commercialization) |
| 113 | **paid-ads-strategy**: Two modes—PMF testing (small budget) vs conversion-driven (post-PMF); when to add paid after cold start |
| 114 | **google-ads**: PMF testing setup; small-budget validation |
| 115 | **discount-marketing-strategy**: LTD structure, pricing, trade-offs; cold start uses LTD as channel |
| 116 | **product-hunt-launch**: Product Hunt preparation and launch |
| 117 | **directory-submission**: Taaft, G2, curated lists—directory listings as cold-start channel |
| 118 | **community-forum**: Indie Hackers, HN, Reddit—forum/community as cold-start channel |
| 119 | **reddit-posts**: Reddit post copy for cold-start posts |
| 120 | **integrated-marketing**: Channel mix; cold start is early-stage channel strategy |
| 121 | **media-kit-page-generator**: Assets required for Product Hunt and directory submissions |
| 122 | **indie-hacker-strategy**: Indie hacker first 100 users; Build in Public; Pieter Levels tactics; channel fit; this skill = generic cold start; indie-hacker = indie-specific |
| 123 |
Discussion
Alternatives
/bragTurn the current project website into a short, polished, shareable launch video using Hyperframes. Use when someone says "/brag", "let's brag about this", "make a launch video", "turn this into a video", or wants to share what they built. Reads the project code directly — no live URL or screenshots needed./brag-slimTurn a project directory or a website URL into a short, shareable launch video with music, motion, and share copy. One file, no bundled assets — built entirely by the model with the tools already on the machine. Use when someone says "/brag-slim", "let's /brag about this", "brag about <url>", "make a launch video", or wants to show off what they built. If the /brag skill is also installed, let /brag handle those phrases; it hands off here on Opus 5.5.
Business motion filmPlan, build and quality-check a premium short commercial for a real business (roofing, property, ecommerce, B2B software) using AI-generated footage, code-built motion (HTML/GSAP), selective Three.js and an independent-critic "Gauntlet" loop. Use when asked to make a launch-style / SaaS-style video, business ad, explainer, sample reel or pitch video, or to review and improve one. Encodes motion principles distilled from 28 professional launch films, a quality bar, audio rules and a business-offer playbook.
AI Product Launch PlaybookLaunch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.Browse more free Claude skills or everything in Product.