cold-start-strategy▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
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:
- Product type: AI tool, SaaS, app, B2B, B2C
- Target audience: Where they spend time
- Budget: Zero, minimal ($500–1K), or moderate
- 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 |
| 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
How to use cold-start-strategy on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add cold-start-strategy
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches cold-start-strategy from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate cold-start-strategy. Access the skill through slash commands (e.g., /cold-start-strategy) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★72 reviews- ★★★★★Emma Mehta· Dec 28, 2024
cold-start-strategy reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Emma Li· Dec 24, 2024
cold-start-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Noor Garcia· Dec 20, 2024
I recommend cold-start-strategy for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Diego Sharma· Dec 16, 2024
cold-start-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Amelia Mensah· Dec 8, 2024
Useful defaults in cold-start-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Chen Gill· Dec 4, 2024
We added cold-start-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Carlos Taylor· Dec 4, 2024
Useful defaults in cold-start-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Zaid Nasser· Dec 4, 2024
Registry listing for cold-start-strategy matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Zaid Abbas· Nov 23, 2024
cold-start-strategy reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Xiao Agarwal· Nov 23, 2024
cold-start-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 72