Back to Skills

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.

37,821stars4,774forksUpdated 8/14/2026

Security Assessment

Safe(96/100)
Security Score96/100

About gtm-partnership-architecture

gtm-partnership-architecture is a strategy playbook, not a piece of software. It packages patterns for building and scaling partner ecosystems that drive revenue and platform adoption, drawn from the author's experience running partner programs and a developer marketplace. The problem it addresses is that most so-called partnerships are "co-marketing theater" — logo swaps, joint webinars, press releases with no real economic commitment — and the skill helps a user distinguish partnerships with genuine skin in the game from handshakes that will not move the business.

The content is organized around a set of decision frameworks. It offers a Three-Sided Value Proposition (value for your company, the partner, and shared customers), a build-vs-partner and open-vs-curated ecosystem decision tree that treats control as a matter of discovery and trust layers rather than gatekeeping, and a Partnership Leverage Types hierarchy that ranks requirement, economic, competitive, customer, and co-marketing leverage. Each framework comes with triggers, decision criteria, and common mistakes so an agent can apply it to a concrete situation such as tiering partners, structuring deals, or planning a crawl-walk-run rollout.

The intended users are founders, product and GTM leaders, business-development and partnerships staff, and ecosystem managers who are standing up a partner program from scratch (0 to 1) or scaling an existing one (1 to 100). Typical use cases include evaluating a build-vs-partner decision, deciding whether to open or curate a marketplace, and pressure-testing whether a proposed partnership carries real mutual risk. It is a single-document conceptual guide with no code or tooling.

FAQ

What does this skill actually produce?

It provides frameworks and decision criteria — the Three-Sided Value Proposition, open-vs-curated ecosystem trees, and Partnership Leverage Types — to reason through partnership decisions. It is guidance, not automation or code.

When should I invoke it?

When building a partner program from scratch, tiering partners, making build-vs-partner decisions, structuring partner economics, or planning partner GTM motions, per the triggers listed in the skill.

Are there prerequisites or dependencies?

None. It is a single SKILL.md document with no tools, APIs, or installation steps required.

What is the core idea it keeps returning to?

Real partnerships require economic commitment and mutual risk on both sides; if either party can walk away at zero cost, it is a handshake, not a partnership.

Who is it for?

Founders, GTM and product leaders, and business-development or ecosystem managers working on partner programs and marketplace strategy.

Install gtm-partnership-architecture

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill