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.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and positioning.
Identify:
ChannelAudienceUseNotesProduct HuntIndie makers, early adoptersLaunch-day buzz; community upvotes3% conversion; traffic spike; see product-hunt-launch****AppSumo / LTDDeal seekers, early adoptersLifetime deal for fast revenue, validationQuick cash; price-sensitive users; see discount-marketing-strategy for LTD structure, trade-offsRedditSubreddit-specificr/AlphaAndBetaUsers, r/roastmystartup, r/devops, r/SaaS80/20 rule; 5+ months for traction; lead with storyIndie HackersIndie makers, foundersSustained engagement; authentic journey23% conversion; 4–6 months; see indie-hacker-strategy for tacticsHacker NewsTech, startupsShow HN launchLuck + timing; front page = traffic spikeDirectory submissionAI tools, product launchTaaft, G2, niche directoriesValidate PMF; seed users; see directory-submission****Founder-led outboundB2B, high ACVCold email, LinkedIn; 10–15 personalized outreaches/dayPre-$5K MRR; only reliable path when ACV >$500/moCommunity engagementTarget usersForums, LinkedIn groups, Discord45–90 days; contribute value first
Low-cost ways to find and reach users who are already expressing need. Use when Product Hunt, directories, or forums are not enough.
Search Twitter/X, LinkedIn, Reddit, and niche communities for demand signals:
SignalWhat to seekKeywordsIndustry terms, category keywords, "looking for [X] tool," "best alternative to [Y]"DiscussionIndustry threads, complaints about competitors, "anyone used…" or "recommend…" postsPlatformChoose where your audience spends time (Twitter/X, LinkedIn, Reddit, Discord, vertical forums)
StepPracticeSearchService requests related to your product (e.g. "need logo design," "looking for video editor")IdentifyBuyers in job descriptions or comments who have related needsReachOffer help or tool recommendation; introduce product politely
Users often have clear need and budget; high intent.
PracticeGuidelineSearchBrand, category, "looking for AI tool," "best alternative to…"ReplyComment on posts where users express need; avoid spamToneSincere; honest that it's your product; invite trial and feedbackAvoidHard 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.
Coordinated launch across channels yields 5–6× more users than single-channel:
WeekFocus1–2Audience building (LinkedIn 3×/week)3–4Beta; community engagement5Pre-launch countdown6Product Hunt + Reddit/Indie Hackers7Post-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.