cold-start-strategy

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

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:

Freelance Platforms (Fiverr, Upwork)

Users often have clear need and budget; high intent.

Comment Outreach (Twitter/X, etc.)

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:

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