sales-launch-directory

What this skill does

# Startup Directory Launch Strategy

Helps the user plan and execute a coordinated launch across multiple startup directories and discovery platforms — choosing which to submit to, in what order, and how to optimize each listing for maximum visibility, backlinks, and early users.

## Step 1 — Gather context


If `references/learnings.md` exists, read it first for accumulated knowledge.

Ask the user:

1. **What are you launching?**
   - A) SaaS / software tool
   - B) Mobile app
   - C) API / developer tool
   - D) No-code / low-code tool
   - E) Physical product or service
   - F) Something else — describe it

2. **What stage is your product?**
   - A) Idea / concept — no working product yet
   - B) MVP / prototype — functional but early
   - C) Launched — live with some users
   - D) Growing — looking for more distribution

3. **What's your primary goal?**
   - A) First users and feedback
   - B) SEO backlinks
   - C) Community visibility and social proof
   - D) All of the above

4. **What's your budget for paid listings?**
   - A) $0 — free submissions only
   - B) Under $50 — can afford one or two paid options
   - C) $100-500 — willing to invest in expedited/featured placements
   - D) Budget is flexible — optimize for results

5. **Any timing constraints?**
   - A) ASAP — want listings live as fast as possible
   - B) Coordinating with a specific launch date
   - C) No rush — steady rollout over weeks/months

**If the user's request already provides most of this context, skip directly to the relevant step.** Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end.

## Step 2 — Route or answer directly

If the request maps to a single platform, route:
- Open Launch-specific questions → `/sales-openlaunch`
- CtrlAlt.cc-specific questions → `/sales-ctrlaltcc`
- MicroLaunch-specific questions → `/sales-microlaunch`
- LaunchingNext-specific questions → `/sales-launchingnext`
- ProductBurst-specific questions → `/sales-productburst`
- SoloPush-specific questions → `/sales-solopush`
- SideProjectors-specific questions → `/sales-sideprojectors`
- Huzzler-specific questions → `/sales-huzzler`
- Firsto-specific questions → `/sales-firsto`
- OpenHunts-specific questions → `/sales-openhunts`
- Tiny Startups-specific questions → `/sales-tinystartups`
- DevHunt-specific questions → `/sales-devhunt`
- TinyLaunch-specific questions → `/sales-tinylaunch`
- Uneed-specific questions → `/sales-uneed`
- Fazier-specific questions → `/sales-fazier`
- Peerlist-specific questions → `/sales-peerlist`
- Awesome Indie-specific questions → `/sales-awesomeindie`
- LaunchDay-specific questions → `/sales-launchday`
- Super Launch-specific questions → `/sales-superlaunch`
- JustGotFound-specific questions → `/sales-justgotfound`
- Altern-specific questions → `/sales-altern`
- StartupBase-specific questions → `/sales-startupbase`
- Startup Stash-specific questions → `/sales-startupstash`
- PitchWall-specific questions → `/sales-pitchwall`
- Futurepedia-specific questions → `/sales-futurepedia`
- TAAFT-specific questions → `/sales-theresanaiforthat`
- TopAI.tools-specific questions → `/sales-topai`
- Toolify-specific questions → `/sales-toolify`
- BetaList-specific questions → `/sales-betalist`
- LaunchCaster-specific questions → `/sales-launchcaster`
- SaaSHunt-specific questions → `/sales-saashunt`
- Resource.fyi-specific questions → `/sales-resourcefyi`
- LaunchVibe-specific questions → `/sales-launchvibe`
- Indie Hackers-specific questions → `/sales-indiehackers`
- Product Hunt-specific questions → `/sales-producthunt`
- Email marketing to subscribers → `/sales-email-marketing`
- Landing page optimization → `/sales-checkout`
- Audience growth strategy → `/sales-audience-growth`

- Comparing directory submission services → `/sales-directory-submission`
- Managed directory submission service → `/sales-getmorebacklinks`

Otherwise, answer directly from the directory knowledge below.

## Step 3 — Directory reference

**Read `references/platform-guide.md`** for detailed module documentation, pricing, integrations, and data model.

*You no longer need the platform guide details — focus on the user's specific situation.*

## Gotchas

*Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.*

- **Pricing changes.** All prices listed are best-effort snapshots. MicroLaunch Pro, LaunchingNext expedited, CtrlAlt.cc paid launch, and BetaList pricing may change. Verify before purchasing.
- **DR/DA numbers fluctuate.** Domain ratings change over time. The rankings above are directionally correct but exact numbers may shift.
- **Product Hunt is not a directory.** It's a launch event. Don't treat it like the others — it requires separate preparation, community building, and timing strategy.
- **"Dofollow" claims vary.** Some directories report dofollow but individual listings may vary. Always verify after your listing goes live by inspecting the HTML.
- **Editorial queues are unpredictable.** "Up to 2 months" is a documented worst case, not a guarantee. Some platforms review faster, some slower.
- **Small platforms have small traffic.** Most directories in this list have modest traffic (5K-25K/mo). Set realistic expectations — directory submissions are a long-term SEO play, not an overnight traffic source.

- **Self-improving**: If you discover something not covered here, append it to `references/learnings.md` with today's date.

## Before recommending a specific platform skill

This skill covers a strategy domain across many platforms. **Before pointing the user to any specific platform skill** (any `/sales-{platform}` listed in `## Related skills`, e.g., `/sales-mailshake`, `/sales-klaviyo`, `/sales-apollo`), read that platform skill's actual `SKILL.md` first. The 1-line description in `## Related skills` is enough to *identify* a candidate — it's not enough to *commit* to it or to write a prompt that invokes it well.

**How to read it:**
- If `~/.claude/skills/{skill-name}/SKILL.md` exists locally, `Read` it.
- For `sales-*` skills, `WebFetch` directly from this repo: `https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md` — e.g., for `sales-mailshake`: `https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md`.
- For non-`sales-*` skills (third-party), look up `{org}/{repo}` in `~/.claude/skills/sales-do/references/skill-sources.md` if installed and fetch the same `skills/{skill-name}/SKILL.md` path under that repo.

**After reading,** ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its `argument-hint` shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's `argument-hint`. If the platform skill turns out not to fit the user's situation, swap to another or handle the question here directly rather than recommending a poor fit.

## Related skills

- `/sales-openlaunch` — Open Launch platform help (open-source PH alternative, DR65 backlinks)
- `/sales-ctrlaltcc` — CtrlAlt.cc platform help
- `/sales-productburst` — ProductBurst platform help (daily/weekly rankings, badges)
- `/sales-microlaunch` — MicroLaunch platform help (30-day leaderboard, deals marketplace)
- `/sales-launchingnext` — LaunchingNext platform help (curated startup directory)
- `/sales-solopush` — SoloPush platform help (indie maker community, no-pressure launch)
- `/sales-sideprojectors` — SideProjectors platform help (buy/sell side projects)
- `/sales-huzzler` — Huzzler platform help (founder community, weekly Launch Arena competition)
- `/sales-firsto` — Firsto platform help (fair launch platform, sustained SEO discovery, Open Launch fork)
- `/sales-openhunts` — OpenHunts platform help (weekly launch cycle, DR50 backlinks)
- `/sales-awesomeindie` — Awesome Indie platform help (curated indie d