cold-start-strategy

$npx mdskill add kostja94/marketing-skills/cold-start-strategy

Plan cold start strategies to acquire first users for zero-traction products.

  • Solves the chicken-and-egg problem of getting first users with no traction.
  • Depends on project context files and user-provided product details.
  • Assesses product type, target audience, and available channels to recommend tactics.
  • Delivers actionable launch plans with specific channels like Product Hunt or comment outreach.

SKILL.md

.github/skills/cold-start-strategyView on GitHub ↗
---
name: cold-start-strategy
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.
metadata:
  version: 1.3.0
---

# 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

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and positioning.

Identify:
1. **Product type**: AI tool, SaaS, app, B2B, B2C
2. **Target audience**: Where they spend time
3. **Budget**: Zero, minimal ($500–1K), or moderate
4. **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 |
| **Reddit** | 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

More from kostja94/marketing-skills

SkillDescription
404-page-generatorWhen the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
about-page-generatorWhen the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
affiliate-marketingWhen the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
affiliate-page-generatorWhen the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
ai-traffic-trackingWhen the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
alternatives-page-generatorWhen the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
api-page-generatorWhen the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
app-adsWhen the user wants to run app install ads, user acquisition (UA), or promote mobile apps. Also use when the user mentions "app ads," "app install ads," "UA," "user acquisition," "Google App Campaigns," "Apple Search Ads," "ASA," "UAC," "App Store ads," "Play Store ads," "CPI," or "app promotion." For store listings, use distribution-channels.
article-contentWhen the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
backlink-analysisWhen the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building.