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 star...

Security Scan

This is an instruction-only strategy skill whose requirements and runtime instructions align with its stated purpose and do not request credentials or install code.

Purpose & Capability

Name and description (cold-start/growth tactics) match the SKILL.md content. The skill is instruction-only and does not ask for unrelated binaries, cloud credentials, or system access.

Instruction Scope

Instructions are focused on outreach, channels, and launch sequencing. The only file reads the skill suggests are .claude/project-context.md or .cursor/project-context.md to gather product context — this is reasonable for tailoring advice but is the only scope-expanding action and should be acceptable if those files are meant to hold product notes. The skill does not instruct the agent to read arbitrary system files, access secrets, or transmit data to unexpected endpoints.

Install Mechanism

No install spec and no code files: lowest-risk model (instruction-only). Nothing is downloaded or written to disk by the skill itself.

Credentials

No required environment variables, credentials, or config paths are declared. The instructions do not reference other env vars or request secrets.

Persistence & Privilege

always:false (default). Skill can be invoked autonomously (platform default) but does not request permanent presence or modify other skills or system settings.

Assessment

This skill appears coherent and low-risk: it only provides launch and outreach advice and asks (optionally) to read project-context files for tailoring. Before installing, confirm that .claude/project-context.md or .cursor/project-context.md (if present) contain no secrets you wouldn't want read by a skill. Also remember the skill gives outreach templates — follow anti-spam best practices when contacting users. No credentials or installs are requested.

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