sales-betalist

name	sales-betalist
description	BetaList platform help — pre-launch startup discovery directory where early adopters find startups before they make it big (15,000+ featured startups, 100K+ early adopters, DR67 dofollow backlink). Covers submission optimization, acceptance criteria (21% acceptance rate), free queue vs paid Priority listing, newsletter inclusion (30K+ subscribers), listing best practices, and API access. Use when your startup needs early adopter signups, BetaList submission got rejected, not sure if the paid Priority listing is worth it, or listing isn't attracting enough interest. Do NOT use for multi-directory launch strategy (use /sales-launch-directory). Do NOT use for Product Hunt (use /sales-producthunt).
argument-hint	[describe what you need help with on BetaList]
license	MIT
version	1.0.1
tags	["sales","product-launch","startup","directory","platform"]
github	https://github.com/betalist

BetaList Platform Help

Helps with everything related to using BetaList — a pre-launch startup discovery platform founded in 2010 by Marc Kohlbrugge. BetaList connects founders with 100,000+ registered early adopters who actively seek new products to try before mainstream launch.

Step 1 — Gather context

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

Ask the user:

1. What are you trying to do on BetaList?

   • A) Submit my startup for the first time
   • B) Optimize an existing or upcoming listing
   • C) Decide between free queue and Priority ($129)
   • D) Understand why my submission was rejected
   • E) Access the BetaList API
   • F) Something else — describe it

2. What stage is your product?

   • A) Pre-launch — no public access yet (private beta, waitlist)
   • B) Recently launched — live but early stage
   • C) Established — been live for a while
   • D) Not sure if BetaList is the right fit

3. What's your primary goal?

   • A) Get beta testers and early feedback
   • B) SEO backlink (DR67 dofollow)
   • C) Newsletter exposure (30K+ subscribers)
   • D) All of the above

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 different skill, route:

• Multi-directory launch strategy → /sales-launch-directory
• Product Hunt launch → /sales-producthunt
• General audience growth → /sales-audience-growth
• Email marketing for subscribers → /sales-email-marketing
• Landing page optimization → /sales-checkout

Otherwise, answer directly from the platform knowledge below.

Step 3 — BetaList platform reference

Read references/platform-guide.md for detailed directory documentation, pricing, acceptance criteria, and backlink value.

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

Step 4 — Actionable guidance