메뉴
Build and scale developer-led adoption through ecosystem programs. Use when deciding open vs curated ecosystems, building developer programs, scaling platform adoption, or designing student program pipelines.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Build and scale partner ecosystems that drive revenue and platform adoption. Use when building partner programs from scratch, tiering partnerships, managing co-marketing, making build-vs-partner decisions, or structuring crawl-walk-run partner deployment.
Launch new products from idea to first customers. Use when launching products, finding early adopters, building launch week playbooks, diagnosing why adoption stalls, or learning that press coverage does not equal growth. Includes the three-layer diagnosis, the 2-week experiment cycle, and the launch that got 50K impressions and 12 signups.
Go-to-market strategy for AI products. Use when positioning AI products, handling "who is responsible when it breaks" objections, pricing variable-cost AI, choosing between copilot/agent/teammate framing, or selling autonomous tools into enterprises.
Board meeting preparation, investor updates, and executive communication. Use when preparing board decks, writing investor updates, handling bad news with the board, structuring QBRs, or building board-level metric discipline. Includes the "Three Things" narrative model, the 4-tier metric hierarchy, and the pre-brief pattern that prevents board surprises.
Strategic account planning and execution for enterprise deals. Use when planning complex sales cycles, managing multiple stakeholders, applying MEDDICC qualification, tracking deal health, or building mutual action plans. Includes the "stale MAP equals dead deal" pattern.
Four-phase framework for onboarding enterprise customers from contract to value realization. Use when implementing new enterprise customers, preventing churn during onboarding, or solving the adoption cliff that kills deals post-go-live. Includes the Week 4 ghosting pattern.
| name | developer-ecosystem |
| description | Build and scale developer-led adoption through ecosystem programs. Use when deciding open vs curated ecosystems, building developer programs, scaling platform adoption, or designing student program pipelines. |
| license | MIT |
| metadata | {"author":"Smit Patel (https://linkedin.com/in/smitkpatel)","version":"3.0.0","category":"gtm"} |
Build and scale developer-led adoption through ecosystem programs, community, and partnerships. Focus on what actually drives adoption, not vanity metrics.
Triggers:
Context:
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:
Result: Network effects won. Thousands of integrations published. Quality surfaced through usage, not through us deciding upfront.
Decision Framework:
Common Mistake:
Defaulting to curated because "we need quality control." This works when you have 10 partners. At 100+, you become the bottleneck. Build discovery and trust systems instead.
The Pattern:
Most developer programs optimize for quick wins. Better approach: Build long-term talent pipeline.
Year 1: University Partnerships
Year 2: Student Community & Certification
Year 3: Career Bridge
Why This Works:
Students become enterprise buyers 5-10 years later. You're building brand loyalty before they have purchasing power.
Common Mistake:
Treating students as immediate revenue. They're not. They're future enterprise decision-makers.
Stage 1: Awareness
Stage 2: Onboarding
Stage 3: Integration
Stage 4: Production
Stage 5: Advocacy
Metrics That Matter:
Common Mistake:
Measuring vanity metrics (sign-ups, downloads) instead of real engagement (API calls, production deployments).
Tier 1: Quick Starts (Get to Value Fast)
Tier 2: Guides (Solve Real Problems)
Tier 3: Reference (Complete API Docs)
Tier 4: Conceptual (Understand the System)
Most developers need: Tier 1 first, then Tier 2. Very few read Tier 4.
Common Mistake:
Starting with Tier 3 (comprehensive API reference). Developers want quick wins first.
Community (Async, Scalable):
Support (Sync, Expensive):
How to Route:
Community first:
Escalate to support when:
Common Mistake:
Providing white-glove support to everyone. Doesn't scale. Build community that helps itself.
Tier 1: Integration Partners (Self-Serve)
Tier 2: Strategic Partners (Co-Development)
Don't over-tier. 2 tiers is enough. More creates confusion.
Is brand damage risk high if low-quality partners join?
├─ Yes (regulated, security) → Curated
└─ No → Continue...
│
Can you scale human review?
├─ No (hundreds/thousands) → Open + discovery systems
└─ Yes (dozens) → Curated
Is this a common question?
├─ Yes → Community (forum, Slack, docs)
└─ No → Continue...
│
Is requester paying customer?
├─ Yes → Support (email, dedicated)
└─ No → Community (with escalation path)
1. Building ecosystem before product-market fit
2. No developer success team
3. Poor documentation
4. Treating all developers equally
5. No integration quality standards
6. Measuring only vanity metrics
7. Developer advocates with no technical depth
Open ecosystem checklist:
Developer journey metrics:
Documentation hierarchy:
Partner tiers:
Student program timeline:
Based on building developer ecosystems at multiple platform companies, including the open vs curated marketplace decision, student program development (3-year arc building talent pipeline), and partner ecosystem growth. Not theory — patterns from building developer ecosystems that actually drove platform adoption and multi-year brand loyalty.