cold-start-strategy
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.
Best use case
cold-start-strategy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using cold-start-strategy should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cold-start/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cold-start-strategy Compares
| Feature / Agent | cold-start-strategy | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
AI Agent for Cold Email Generation
Discover AI agent skills for cold email generation, outreach copy, lead personalization, CRM support, and sales-adjacent messaging workflows.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
SKILL.md Source
# 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
Related Skills
seo-strategy
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.
retention-strategy
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
pmf-strategy
When the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.
indie-hacker-strategy
When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.
gtm-strategy
When the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.
pricing-strategy
When the user wants to plan, design, or optimize pricing strategy and structure. Also use when the user mentions "pricing strategy," "pricing model," "pricing tiers," "freemium," "value-based pricing," "anchoring," "price structure," or "monetization strategy." For pricing page, use pricing-page-generator.
discount-marketing-strategy
When the user wants to plan, implement, or optimize discount and promotional pricing strategy. Also use when the user mentions "discount strategy," "promo code," "coupon," "redeem code," "lifetime deal," "LTD," "AppSumo," "Black Friday," "Cyber Monday," "BFCM," "seasonal sale," or "promotional pricing." For pricing page, use pricing-page-generator.
paid-ads-strategy
When the user wants to plan paid ads strategy, allocate ad budget, or choose paid channels. Also use when the user mentions "paid ads," "paid media," "PPC," "SEM," "web ads," "app ads," "TV ads," "CTV," "OOH," "banner ads," "ad network," "ad alliance," "Taaft ads," "Shopify App Store ads," "Google Ads," "Meta Ads," "PMF testing," "PMF validation," "test product-market fit with ads," "ad spend," "ad budget," "ROAS," "paid acquisition," "Quality Score," or "ad-to-page alignment." For Google Ads execution, use google-ads. For Meta Ads execution, use meta-ads. For landing page alignment, use landing-page-generator.
open-source-strategy
When the user wants open source strategy, OSS commercialization, or open source growth. Also use when the user mentions "open source strategy," "OSS strategy," "open source commercialization," "open source to paid," "open core," "COSS," "commercial open source," "GitHub stars strategy," "DevHunt," "open source marketing," "open source growth," "Llama," "Dify," "Cursor," "open source business model," or "developer tools directory." For GitHub tactics, use github.
localization-strategy
When the user wants to plan or implement localization strategy for multilingual and global growth. Also use when the user mentions "localization," "multilingual," "i18n," "global expansion," "market entry," "localization strategy," "hreflang," "multi-language SEO," or "international SEO." For translation workflow, glossary, and style guide, use translation.
rebranding-strategy
When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement. Also use when the user mentions "rebranding," "rebrand," "domain change," "domain migration," "301 redirect," "change domain name," "rebrand announcement," "social media rebrand," "brand launch," or "domain redirect." For domain choice, use domain-selection.
content-strategy
When the user wants to plan content for SEO, create content calendar, or build topic clusters. Also use when the user mentions "content strategy," "content plan," "topic clusters," "pillar content," "pillar page," "cluster articles," "editorial calendar," "content hub," "content planning," "content clusters," "topic cluster strategy," "content strategy for SEO," or "content calendar." For editorial mix, use content-marketing.