partnership-development
Partner strategy, co-selling, and co-marketing governance for ecosystem growth
View on GitHubTable of content
Partner strategy, co-selling, and co-marketing governance for ecosystem growth
Installation
npx claude-plugins install @gtmagents/gtm-agents/partnership-development
Contents
Folders: agents, commands, skills
Included Skills
This plugin includes 4 skill definitions:
co-marketing-governance
Governance playbook for joint marketing programs, MDF, and performance
View skill definition
Co-Marketing Governance Skill
When to Use
- Planning joint campaigns, launches, or events with partners.
- Managing MDF budgets, approvals, and performance tracking.
- Preparing partner QBRs or exec updates focused on demand-generation impact.
Framework
- Program Intake – business case, audience, KPIs, required assets, legal/compliance checks.
- Approval Workflow – decision matrix for marketing, partner, and finance stakeholders.
- Execution Cadence – sprint plan, shared tracking sheets, and content governance.
- Measurement & Attribution – agreed metrics (MQLs, pipeline, revenue, influence) + reporting cadence.
- Closeout & Learnings – retro template, MDF reconciliation, and next-play recommendations.
Templates
- Co-marketing brief + approval form.
- MDF budget tracker with forecast vs actuals.
- Post-campaign report outline with KPIs and narrative prompts.
Tips
- Align messaging with joint solution blueprints to keep storytelling consistent.
- Attach MDF approval deadlines to campaign calendars to avoid delays.
- Pair with
run-partner-qbrto highlight impact and secure additional investment.
joint-solution-blueprint
Template for documenting co-built solutions, integrations, and GTM motions
View skill definition
Joint Solution Blueprint Skill
When to Use
- Launching or refreshing a co-built integration or packaged service.
- Equipping field teams with architecture, value props, and proof points.
- Coordinating enablement across product, marketing, and partner teams.
Framework
- Use Case Definition – target persona, pain point, and success metrics.
- Architecture Overview – system diagram, data flows, dependencies, security notes.
- Value Narrative – customer outcomes, ROI proof, competitive differentiation.
- Go-To-Market Plays – positioning, pricing principles, launch checklist, asset library.
- Support & Lifecycle – roles, escalation paths, roadmap commitments.
Templates
- One-page solution brief with messaging + CTA.
- Architecture diagram checklist.
- Launch plan with tasks, owners, and deadlines.
Tips
- Keep diagrams simple enough for sales decks, with appendix for technical deep dives.
- Include customer stories or beta insights to increase credibility.
- Pair with
build-co-sell-playbookso reps know how to pitch + progress deals.
partner-ecosystem-map
Visualization toolkit for mapping partner landscape, coverage, and priorities.
View skill definition
Partner Ecosystem Map Skill
When to Use
- Planning partner strategy, territorial coverage, or whitespace analysis.
- Presenting ecosystem status to executives or cross-functional stakeholders.
- Tracking progress against partner recruitment and ramp goals.
Framework
- Segmentation Layer – partner type, region, vertical, solution fit, maturity.
- Value Layer – pipeline contribution, ARR influenced, co-sell velocity, joint wins.
- Health Layer – certification status, enablement completion, NPS, engagement cadence.
- Gaps & Targets – highlight priority segments needing recruits or investment.
- Narrative Hooks – pair visuals with summary insights, risks, and next plays.
Templates
- Ecosystem matrix with rows (partner type) × columns (value/health metrics).
- Geo overlay map for territory coverage vs whitespace.
- Executive summary slide linking visuals to investment requests.
Tips
- Keep visuals updated monthly so leadership trusts the snapshot.
- Link each gap to a specific recruiting or enablement initiative.
- Pair with
design-partner-ecosystemfor streamlined planning packages.
partner-revenue-desk
Operating model for tracking, attributing, and accelerating partner-sourced
View skill definition
Partner Revenue Desk Skill
When to Use
- Forecasting partner-sourced/ influenced revenue for leadership updates.
- Monitoring incentives, SPIFs, and MDF utilization tied to partner pipeline.
- Coordinating RevOps, finance, and partner teams on attribution disputes.
Framework
- Revenue Taxonomy – sourced vs influenced vs co-sell, stage definitions, SLAs.
- Process Flow – intake → validation → attribution → approval → reporting.
- Data Stack – CRM objects, PRM integrations, BI dashboards, alerting.
- Incentive Hooks – payout rules, MDF governance, exception workflows.
- Escalation Paths – playbooks for disputes, double counting, or compliance risks.
Templates
- Revenue desk runbook with RACI + cadence.
- Attribution audit checklist.
- MDF utilization tracker with projected ROI.
Tips
- Align definitions with finance early; lock requirements before launching SPIFs.
- Automate alerts for stalled partner deals to keep velocity high.
- Pair with
build-co-sell-playbookandrun-partner-qbrfor closed-loop reporting.