gtm-developer-ecosystem

# Developer Ecosystem Build and scale developer-led adoption through ecosystem programs, community, and partnerships. Focus on what actually drives adoption, not vanity metrics. ## When to Use **Triggers:** - "How do we build a developer ecosystem?" - "Should we curate quality or go open?" - "Developer community isn't growing" - "Nobody's building on our API" - "How do we compete with larger platforms?" **Context:** - API platforms and developer tools - Products with extensibility (plugins, integrations) - Developer-first GTM motion - Platform business models --- ## Core Frameworks ### 1. Open vs Curated Ecosystem (The Marketplace Decision) **The Pattern:** Running ecosystem at a developer platform. Leadership debate: Open the marketplace to anyone, or curate for quality? **Quality control camp:** "We need gatekeeping. Otherwise we'll get SEO spam, low-quality integrations, brand damage." **Open camp:** "Developers route around gatekeepers. Network effects matter more than quality control." **The decision:** Went open. Quality concerns were real, but we made a bet: control comes from discovery and trust layers, not submission gatekeeping. **What We Built Instead of Gatekeeping:** 1. **Search and discovery** — Surface high-quality integrations through algorithms, not human curation 2. **Trust signals** — Verified badges, usage stats, health scores 3. **Community curation** — User ratings, collections, recommendations 4. **Moderation** — Remove spam after publicat...