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.
What this skill does
# 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 in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".