gtm-partnership-architecture
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.
Profile →npx skills add github/awesome-copilot --skill gtm-partnership-architecture --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Partnership Architecture Build and scale partner ecosystems that drive revenue and platform adoption. These aren't theory — they're patterns from building partner programs that drove 8-figure ARR and observing partnerships with real economic commitment. ## When to Use **Triggers:** - "How do I structure a partner program?" - "Should we build this or partner for it?" - "Partner-led vs direct sales motion" - "Ecosystem strategy" - "How to recruit and tier partners" - "Co-marketing with partners" - "When does a partnership actually matter?" **Context:** - Building partnership program from scratch (0→1) - Scaling existing program (1→100) - Evaluating build vs partner decisions - Structuring partner deals and economics - Planning partner GTM motions --- ## Core Frameworks ### 1. Real Partnerships Require Skin in the Game **The Pattern:** Most "partnerships" are co-marketing theater. Joint webinars, logo swaps, press releases. No economic commitment. No real skin in the game. Real partnerships look different: - Economic commitment (spend, revenue share, co-investment) - Product roadmap alignment (features built for the partnership) - Executive sponsorship (leadership engaged quarterly)
- When to Use
- Core Frameworks
- 1. Real Partnerships Require Skin in the Game
- 2. Ecosystem Control = Discovery, Not Gatekeeping
- 3. Partnership Tactics > Partnership Theater
- 4. Partner Tiering: Three-Tier Model
- 5. Crawl-Walk-Run Partnership Deployment
- 6. Partnership Value Exchange Clarity
- 7. Co-Marketing Execution Checklist
- Decision Trees
- Should We Build or Partner?
- Which Partner Tier?
- Should We Continue This Partnership?
- Common Mistakes
What does the gtm-partnership-architecture skill do?
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.
How do I install it?
Run `npx skills add github/awesome-copilot --skill gtm-partnership-architecture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.